Bug 435111 – crash in Text Editor: trying to save the text ...

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 435111 - crash in Text Editor: trying to save the text ...


Summary:	crash in Text Editor: trying to save the text ...


Status:	RESOLVED DUPLICATE of bug 360280

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:

Depends on:
Blocks:

Reported:	2007-05-02 07:05 UTC by aqvarious
Modified:	2007-05-02 07:47 UTC

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

Description aqvarious 2007-05-02 07:05:09 UTC

Version: 2.16.1

What were you doing when the application crashed?
trying to save the text file


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

Memory status: size: 100843520 vsize: 0 resident: 100843520 share: 0 rss: 25489408 rss_rlim: 0
CPU usage: start_time: 1178089265 rtime: 0 utime: 1409 stime: 0 cutime:1372 cstime: 0 timeout: 37 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 -1226770768 (LWP 6651)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 131836

Thread 1 (Thread -1226770768 (LWP 6651))

#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 free
from /lib/tls/i686/cmov/libc.so.6
#5 g_free
from /usr/lib/libglib-2.0.so.0
#6 gtk_icon_info_free
from /usr/lib/libgtk-x11-2.0.so.0
#7 gedit_spinner_stop
#8 gedit_spinner_start
#9 gedit_notebook_set_always_show_tabs
#10 g_cclosure_marshal_VOID__PARAM
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 g_object_class_override_property
from /usr/lib/libgobject-2.0.so.0
#16 g_enum_register_static
from /usr/lib/libgobject-2.0.so.0
#17 g_object_notify
from /usr/lib/libgobject-2.0.so.0
#18 _gedit_tab_new
#19 _gedit_tab_save_as
#20 _gedit_cmd_file_save_documents_list
#21 g_cclosure_marshal_VOID
from /usr/lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#28 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#29 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#33 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#36 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#37 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#38 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#39 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#40 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#41 main
#0 __kernel_vsyscall

Comment 1 Paolo Borelli 2007-05-02 07:47:16 UTC

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 360280 ***