GNOME Bugzilla – Bug 593707
crash in Evolution: Opening email
Last modified: 2009-08-31 19:56:16 UTC
What were you doing when the application crashed? Opening email Distribution: SUSE Linux Enterprise Desktop 11 (x86_64) Gnome Release: 2.24.1 2009-06-27 (SUSE) BugBuddy Version: 2.24.1 System: Linux 2.6.27.29-0.1-default #1 SMP 2009-08-15 17:53:59 +0200 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: Gilouche Memory status: size: 646086656 vsize: 646086656 resident: 38744064 share: 23621632 rss: 38744064 rss_rlim: 18446744073709551615 CPU usage: start_time: 1251744172 rtime: 214 utime: 178 stime: 36 cutime:8 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0x7f3b5c787950 (LWP 4157)] [New Thread 0x7f3b4e584950 (LWP 4136)] [New Thread 0x7f3b512ff950 (LWP 4135)] [New Thread 0x7f3b59b36950 (LWP 4107)] [New Thread 0x7f3b5a36c950 (LWP 4106)] [New Thread 0x7f3b5bf86950 (LWP 4098)] [New Thread 0x7f3b5cf88950 (LWP 4095)] 0x00007f3b710fd5af in waitpid () from /lib64/libpthread.so.0
+ Trace 217251
Thread 2 (Thread 0x7f3b5c787950 (LWP 4157))
----------- .xsession-errors (488 sec old) --------------------- Initializing nautilus-open-terminal extension ** (nautilus:3569): WARNING **: Unable to add monitor: Not supported Nautilus-Share-Message: REFRESHING SHARES Nautilus-Share-Message: ------------------------------------------ Nautilus-Share-Message: spawn arg "net" Nautilus-Share-Message: spawn arg "usershare" 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 --------------------------------------------------
This has been fixed in more recent versions. *** This bug has been marked as a duplicate of bug 569700 ***