Bug 505003 – crash in Panel:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 505003 - crash in Panel:


Summary:	crash in Panel:


Status:	RESOLVED DUPLICATE of bug 487049

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-12-22 08:30 UTC by Cyrille Chépélov
Modified:	2008-01-11 07:01 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description Cyrille Chépélov 2007-12-22 08:30:28 UTC

Version: 2.20.1

What were you doing when the application crashed?



Distribution: redhat-4
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-1-amd64 #1 SMP Fri Nov 30 12:19:15 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: default.kde

Memory status: size: 379928576 vsize: 379928576 resident: 23764992 share: 11796480 rss: 23764992 rss_rlim: 18446744073709551615
CPU usage: start_time: 1197417843 rtime: 21622 utime: 20298 stime: 1324 cutime:0 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b226be3ff90 (LWP 7266)]
[New Thread 0x40040950 (LWP 9449)]
(no debugging symbols found)
0x00002b2265b4c34f in waitpid () from /lib/libpthread.so.0

+ Trace 182615

Thread 1 (Thread 0x2b226be3ff90 (LWP 7266))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 g_slist_remove
from /usr/lib/libglib-2.0.so.0
#6 ??
from /usr/lib/gnome-panel/libclock-applet.so
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 ??
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 ??
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 ??
from /usr/lib/libedataserver-1.2.so.9
#16 ??
from /usr/lib/libORBit-2.so.0
#17 ??
from /usr/lib/libORBit-2.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 ??
from /usr/lib/libglib-2.0.so.0
#20 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#21 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#22 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (404503 sec old) ---------------------
(evolution:2384): camel-imap-provider-WARNING **: No information for message 13
(evolution:2384): camel-imap-provider-WARNING **: No information for message 13
(evolution:2384): camel-imap-provider-WARNING **: No information for message 13
(evolution:2384): camel-imap-provider-WARNING **: No information for message 13
(evolution:2384): camel-imap-provider-WARNING **: No information for message 13
(evolution:2384): camel-imap-provider-WARNING **: No information for message 13
(evolution:2384): camel-imap-provider-WARNING **: No information for message 13
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Susana 2007-12-23 21:53:18 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 2 Philip Withnall 2008-01-11 07:01:39 UTC


*** This bug has been marked as a duplicate of 487049 ***