Bug 390719 – crash in Text Editor: datei abgespeichert

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 390719 - crash in Text Editor: datei abgespeichert


Summary:	crash in Text Editor: datei abgespeichert


Status:	RESOLVED DUPLICATE of bug 350988

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-12-29 16:43 UTC by 2407
Modified:	2006-12-29 16:58 UTC

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

Description 2407 2006-12-29 16:43:42 UTC

Version: 2.16.1

What were you doing when the application crashed?
datei abgespeichert


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

Memory status: size: 150749184 vsize: 0 resident: 150749184 share: 0 rss: 100945920 rss_rlim: 0
CPU usage: start_time: 1167395331 rtime: 0 utime: 10346 stime: 0 cutime:10197 cstime: 0 timeout: 149 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 -1227139408 (LWP 5347)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 97827

Thread 1 (Thread -1227139408 (LWP 5347))

#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_file_chooser_default_new
from /usr/lib/libgtk-x11-2.0.so.0
#11 _gtk_file_chooser_embed_should_respond
from /usr/lib/libgtk-x11-2.0.so.0
#12 _gtk_file_chooser_embed_set_delegate
from /usr/lib/libgtk-x11-2.0.so.0
#13 _gtk_file_chooser_embed_should_respond
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_file_chooser_dialog_new
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#30 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#34 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#35 main
#0 __kernel_vsyscall

Comment 1 Paolo Borelli 2006-12-29 16:58:52 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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