GNOME Bugzilla – Bug 646725
crash in Evolution: Try to start evolution.
Last modified: 2011-04-04 18:04:01 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
+ Trace 226584
Thread 1 (Thread 0x7f554932b980 (LWP 8104))
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 --------------------------------------------------
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 ***