Bug 361323 – crash in Text Editor: Saving a file using 'Sav...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 361323 - crash in Text Editor: Saving a file using 'Sav...


Summary:	crash in Text Editor: Saving a file using 'Sav...


Status:	RESOLVED DUPLICATE of bug 350988

Product:	gedit
Classification:	Applications
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Duplicates:	426396 427333 427425 (view as bug list)
Depends on:
Blocks:

Reported:	2006-10-11 02:44 UTC by Jeff Greene
Modified:	2007-04-08 11:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Attachments
Save As Bug (40.07 KB, image/png) 2006-10-11 02:49 UTC, Jeff Greene	Details

Description Jeff Greene 2006-10-11 02:44:39 UTC

Version: 2.16.1

What were you doing when the application crashed?
Saving a file using 'Save As'.
To replicate:
1. Open up Firefox, gedit, or anything which can open the 'Save As' window.
2. Click 'File' and have your mouse hover over the menu.
3. Hit the underlined letter in 'Save As' which should open the dialog.
4. IMMEDIATELY after doing step 3, press Enter.

The problem is that the dialog has not selected the default directory to save the file in, so it tries to save the file before a directory was specified.

Here is the error that the terminal gives me:
Gtk-ERROR **: file gtkfilechooserdefault.c: line 7772 (gtk_file_chooser_default_should_respond): assertion failed: (path != NULL)
aborting...
Aborted (core dumped)



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 80097280 vsize: 0 resident: 80097280 share: 0 rss: 23363584 rss_rlim: 0
CPU usage: start_time: 1160534284 rtime: 0 utime: 101 stime: 0 cutime:94 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gedit'

(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 -1226955088 (LWP 19086)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75727

Thread 1 (Thread -1226955088 (LWP 19086))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 _gtk_file_chooser_default_new
from /usr/lib/libgtk-x11-2.0.so.0
#11 _gtk_file_chooser_embed_should_respond
from /usr/lib/libgtk-x11-2.0.so.0
#12 _gtk_file_chooser_embed_set_delegate
from /usr/lib/libgtk-x11-2.0.so.0
#13 _gtk_file_chooser_embed_should_respond
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_file_chooser_dialog_new
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#30 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#31 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#32 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#35 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#36 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#37 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#38 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#39 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#40 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#41 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#42 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#43 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#44 main
#0 __kernel_vsyscall

Comment 1 Jeff Greene 2006-10-11 02:49:30 UTC

Created attachment 74453 [details]
Save As Bug

This is what the dialog box appears like before it has selected a directory. In the few milliseconds that it is in this state, the program is vulnerable to crash if enter is pressed.

Comment 2 Karsten Bräckelmann 2006-10-11 02:50:46 UTC

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.


Matches the stacktrace in bug 351666, which has been marked as a duplicate of bug 350988.

Comment 3 Karsten Bräckelmann 2006-10-11 02:51:20 UTC


*** This bug has been marked as a duplicate of 350988 ***

Comment 4 Karsten Bräckelmann 2006-10-11 02:53:54 UTC

Thanks, Jeff. Your love to details is much appreciated. :-)

Comment 5 palfrey 2007-04-05 16:05:09 UTC

*** Bug 426396 has been marked as a duplicate of this bug. ***

Comment 6 palfrey 2007-04-07 21:22:33 UTC

*** Bug 427333 has been marked as a duplicate of this bug. ***

Comment 7 palfrey 2007-04-08 11:54:01 UTC

*** Bug 427425 has been marked as a duplicate of this bug. ***