Bug 69825

Summary: udisks2 / udev don't detect optical drive
Product: udisks Reporter: Arnaud R (elboulangero) <elboulangero>
Component: detectionAssignee: David Zeuthen (not reading bugmail) <zeuthen>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: some commands

Description Arnaud R (elboulangero) 2013-09-25 22:10:10 UTC
Created attachment 86602 [details]
some commands

Hi,

on my system, I have both udisks and udisks2 installed.


After a clean boot, only udisks2 is running. The situation looks like this:

$ ps fax | grep udisks
 4601 pts/0    S+     0:00  |   \_ grep udisks
 3327 ?        Sl     0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
 3330 ?        Sl     0:00 /usr/lib/udisks2/udisksd --no-debug

In this situation, if I insert/eject the drive, there is no udev event generated (I can see that with udevadm monitor). Therefore, my file manager (Thunar) doesn't display the optical drive in the device list.

Now, if I issue a simple udisks command:
$ udisks --enumerate

It has the consequence to launch the udisks daemon:
$ ps fax | grep udisks
 4614 pts/0    S+     0:00  |   \_ grep udisks
 3327 ?        Sl     0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
 3330 ?        Sl     0:00 /usr/lib/udisks2/udisksd --no-debug
 4604 ?        Sl     0:00 /usr/lib/udisks/udisks-daemon
 4605 ?        S      0:00  \_ udisks-daemon: polling /dev/sr0

From this point, everything works (almost) fine. I see udev events, and I see my optical drive in Thunar.


I have no idea about the dependency between udev and udisks, but apparently there is some dependencies. And it looks like udisks2 doesn't work properly, while udisks does.

Or is it possible that there is something wrong in my configuration ?


Thanks for your help.

--

System: Debian Sid, Openbox

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.