GNOME Bugzilla – Bug 149892
the gnome-panel is crashing repeatedly. I am running gnome on a Redhat enterprise linux on a hosted machine. And using tarantella native client for remote access.
Last modified: 2004-12-22 21:47:04 UTC
Description of Problem: Steps to reproduce the problem: 1. Login using tarantella native client 2. 3. Actual Results: gnome-panel crashes repeatedly. Expected Results: How often does this happen? everytime. Additional Information: kde or fvwm2 seem to work fine.
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused the crash. Please see http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace.
vijay, I rebooted(remotely) the m/c. Now the problem is not occuring. I am new to using gdb for trace. I tried issuing "run" command in gdb, since the gnome-panel was already running and, it didnt allow me to do it. So no trace for now. Prbbly this bug can be closed for now, I'll reopen the bug if it resurfaces. I'll also furnish the trace then. Thanks. -Srinivas
srinivas, You can refer the above provided link to get stack trace. If the process is already running then you can attach PID to gdb. Reopen if you see the problem and attach stack trace. Closing. Thanks -Vijay.
oops...we closed this one too early i guess... gnome-panel crashed again...this time, it exactly happened when i right-clicked on the panel to view its properties... i got the trace using Bug Buddy. Trace: ------------------------------------------------------------------------ Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1232438784 (LWP 5450)] 0xb72aa76e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 49261
Thread 1 (Thread -1232438784 (LWP 5450))
The panel has been automatically restarted and is running fine at this moment. But dont know when it'll bomb again. Let me know if more details are required. -Srinivas
Srinivas, Unfortunately, that stack trace is not very useful in determining the cause of the crash Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces. Thanks -Vijay.
What version of GNOME are you running? This looks similar to a GTK+ bug which was fixed in 2.2 or 2.4, IIRC.
i'll get back with a better stack next time the panel crashes. i m using gnome 2.2.2.
somebody save me. gnome panel crashed again...i used gdb to get the trace for the crashed process(15164). This is what i got after issuing a "thread apply all bt" cmd at the gdb prompt :
+ Trace 49305
Thread 1 (Thread -1232438784 (LWP 15164))
i m a novice on debugging on linux with trace and all. So please excuse me if i have given a useless stack again...but this is exactly what i obtained by following the steps given in the link provided by vijay. rgds, srinivas.
This is fixed. You should upgrade GTK+. *** This bug has been marked as a duplicate of 105745 ***