FS#24643 - [k3b] missing hal dependency

Attached to Project: Arch Linux
Opened by Eric Belanger (Snowman) - Thursday, 09 June 2011, 03:10 GMT
Last edited by Jan de Groot (JGC) - Thursday, 09 June 2011, 08:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

k3b depends on hal to find devices. Error message:

No optical drive found.
K3b did not find any optical device in your system.
Solution: Make sure HAL daemon is running, it is used by K3b for finding devices.
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 09 June 2011, 08:32 GMT
Reason for closing:  Not a bug
Comment by Gerardo Exequiel Pozzi (djgera) - Thursday, 09 June 2011, 04:20 GMT
Looks like you are running KDE (or your desktop enviroment) without a consolekit session. Otherwise should work.
Comment by Jan de Groot (JGC) - Thursday, 09 June 2011, 05:56 GMT
Now KDE has been ported to udisks, I can't understand any reason for K3b to still use hal for device detection. I guess you're missing dbus in DAEMONS. Starting hal also starts the dbus daemon. Really, you don't need hal.
Comment by Tobias Powalowski (tpowa) - Thursday, 09 June 2011, 06:56 GMT
k3b runs fine without any hal running. Try starting dbus instead.
Comment by Eric Belanger (Snowman) - Thursday, 09 June 2011, 07:07 GMT
It works with the dbus daemon running. I was supposed to be running the dbus daemon but I probably disabled it by mistake when I removed hal from my system a while ago as I relied on hal to start it. So shouldn't dbus-core be added as a dependency instead?
Comment by Jan de Groot (JGC) - Thursday, 09 June 2011, 08:31 GMT
It is in the dependency chain and you're responsible for putting it in DAEMONS. Dbus is a requirement for desktop systems these days.

Loading...