Description of problem: K3b error: "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." Version-Release number of selected component (if applicable): K3b 2.0.0 Using KDE Development Platform 4.4.95 (KDE 4.4.95 (KDE 4.5 >= 20100723)) How reproducible: Unknown. Steps to Reproduce: 1.With DRW-1608P2S or a compatible ASUS DVD-RAM writer 2.Insert the Fedora 14 Alpha installation DVD media and boot from it 3.Choose to install KDE SC 4.5 (only) - with default packages for KDE Actual results: No optical drive found. Expected results: Full DVD±RW drive functionality. Additional info: OS: Linux 2.6.35-0.57.rc6.git1.fc14.i686.PAE i686 Current user: user System: Fedora release 14 (Branched) KDE: 4.4.95 (KDE 4.4.95 (KDE 4.5 >= 20100723)) *-cdrom description: DVD-RAM writer product: DRW-1608P2S vendor: ASUS physical id: 0.0.0 bus info: scsi@4:0.0.0 logical name: /dev/cdrom logical name: /dev/cdrw logical name: /dev/dvd logical name: /dev/dvdrw logical name: /dev/scd0 logical name: /dev/sr0 version: 1.22 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram configuration: ansiversion=5 status=ready *-medium physical id: 0 logical name: /dev/cdrom
OK, let's check if hal is running, $ service haldaemon status In the meantime, I'd recommend you update, you're using kde-4.4.95, and we have kde-4.5.1 available now.
[user@localhost ~]$ service haldaemon status hald (pid 1173) is running... I will update to kde-4.5.1.
[root@localhost ~]# yum groupupdate kde-desktop Reboot... [root@localhost ~]# yum update Reboot... [user@localhost ~]$ service haldaemon status hald (pid 1360) is running... K3b Version 2.0.1 Using KDE Development Platform 4.5.1 (KDE 4.5.1) K3b error: "K3b did not find any optical device in your system."
OK, looks like we have some sort of genuine kernel/hal problem here. Trying to determine exactly how k3b probes hal for optical devices, in an attempt to come up with some sort of minimal test-case.
Meh, my eyes are bleeding. :) Someone mind asking upstream here (mailing list, bugs.kde.org , whatever)?
Hi friends. Hi had a similar issue (Fedora 14 alpha & kde 4.5.1) and was a group problem. Try to add the groups users, cdrom and disk to your user and restart your session.
I had a similar problem and it indeed turned out to be a group problem. My user was in the 'users' group and the described problem occured. When I added the 'cdrom' group to that user account, the problem was gone. At no time, that user was part of the 'disk' group, so I'm pretty sure that 'cdrom' is the crucial group, although I must admit that I didn't test the combination of being in the 'cdrom', but not the 'users' group.
I find I don't get this error (with a default install) if a blank disc is inserted before I start K3b. It's also happy with the drive empty when K3b is run subsequently. (K3b/udisks compatibility issue?)
more like possibly a hal/udisks compatibility issue, but yeah.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Should be fixed in KDE 4.6.0, basically the same symptoms as in https://bugs.kde.org/show_bug.cgi?id=261834. Do you happen to run KDE pre4.6 on F14? :)