GNOME Bugzilla – Bug 615739
crash in Evolution:
Last modified: 2010-04-15 02:28:14 UTC
What were you doing when the application crashed? Distribution: openSUSE 11.2 (x86_64) Gnome Release: 2.28.2 (null) (SUSE) BugBuddy Version: 2.28.0 System: Linux 2.6.31.12-0.2-default #1 SMP 2010-03-16 21:25:39 +0100 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: bluebubble Icon Theme: Neu GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 522928128 vsize: 522928128 resident: 92393472 share: 13852672 rss: 92393472 rss_rlim: 18446744073709551615 CPU usage: start_time: 1271249203 rtime: 112 utime: 86 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/evolution/2.28/evolution-exchange-storage.bin' [Thread debugging using libthread_db enabled] [New Thread 0x7f45c3fff910 (LWP 6746)] [New Thread 0x7f45c17fa910 (LWP 6734)] [New Thread 0x7f45c37fe910 (LWP 6728)] [New Thread 0x7f45c881d910 (LWP 6663)] [New Thread 0x7f45db550910 (LWP 6640)] 0x00007f45d302cd03 in poll () from /lib64/libc.so.6
+ Trace 221370
Thread 4 (Thread 0x7f45c37fe910 (LWP 6728))
A debugging session is active. Inferior 1 [process 6639] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (587 sec old) --------------------- Nautilus-Share-Message: spawn arg "info" Nautilus-Share-Message: end of spawn args; SPAWNING Nautilus-Share-Message: returned from spawn: SUCCESS: Nautilus-Share-Message: exit code 255 Nautilus-Share-Message: ------------------------------------------ Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: usershares are currently disabled Launching a SCIM daemon with Socket FrontEnd... Loading simple Config module ... Creating backend ... Loading socket FrontEnd module ... Starting SCIM as daemon ... GTK Panel of SCIM 1.4.7 --------------------------------------------------
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 508447 ***