Ubuntu
kdebase-workspace package

KDE4 sensitive to /tmp space

Bug #290989 reported by karaluh on 2008-10-30

This bug report is a duplicate of: Bug #99044: KDE should warn about disk space shortage. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	kdebase-workspace (Ubuntu)	Incomplete	Undecided	Unassigned

Bug Description

Most of kde4 apps including Plasma crashes, and all I can get is unusable desktop with whole white screen. Thanks to yakuake I am able to start some apps. This is the error I get, when i try to start plasma from yakuake:

<unknown program name>(12054)/ checkComposite: Plasma has an argb visual 0x80612e8 14680065
<unknown program name>(12054)/ checkComposite: Plasma is COMPOSITE-less on 0x805a870
qUncompress: Input data is corrupted
qUncompress: Input data is corrupted
plasma(12054): Communication problem with "plasma" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

konqueror, kmail and so on all crash with qUncompress: Input data is corrupted. The workaround is to remove /var/tmp/kdecache-username

See original description

karaluh (karaluh) on 2008-10-30

description:

updated

Revision history for this message

Roderick B. Greening (roderick-greening) wrote on 2008-10-30:

Is this reproducible (i.e. do you always have to remove the cache file in tmp) or was this a one time occurrence?

Is this hardy or intrepid and if intrepid, was it a clean install or an upgrade? Did anything fail/crash during the upgrade/install in this case?

Changed in kdebase-workspace:
status:	New → Incomplete

Revision history for this message

karaluh (karaluh) wrote on 2008-10-30:

> Is this reproducible (i.e. do you always have to remove the cache file in tmp) or was this a one time
> occurrence?

After the removal everything seems to be working fine. I guess this bug could be reproduced by filing /var to 100% and loging out.

> Is this hardy or intrepid and if intrepid, was it a clean install or an upgrade? Did anything fail/crash
> during the upgrade/install in this case?

It's Hardy to Intrepid upgrade. Some things went wrong during the upgrade (a lot of actualy), but none of them is the cause here. First login was succesful. I didn't clean the cache after upgrade (that was stupid), uncommented third party repositories in sources.list, tried to update and failed because of lack of free space on /var. Then I rebooted and all the crashing started. My guess would be that during the logout process the cache file got corrupted because of the lack of free space.