k3b locks up on searching for devices after running app 1st time on 2.6.12-10-686-smp

Please attach dmesg output. This very likely wont be fixed for Breezy, so if you could test Dapper (even just the liveCD, which doesn't require upgrading the kernel) to verify the bug there, I would appreciate it.

Thanks

http://cdimage.ubuntulinux.org/releases/dapper/flight-3/

I have the same problem with dapper. As I found the problem is related to k3b in conjunction to kernel >= 2.6.14.
See related link http://k3b.plainblack.com/message-board/-k3b-start-freeze--kernel-gt-2.6.14

Maybe an update to a newer k3b (k3b-0.12.15) can help as somebody mentioned there.

I believe I have the same problem in Dapper, kernel version 2.6.15-27-386. I recently installed Dapper and downloaded the latest updates, then installed the latest k3b off the repository. k3b would not run from the icon in the menu, nor from the command line. k3bsetup would not run either expecting to find a file called k3bsetup2 (non existent).

After trying various combinations of command line starts including "gksudo k3b", I got it to start once using "k3b --copycd". At startup I got error messages along the lines of:

X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kbuildsycoca running...
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

There were also some DCOPClient errors which I did not capture but were similar to those listed below.

Burnt a CD successfully but k3b did not exit cleanly from the command line with the following error:

ICE default IO error handler doing an exit(), pid = 11328, errno = 0
ICE default IO error handler doing an exit(), pid = 11339, errno = 0

I had to use CTRL-C to get back to command line.

After the next re-boot was back to the same situation (no k3b startup).

I noted that if trying to start via Command line (no gksudo) I would get the additional DCOPClient error messages as below and the X Errors.

DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
Link points to "/tmp/ksocket-mvr"
Link points to "/tmp/kde-mvr"

Also found that in System monitor, k3b would appear as Running for a few seconds on startup and then move to Uniterruptible state. I could not kill k3b either in System Monitor or using command-line kill. Trying to start additional k3b instances would result in them going to Zombie state though these processes could be killed. The system would also lockup on trying to shutdown or restart and I would have to hit the Reset button on the machine (PIII 866MHz) to re-boot.

I have rebooted the machine several times and have not been able to get k3b running again but have noticed exactly the above situation (k3b in Uninterruptible state).

Hope this points to a solution as I am new to Linux so am unable to resolve it. Have tried various solutions found on the web that involve either deleting .ICEauthority file or changing its ownership but these have not worked. Have also requested support in Ubuntu forums but the only solution I was offered was to remove k3b and re-install (which did not work).

I'm experiencing this too since updating to Feisty (and new kernel image) and beryl.

With the new 2.6.20 k3b refuses to recognize the Plextor DVDR PX-716A altogether, although the device is recognized in dmesg and asigned sr0, as well as Gnome device manager.

In 2.6.17-11 I can launch and burn once. If the application is set to eject the disk after burning, that's where it starts locking. After a burn GUI and CLI CD access tools cannot access the SATA burner, the LED reporting drive activity glows solidly after this, though the button ejection of the device still works.

dmesg says this during these episodes:
[75578.553656] sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
[75578.553663] sr: Current [descriptor]: sense key: Aborted Command
[75578.553666] Additional sense: Scsi parity error
[75580.664892] ata1 is slow to respond, please be patient
[75591.059913] ata1 failed to respond (30 secs)
[75591.064241] ata1: command 0xa0 timeout, stat 0xd0 host_stat 0x0
[75591.064245] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[75591.056432] sr 0:0:0:0: ioctl_internal_command return code = 8000002
[75591.056438] : Current [descriptor]: sense key: Aborted Command
[75591.056443] Additional sense: Scsi parity error
[75596.176401] ata1 is slow to respond, please be patient
[75606.573079] ata1 failed to respond (30 secs)
[75606.577421] ata1: command 0xa0 timeout, stat 0xd0 host_stat 0x0
[75606.577428] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[75608.689056] ata1 is slow to respond, please be patient
[75619.085733] ata1 failed to respond (30 secs)
[75619.090122] ata1: command 0xa0 timeout, stat 0xd0 host_stat 0x0
[75619.090129] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00

Every burn that has caused this is has been good data-wise, so far. It almost looks like it's hardware related except it happened the 1st burn after upgrading to Feisty, which was 15 minutes after install end, and never before.

When I look at processes k3b and supporting kde-libs are the only programs associated still running. I don't see cdrecord or cdparanoia hanging out. k3b is difficult to kill needing a few "sudo kill -9 'PID'" to remove.

System: Asus A8V AMD Athalon X2 4800 4Gb RAM NVidia Geforce 6800
Kernel: Linux 64-bit 2.6.17-11-generic #2 SMP Tue Mar 13 22:06:20 UTC 2007 x86_64 GNU/Linux
Xconfig: gdm and beryl

I have had this problem resolved in the last week after submitting a bug report to the k3b developer (Sebastian Trueg). I was able to narrow the problem to k3b due to changing my CDRW to a DVDRW drive on my PC.

Apparently there was a problem with the way k3b was communicating with the hardware (SCSI commands) and this showed up only on some hardware hence not everyone experienced it. Ubuntu currently provides version 0.12 of k3b in the repositories. I was instructed to compile the latest version (V1.0) of k3b and this continued to have the same problem. I was then sent a patch which fixed the problem - I can now run k3b reliably. The latest version of k3b now has this patch (v1.0.1) and this can be found here:

http://k3b.plainblack.com/download

Instructions on compiling are provided from this page and I have compiled and used k3b successfully in Ubuntu 6.06. I would recommend this is tried to see if the bug is resolved.

Thanks for the reply!

Nope. I finally got a few spare moments to download and install the kde and qt requirements and build.

Version 1.0.1 has the same issuses exactly as above.

Gnomebaker has, in this time, been burning images with no problems so I doubt it's a hardware cause.

The one difference i see between your situation and mine is that I'm using 7.04, and the upgrade to the supporting libraries or binaries might be the root of the issue.

It does die after a while now but leaves kde envirnoment binaries running like:

22642 ? 00:00:00 kdeinit
22647 ? 00:00:00 dcopserver
22650 ? 00:00:00 klauncher
22652 ? 00:00:00 kded
22751 ? 00:00:00 kio_file
22786 ? 00:00:00 kdesud
22887 ? 00:00:01 artsd
22967 ? 00:00:00 knotify
22970 ? 00:00:02 artsd

(I'm kind of confused about artsd showing up twice.)

I'll keep my eyes on the development and maybe submit a bug report to Sebastian as it's the most feature full burning application I've seen for linux and I miss its functionality dearly.

This bug has had no activity for a considerable period. This is a check to see if there is still interest in considering this bug report.

Closing.