Partitioning options do not come up in ubiquity & d-i

Ubiquity 2.13.6
Error: "/var/tmp/kdecache-kubuntu" is owned by uid 999 instead of uid 0.
mkdir failed: : Permission denied
TEXT <small>If more than one person will use this computer, you can set up multiple accounts after installation.</small>
TEXT <small>Enter the same password twice, so that it can be checked for typing errors.</small>
TEXT <small>The name it uses when it talks to other computers.</small>
TEXT <small>If more than one person will use this computer, you can set up multiple accounts after installation.</small>
TEXT <small>Enter the same password twice, so that it can be checked for typing errors.</small>
TEXT <small>The name it uses when it talks to other computers.</small>
QSocketNotifier: Invalid socket 15 and type 'Read', disabling...
QSocketNotifier: Invalid socket 15 and type 'Exception', disabling...
QSocketNotifier: Invalid socket 15 and type 'Write', disabling...
QSocketNotifier: Invalid socket 15 and type 'Read', disabling...
QSocketNotifier: Invalid socket 15 and type 'Exception', disabling...
QSocketNotifier: Invalid socket 15 and type 'Write', disabling...

After messing around with the partitions a bit ( by which I mean deleting all of them ), I got the installer to work.

Status changed to 'Confirmed' because the bug affects multiple users.

Resize/reuse are getting stuck at ntfs (see below) and or possibly fat partitions (myself):

<xnox> $ sudo chmod -x /lib/partman/automatically_partition/*5*/choices
<xnox> when ubiquity comes up, but before clicking next on the prepare step.
<xnox> and please tell me if that fixes for you.
<shadeslayer> afiestas: ^ since you probably are the one who can test this the quickest
<xnox> I have managed to kind of reproduce it with a fat partition, but ntfs might be also a trigger for this bug.
<afiestas> xnox: if I kill ubiquity and startit again, will it work?
<afiestas> or should I do a clean start?
<xnox> afiestas: if you already had a hang, killing ubiquity will not help.
<xnox> afiestas: just reboot.
<afiestas> ookz
<afiestas> restarting then
<afiestas> xnox: worked
<xnox> afiestas: now, tell me a lot of how you booted and how many disks you had attached to your system.
<xnox> afiestas: did you boot from USB or CD?
<afiestas> oks
<afiestas> I booted from USB
<afiestas> dd if of the image
<xnox> afiestas: how many hard-drives do you have?
<afiestas> I had windows 8 installed, using the whole harddisk (it is a laptop, only have 1)
<xnox> afiestas: that's it?
<afiestas> the machien is a dell XPS1330 the ones that shipped with Ubuntu years ago
<xnox> afiestas: ok. thanks a lot.
<afiestas> yes

Both reuse & replace recipes use blkid, in my local experimentation I did managed to get blkid to hang on fat32 partition approximately similar to bug 987718 and bug 1044111.

But that got me thinking - both recipes are trying to detect existing ubuntu installations which should not be on a fat32/ntfs/hfs/swap partitions, so I want to skip mounting those & skip using blkid.

I'm having the same problem.Doing what Dmitrijs Ledkovs sait in comment#5 fixed it for me.

This bug was fixed in the package partman-auto - 105ubuntu2

---------------
partman-auto (105ubuntu2) raring; urgency=low

  * Reuse & Replace recipes:
    - Avoid using blkid, as it may sometimes hang indefinitely without
      timing out. See blkid bugs http://pad.lv/987718 and
      http://pad.lv/1044111. This change should address (LP: #1085991)
    - Skip mounting filesystems that ought to not be Ubuntu root
      filesystems (empty, swap, fat, ntfs, hfs). This also should speed up
      automatic partitioning page.
    - Silence warnings from umount in the clean-up (typically should
      already be unmounted)
 -- Dmitrijs Ledkovs <email address hidden> Wed, 02 Jan 2013 14:00:50 +0000

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.