Bug 539300 – crash in Panel: I quit Evolution.....

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 539300 - crash in Panel: I quit Evolution.....


Summary:	crash in Panel: I quit Evolution.....


Status:	RESOLVED DUPLICATE of bug 378854

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:	2008-06-20 14:59 UTC by Cassiano Leal
Modified:	2008-06-20 16:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description Cassiano Leal 2008-06-20 14:59:07 UTC

Version: 2.20.3

What were you doing when the application crashed?
I quit Evolution.....


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: black-white_2-Neon

Memory status: size: 65105920 vsize: 65105920 resident: 29593600 share: 16109568 rss: 29593600 rss_rlim: 4294967295
CPU usage: start_time: 1213963857 rtime: 1798 utime: 1698 stime: 100 cutime:0 cstime: 1 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 0xb6ebca20 (LWP 3958)]
[New Thread 0xb6997b90 (LWP 11381)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 200940

Thread 1 (Thread 0xb6ebca20 (LWP 3958))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 IA__g_slist_remove
at /build/buildd/glib2.0-2.16.3/glib/gslist.c line 321
#7 backend_died_cb
at calendar-sources.c line 432
#8 IA__g_cclosure_marshal_VOID__VOID
at /build/buildd/glib2.0-2.16.3/gobject/gmarshal.c line 77
#9 IA__g_closure_invoke
at /build/buildd/glib2.0-2.16.3/gobject/gclosure.c line 490
#10 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2440
#11 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2199
#12 IA__g_signal_emit
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2243
#13 backend_died_cb
at e-cal.c line 428
#14 IA__g_cclosure_marshal_VOID__VOID
at /build/buildd/glib2.0-2.16.3/gobject/gmarshal.c line 77
#15 IA__g_closure_invoke
at /build/buildd/glib2.0-2.16.3/gobject/gclosure.c line 490
#16 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2440
#17 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2199
#18 IA__g_signal_emit
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2243
#19 ??
from /usr/lib/libedataserver-1.2.so.9
#20 ??
#21 ??
#22 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
report junk?? NEW jobs matching your criteria
report junk?? NEW jobs matching your criteria
report junk?? Qa Jobs from The IT Job Board
report junk?? NEW jobs matching your criteria
(evolution:4137): evolution-mail-WARNING **: Error occurred while existing dialogue active:
IMAP command failed: Unknown Mailbox: INBOX (Failure)
(evolution:4137): evolution-mail-WARNING **: Error occurred while existing dialogue active:
IMAP command failed: Unknown Mailbox: INBOX (Failure)
warning: .dynamic section for "/usr/lib/libX11.so.6" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------

Comment 1 Philip Withnall 2008-06-20 16:31:56 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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