Bug 492611 – crash in Text Editor: I was trying to exit. I ...

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 492611 - crash in Text Editor: I was trying to exit. I ...


Summary:	crash in Text Editor: I was trying to exit. I ...


Status:	RESOLVED DUPLICATE of bug 443083

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-02 08:22 UTC by k-nine
Modified:	2007-12-25 11:33 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description k-nine 2007-11-02 08:22:03 UTC

Version: 2.18.2

What were you doing when the application crashed?
I was trying to exit.
I pressed 'X' button on the right top corner of the gedit window.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 100769792 vsize: 100769792 resident: 22982656 share: 19062784 rss: 22982656 rss_rlim: 4294967295
CPU usage: start_time: 1193970807 rtime: 537 utime: 479 stime: 58 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 -1208584480 (LWP 8972)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 174544

Thread 1 (Thread -1208584480 (LWP 8972))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gnome_print_config_unref
from /usr/lib/libgnomeprint-2-2.so.0
#5 g_datalist_clear
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libgobject-2.0.so.0
#7 ??
from /usr/lib/libgtk-x11-2.0.so.0
#8 ??
from /usr/lib/libgtksourceview-1.0.so.0
#9 ??
#10 g_object_unref
from /lib/libgobject-2.0.so.0
#11 gtk_text_layout_set_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_object_unref
from /lib/libgobject-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
#17 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#18 ??
from /lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /lib/libgobject-2.0.so.0
#20 ??
from /lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#22 g_signal_emit
from /lib/libgobject-2.0.so.0
#23 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib/libgtk-x11-2.0.so.0
#25 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#26 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#34 ??
from /lib/libgobject-2.0.so.0
#35 g_closure_invoke
from /lib/libgobject-2.0.so.0
#36 ??
from /lib/libgobject-2.0.so.0
#37 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#38 g_signal_emit
from /lib/libgobject-2.0.so.0
#39 ??
from /usr/lib/libgtk-x11-2.0.so.0
#40 ??
from /usr/lib/libgtk-x11-2.0.so.0
#41 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#42 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#43 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#44 ??
from /usr/lib/libgtk-x11-2.0.so.0
#45 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#46 ??
from /usr/lib/libgtk-x11-2.0.so.0
#47 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#48 ??
from /lib/libgobject-2.0.so.0
#49 g_closure_invoke
from /lib/libgobject-2.0.so.0
#50 ??
from /lib/libgobject-2.0.so.0
#51 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#52 g_signal_emit
from /lib/libgobject-2.0.so.0
#53 ??
from /usr/lib/libgtk-x11-2.0.so.0
#54 ??
from /usr/lib/libgtk-x11-2.0.so.0
#55 g_object_unref
from /lib/libgobject-2.0.so.0
#56 ??
#57 ??
from /usr/lib/libgtk-x11-2.0.so.0
#58 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#59 gedit_notebook_remove_all_tabs
#60 gedit_window_close_all_tabs
#61 ??
#62 ??
#63 ??
from /usr/lib/libgtk-x11-2.0.so.0
#64 g_closure_invoke
from /lib/libgobject-2.0.so.0
#65 ??
from /lib/libgobject-2.0.so.0
#66 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#67 g_signal_emit
from /lib/libgobject-2.0.so.0
#68 ??
from /usr/lib/libgtk-x11-2.0.so.0
#69 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#70 ??
from /usr/lib/libgdk-x11-2.0.so.0
#71 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#72 ??
from /lib/libglib-2.0.so.0
#73 g_main_loop_run
from /lib/libglib-2.0.so.0
#74 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#75 main
#0 __kernel_vsyscall


No plugin installed in $HOME.

Module versions:
  - glib                  2.12.13
  - gtk+                  2.10.14
  - gtksourceview         
  - libgnomeui            2.18.1
  - libglade              2.6.0
  - libgnomeprintui       2.18.0
  - gnome-vfs             2.18.1
  - pygobject             2.12.3
  - pygtk                 2.10.6
  - gnome-python          
  - gnome-python-desktop  2.18.0
  - enchant               
  - iso-codes             

Python module versions:
  - python                2.5
  - pygtk                 site.py, Pzm failed

  - gnome-python          site.py, Pzm failed

Comment 1 Teppo Turtiainen 2007-12-25 11:33:40 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 443083 ***