Bug 351094 – crash on Text Editor

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 351094 - crash on Text Editor


Summary:	crash on Text Editor


Status:	RESOLVED DUPLICATE of bug 350776

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-08-12 21:03 UTC by Andrew
Modified:	2006-08-18 17:44 UTC

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

Attachments
Full backtrace of hello, copy and exit (6.49 KB, text/plain) 2006-08-18 17:40 UTC, Andrew	Details

Description Andrew 2006-08-12 21:03:03 UTC

What were you doing when the application crashed?



Distribution: Gentoo Base System version 1.12.4
Gnome Release: 2.15.91 2006-08-09 (Gentoo)
BugBuddy Version: 2.15.90

Memory status: size: 173568000 vsize: 173568000 resident: 34095104 share: 15548416 rss: 34095104 rss_rlim: -1
CPU usage: start_time: 1155415641 rtime: 435 utime: 418 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gedit'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47627049489120 (LWP 3161)]
0x00002b5108cefed4 in waitpid () from /lib/libpthread.so.0

+ Trace 70330

Thread 1 (Thread 47627049489120 (LWP 3161))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_segv_handle
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 g_logv
from /usr/lib/libglib-2.0.so.0
#6 g_log
from /usr/lib/libglib-2.0.so.0
#7 gtk_container_get_children
from /usr/lib/libgtk-x11-2.0.so.0
#8 update_node
from /usr/lib/libgtk-x11-2.0.so.0
#9 update_node
from /usr/lib/libgtk-x11-2.0.so.0
#10 update_node
from /usr/lib/libgtk-x11-2.0.so.0
#11 do_updates
from /usr/lib/libgtk-x11-2.0.so.0
#12 do_updates_idle
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#14 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#15 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#16 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#17 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Christian Kirbach 2006-08-13 17:37:38 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Andrew 2006-08-18 15:05:02 UTC


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

Comment 3 Andrew 2006-08-18 17:40:12 UTC

Created attachment 71168 [details]
Full backtrace of hello, copy and exit

Paolo,

This works everytime for me:

1) open Gedit (default untitled document appears)
2) type "hello"
3) select "hello" and copy it to the clipboard (ctrl a, ctrl c)
4) close Gedit (close without saving, if you choose save the crash happens after the file is successfully saved before the crash occurs)

If I don't copy anything to the clipboard (miss out step 3) everything is fine. The surrounding events seem to be arbitrary, if anything has been copied to the clipboard before Gedit is closed this crash occurs.

I've attached my own backtraces (of the exact above steps) for good measure, until the original submitter can confirm this method.

Comment 4 Andrew 2006-08-18 17:44:40 UTC

Ooops, sorry I posted above comment to wrong bug, see #350776