Bug 393023 – crash in Text Editor: Nothing particular. Mayb...

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 393023 - crash in Text Editor: Nothing particular. Mayb...


Summary:	crash in Text Editor: Nothing particular. Mayb...


Status:	RESOLVED DUPLICATE of bug 373476

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:

Depends on:
Blocks:

Reported:	2007-01-05 05:53 UTC by John Pye
Modified:	2007-01-05 17:11 UTC

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

Description John Pye 2007-01-05 05:53:41 UTC

Version: 2.16.1

What were you doing when the application crashed?
Nothing particular. Maybe typing alt-F-S, or maybe switching tabs. Sorry if it's a dupe.


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

Memory status: size: 103481344 vsize: 0 resident: 103481344 share: 0 rss: 31944704 rss_rlim: 0
CPU usage: start_time: 1167956809 rtime: 0 utime: 10980 stime: 0 cutime:10672 cstime: 0 timeout: 308 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".
[Thread debugging using libthread_db enabled]
[New Thread -1226819920 (LWP 16641)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 99520

Thread 1 (Thread -1226819920 (LWP 16641))

#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 collect
at ../Modules/gcmodule.c line 710
#24 PyGC_Collect
at ../Modules/gcmodule.c line 1196
#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 Bruno Boaventura 2007-01-05 17:11:38 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 373476 ***