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 494385 - crash in Panel: I just ran 'evolution --...
crash in Panel: I just ran 'evolution --...
Status: RESOLVED DUPLICATE of bug 494811
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-07 00:15 UTC by Sam Morris
Modified: 2007-11-08 01:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Sam Morris 2007-11-07 00:15:54 UTC 
Version: 2.20.1

What were you doing when the application crashed?
I just ran 'evolution --force-shutdown'


Distribution: Debian lenny/sid
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-fixdso #1 SMP Sat Aug 25 16:14:05 BST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: gnome

Memory status: size: 87007232 vsize: 87007232 resident: 31113216 share: 9957376 rss: 31113216 rss_rlim: 4294967295
CPU usage: start_time: 1193605676 rtime: 56261 utime: 50684 stime: 5577 cutime:6 cstime: 156 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 0xb6e6f6b0 (LWP 4516)]
[New Thread 0xb6439b90 (LWP 7949)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 175900

Thread 1 (Thread 0xb6e6f6b0 (LWP 4516))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 IA__g_slist_remove
    at /tmp/buildd/glib2.0-2.14.1/glib/gslist.c line 207
  • #5 backend_died_cb
    at calendar-sources.c line 432
  • #6 IA__g_cclosure_marshal_VOID__VOID
    at /tmp/buildd/glib2.0-2.14.1/gobject/gmarshal.c line 77
  • #7 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
  • #8 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2440
  • #9 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2199
  • #10 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2243
  • #11 backend_died_cb
    at e-cal.c line 428
  • #12 IA__g_cclosure_marshal_VOID__VOID
    at /tmp/buildd/glib2.0-2.14.1/gobject/gmarshal.c line 77
  • #13 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
  • #14 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2440
  • #15 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2199
  • #16 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2243
  • #17 connection_listen_cb
    at e-component-listener.c line 50
  • #18 link_connection_emit_broken
    at linc-connection.c line 141
  • #19 link_connection_broken_idle
    at linc-connection.c line 162
  • #20 g_idle_dispatch
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 4132
  • #21 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2061
  • #22 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2694
  • #23 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2898
  • #24 IA__gtk_main
    at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkmain.c line 1146
  • #25 main
    at main.c line 95
  • #0 __kernel_vsyscall 


----------- .xsession-errors (78218 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Sam Morris 2007-11-08 01:08:28 UTC 

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