Comment 11 for bug 285080

A related problem that may shed further light on this bug:

Simultabeous to this is a bug that keeps making Thunar crash.

I just tried reporting that bug using ubuntu-bug and got this error:

"""
The problem cannot be reported:

Your home partition has less than 38.345728 MB of free space available, which leads to problems using applications and installing updates. Please free some space.
"""

Yet df shows:

/dev/mapper/compo--vg-home 133915952 10444732 116645648 9% /home

Its full output suggests nothing is full or even near ful:

/dev/mapper/compo--vg-root 321041 262500 37447 88% /
none 4 0 4 0% /sys/fs/cgroup
udev 1779984 4 1779980 1% /dev
tmpfs 358844 1032 357812 1% /run
none 5120 0 5120 0% /run/lock
none 1794200 84 1794116 1% /run/shm
none 102400 36 102364 1% /run/user
/dev/mapper/compo--vg-tmp 368615 2072 342991 1% /tmp
/dev/sda1 240972 48642 179889 22% /boot
/dev/mapper/compo--vg-home 133915952 10444732 116645648 9% /home
/dev/mapper/compo--vg-usr 8516872 5600364 2460828 70% /usr
/dev/mapper/compo--vg-var 2817056 886872 1767368 34% /var
/home/user/.Private 133915952 10444732 116645648 9% /home/user
/dev/sdb2 447233912 298588468 125904196 71% /media/user/74f8b831-ce17-4911-8787-162f5debcd24

Interestingly, another size problem has arisen. This manifested this afternoon, for example, when I copied one large zip file on my local disk over a smaller one of the same name on an external disk (both encrypted separately). After the copy was complete the size was given as a smaller size. It suggested to me the copy had been unsuccessful. But while I was looking at this Thunar crashed. I restarted it and the file was showing the correct, larger size.

Ah but look again at the df output above.

/tmp has just 34Mb space.

So the Thunar error was wrong. It is not that my home directory doesn't have enough space, it is that my tmp doesn't have enough space.

So Elias' orginal report was correct to say the error report was wrong. It is also true that the real problem is that /tmp is getting full and the o/s can't handle it.

It looks like the two are related. The o/s doesn't even know what the problem is to report it properly.

It suggests Xubuntu/Ubuntu guided install procedure for separate partitions is failing to provide paretitions of the correct sizes (this problem has persisted for years). It suggests also that Xubuntu/Ubuntu are unable to work with the partition sizes they opt to give themselves.

(One other event happened in the course of these reports that may or may not have significance for any attempt at diagnosis. That is that I installed KSystemLog using the Ubuntu Software Centre. (This incidentally failed to install an icon on the system menu - this leaves me with no surprise but much despair, but that has become par for the course for this bug-ridden operating system. How about ceasing the annual distributions until the base is solid and stable - and then proceed at a slower pace: users are suffering and spending too much time wrestling with bugs. It is getting ridiculous)).