| Summary: | hal grants permissions to mount/use/unmount a device, but not to eject it | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ernst Bachmann <e.bachmann> |
| Component: | [OLD] Core system | Assignee: | Daniel Gryniewicz (RETIRED) <dang> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | CC: | freedesktop-bugs |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Ernst Bachmann
2009-05-19 12:03:35 UTC
(sorry for the delay, I was on vacation) I've tested this, and I can eject fine using gnome-mount, which should be the equivalent of solid-hardware, without being in the disk group. The reason is that haldaemon is in the disk group, and it's what invokes /usr/bin/eject. Is haldaemon in the disk group on your system? Lets see: # id haldaemon uid=102(haldaemon) gid=411(haldaemon) groups=411(haldaemon),6(disk),11(floppy),19(cdrom),80(cdrw),85(usb),409(plugdev) So Haldaemon is in the disk group. But it looks like eject isn't called by hal on my system. For one, I see the eject message on the console I used to invoke "solid-hardware unmount", and not somewhere in the system log. And my "/usr/share/hal/fdi" files only contain references to "/usr/libexec/hal-storage-eject" being used to eject. I'll try if I can get some usefull informations out of hald by setting HALD_VERBOSE="yes" in /etc/conf.d/hald. hal-storage-eject actually invokes eject, and prints it's stderr to stderr if it fails. hal-storage-eject should, I believe, be invoked by hald, and the client should send dbus messages; if solid-hardware is directly calling hal-storage-eject, that's probably wrong. gnome-mount, for example, calls org.freedesktop.Hal.Device.Volume.Eject via DBUS (assuming the volume is *not* in /etc/fstab; if it is, it executes eject directly). I guess that's something to check: is the mount point in question listed in fstab? The bug was marked as fixed upstream: https://bugs.kde.org/show_bug.cgi?id=169060#c7 I will check if it behaves better once a fixed version is released. |