http://bugzilla.opensuse.org/show_bug.cgi?id=1009637 http://bugzilla.opensuse.org/show_bug.cgi?id=1009637#c3 --- Comment #3 from Boian Berberov <bberberov+suse@gmail.com> --- (In reply to Dominique Leuenberger from comment #1)
'a couple of months' is quite bad - and makes it quite difficult to narrow down what could cause it now.
I assumed it was something with Mesa/DRI/graphics stack. It usually is, but I doubt it now. I am running Intel Sandy Bridge, but the way, but I also have and Optimus NVidia that should be disabled 'games' is not the main repo. I was not sure how things are handled in OpenSUSE; if the bug would even be looked at. In the end I was hoping you have a 'bisect-like' tool, if it was reproducible.
What openSUSE Version are you playing this on? (I'm just installing it again and will try to reproduce - I'm using TUmbleweed)
I'm running Tumbleweed and it's updated weekly. Will be updating tonight.
That's the actual issue we need to narrow down. If you run this on a recent version of openSUSE, systemd-crashhandler should have intercepted it and produced a coredump.
I am not sure coredumps are produced, but I'll check. I think that can be enabled.
gdb MIGHT be asking you to install -debuginfo packages; follow the instructions given by gdb how to do it (you can copy the zypper command line produced) - then reproduce above steps, until no further debuginfo is missing.
Then copy the output of "bt" in a text file and attach it here for review.
I'll install the debuginfo packages and try to generate some kind of trace. -- You are receiving this mail because: You are on the CC list for the bug.