Bug 361843 – crash in Text Editor: when i edit a read only ...

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 361843 - crash in Text Editor: when i edit a read only ...


Summary:	crash in Text Editor: when i edit a read only ...


Status:	RESOLVED DUPLICATE of bug 354347

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:	2006-10-13 01:47 UTC by alang.yl
Modified:	2006-10-13 01:51 UTC

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

Description alang.yl 2006-10-13 01:47:45 UTC

Version: 2.16.1

What were you doing when the application crashed?
when i edit a read only file and modify it ,i close the gedit,and chose "Don't save and close!" button.Then ,crashed!


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

Memory status: size: 66543616 vsize: 0 resident: 66543616 share: 0 rss: 23584768 rss_rlim: 0
CPU usage: start_time: 1160703891 rtime: 0 utime: 159 stime: 0 cutime:151 cstime: 0 timeout: 8 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 -1227183936 (LWP 18261)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 76078

Thread 1 (Thread -1227183936 (LWP 18261))

#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 Py_Main
from /usr/lib/libpython2.4.so.1.0
#5 PyDict_Next
from /usr/lib/libpython2.4.so.1.0
#6 initgc
from /usr/lib/libpython2.4.so.1.0
#7 PyGC_Collect
from /usr/lib/libpython2.4.so.1.0
#8 gedit_python_garbage_collect
#9 gedit_plugins_engine_garbage_collect
#10 _gedit_window_move_tab_to_new_window
#11 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#12 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#14 gedit_app_get_default
#15 _gedit_app_restore_window
#16 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#23 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#24 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 main
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-13 01:51:11 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.

Also, the maintainers need more information to fix the bug. Could you please answer the questions in the other report?


Matches bug 354683, which has been marked as a duplicate of 354347.

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