Quote:
Originally Posted by oimon
I just experienced this problem and resolved it by telling k3b not to eject the media after it finishes burning.
Did you already file a bug for this?
|
I didn't
- but see below
I suspect the maintainer is well aware of the problem. The fact that it works for you but not for me, and that what works in one version fails in another, strongly indicates that k3b is having to handle different hardware dependencies. When I last rummaged around on Google about the problem, this seemed to be the case.
In which case, the k3b guy likely doesn't have lots of hardware to do testing on, which is why I'm sympathetic to the problem and why I suspect it isn't just a bug that can be fixed easily - it needs extensive testing resources and time to get right.
PS It's nice to know that toggling the "eject after burning" flag still works for someone.