Bug 519506 – crash in Text Editor: Exiting a single text fi...

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 519506 - crash in Text Editor: Exiting a single text fi...


Summary:	crash in Text Editor: Exiting a single text fi...


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:	2008-02-29 13:15 UTC by rhm31
Modified:	2008-02-29 13:17 UTC

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

Description rhm31 2008-02-29 13:15:29 UTC

Version: 2.18.2

What were you doing when the application crashed?
Exiting a single text file



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

System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 16:52:18 EST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 444227584 vsize: 444227584 resident: 29470720 share: 19566592 rss: 29470720 rss_rlim: 18446744073709551615
CPU usage: start_time: 1204290859 rtime: 106 utime: 97 stime: 9 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496345872 (LWP 3913)]
(no debugging symbols found)
0x000000352140d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 190842

Thread 1 (Thread 46912496345872 (LWP 3913))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_free
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_type_check_instance_is_a
from /lib64/libgobject-2.0.so.0
#4 gnome_print_config_unref
from /usr/lib64/libgnomeprint-2-2.so.0
#5 g_datalist_clear
from /lib64/libglib-2.0.so.0
#6 ??
#7 g_object_unref
from /lib64/libgobject-2.0.so.0
#8 gtk_text_layout_set_buffer
from /usr/lib64/libgtk-x11-2.0.so.0
#9 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#10 g_object_unref
from /lib64/libgobject-2.0.so.0
#11 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#12 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#13 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#14 g_free
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#16 g_signal_emit
from /lib64/libgobject-2.0.so.0
#17 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#18 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#19 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#20 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#21 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#22 g_free
from /lib64/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#24 g_signal_emit
from /lib64/libgobject-2.0.so.0
#25 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#26 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#27 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#28 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#29 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#30 g_free
from /lib64/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#32 g_signal_emit
from /lib64/libgobject-2.0.so.0
#33 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#34 g_object_unref
from /lib64/libgobject-2.0.so.0
#35 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#36 gedit_window_close_all_tabs
#37 ??
#38 ??
#39 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#40 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#41 g_free
from /lib64/libgobject-2.0.so.0
#42 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#43 g_signal_emit
from /lib64/libgobject-2.0.so.0
#44 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#45 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#46 g_free
from /usr/lib64/libgdk-x11-2.0.so.0
#47 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#48 g_free
from /lib64/libglib-2.0.so.0
#49 g_main_loop_run
from /lib64/libglib-2.0.so.0
#50 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#51 main
#0 waitpid
from /lib64/libpthread.so.0


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       
  - 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





----------- .xsession-errors ---------------------
CalDAV Eplugin starting up ...
/usr/libexec/evolution-alarm-notify: No such file or directory.
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff8dbfd000
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200058 (Buddy List)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Model not found, discarding config
** (gedit:3913): WARNING **: could not set the value of Settings.Document.Filter, node not found
** (gedit:3913): WARNING **: could not set the value of Settings.Document.Filter, node not found
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff937fd000
--------------------------------------------------

Comment 1 Baptiste Mille-Mathias 2008-02-29 13:17:30 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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