Bug 377402 – crash in Text Editor: browsing undo/redo actio...

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 377402 - crash in Text Editor: browsing undo/redo actio...


Summary:	crash in Text Editor: browsing undo/redo actio...


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:

Depends on:
Blocks:

Reported:	2006-11-20 14:39 UTC by Peter.Dedecker
Modified:	2006-11-20 21:56 UTC

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

Description Peter.Dedecker 2006-11-20 14:39:53 UTC

Version: 2.16.1

What were you doing when the application crashed?
browsing undo/redo actions


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

Memory status: size: 77090816 vsize: 0 resident: 77090816 share: 0 rss: 28667904 rss_rlim: 0
CPU usage: start_time: 1164019797 rtime: 0 utime: 2011 stime: 0 cutime:1943 cstime: 0 timeout: 68 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 -1226766672 (LWP 11354)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 87979

Thread 1 (Thread -1226766672 (LWP 11354))

#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_buffer_cut_clipboard
from /usr/lib/libgtk-x11-2.0.so.0
#12 _gtk_marshal_VOID__OBJECT_BOXED_BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#18 _gtk_text_buffer_notify_will_remove_tag
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgtksourceview-1.0.so.0
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#0 __kernel_vsyscall

Comment 1 Susana 2006-11-20 21:56:59 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 363172 ***