| Summary: | gnome and gnome-related software crashes | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Martin Wolters <sirdzstic> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
xsession-errors
gnome-terminal stderr output xsession-errors with backtrace xsession-errors .xsession-errors Xorg.0.log.old |
||
|
Description
Martin Wolters
2010-02-03 15:18:32 UTC
Created attachment 218295 [details]
xsession-errors
This is the ~/.xsession-errors created while GNOME crashes.
Created attachment 218297 [details]
gnome-terminal stderr output
As suggested, I built sys-apps/dbus with debug symbols (USE=debug) and ran a random GNOME application (gnome-terminal) to supply you with a backtrace.
Created attachment 218299 [details]
xsession-errors with backtrace
This is the ~/.xsession-errors created with a backtrace of dbus.
Rebuilding glib bindings (dev-libs/dbus-glib, dev-cpp/glibmm and net-libs/telepathy-glib) seemed to have had some positive effect. GNOME now starts, but some panel items are missing. These are the workspace selector, clock and window selector, among others. Application starters and the menu are there and working. When I try to add something to a panel, both panels hang, i.e. they don't update anymore and clicking on them does nothing. Using previously opened windows keeps working, though. you may be facing bug #297483. Which version of glib are you running ? Installed versions: 2.22.4(2)(05:23:11 PM 02/03/2010)(fam -debug -doc -hardened -selinux -xattr) Since in the referenced bug report it was suggested to rebuild glib's reverse dependencies and the ebuilds which I rebuilt (dbus-glib etc) were direct reverse dependencies of glib, I'm now running "revdep-rebuild -L libglib-2.0.so.0". It's 221 packets to rebuild, so it'll take some time. I'll report whether this works. also, it would be nice to know if you had 2.22.3 installed at any time and if you already had to rebuild some packages depending on glib to fix eventual problems that occured with the 2.22.2 -> 2.22.3 upgrade. genlop tells me this:
Sat Dec 19 15:39:21 2009 >>> dev-libs/glib-2.22.3
Sat Jan 30 21:52:48 2010 >>> dev-libs/glib-2.22.4
Problems arose only after 2.22.4 had been installed, but then instantly. I noticed firefox first, so I opened the other bug, but it soon was obvious that other programs broke as well.
20 packets into the rebuild of all reverse dependencies of glib, pidgin started working again. Seems like I'm on the right path. Done. And now almost nothing in X works anymore. gdm and kdm show unreadable messed up fonts. gdm locks up. gnome starts to some extend, then hangs before completely done, triggering a restart of X. Even Fluxbox hangs randomly. Sometimes these errors hang the complete system. I have no idea how to even diagnose these problems. .xsession-errors tell me about resources not being available. Any help where to look would be appreciated. Created attachment 218335 [details]
xsession-errors
New .xsession-errors after starting gnome after rebuild of all reverse dependencies of glib
looks like you are having a problem with xcb now which kills X. Created attachment 218383 [details]
.xsession-errors
I rebuilt x11-libs/xcb-util-0.3.6, x11-proto/xcb-proto-1.6 and x11-libs/libxcb-1.5
Still gnome crashes. I don't know what exactly caused it, since I rebuilt quite a lot last night, but gdm works fine now. No more messed up text or crashes. Fluxbox also works. So I have least an X session now.
I am slowly coming to think that my system plays a fucking bad joke on me. :( I'm wondering why you're not getting bug-buddy popping up when gnome programs crash... That would at least give us some backtraces. Or maybe I'm just confused as to what happens. If you start a gnome session, does it come up at all? Does it hang? Does it kick you back to gdm? If you're in flukebox, and you run a gnome program (say gnome-terminal) does it work? Does it crash? To many sets of rebuilds and changing symptoms have confused me as to what's going on right now. > I'm wondering why you're not getting bug-buddy popping up when gnome programs > crash... That would at least give us some backtraces. > > Or maybe I'm just confused as to what happens. If you start a gnome session, > does it come up at all? Does it hang? Does it kick you back to gdm? When I start a gnome session, it begins to start. Then, right after the panels pop up, X seems to crash. I cant' move the cursor or do anything for a few seconds. Then gdm comes back again. > If you're in flukebox, and you run a gnome program (say gnome-terminal) does > it work? Does it crash? I didn't test a lot of programs, but pidgin and gnome-terminal run perfectly well. I don't think it's a gnome problem anymore. > To many sets of rebuilds and changing symptoms have confused me as to what's > going on right now. I'm sorry. But I can tell you, I am quite confused as well. I thought, maybe it would help to get a backtrace of X, as it seems to me, since the cursor won't move and bug-buddy doesn't pop up that's what actually crashes. I also don't get that "Your session lasted less than 10 seconds" message, although the session obviously lasted much less. Is there a way to run X in gdb to get a backtrace? I have noticed, that if I put gnome-session into .xinitrc and then just run startx, X crashes at the exact same moment as it would after I started gnome with gdm, but when it does, I can't do anything at all. The screen freezes and I can't get back to the VT. A cold reboot is all I can do. So I'd rather not start X by itself, but use gdm when I try to get a backtrace. If I can't run X in gdb in any sensible way, maybe there is another way to get some diagnostics. Thanks in advance. Actually, X prints it's backtrace into it's log when it crashes. Look in /var/log/Xorg.0.log.old which should be the previous (crashed) session. That should be useful. Created attachment 218553 [details]
Xorg.0.log.old
This is the log file. It doesn't contain a backtrace, but maybe there's something else in it that helps.
After having a look on the Xorg log, I figured I had been using some more or less experimental video driver; maybe that was the cause. I updated mesa, libdrm and xf86-video-nouveau (all from git) and just to make sure, the kernel (git), and everything seems fine now. I feel honestly stupid and I'm sorry to have wasted your time. But thanks a lot for all your patience. No problem. Glad it's working again. |
