GNOME Bugzilla – Bug 616148
Crash in get_folder_info_offline at camel-imap-store.c line 2812
Last modified: 2010-04-19 23:41:06 UTC
What were you doing when the application crashed? Working in an RDP session to a Win7 boxl, completely unaware what was going on (why it would load Evolution) at that time Distribution: Debian squeeze/sid Gnome Release: 2.28.2 2009-12-18 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.32-3-amd64 #1 SMP Thu Feb 25 07:33:41 UTC 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10706000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 106590208 vsize: 106590208 resident: 20361216 share: 16691200 rss: 20361216 rss_rlim: 18446744073709551615 CPU usage: start_time: 1271657134 rtime: 31 utime: 28 stime: 3 cutime:0 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xf1b78b70 (LWP 14197)] [New Thread 0xf2379b70 (LWP 14196)] [New Thread 0xf2b9fb70 (LWP 14194)] [New Thread 0xf3c01b70 (LWP 14169)] [New Thread 0xf4402b70 (LWP 14168)] 0xf76f8425 in __kernel_vsyscall ()
+ Trace 221441
Thread 2 (Thread 0xf1b78b70 (LWP 14197))
Inferior 1 [process 14137] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- 'PRIMARYCLIPBOARD' looks at both PRIMARY and CLIPBOARD when sending data to server. 'CLIPBOARD' looks at only CLIPBOARD. -0: attach to console -4: use RDP version 4 -5: use RDP version 5 (default) ** (gnome-settings-daemon:14132): WARNING **: Failed to acquire org.gnome.SettingsDaemon ** (gnome-settings-daemon:14132): WARNING **: Could not acquire name evolution-shell-Message: Killing old version of evolution-data-server... (evolution:14137): camel-WARNING **: camel_exception_get_id called with NULL parameter. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of bug 587057 ***