Bug 530493 – crash in Panel: I was calling 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 530493 - crash in Panel: I was calling evolution ...


Summary:	crash in Panel: I was calling evolution ...


Status:	RESOLVED DUPLICATE of bug 378854

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-04-29 05:51 UTC by bugreports
Modified:	2008-04-29 06:37 UTC

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

Description bugreports 2008-04-29 05:51:49 UTC

Version: 2.22.1.3

What were you doing when the application crashed?
I was calling evolution --force-shutdown.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-sonne #9 SMP PREEMPT Thu Apr 17 17:27:03 CEST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 86769664 vsize: 86769664 resident: 28999680 share: 14962688 rss: 28999680 rss_rlim: 4294967295
CPU usage: start_time: 1209310371 rtime: 41949 utime: 39054 stime: 2895 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6e27720 (LWP 26623)]
[New Thread 0xb60f1b90 (LWP 15856)]
0xb7fa2424 in __kernel_vsyscall ()

+ Trace 196407

Thread 1 (Thread 0xb6e27720 (LWP 26623))

#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 connection_listen_cb
at e-component-listener.c line 53
#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 ??
#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 /build/buildd/glib2.0-2.16.3/glib/gmain.c line 4087
#0 __kernel_vsyscall

Comment 1 Philip Withnall 2008-04-29 06:08:25 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 ***

Comment 2 bugreports 2008-04-29 06:13:29 UTC

are you sure this is a duplicate? because I am using gnome (and panel) version 2.22

Comment 3 Philip Withnall 2008-04-29 06:28:59 UTC

Are you running version 2.22.1 of gnome-panel, or just version 2.22.0?

Comment 4 bugreports 2008-04-29 06:31:37 UTC

2.22.0 - you sound like it was fixed in .1 - so I will install the new version when I get hold of it.

Comment 5 Philip Withnall 2008-04-29 06:37:19 UTC

From comments in the other bug report I believe it was fixed in 2.22.1, yes. Please re-open this bug report if you continue to have the problem in 2.22.1.

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