Bug 520649 – 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 520649 - crash in Panel:


Summary:	crash in Panel:


Status:	RESOLVED DUPLICATE of bug 446183

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-03-06 01:31 UTC by mail
Modified:	2008-03-06 07:08 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description mail 2008-03-06 01:31:40 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 20:27:10 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 336551936 vsize: 336551936 resident: 36569088 share: 32456704 rss: 36569088 rss_rlim: 18446744073709551615
CPU usage: start_time: 1204767054 rtime: 14 utime: 9 stime: 5 cutime:0 cstime: 0 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496503664 (LWP 18292)]
(no debugging symbols found)
0x000000391660d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 191455

Thread 1 (Thread 46912496503664 (LWP 18292))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#4 g_hash_table_foreach
from /lib64/libglib-2.0.so.0
#5 gtk_rc_reset_styles
from /usr/lib64/libgtk-x11-2.0.so.0
#6 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#7 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#8 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit
from /lib64/libgobject-2.0.so.0
#11 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#12 g_object_notify
from /lib64/libgobject-2.0.so.0
#13 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#14 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgdk-x11-2.0.so.0
#16 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#17 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#18 g_main_loop_run
from /lib64/libglib-2.0.so.0
#19 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#20 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
 Wed Mar  5 19:30:00 2008
alarm-queue.c:512 (add_component_alarms) - Alarm added for 20080302T042147Z-3459-500-3423-7@pancks.dickens
alarm-queue.c:401 (alarm_trigger_cb) - Setting Last notification time to Wed Mar  5 19:30:00 2008
alarm-queue.c:1581 (popup_notification)
alarm-queue.c:1438 (display_notification)
alarm-queue.c:1277 (open_alarm_dialog) 
alarm-queue.c:1401 (tray_list_add_async) - Add 0x712e20
alarm-queue.c:445 (alarm_trigger_cb) - Notification sent:2
alarm-queue.c:1199 (notify_dialog_cb) - Received from dialog
(evolution:18309): evolution-mail-WARNING **: Failed to refresh folders: Cannot get folder `/home/jmelody/Maildir/.#evolution': not a maildir directory.
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff4c9fd000
--------------------------------------------------

Comment 1 Philip Withnall 2008-03-06 07:08:55 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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