k3b causes complete system freeze on startup

[Russ Brown]

Binary package hint: k3b

I am finding that attempting to run k3b completely freezes my system, before k3b shows anything on screen. CTRL+ALT+DEL doesn't work, pressing numlock does not change the keyboard light state, ping, ssh and nmap attempts from other machines imply a completely dead system, and animated screen elements such as system load graphs in the panel also freeze.

This happened both before and after an upgrade from kde 4.3.2 to 4.3.4. I am running kubuntu karmic.

I have tried starting k3b from the command line to view any output, but there was none. I also tried tailing /var/log/syslog and /var/log/messages while starting it, but nothing. Finally, I attempted to use strace and redirect output from both stdout and stderr to a file, but upon reboot this file was empty: either there was no output, or the output never made it to disk before the system crashed.

At this point I am out of ideas on how to proceed with diagnosing this, so any help on what I should try next would be appreciated.

[Rohan Garg (rohangarg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

[Russ Brown (pickscrape)]

Hi,

Sorry, I'd forgotten about this bug. I can confirm that in 10.10 this no longer occurs.

I would close the bug off myself but I don't know if you want it marked as "Invalid" or "Fix Released", so I'll leave it to you to deal with appropriately.

Thanks for looking!

[Rohan Garg (rohangarg)]

Thanks for the info,ill close this bug as Fix released as this was fixed in the latest dev version