On Tuesday 18 March 2008 07:10:47 pm Nico Golde wrote: > Hi Scott, > > * supaplex <[EMAIL PROTECTED]> [2008-03-18 20:05]: > > I've also compiled a debug DEB_BUILD_OPTIONS=nostrip release of this > > package, and attached backtraces. I'm also including a copy of a > > backtrace on firefox-bin, as the problem origionally appeared to be an > > unresponsive firefox (it was acting a little strange). firefox and > > openbox seemed to lockup at the same time. firefox wasn't using any cpu > > time (two cores on this box), but openbox pegged one of the cores (has > > for the last 10m while researching this report). > > How do you think can I debug this? Again, your original top > output shows *two* openbox processes running which is not > possible unless your old X session didn't cleanly exit which > is not an openbox issue. Did you try the openbox version > from backports? > > Kind regards > Nico
This is a new report. I will try the backport and update you if it happens again. You closed the old bug just before I was to follow up on it. I've since restarted my system anyhow. I gave up on it until "next time" (which would be now). The second instance from the old report didn't start until after I opened a bug report. Anyway, let's bury the old bug report. I think it all started after bzflag exited abnormally. Thanks, Scott Edwards -- Daxal Communications - http://daxal.com/?from=debian+bts -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
