GNOME Bugzilla – Bug 156507
crashes on login
Last modified: 2005-10-13 16:53:17 UTC
Distribution: Debian 3.1 Package: gnome-utils Severity: normal Version: GNOME2.8.1 2.8.1 Gnome-Distributor: Debian Synopsis: crashes on login Bugzilla-Product: gnome-utils Bugzilla-Component: logview Bugzilla-Version: 2.8.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: gnome-system-log apparantly has issues with session management: When I launch it manually it runs just normal. If it is restarted on logon from a previously saved session, it will invariably crash first time it gets the focus. Steps to reproduce the crash: 1. Start gnome-system-log 2. save session 3. log out 4. log in, be patient while session manager restores saved session 5. Click into logview window 6. See it crash How often does this happen? always Debugging Information: Backtrace was generated from '/usr/bin/gnome-system-log' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1082747296 (LWP 2152)] 0x4118a40e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 51351
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-26 14:50 ------- Unknown version 2.8.1 in product gnome-utils. Setting version to "1.4.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-utils". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Do you log in as root ?
Of course not.
When you save the session, do you have any opened log in gnome-system-log ?
Yes. I have auto-save-session on logout turned on. I typically have three logfiles open at a time, including /var/log/syslog and /var/log/auth.log. I did expect the program to save its current state at logout and to restore it next time without crashing. Isn't that what session management is all about?
You're totally right in your expectations, and I'm trying to understand your setup in order to fix the problem. Actually gnome-system-log cannot open the logfiles if you don't have the permissions on them. Does your user account have the permissions to open the /var/log/syslog and /var/log/auth.log files ? Otherwise, how did you open them ?
On Debian, members of the adm have read access to most of the contens of /var/log, including syslog and auth.log.
I meant to say "adm group". So to make it absolutely clear: I access the logfiles directly. No sudo involved.
I'm trying to fix this issue for the next release of gnome-utils (2.9.1). The use of command line parameters should work better now (I don't even think it was working before). These changes are in CVS if you want to give it a try, the crash should be gone at least.
Could you try the newly released gnome-utils 2.9.0 and see if the problem is fixed ?
Do I need to update the GNOME libraries to build them?
Well your gtk+ must be from the 2.5 series but apart from that nothing else is required I think.
*** Bug 160860 has been marked as a duplicate of this bug. ***
Johannes : were you able to see if a recent gnome-system-log fixes your problem ?
I'm sorry, but since gtk+-2.6 has not yet hit Debian unstable I'm unable to test this easily.
Johannes : any news about this ?
I cannot verify if it still happens. The reason is that current gnome-system-log doesn't seem to handle session management. It simply doesn't restart when I log in. Apart from that I've just submitted a new report, #308009 also a crash in gnome-system-log.
Hey Johannes, you were totally right - session management was hosed in gnome-system-log 2.12. This is now fixed on cvs (and will be in the upcoming 2.13.1 release of gnome). As gnome-system-log does not use popt anymore (which appears in the backtrace), I think this specific crash will no longer happen (new crash are always possible though ;-)) - so I'm closing this bug.