Bug 419704 – crash in Text Editor: closing gedit

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 419704 - crash in Text Editor: closing gedit


Summary:	crash in Text Editor: closing gedit


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:	2007-03-18 12:36 UTC by Barry
Modified:	2007-04-09 00:10 UTC

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

Description Barry 2007-03-18 12:36:48 UTC

Version: 2.16.1

What were you doing when the application crashed?
closing gedit


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

Memory status: size: 72192000 vsize: 0 resident: 72192000 share: 0 rss: 21782528 rss_rlim: 0
CPU usage: start_time: 1174221368 rtime: 0 utime: 78 stime: 0 cutime:71 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 -1226921792 (LWP 10642)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 119694

Thread 1 (Thread -1226921792 (LWP 10642))

#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 PyType_IsSubtype
from /usr/lib/libpython2.4.so.1.0
#5 PyDict_Next
from /usr/lib/libpython2.4.so.1.0
#6 PyDict_Next
from /usr/lib/libpython2.4.so.1.0
#7 initgc
from /usr/lib/libpython2.4.so.1.0
#8 PyGC_Collect
from /usr/lib/libpython2.4.so.1.0
#9 gedit_python_garbage_collect
#10 gedit_plugins_engine_garbage_collect
#11 _gedit_window_move_tab_to_new_window
#12 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#13 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#18 _gedit_window_move_tab_to_new_window
#19 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#24 gedit_module_get_path
#25 gtk_notebook_popup_enable
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#27 gedit_notebook_remove_all_tabs
#28 gedit_window_close_all_tabs
#29 gedit_app_get_default
#30 _gedit_app_restore_window
#31 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-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_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#38 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#39 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#40 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#41 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#42 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#43 main
#0 __kernel_vsyscall

Comment 1 Pedro Villavicencio 2007-04-09 00:10:49 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?


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