Bug 377814 – crash in Text Editor: I tried to close the ged...

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 377814 - crash in Text Editor: I tried to close the ged...


Summary:	crash in Text Editor: I tried to close the ged...


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-11-21 16:04 UTC by peaolo1981
Modified:	2006-11-22 00:01 UTC

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

Description peaolo1981 2006-11-21 16:04:25 UTC

Version: 2.16.1

What were you doing when the application crashed?
I tried to close the gedit with two files opened: they were syslog and partman, 'cause I was already reporting another bug. An install bug.


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

Memory status: size: 169332736 vsize: 169332736 resident: 31248384 share: 15630336 rss: 31248384 rss_rlim: -1
CPU usage: start_time: 1164128397 rtime: 306 utime: 291 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47579946841520 (LWP 30328)]
(no debugging symbols found)
0x00002b460c373eb5 in waitpid () from /lib/libpthread.so.0

+ Trace 88278

Thread 1 (Thread 47579946841520 (LWP 30328))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 Py_Main
from /usr/lib64/libpython2.4.so.1.0
#4 initgc
from /usr/lib64/libpython2.4.so.1.0
#5 PyGC_Collect
from /usr/lib64/libpython2.4.so.1.0
#6 gedit_python_garbage_collect
#7 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#8 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#15 gedit_module_get_path
#16 gtk_notebook_popup_enable
from /usr/lib64/libgtk-x11-2.0.so.0
#17 gedit_window_close_all_tabs
#18 gedit_app_get_default
#19 _gedit_app_restore_window
#20 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib64/libgtk-x11-2.0.so.0
#21 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#22 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#24 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#25 gtk_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#26 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#27 _gdk_events_init
from /usr/lib64/libgdk-x11-2.0.so.0
#28 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#29 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#30 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#31 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#32 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 André Klapper 2006-11-22 00:01:20 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 ***