Re: [opensuse-testing] bizarre GNOME 3 issue - how to capture what's happening?

I have lots more info now. I set /proc/sys/kernel/core_pattern and discovered that it's a Chrome crash. The Chrome executable is wrapped by a bash script that has this line at the bottom: # We don't want bug-buddy intercepting our crashes. http://crbug.com/24120 export GNOME_DISABLE_CRASH_DIALOG=SET_BY_GOOGLE_CHROME so I wonder if Chrome even managed to send a message up to Google on the way down - the crash is so fast that I'd be surprised. Google doesn't supply debug symbols for Chrome so I think I'll switch to Chromium where we have a real open source debugging process ;-) On Wed, Nov 2, 2011 at 1:59 AM, Bruno Friedmann wrote:

On 11/01/2011 09:12 PM, M. Edward (Ed) Borasky wrote:

...

On Tue, Nov 1, 2011 at 12:23 AM, Bernhard M. Wiedemann wrote:

...

Am 01.11.2011 06:07, schrieb M. Edward (Ed) Borasky:

...

I've got a bizarre GNOME 3 issue on my openSUSE 12.1 RC2 laptop. I usually am in the Chrome browser, but it fails in Chromium as well. At seemingly random times, I'll browse to a web site or activate some JavaScript widget and the screen will suddenly drop back to a login prompt! I think I can poke around and find a sequence of operations that will trigger this, but what do I have to do to get log files / crash dumps to figure out what's happening?

could be a Xorg crash. Check /var/log/Xorg.0.log

if there is a segfault, you can get a useful backtrace by following http://en.opensuse.org/openSUSE:Bugreport_X#How_to_test_the_latest_Xorg

It looks normal - no segfaults, anyhow. I'm guessing GNOME at this point. Are there log files from GNOME somewhere?

I did push ulimit up - with luck I'll get a core dump and can find a guilty / victim process.

...

Ciao Bernhard M. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-testing+owner@opensuse.org

Perhaps the other way to backtrace that is opening the chrome then in a console session like tty2 use gdb attach Pid of chrome

so the debugger is outside X

Another place to look is inside ~/.xsession-errors

--

Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-testing+owner@opensuse.org

-- http://twitter.com/znmeb http://borasky-research.net "A mathematician is a device for turning coffee into theorems." -- Paul Erdős -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-testing+owner@opensuse.org