[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software




2.6.8-4 makes situation better. It's working now in root-mode.
User mode in k3b is still not working.
One of my burners is still only recognised as reading-device
and burning stops with debug message below.

But this looks like a "wanted" (how strange things can be)
result as I'm reading the kernel discussions...

So its time for the app-developer to come up with a solution.
<sarcasm>Don't think they are happier than I.</sarcasm>

Maybe it's done by simply adding a conflict to the package.

Thanks for your fast response.
Cheers
Helmut

System
-----------------------
K3b Version:0.11.14
KDE Version: 3.3.0
QT Version: 3.3.3

growisofs
-----------------------
INFO: ISO-8859-15 character encoding detected by locale settings.
 Assuming ISO-8859-15 encoded filenames on source filesystem,
 use -input-charset to override.
:-( unable to PREVENT MEDIA REMOVAL: Operation not permitted

growisofs comand:
-----------------------
/usr/bin/growisofs -Z /dev/hdc -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=dao -dvd-compat -speed=4 -gui -graft-points -volid KK -volset -appid K3B THE CD KREATOR VERSION 0.11.14 (C) 2003 SEBASTIAN TRUEG AND THE K3B TEAM -publisher -preparer K3b - Version 0.11.14 -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-heli/k3bUUtCoa.tmp -rational-rock -hide-list /tmp/kde-heli/k3b9q7A7a.tmp -joliet -hide-joliet-list /tmp/kde-heli/k3b1qQN8a.tmp -udf -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-heli/k3bxklNcc.tmp



Sven Luther wrote:
On Fri, Aug 27, 2004 at 03:29:53PM +0200, Toplitzer Helmut wrote:

Package: kernel-source-2.6.8
Version: 2.6.8-3
Tags: sarge, sid

The new kernel breaks all CD bruning software in one
or another way. Tested this with K3B and its
making problems even in root-only mode.
Other kernel-versions (<=2.6.7) are working without problems.


This seems to be at least partially fixed in kernel-source 2.6.8-4, and you
should never have even seen that 2.6.8-3 package you are referencing, since it
never reached any archive.

Can you please try the latest kernels, and verify that this is indeed fixed
for you ?
Friendly,

Sven Luther




Reply to: