Bug 477772 – crash in Text Editor: Closing Text Editor with...

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 477772 - crash in Text Editor: Closing Text Editor with...


Summary:	crash in Text Editor: Closing Text Editor with...


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-09-17 14:00 UTC by dougdavidson
Modified:	2007-10-06 13:55 UTC

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

Description dougdavidson 2007-09-17 14:00:48 UTC

Version: 2.18.2

What were you doing when the application crashed?
Closing Text Editor without savins document.


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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 66146304 vsize: 66146304 resident: 27848704 share: 21463040 rss: 27848704 rss_rlim: 4294967295
CPU usage: start_time: 1190036956 rtime: 238 utime: 219 stime: 19 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 -1209125152 (LWP 2723)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 163547

Thread 1 (Thread -1209125152 (LWP 2723))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_type_check_instance_is_a
from /lib/libgobject-2.0.so.0
#5 gnome_print_config_unref
from /usr/lib/libgnomeprint-2-2.so.0
#6 g_datalist_clear
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libgobject-2.0.so.0
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
from /usr/lib/libgtksourceview-1.0.so.0
#10 ??
#11 g_object_unref
from /lib/libgobject-2.0.so.0
#12 gtk_text_layout_set_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_object_unref
from /lib/libgobject-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
#18 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#19 ??
from /lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /lib/libgobject-2.0.so.0
#21 ??
from /lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#23 g_signal_emit
from /lib/libgobject-2.0.so.0
#24 ??
from /usr/lib/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib/libgtk-x11-2.0.so.0
#26 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#27 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib/libgtk-x11-2.0.so.0
#34 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#35 ??
from /lib/libgobject-2.0.so.0
#36 g_closure_invoke
from /lib/libgobject-2.0.so.0
#37 ??
from /lib/libgobject-2.0.so.0
#38 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#39 g_signal_emit
from /lib/libgobject-2.0.so.0
#40 ??
from /usr/lib/libgtk-x11-2.0.so.0
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#43 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#44 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#45 ??
from /usr/lib/libgtk-x11-2.0.so.0
#46 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#47 ??
from /usr/lib/libgtk-x11-2.0.so.0
#48 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#49 ??
from /lib/libgobject-2.0.so.0
#50 g_closure_invoke
from /lib/libgobject-2.0.so.0
#51 ??
from /lib/libgobject-2.0.so.0
#52 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#53 g_signal_emit
from /lib/libgobject-2.0.so.0
#54 ??
from /usr/lib/libgtk-x11-2.0.so.0
#55 ??
from /usr/lib/libgtk-x11-2.0.so.0
#56 g_object_unref
from /lib/libgobject-2.0.so.0
#57 ??
#58 ??
from /usr/lib/libgtk-x11-2.0.so.0
#59 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#60 gedit_notebook_remove_all_tabs
#61 gedit_window_close_all_tabs
#62 ??
#63 g_cclosure_marshal_VOID
from /lib/libgobject-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 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#69 ??
from /usr/lib/libgtk-x11-2.0.so.0
#70 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#71 g_closure_invoke
from /lib/libgobject-2.0.so.0
#72 ??
from /lib/libgobject-2.0.so.0
#73 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#74 g_signal_emit
from /lib/libgobject-2.0.so.0
#75 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#76 ??
from /usr/lib/libgtk-x11-2.0.so.0
#77 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#78 ??
from /lib/libgobject-2.0.so.0
#79 g_closure_invoke
from /lib/libgobject-2.0.so.0
#80 ??
from /lib/libgobject-2.0.so.0
#81 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#82 g_signal_emit
from /lib/libgobject-2.0.so.0
#83 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#84 ??
from /usr/lib/libgtk-x11-2.0.so.0
#85 ??
from /usr/lib/libgtk-x11-2.0.so.0
#86 ??
from /lib/libgobject-2.0.so.0
#87 g_closure_invoke
from /lib/libgobject-2.0.so.0
#88 ??
from /lib/libgobject-2.0.so.0
#89 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#90 g_signal_emit
from /lib/libgobject-2.0.so.0
#91 ??
from /usr/lib/libgtk-x11-2.0.so.0
#92 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#93 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#94 ??
from /usr/lib/libgdk-x11-2.0.so.0
#95 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#96 ??
from /lib/libglib-2.0.so.0
#97 g_main_loop_run
from /lib/libglib-2.0.so.0
#98 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#99 main
#0 __kernel_vsyscall


No plugin installed in $HOME.

Module versions:
  - glib                  
  - gtk+                  
  - gtksourceview         
  - libgnomeui            
  - libglade              
  - libgnomeprintui       
  - gnome-vfs             
  - pygobject             
  - pygtk                 
  - 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





----------- .xsession-errors (39 sec old) ---------------------
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
** (gedit:2723): WARNING **: IPP request failed with status 1030
Model not found, discarding config
** (gedit:2723): WARNING **: could not set the value of Settings.Document.Filter, node not found
** (gedit:2723): WARNING **: could not set the value of Settings.Document.Filter, node not found
** (gedit:2723): WARNING **: could not set the value of Settings.Document.Filter, node not found
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
--------------------------------------------------

Comment 1 Susana 2007-10-06 13:55:15 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 ***