GNOME Bugzilla – Bug 408675
crash in Evolution: I was trying to save an ...
Last modified: 2008-04-18 19:56:04 UTC
What were you doing when the application crashed? I was trying to save an attachment. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 106348544 vsize: 0 resident: 106348544 share: 0 rss: 28545024 rss_rlim: 0 CPU usage: start_time: 1171651784 rtime: 0 utime: 567 stime: 0 cutime:499 cstime: 0 timeout: 68 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233348944 (LWP 1161)] [New Thread -1286677600 (LWP 1173)] [New Thread -1278284896 (LWP 1168)] [New Thread -1259484256 (LWP 1166)] [New Thread -1251054688 (LWP 1164)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 111309
Thread 1 (Thread -1233348944 (LWP 1161))
*** Bug 413025 has been marked as a duplicate of this bug. ***
I have the same problem. When I right click the attachment in the attachment bar and choose "Save As..." the location selector is blank. If I click it and select any location, then everything is fine. If I leave it blank, but type a filename (even a full path) into the filename box, Evolution aborts with Gtk-ERROR **: file gtkfilechooserdefault.c: line 7772 (gtk_file_chooser_default_should_respond): assertion failed: (path != NULL) aborting... Aborted
I have this problem running Evolution in FC6 and KDE. The work around described by Brian works to save my mail. :) Running Evolution from the CLI, I get ---Error info--- CalDAV Eplugin starting up ... libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files (evolution:22740): Gtk-CRITICAL **: gtk_file_system_unix_get_info: assertion `g_path_is_absolute (filename)' failed Gtk-ERROR **: file gtkfilechooserdefault.c: line 8069 (gtk_file_chooser_default_should_respond): assertion failed: (path != NULL) aborting... --- End Error info --- Of course Bug Buddy, generates it's own error message and closes when I try to submit. evolution-2.8.3-2.fc6 I didn't have any problems with Gnome just before changing to KDE using the same software, only the desktop changing. I have not had any good experiences with Evolution. :(
*** Bug 466090 has been marked as a duplicate of this bug. ***
My problem was not with Evolution, but with gedit only (bug report 466090). http://bugzilla.gnome.org/show_bug.cgi?id=466090 ------- Comment #1 from Tom Parker 2007-08-13 14:20 UTC ------- 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? I don't see any questions to answer on this page, I am new to Ubuntu, and this is my first bug report, so I may be just not looking in the right place. I can't remember if the "location" field was blank or not, but I know I didn't specify one because I was trying to save the new file in the same location as the old one I was working from. gedit was working fine until I tried to save the document I was working on as a new filename. I can tell you I had several applications open including Blender, Netbeans, and SunFlow as well as a couple file browser windows open, and likely a lot of geometry data in memory. Could there be a problem with trying to create a new file in a folder while that folder open in a file browser window? I'm just thinking there might be a scheduling conflict with updating the open browser window while trying to create the file at the same time.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 350988 ***