Arch Linux

is your user in the group disc ?

any kernel or udev upgrades?

i cannot imagine, that this is caused by dvd+rw-tools and/or k3b

Arjan Timmerman: Yes, my user is in the disc group.

Damir Perisa: It has worked properly since the time when I booted my computer into kernel 2.6.10_RC2 83 days ago. It was a software change that broke it. It works as expected as root. I have full read-write permissions to the device. I can burn CDs fine, but I do not burn CDs anymore, they are so itty bitty.

The error relates to growisofs not being able to lock the drive, which means it can not guarantee that the disc will not be ejected during burning, which means it can not allow the burn to occur.

Damir Perisa: Oh, and as I said in my initial comment, I am using devfs and not udev.

devfs is most probably the source of your trouble

Damir Perisa: DVD burning has long worked with devfs ... you are not reading the comments. It worked when I booted my computer. What kind of crappy, unhelpful comment is "devfs is most probably the source of your trouble" ? Devfs is just a way to access device nodes, it does not change what the devices are capable of. Rather than giving random "advice", just say that you have no clue what the problem is.

1) soft language, please

2) i never said i knew in detail, what your problem is ... but "Operation not permitted" means most probably that there are wrong permissions to do things ... and this is handled by the kernel and udev/devfs in primary and only secondary by growisofs. it is absolutely possible that it is caused by dvd+rw-tools, but then it would be an incompatibility or trouble of dvd+rw-tools with your drive and in this case, please be so kind and contact the dvd+rw-tools devs.

3) arch is now using udev as default /dev popluation and over long time things will get broken if you keep devfs (devfs is marked in any current kernel as OBSOLETE)

4) please provide verions of used kernel and devfs, dvd+rw-tools, k3b and all others

Damir Persia: Again you are not actually reading any of the comments I am writing. I stated above that I am using kernel 2.6.10_RC2. Everything else is up-to-date Arch Linux packages. It worked as user when I booted up, so the problem is related to software changes, not the kernel.

Qt: 3.3.4
KDE: 3.3.2
K3b: 0.11.20

* growisofs by <appro@fy.chalmers.se>, version 5.21,
front-ending to mkisofs: mkisofs 2.01 (i686-pc-linux-gnu)

devfsd 1.3.25-4

GLIBC 2.3.3

dvd+rw-tools 5.21.4.10.8-2

thank you very much on the infos.

i read all your comments and only wanted to be sure, you are using a release candidate kernel. if you once again suspect me of "not reading the comments", i will for sure stop reading them and close this bug as "worksforme". you must understand that english is not my native language and things may sound different for a native speaker - sorry for any misconceptions caused by this

is there any important reason, why you use a 2.6.10_rc2 kernel? release candidate kernels are known to be un-reliable and tricky for some things. is there a chance, that you try the kernel26 instead? i'm asking this, because i know that the optical drive access was changed in the kernel several times from 2.6.8 over 2.6.8.1, 2.6.9 and 2.6.10 and now modern apps are not longer able to handle one of the older kernels for burning (for details on this changes related to k3b, have a look here: http://k3b.plainblack.com/index.pl/news2 )

i cannot reproduce your trouble with the stock-kernel

please try the stock-kernel and report if you can reproduce it

-> this bug will be closed on sunday morning

Re-opened by request from Raven Morris.

I am on a 2.6.11_RC4 kernel now, and like when I first booted into my former kernel, CD burning worked as my user ... for a couple hours. I think I have tracked down what is causing this "can not lock the DVD drive, so we can't burn a DVD" business. Sometimes after burning a DVD, the drive is still locked and I can't use the eject button. Rather than going into k3b and "Right-clicking > Unlock", I usually just run the "eject" command.

It seems that the eject command is what is breaking the users ability to lock the DVD. After eject forcibly unlocks and ejects the disc, the user can no longer lock the drive. I would appreciate it if anyone else could test this theory a bit on their systems. After burning a DVD, check if you can hit the eject button, if not use the "eject /dev/dvd" or similar command, and then try burning another DVD. If it always unlocks it, perhaps just try locking it with k3b using "Right-click > Lock", and then using the eject command.

I have no idea if this is a kernel problem or a growisofs problem, but I did not get it on 2.6.8 and earlier.

If nobody else can reproduce the "unlockable DVD drive" on their Arch Linux systems after using eject on a locked drive, I will assume it has nothing to do with Arch Linux.

How exactly are we supposed to support custom built kernels?

2005-03-06 - bug squashing day discussion:
conclusion:

custom kernel - devfs - closing