Bug 368768 – crash in Text Editor: X-win32 8.o on windows x...

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 368768 - crash in Text Editor: X-win32 8.o on windows x...


Summary:	crash in Text Editor: X-win32 8.o on windows x...


Status:	RESOLVED DUPLICATE of bug 344826

Product:	gedit
Classification:	Applications
Component:	general
Version:	2.15.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-01 09:21 UTC by royweiluo
Modified:	2006-11-03 14:06 UTC

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

Description royweiluo 2006-11-01 09:21:24 UTC

Version: 2.15.9

What were you doing when the application crashed?
X-win32 8.o on windows xp sp2 english version

use mouse scorll bar


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 109047808 vsize: 0 resident: 109047808 share: 0 rss: 27828224 rss_rlim: 0
CPU usage: start_time: 1162370896 rtime: 0 utime: 893 stime: 0 cutime:805 cstime: 0 timeout: 88 it_real_value: 0 frequency: 0

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 -1209100592 (LWP 6141)]
(no debugging symbols found)
0x00b06402 in __kernel_vsyscall ()

+ Trace 81349

Thread 1 (Thread -1209100592 (LWP 6141))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/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/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_source_view_get_show_line_numbers
from /usr/lib/libgtksourceview-1.0.so.0
#13 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /lib/libgobject-2.0.so.0
#16 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#18 g_signal_emit
from /lib/libgobject-2.0.so.0
#19 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#22 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#23 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#24 g_main_context_check
from /lib/libglib-2.0.so.0
#25 g_main_loop_run
from /lib/libglib-2.0.so.0
#26 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 main
#0 __kernel_vsyscall

Comment 1 Paolo Maggi 2006-11-01 09:48:51 UTC

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 Karsten Bräckelmann 2006-11-03 14:06:08 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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