Bug 399646 – crash in Text Editor: closing textedit while o...

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 399646 - crash in Text Editor: closing textedit while o...


Summary:	crash in Text Editor: closing textedit while o...


Status:	RESOLVED DUPLICATE of bug 363172

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:

Duplicates:	407193 (view as bug list)
Depends on:
Blocks:

Reported:	2007-01-23 03:28 UTC by ropers
Modified:	2007-03-24 11:10 UTC

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

Description ropers 2007-01-23 03:28:49 UTC

Version: 2.16.1

What were you doing when the application crashed?
closing textedit while opening internet explorer (IEs4Linux) -- cf. tatanka.com.br/ies4linux/


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

Memory status: size: 82198528 vsize: 0 resident: 82198528 share: 0 rss: 24252416 rss_rlim: 0
CPU usage: start_time: 1169502364 rtime: 0 utime: 23455 stime: 0 cutime:22465 cstime: 0 timeout: 990 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227134784 (LWP 21360)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 104467

Thread 1 (Thread -1227134784 (LWP 21360))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 _gtk_text_btree_tag
from /usr/lib/libgtk-x11-2.0.so.0
#11 _gtk_text_btree_notify_will_remove_tag
from /usr/lib/libgtk-x11-2.0.so.0
#12 _gtk_text_buffer_notify_will_remove_tag
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_text_tag_new
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_text_tag_new
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#16 gtk_text_tag_table_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#17 _gtk_text_tag_table_remove_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_text_buffer_cut_clipboard
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_source_buffer_new_with_language
from /usr/lib/libgtksourceview-1.0.so.0
#20 gedit_document_new
#21 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#22 init_gobject
from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
#23 initgc
from /usr/lib/libpython2.4.so.1.0
#24 PyGC_Collect
from /usr/lib/libpython2.4.so.1.0
#25 gedit_text_region_intersect
#26 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#28 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#29 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#30 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#31 main
#0 __kernel_vsyscall

Comment 1 Mariano Suárez-Alvarez 2007-01-23 09:24:16 UTC

This is a dup of bug 373476, which got closed INCOMPLETE, so I'll not dup it to keep it alive.

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 palfrey 2007-02-21 17:47:23 UTC

*** Bug 407193 has been marked as a duplicate of this bug. ***

Comment 3 Paolo Maggi 2007-03-24 11:10:29 UTC


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