GNOME Bugzilla – Bug 93951
Application panel crashed at login (seg fault)
Last modified: 2004-12-22 21:47:04 UTC
Description of Problem: Error message is 'Application "panel" (process 10493) has crashed due to a fatal error. (Segmentation fault) Steps to reproduce the problem: 1. login 2. 3. Actual Results: Expected Results: How often does this happen? Random It happened when I logged in first thing in the morning (ie. the machine was idle for a long time before the login) Additional Information: Running Redhat Linux 7.3 It may be related to the previous logout, here is a piece of /var/log/messages. The logout at 15:55 the previous day is not normal. (There is nothing in the log between 15:55 and 08:46). Sep 20 15:55:24 serpico gdm(pam_unix)[1261]: session closed for user mark Sep 20 15:55:24 serpico gdm[1261]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Sep 20 15:55:24 serpico gnome-name-server[5850]: input condition is: 0x11, exiting Sep 20 15:55:26 serpico modprobe: modprobe: Can't locate module char-major-81 Sep 20 15:55:51 serpico gconfd (mark-1451): GConf server is not in use, shutting down. Sep 20 15:55:51 serpico gconfd (mark-1451): Exiting Sep 23 08:46:28 serpico gdm(pam_unix)[10250]: session opened for user mark by (uid=0) Sep 23 08:46:36 serpico gnome-name-server[10499]: starting Sep 23 08:46:36 serpico gnome-name-server[10499]: name server starting Sep 23 08:46:36 serpico gnome-name-server[10500]: starting Sep 23 08:46:36 serpico gnome-name-server[10500]: name server was running on display, exiting Sep 23 08:46:39 serpico gconfd (mark-10502): starting (version 1.0.9), pid 10502 user 'mark'
Without a stack trace, this bug report is unfortunately not very useful. If you can still duplicate the bug, please use bug-buddy or gdb to get a stack trace, and submit it to bugzilla.
Redhat 8.0 panel moved to the right side of the screen last login than it crashes, as soon as i move it again to the bottom of the screen the problem is solved
Bart: Thanks for updating the steps in simulating the crash. With a stack trace we could do two things. a) mark it as a duplicate of another bug already filed. or b) if its a new trace, then re-open the bug. But as Mark says without a stack trace we can't be of much help.
this is a freshly kickstarted RH7.2 system, and it's crashing on login for me as well. Gnome panel 1.4.0.4 Linux 2.4.7-10, RH7.2 RPM i think the color depth is 16 bits if a stack trace or core file is necessary, how can we generate one?
Crash on login with RH 7.2 is a well known problem. Should be fixed in the latest 1.4.x release. You can get a stack trace if you install bug-buddy. It should pop up a window when the crash happens and take you through a wizard telling you what to do.
It's crashing on RH 8.0 for me. I installed 8.0 in RL3 everything was fine Switched to RL5 in inittab, rebooted panel started crashing Switched back to RL3 in inittab, rebooted panel still crashing
mpeters: again without a stack trace this report is of no use. You could provide one as Kjartan suggests above. Request you to read the whole report before updating it. Probably pointers would have been already provided as how to make the reporting more useful. Please have a look at the below link, ie if you not already seen it.:) http://bugzilla.gnome.org/bug-HOWTO.html Thanks.
I'm not familiar with gdb. I run it with the following result- [mike@mpetershomenetwork mike]$ gdb gnome-terminal 2640 GNU gdb Red Hat Linux (5.2.1-4) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... (no debugging symbols found)... Attaching to program: /usr/bin/gnome-terminal, process 2640 0x420ae169 in ?? () (gdb) I'm not all familiar with gdb so you'll have to forgive me if that isn't what you were looking for. In the morning I look up something better than the man page for gdb and see if then I can maybe get what you want.
You could install bug-buddy. It's a wizard that would take you through an application crash and provide a stack trace.
Created attachment 11568 [details] gdb gnome-panel PID and then bt command
I'm sorry. That last file is bad- I typed gnome-terminal in the gdb, not gnome-panel.
Created attachment 11569 [details] New file containing correct gdb session with backtrace
mpeters: thanks for going to all that trouble. You've hit the most commonly reported bug with GNOME on RH8.0. Please see bug #94625 for more details. *** This bug has been marked as a duplicate of 94625 ***