Bug 406608 – crash in Text Editor: Clicked on Applications ...

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 406608 - crash in Text Editor: Clicked on Applications ...


Summary:	crash in Text Editor: Clicked on Applications ...


Status:	RESOLVED DUPLICATE of bug 364113

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-02-11 05:30 UTC by jay.bermal
Modified:	2007-03-04 14:57 UTC

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

Description jay.bermal 2007-02-11 05:30:47 UTC

Version: 2.16.1

What were you doing when the application crashed?
Clicked on Applications -> Accessories -> Text Editor
In the Text Editor Window, clicked on Open File -> Cancel
Crash

Other Application that are open:
xchat
firefox
rhythmbox music player (streaming music off the net)
azureus (which seems to crash every so often; big downloads never seem to get completed)



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

Memory status: size: 81580032 vsize: 0 resident: 81580032 share: 0 rss: 22872064 rss_rlim: 0
CPU usage: start_time: 1171128188 rtime: 0 utime: 204 stime: 0 cutime:190 cstime: 0 timeout: 14 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 -1227372880 (LWP 9642)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 109710

Thread 1 (Thread -1227372880 (LWP 9642))

#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 strlen
from /lib/tls/i686/cmov/libc.so.6
#5 g_string_insert_len
from /usr/lib/libglib-2.0.so.0
#6 g_string_append
from /usr/lib/libglib-2.0.so.0
#7 gnome_vfs_uri_to_string
from /usr/lib/libgnomevfs-2.so.0
#8 fs_module_init
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#9 fs_module_create
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#10 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
from /usr/lib/libglib-2.0.so.0
#17 ??
#18 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#19 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 main
#0 __kernel_vsyscall

Comment 1 palfrey 2007-02-21 14:56:58 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 Rob Bradford 2007-03-04 14:57:41 UTC



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