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 646725 - crash in Evolution: Try to start evolution.
crash in Evolution: Try to start evolution.
Status: RESOLVED DUPLICATE of bug 645105
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.32.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-04-04 16:43 UTC by ralf.bubeck
Modified: 2011-04-04 18:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description ralf.bubeck 2011-04-04 16:43:34 UTC
What were you doing when the application crashed?
Try to start evolution.


Distribution: Debian wheezy/sid
Gnome Release: 2.30.2 2010-11-12 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Darklooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 451805184 vsize: 451805184 resident: 22859776 share: 15822848 rss: 22859776 rss_rlim: 18446744073709551615
CPU usage: start_time: 1301935257 rtime: 38 utime: 30 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0x7f552ffe4700 (LWP 8107)]
0x00007f5548657b4d in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7f554932b980 (LWP 8104))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    at /tmp/buildd/glib2.0-2.28.2/./glib/gspawn.c line 392
  • #2 g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.28.2/./glib/gspawn.c line 706
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 segv_redirect
    at main.c line 283
  • #5 <signal handler called>
  • #6 g_object_ref
    at /tmp/buildd/glib2.0-2.28.2/./gobject/gobject.c line 2636
  • #7 ??
    from /usr/lib/evolution/2.32/plugins/liborg-freedesktop-Tracker-evolution-plugin.so
  • #8 g_type_create_instance
    at /tmp/buildd/glib2.0-2.28.2/./gobject/gtype.c line 1889
  • #9 g_object_constructor
    at /tmp/buildd/glib2.0-2.28.2/./gobject/gobject.c line 1615
  • #10 g_object_newv
    at /tmp/buildd/glib2.0-2.28.2/./gobject/gobject.c line 1479
  • #11 g_object_new_valist
    at /tmp/buildd/glib2.0-2.28.2/./gobject/gobject.c line 1596
  • #12 g_object_new
    at /tmp/buildd/glib2.0-2.28.2/./gobject/gobject.c line 1311
  • #13 ??
    from /usr/lib/evolution/2.32/plugins/liborg-freedesktop-Tracker-evolution-plugin.so
  • #14 e_plugin_lib_enable
    from /usr/lib/evolution/2.32/plugins/liborg-freedesktop-Tracker-evolution-plugin.so
  • #15 plugin_lib_loadmodule
    at e-plugin-lib.c line 70
  • #16 plugin_lib_construct
    at e-plugin-lib.c line 154
  • #17 ep_load_plugin
    at e-plugin.c line 367
  • #18 ep_load
    at e-plugin.c line 413
  • #19 e_plugin_load_plugins
    at e-plugin.c line 564
  • #20 main
    at main.c line 662

	Inferior 1 [process 8104] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
Loaded configuration: 
ask_confirmation = False
show_notification = True
preset = paste.debian.net
open_browser = False
** (gnome-screensaver:3967): WARNING **: Config key not handled: /desktop/gnome/lockdown/disable_application_handlers
** (gnome-screensaver:3967): WARNING **: Config key not handled: /desktop/gnome/lockdown/disable_command_line
** (gnome-screensaver:3967): WARNING **: Config key not handled: /desktop/gnome/lockdown/disable_printing
** (gnome-screensaver:3967): WARNING **: Config key not handled: /desktop/gnome/lockdown/disable_print_setup
** (gnome-screensaver:3967): WARNING **: Config key not handled: /desktop/gnome/lockdown/disable_save_to_disk
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2011-04-04 18:04:01 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 bug 645105 ***