Bug 417111 – crash in Text Editor: Die Anwendung war nicht ...

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 417111 - crash in Text Editor: Die Anwendung war nicht ...


Summary:	crash in Text Editor: Die Anwendung war nicht ...


Status:	RESOLVED DUPLICATE of bug 373226

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-03-11 15:22 UTC by frederikbraun
Modified:	2007-03-11 15:35 UTC

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

Description frederikbraun 2007-03-11 15:22:47 UTC

Version: 2.16.1

What were you doing when the application crashed?
Die Anwendung war nicht aktiv. Ich schloss den Terminal und bin mir relativ sicher, dass ich selbst dadurch nicht in gedit hätte zurückspringen müssen, sondern in ein andeers Programm


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

Memory status: size: 101314560 vsize: 0 resident: 101314560 share: 0 rss: 29028352 rss_rlim: 0
CPU usage: start_time: 1173625679 rtime: 0 utime: 1461 stime: 0 cutime:1352 cstime: 0 timeout: 109 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 -1226791248 (LWP 14911)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 117719

Thread 1 (Thread -1226791248 (LWP 14911))

#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 fs_module_create
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#11 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#12 fs_module_init
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#13 gnome_vfs_connect_to_server
from /usr/lib/libgnomevfs-2.so.0
#14 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 main
#0 __kernel_vsyscall

Comment 1 bugreport 2007-03-11 15:25:19 UTC

What were you doing when the application crashed?
(translated to English:)
gedit was in the background, when i closed "Terminal" and got back to another application (not gedit). then bugzille opened (and this was the moment i noticed gedit has crashed)

Comment 2 Paolo Borelli 2007-03-11 15:35:18 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 373226 ***