Comment 3 for bug 26572

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).