Bug 453896 – crash in Panel: logging in / starting a ...

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 453896 - crash in Panel: logging in / starting a ...


Summary:	crash in Panel: logging in / starting a ...


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:	2007-07-05 08:18 UTC by mybudbuddyreport
Modified:	2007-07-05 10:16 UTC

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

Description mybudbuddyreport 2007-07-05 08:18:13 UTC

Version: 2.18.2

What were you doing when the application crashed?
logging in / starting a user session


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 50040832 vsize: 50040832 resident: 23199744 share: 20750336 rss: 23199744 rss_rlim: 4294967295
CPU usage: start_time: 1183623411 rtime: 10 utime: 9 stime: 1 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208215840 (LWP 4226)]
(no debugging symbols found)
0x00565402 in __kernel_vsyscall ()

+ Trace 145852

Thread 1 (Thread -1208215840 (LWP 4226))

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



----------- .xsession-errors ---------------------
alarm-notify.c:316 (cal_opened_cb) file:///home/sa/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:1998 (alarm_queue_add_async) - 0x9a00480
alarm-queue.c:585 (load_alarms_for_today) - From Thu Jul  5 10:16:55 2007
 to Thu Jul  5 10:16:55 2007
alarm-queue.c:522 (load_alarms) 
alarm-queue.c:551 (load_alarms) - Setting Call backs 
alarm-queue.c:1998 (alarm_queue_add_async) - 0x9a1de50
alarm-queue.c:585 (load_alarms_for_today) - From Thu Jul  5 10:16:55 2007
 to Thu Jul  5 10:16:55 2007
alarm-queue.c:522 (load_alarms) 
alarm-queue.c:551 (load_alarms) - Setting Call backs 
alarm-queue.c:1998 (alarm_queue_add_async) - 0x9a18950
alarm-queue.c:585 (load_alarms_for_today) - From Thu Jul  5 10:16:55 2007
 to Thu Ju
--------------------------------------------------

Comment 1 André Klapper 2007-07-05 10:16:57 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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