Bug 205761 - Plasma hangs after mounting usb-drive
Summary: Plasma hangs after mounting usb-drive
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 219253 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-08-31 08:50 UTC by Torben Hansen
Modified: 2012-05-16 11:36 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Torben Hansen 2009-08-31 08:50:59 UTC 
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    SuSE RPMs

When I mount my (large 1TB) usb-drive plasma hangs while the drive seems to be scanned.
Only process that according to lsof uses the drive is kio_thumb.
I'm able to read the files on the drive immediately after mount, so the drive does not itself hang.
Comment 1 Isaac 2010-01-30 20:08:49 UTC 
This bug is present on 4.3.3 installed from gentoo ebuild.
Comment 2 Rettich 2010-02-08 17:38:59 UTC 
The problem ist, that plasma (or a widget) tries to determine the free space, which can take some time on large devices.

Don't know if it is already solved in KDE4.4
Comment 3 Nicolas L. 2010-06-07 10:54:20 UTC 
Do you reproduce with kde 4.4.4 or 4.5 beta ?
Comment 4 Stefan Burnicki 2010-07-10 10:34:59 UTC 
There is a similar bug report n novells bugzilla. Does this fit?
https://bugzilla.novell.com/show_bug.cgi?id=581585
I had the same problem, too, before I tried the workaround discussed in the bug report mentioned above.
Comment 5 Thijs 2011-12-02 15:52:53 UTC 
As opensuse closed it as wontfix, i do the same here; assuming it is the same issue, there is a work around a lot of improvement since 4.4, and the hope that vfat will go away anyway.
Comment 6 Myriam Schweingruber 2012-05-16 11:36:45 UTC 
*** Bug 219253 has been marked as a duplicate of this bug. ***