© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This bug should perhaps be assigned to kdelibs, as it is not really a plasma bug ... thought it could be worked-around in kickoff. See Bug#316655 which has more information on the problem. The culprit is the free space checking code; it makes a blocking call and when the mount point is not available this simply hangs. This problem affects several KDE components (among other software out there) ... one possibility is to simply not show the free space in kickoff, though that probably involves moving away from PlacesModel (assuming that is what is still used). So a proper solution in the free space checker is probably the best approach.
My suggestion would be look at the filesystem type advertised for the mount point and simply avoid any free space (or similar info fetching) attempts on nfs, cifs, etc. and perhaps also fuse mounts.
@Szczepan "I don't see why it necessarily couldn't work, and this appropach hasn't been tried yet, unlike much everything else that has been *proven* ineffective over the last five years."
You are not the first person think that behaving badly will make things better. It has been tried many times in the past and honestly doesn't work.
Regardless of whether it works or not, it is not welcome in KDE. Please see: https:/
@Tilman Vogel: If you can not fix it yourself, and evidently people who may be able to are not motivated to do so, then perhaps paying someone to fix it would be a possibility. Not everything gets accomplished gratis. (No, I'm not interested in being paid to fix this :)