GNOME Bugzilla – Bug 610931
Starting Evolution when off-line: Segmentation fault
Last modified: 2010-02-25 09:29:38 UTC
Evolution does not start when I am off-line. I get following error messages on the command line: ========================================= $ evolution ** (evolution:16200): WARNING **: Unexpected kerberos error -1765328164 ** (evolution:16200): WARNING **: Unexpected kerberos error -1765328164 ** (evolution:16200): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed (evolution:16200): GVFS-RemoteVolumeMonitor-WARNING **: cannot open directory /usr/share/gvfs/remote-volume-monitors: Error opening directory '/usr/share/gvfs/remote-volume-monitors': No such file or directory Segmentation fault ========================================= As I am mostly on-line, I don't know exactly when this problem started but it could be that it started after adding a Google calendar. BTW: I have Kubuntu 9.10 and I run Evolution on a KDE desktop.
warning is related to gvfs Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I have installed the debug packages for evolution, glib, and gtk+ but I did not find the debug package for gvfs. Does anybody know how this debug package is called on Ubuntu 9.10? After installing the debug packages, closing evolution, going off-line and re-starting evolution, the same error/warning messages as before are shown -- no additional information :-( If I start evolution while on-line the same error message regarding GVFS is shown but evolution works (as usual). ========================================= $ evolution ** (evolution:17435): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed (evolution:17435): GVFS-RemoteVolumeMonitor-WARNING **: cannot open directory /usr/share/gvfs/remote-volume-monitors: Error opening directory '/usr/share/gvfs/remote-volume-monitors': No such file or directory ** (evolution:17435): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [...] =========================================
If you can reproduce it while running under gdb (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details about how to do this), that might help getting a better trace
Created attachment 154661 [details] Stack trace
Thanks for the new instructions. I have attached the stack trace (see above).
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 528022 ***
I really want to be able to run evolution when I am off-line. Is there any workaround?