Bug 473957 – crash in Text Editor: Closing the application ...

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 473957 - crash in Text Editor: Closing the application ...


Summary:	crash in Text Editor: Closing the application ...


Status:	RESOLVED DUPLICATE of bug 468964

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-09-05 16:26 UTC by brian_borowski
Modified:	2007-09-05 17:57 UTC

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

Description brian_borowski 2007-09-05 16:26:11 UTC

Version: 2.18.2

What were you doing when the application crashed?
Closing the application with multiple tabs still open.


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.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: gnome

Memory status: size: 97415168 vsize: 97415168 resident: 37793792 share: 22011904 rss: 37793792 rss_rlim: 4294967295
CPU usage: start_time: 1188876889 rtime: 5142 utime: 4871 stime: 271 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 -1208224032 (LWP 12784)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 160674

Thread 1 (Thread -1208224032 (LWP 12784))

#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                 2.10.6 (GTK+ 2.10.14)
  - gnome-python          2.18.1

Comment 1 palfrey 2007-09-05 17:57:58 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

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