Bug 258893 - 4.6 beta 1: Device notifier lists removable media twice
Summary: 4.6 beta 1: Device notifier lists removable media twice
Status: RESOLVED DUPLICATE of bug 258638
Alias: None
Product: solid
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kevin Ottens
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-05 12:17 UTC by David Nemeskey
Modified: 2010-12-05 17:17 UTC (History)
0 users

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

Attachments
Screenshot with two usb devices plugged in (20.09 KB, image/png)
2010-12-05 12:17 UTC, David Nemeskey 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description David Nemeskey 2010-12-05 12:17:59 UTC 
Created attachment 54146 [details]
Screenshot with two usb devices plugged in

Version:           unspecified (using KDE 4.5.80) 
OS:                Linux

Since 4.6 beta 1, the Device Notifier widget displays two entries in its list for each USB media plugged in. The first is the icon associated with the device type, the second is the generic "USB device" icon. The device can only be mounted/unmounted with the button next to the first icon; the button next to the second icon reports errors (cannot mount, file is in use).

See device_notifier_x2.png for an example.

Reproducible: Always
Comment 1 Pino Toscano 2010-12-05 12:56:36 UTC 
I guess you have both the hal and udisks daemons running, right?
Comment 2 David Nemeskey 2010-12-05 15:05:52 UTC 
(In reply to comment #1)
> I guess you have both the hal and udisks daemons running, right?

I guess so; that was my first idea too. However, I uninstalled libhal-storage, and still the problem was there. I am no Linux guru and I don't know what else are hal and u* used for (in Ubuntu at least, Gimp depends on hal), so instead of trying to remove either of them, I just reverted back to 4.5.4. Especially since  in the beta, CPU usage was at 100% all the time, which may or may not be the result of the two daemons running at the same time.
Comment 3 Pino Toscano 2010-12-05 17:17:21 UTC 

*** This bug has been marked as a duplicate of bug 258638 ***