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 539037 - crash in Clock: evolution --force-shutdo...
crash in Clock: evolution --force-shutdo...
Status: RESOLVED DUPLICATE of bug 378854
Product: gnome-panel
Classification: Other
Component: clock
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-18 21:53 UTC by Russell Harrison
Modified: 2008-06-18 22:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Russell Harrison 2008-06-18 21:53:09 UTC
Version: 2.20.3

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


Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.3 2008-01-08 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.25.4-10.fc8 #1 SMP Thu May 22 23:34:09 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 94736384 vsize: 94736384 resident: 16277504 share: 11243520 rss: 16277504 rss_rlim: 4294967295
CPU usage: start_time: 1213750915 rtime: 214 utime: 194 stime: 20 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/clock-applet'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209116912 (LWP 4872)]
[New Thread -1213338736 (LWP 13377)]
0x00110416 in __kernel_vsyscall ()

Thread 1 (Thread -1209116912 (LWP 4872))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 g_slist_remove
    from /lib/libglib-2.0.so.0
  • #10 backend_died_cb
    at calendar-sources.c line 432
  • #11 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #16 backend_died_cb
    at e-cal.c line 428
  • #17 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #22 connection_listen_cb
    at e-component-listener.c line 50
  • #23 ??
    from /usr/lib/libORBit-2.so.0
  • #24 ??
    from /usr/lib/libORBit-2.so.0
  • #25 ??
    from /lib/libglib-2.0.so.0
  • #26 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #27 ??
    from /lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #29 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #30 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #31 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #32 panel_applet_factory_main_closure
    at panel-applet.c line 1754
  • #33 panel_applet_factory_main
    at panel-applet.c line 1778
  • #34 main
    at clock.c line 2279
  • #35 __libc_start_main
    from /lib/libc.so.6
  • #36 _start
  • #0 __kernel_vsyscall


----------- .xsession-errors (74752 sec old) ---------------------
(Do:4586): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init?
(Do:4586): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(Do:4586): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init?
(Do:4586): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(Do:4586): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init?
(Do:4586): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(Do:4586): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init?
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Gianluca Borello 2008-06-18 22:21:43 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 ***