Bug 373476 – crash in Text Editor: cerraba el editor que te...

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 373476 - crash in Text Editor: cerraba el editor que te...


Summary:	crash in Text Editor: cerraba el editor que te...


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:	376489 393023 400811 (view as bug list)
Depends on:
Blocks:

Reported:	2006-11-10 18:05 UTC by lo.crick
Modified:	2007-03-24 11:11 UTC

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

Description lo.crick 2006-11-10 18:05:00 UTC

Version: 2.16.1

What were you doing when the application crashed?
cerraba el editor que tenía 3 documentos abiertos.


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

Memory status: size: 78041088 vsize: 0 resident: 78041088 share: 0 rss: 29593600 rss_rlim: 0
CPU usage: start_time: 1163176374 rtime: 0 utime: 7489 stime: 0 cutime:7273 cstime: 0 timeout: 216 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 -1227581248 (LWP 5639)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 85121

Thread 1 (Thread -1227581248 (LWP 5639))

#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_python_shutdown
#26 gedit_plugins_engine_shutdown
#27 main
#0 __kernel_vsyscall

Comment 1 Paolo Maggi 2006-11-11 10:45:56 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 André Klapper 2006-11-17 23:02:41 UTC

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

Comment 3 Paolo Maggi 2006-12-07 17:55:16 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 4 Bruno Boaventura 2007-01-05 17:11:38 UTC

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

Comment 5 Bruno Boaventura 2007-01-25 23:27:42 UTC

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

Comment 6 Paolo Maggi 2007-03-24 11:11:18 UTC

This is a duplicate of bug #363172

Comment 7 Paolo Maggi 2007-03-24 11:11:34 UTC


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