K3B won't work-help please.

I’m running 11.1 KDE desktop on a Dell Inspiron 1720.

K3B sees my disc drive(pioneer dvd dr-ki7y ata device). When I put a cd or dvd into the drive, it is detected for an instant then shows nothing. Then K3B displays amessage saying it can’t detect any drive although it does on reboot again.
I ran it thru the terminal and got this:

(K3bDevice::Device) could not open device /dev/sr0 for reading
(Permission denied)
DiskInfo:
Mediatype: Unknown
Current Profile: Unknown
Disk state: unknown
Empty: 0
Rewritable: 0
Appendable: 0
Sessions: 0
Tracks: 0
Layers: 1
Capacity: 00:00:00 (LBA 0) (0 Bytes)
Remaining size: 00:00:00 (LBA 0) (0 Bytes)
Used Size: 00:00:00 (LBA 0) (0 Bytes)
(K3bDevice::Device) could not open device /dev/sr0 for reading
(Permission denied)
(K3bDevice::Device) could not open device /dev/sr0 for reading
(Permission denied)

I don’t know what it all means or how to fix this fault. Any help please! I’ve already tried adding CD & Disk to the user group, this does not work.

Try adding yourself to the “Disk” group in yast.

I had a similar problem. If adding yourself to the cdrom user group in YAST2 doesn’t work, try using the kde3 version in case you’re using the kde4 version.

YAST2 > Security & Users

This solution also worked for me with k3b.

Many thanks!
That has solved the problem. Opensuse 11.1 did a perfect install apart from this snag.

Yes, adding myself to disk and cdrom groups in Yast seemed to work. Should this be raised as a bug in 11.1? I never had to do this before to make k3b work.

rjwilmsi wrote:

>
> Yes, adding myself to disk and cdrom groups in Yast seemed to work.
> Should this be raised as a bug in 11.1? I never had to do this before to
> make k3b work.

All 4 systems here are back in commission after installing the packman
version now up. The version is an update from the distro and both i586 and
x86_64 versions now work w/o jumping through hoops. Don’t know about HAL
issues, but that solved the k3b side of it.


Will Honea

Bug is https://bugzilla.novell.com/show_bug.cgi?id=408252 for those who want to track the fix.