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 551801 - crash in Panel: evolution --force-shutdo...
crash in Panel: evolution --force-shutdo...
Status: RESOLVED DUPLICATE of bug 378854
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-11 11:23 UTC by bugzilla
Modified: 2008-09-11 15:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description bugzilla 2008-09-11 11:23:48 UTC
Version: 2.20.3

What were you doing when the application crashed?
evolution --force-shutdown


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.20.3 2008-07-20 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.25-gentoo-r5 #5 PREEMPT Mon Jul 7 22:49:20 BST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Smooth-Tangerine-Dream
Icon Theme: nuvola

Memory status: size: 176345088 vsize: 176345088 resident: 33591296 share: 14770176 rss: 33591296 rss_rlim: 4294967295
CPU usage: start_time: 1220051679 rtime: 54274 utime: 50813 stime: 3461 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

Really redefine built-in command "frame"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "thread"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "start"? (y or n) [answered Y; input not from terminal]
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ce88d0 (LWP 7226)]
[New Thread 0xb26fab90 (LWP 10257)]
_______________________________________________________________________________
     eax:FFFFFE00 ebx:00002942  ecx:098C2AFC  edx:00000000     eflags:00000293
     esi:098C2AFC edi:00000000  esp:098C2A14  ebp:098C2B18     eip:FFFFE424
     cs:0073  ds:007B  es:007B  fs:0000  gs:0033  ss:007B    o d I t S z A p C 
[007B:098C2A14]---------------------------------------------------------[stack]
098C2A44 : 00 00 00 00  00 00 00 00 - 00 00 00 00  00 00 00 00 ................
098C2A34 : FC 2A 8C 09  00 00 00 00 - 00 00 00 00  00 00 00 00 .*..............
098C2A24 : F4 7F 10 B7  00 00 00 00 - 65 78 0A B7  42 29 00 00 ........ex..B)..
098C2A14 : 18 2B 8C 09  00 00 00 00 - FC 2A 8C 09  AB FF 1C B7 .+.......*......
[007B:098C2AFC]---------------------------------------------------------[ data]
098C2AFC : 80 06 04 B7  42 29 00 00 - FF FF FF FF  FF FF FF FF ....B)..........
098C2B0C : F4 7F 10 B7  00 00 00 00 - 98 2B 8C 09  68 2B 8C 09 .........+..h+..
[0073:FFFFE424]---------------------------------------------------------[ code]
0xffffe424 <__kernel_vsyscall+16>:	pop    %ebp
0xffffe425 <__kernel_vsyscall+17>:	pop    %edx
0xffffe426 <__kernel_vsyscall+18>:	pop    %ecx
0xffffe427 <__kernel_vsyscall+19>:	ret    
0xffffe428:	add    %ch,(%esi)
0xffffe42a:	jae    0xffffe494
------------------------------------------------------------------------------
0xffffe424 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 <signal handler called>
  • #9 IA__g_slist_remove
    at gslist.c line 321
  • #10 backend_died_cb
    at calendar-sources.c line 432
  • #11 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #12 IA__g_closure_invoke
    at gclosure.c line 490
  • #13 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #14 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #15 IA__g_signal_emit
    at gsignal.c line 2243
  • #16 backend_died_cb
    at e-cal.c line 428
  • #17 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #18 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #21 IA__g_signal_emit
    at gsignal.c line 2243
  • #22 connection_listen_cb
    at e-component-listener.c line 50
  • #23 link_connection_emit_broken
    at linc-connection.c line 142
  • #24 link_connection_broken_idle
    at linc-connection.c line 163
  • #25 g_idle_dispatch
    at gmain.c line 4087
  • #26 IA__g_main_context_dispatch
    at gmain.c line 2009
  • #27 g_main_context_iterate
    at gmain.c line 2642
  • #28 IA__g_main_loop_run
    at gmain.c line 2850
  • #29 IA__gtk_main
    at gtkmain.c line 1163
  • #30 main
    at main.c line 95


----------- .xsession-errors (313177 sec old) ---------------------
(evolution:9832): Bonobo-CRITICAL **: impl_set_prop: assertion `value != NULL' failed
(evolution:9832): Gtk-CRITICAL **: gtk_icon_info_free: assertion `icon_info != NULL' failed
(evolution:9832): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion `icon_info != NULL' failed
(evolution:9832): Bonobo-CRITICAL **: impl_set_prop: assertion `value != NULL' failed
(evolution:9832): Gtk-CRITICAL **: gtk_icon_info_free: assertion `icon_info != NULL' failed
(evolution:9832): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion `icon_info != NULL' failed
(evolution:9832): Bonobo-CRITICAL **: impl_set_prop: assertion `value != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Philip Withnall 2008-09-11 15:58:57 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 ***