Bug 394186 – crash in Text Editor: using it

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 394186 - crash in Text Editor: using it


Summary:	crash in Text Editor: using it


Status:	RESOLVED DUPLICATE of bug 364329

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-08 10:29 UTC by kelsey.payne
Modified:	2007-01-08 14:16 UTC

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

Description kelsey.payne 2007-01-08 10:29:06 UTC

Version: 2.16.1

What were you doing when the application crashed?
using it


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

Memory status: size: 66113536 vsize: 0 resident: 66113536 share: 0 rss: 27717632 rss_rlim: 0
CPU usage: start_time: 1168251447 rtime: 0 utime: 1403 stime: 0 cutime:1327 cstime: 0 timeout: 76 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 -1226971472 (LWP 8229)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 100395

Thread 1 (Thread -1226971472 (LWP 8229))

#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_char_segment_new
from /usr/lib/libgtk-x11-2.0.so.0
#11 _gtk_char_segment_new
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_text_line_segment_split
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_text_mark_set_visible
from /usr/lib/libgtk-x11-2.0.so.0
#14 _gtk_text_btree_select_range
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_text_buffer_select_range
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_source_view_get_show_line_numbers
from /usr/lib/libgtksourceview-1.0.so.0
#19 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#25 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#28 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#29 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#30 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#31 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#32 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#33 main
#0 __kernel_vsyscall

Comment 1 Susana 2007-01-08 14:16:10 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 364329 ***