Bug 483467 – crash in Panel: Closed Evolution 2.12

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 483467 - crash in Panel: Closed Evolution 2.12


Summary:	crash in Panel: Closed Evolution 2.12


Status:	RESOLVED DUPLICATE of bug 378854

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-04 19:42 UTC by Michael Schurter
Modified:	2007-10-05 14:19 UTC

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

Description Michael Schurter 2007-10-04 19:42:23 UTC

Version: 2.20.0.1

What were you doing when the application crashed?
Closed Evolution 2.12


Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 74571776 vsize: 74571776 resident: 24080384 share: 14581760 rss: 24080384 rss_rlim: 4294967295
CPU usage: start_time: 1191502733 rtime: 4792 utime: 4458 stime: 334 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6eac6b0 (LWP 9943)]
[New Thread 0xb61f6b90 (LWP 21901)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 167780

Thread 1 (Thread 0xb6eac6b0 (LWP 9943))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /tmp/buildd/glib2.0-2.14.1/glib/gspawn.c line 364
#3 IA__g_spawn_command_line_sync
at /tmp/buildd/glib2.0-2.14.1/glib/gspawn.c line 672
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 IA__g_slist_remove
at /tmp/buildd/glib2.0-2.14.1/glib/gslist.c line 207
#7 backend_died_cb
at calendar-sources.c line 432
#8 IA__g_cclosure_marshal_VOID__VOID
at /tmp/buildd/glib2.0-2.14.1/gobject/gmarshal.c line 77
#9 IA__g_closure_invoke
at /tmp/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
#10 signal_emit_unlocked_R
at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2440
#11 IA__g_signal_emit_valist
at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2199
#12 IA__g_signal_emit
at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2243
#13 backend_died_cb
at e-cal.c line 428
#14 IA__g_cclosure_marshal_VOID__VOID
at /tmp/buildd/glib2.0-2.14.1/gobject/gmarshal.c line 77
#15 IA__g_closure_invoke
at /tmp/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
#16 signal_emit_unlocked_R
at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2440
#17 IA__g_signal_emit_valist
at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2199
#18 IA__g_signal_emit
at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2243
#19 connection_listen_cb
at e-component-listener.c line 50
#20 ??
from /usr/lib/libORBit-2.so.0
#21 ??
#22 ??
#23 ??
from /usr/lib/libORBit-2.so.0
#24 ??
from /usr/lib/libORBit-2.so.0
#25 ??
#26 ??
#27 ??
#28 ??
from /usr/lib/libORBit-2.so.0
#29 ??
#30 ??
#31 ??
#32 ??
from /usr/lib/libORBit-2.so.0
#33 ??
from /lib/i686/cmov/libpthread.so.0
#34 main_context_list
from /usr/lib/libglib-2.0.so.0
#35 ??
#36 ??
from /usr/lib/libglib-2.0.so.0
#37 ??
#38 ??
#39 ??
#40 g_idle_dispatch
at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 4132
#0 __kernel_vsyscall



----------- .xsession-errors (15 sec old) ---------------------
fff
fff
in emp_apps_open_in
fff
fff
fff
fff
fff
fff
fff
fff
fff
fff
** (gnome-panel:9943): WARNING **: The calendar backend for exchange://michael;auth=Basic@THSDC1/;personal/Tasks has crashed.
--------------------------------------------------

Comment 1 palfrey 2007-10-05 14:19:29 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 378854 ***