Description of problem: Editing and existing file, choosing Save As from the menu, typing in a file name, and hitting save leads to program termination with the error message: Gtk-ERROR **: file gtkfilechooserdefault.c: line 8174 (gtk_file_chooser_default_should_respond): assertion failed: (path != NULL) aborting... Vim: Caught deadly signal ABRT Vim: Finished. The save goes OK if a directory is specified. In any case, I think gvim should issue an error message instead of terminating, or at least have a default directory. If gvim is opened without specifying a file and Save As is used after editing the buffer there is no problem. Version-Release number of selected component (if applicable): vim-X11-7.0.109-3 How reproducible: Consistent Steps to Reproduce: 1.Start gvim from terminal to edit existing file 2.Select save as from menu and type in file name 3.Hit save Actual results: Expected results: Additional info:
This may be tangentially related, I am also seeing the message bad async reply GVIM emitted by an application that embeds gvim. It was working fine until the last yum update.
this should be fixed with any vim version later than 7.0.129: 7.0.129 GTK GUI: avoid GTK bug concerning directory for file dialog