Joe Neal wrote: > I got it run with chromium frozen. I just wasn't real sure what to do with > the data from there.
You can copy and paste the backtrace from the terminal or use gdb | tee backtrace.txt to log debugging output to a file[1]. Then I would suggest attaching it to http://crbug.com/48259 (or failing that, the Debian bug). Are there any themes in the backtraces? Is chromium stuck in a different function when frozen than during normal operation? Another ignorant question: are you using compiz? From random searching it seems you can temporarily disable compiz by running "kwin --replace" if kwin is installed. I ask because your symptoms seem vaguely reminiscent of http://crbug.com/29561 [1] a trick from http://wiki.debian.org/Chromium/Debugging -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
