OK, please somebody who knows how to handle dependencies within bugzilla not that bugs #450213, #460791 and #460727 are duplicates. I get bloody MID-AIR-COLLISION! warnings when I try to enter the dependencies.

Broadly speaking only root can burn DVDs/CD-Rs in 11.1, this goes both for KDE and GNOME desktops.

I can confirm this issue. Nero works fine.  Drives will show up if no media is in the drives.  Once media is put in the drives and k3b is started back up the drive is gone.

As well it is not limited to k3b, same thing happens in brassaro. With different systems and drives.

dmesg outputs 

cdrom: This disc doesn't have any tracks I recognize!
sr 6:0:1:0: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sr 6:0:1:0: [sr1] Sense Key : Blank Check [current]
sr 6:0:1:0: [sr1] Add. Sense: No additional sense information
end_request: I/O error, dev sr1, sector 0
Buffer I/O error on device sr1, logical block 0
sr 6:0:1:0: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sr 6:0:1:0: [sr1] Sense Key : Blank Check [current]
sr 6:0:1:0: [sr1] Add. Sense: No additional sense information
end_request: I/O error, dev sr1, sector 0
Buffer I/O error on device sr1, logical block 0

when a  disk is inserted after that the native linux burning apps don't see the drives.

Some other notes.

Logging in as root and then logging back in as the user will make the drive appear again and show the correct info about the burnable medium.

I am also having this problem, I know before my DVD/CD burner was always labeled as /dev/sr0 but in this release according to wodim --devices this is what I have:

SE-03:/home/vendion # wodim --devices
wodim: Overview of accessible drives (1 found) :
-------------------------------------------------------------------------
 0  dev='/dev/scd0'     rwrw-- : 'PIONEER' 'DVD-RW DVR-K17RS'
-------------------------------------------------------------------------

and dmesg has this:

sr 2:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sr 2:0:0:0: [sr0] Sense Key : Blank Check [current]
sr 2:0:0:0: [sr0] Add. Sense: No additional sense information
end_request: I/O error, dev sr0, sector 0
Buffer I/O error on device sr0, logical block 0
sr 2:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sr 2:0:0:0: [sr0] Sense Key : Blank Check [current]
sr 2:0:0:0: [sr0] Add. Sense: No additional sense information
end_request: I/O error, dev sr0, sector 0
Buffer I/O error on device sr0, logical block 0
cdrom: This disc doesn't have any tracks I recognize!

I am able to use my drive with CD rom and burned CDs and DVDs but when I try to use a blank CD/DVD the drive is no where to be found.

*** Bug 450213 has been marked as a duplicate of this bug. ***

*** Bug 460727 has been marked as a duplicate of this bug. ***

Adding the user account to the "cdrom" group, then logging back into of KDE, will work around this problem.

In YaST, go to Security and Users, User and Group Management, and "Edit" the user account - under the "Details" tab.

Even adding the cdrom group is not reliable. I have done this to all users on my system. After logging in they still experienced problems. There are 2 things strange about this:

After logging off and on again (*NO* change in groups list!) they got access to the CD-ROM drive. "cdrom" was already in the group access list, when the problem still existed. I have checked this with the id(1) command inside the affected session.

I have another PC i686, which is LDAP client of my x86_64 server. There I have *NOT* added my users to the group cdrom (they are LDAP users). It was the same game. They needed to log out and in for several times, then k3b could access the DVD writer.

After the first successfull acces to the CD writer the situation seems to be stable for a user. Are there recordings regarding the access rights?

*** This bug has been marked as a duplicate of bug 408252 ***

Adding the cdrom group to the user does not cure the issue at all.  Issue persists with the same behavior.