Gedit Crashes when Cancel is selected in the GtkFileSelection Dialog

Bug #9960 reported by Mike McCabe
8
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Fix Released
Medium
Sebastien Bacher

Bug Description

With one xml file open and on unamed file open and the unamed file as the
selected tabbed, I tried to open a new file. Here's the backtrace without
debugging symbols. How do I enable debugging symbols using dpkg-buildpackage?

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)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 1091203328 (LWP 11615)]
[New Thread 1103473584 (LWP 11619)]
[Thread debugging using libthread_db enabled]
[New Thread 1091203328 (LWP 11615)]
[New Thread 1103473584 (LWP 11619)]
(no debugging symbols found)...[New Thread 1103145904 (LWP 11617)]
(no debugging symbols found)...[New Thread 1102171056 (LWP 11616)]
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...[Thread
debugging using libthread_db enabled]
[New Thread 1091203328 (LWP 11615)]
[New Thread 1103473584 (LWP 11619)]
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...0xffffe410 in
__kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x4093794b in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0x401323dd in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0x40dcd282 in g_type_check_instance_cast ()
   from /usr/lib/libgobject-2.0.so.0
#5 0x40aed53c in gtk_path_bar_get_type () from /usr/lib/libgtk-x11-2.0.so.0
#6 0x40e0d0ac in g_main_context_wakeup () from /usr/lib/libglib-2.0.so.0
#7 0x40e0a962 in g_main_depth () from /usr/lib/libglib-2.0.so.0
#8 0x40e0ba18 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#9 0x40e0bd50 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#10 0x40e0c2f3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#11 0x40abefe3 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x08060997 in main ()

Thread 4 (Thread 1102171056 (LWP 11616)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0x40f4184f in poll () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0x40e0c6d6 in g_main_loop_get_context () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#3 0x40e0bcd0 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#4 0x40e0c2f3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#5 0x40696050 in link_thread_io_context () from /usr/lib/libORBit-2.so.0
No symbol table info available.
#6 0x40e65398 in ?? () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#7 0x41b1cad8 in ?? ()
No symbol table info available.
#8 0x40e254ad in g_static_private_free () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#0 0xffffe410 in __kernel_vsyscall ()

Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you get this crash every time ? Do you use warty or hoary ?
To build a debuging package use DEB_BUILD_OPTIONS="nostrip noopt"
(DEB_BUILD_OPTIONS="nostrip noopt" dpkg-buildpackage ....)

Revision history for this message
Mike McCabe (mccabemt) wrote :

I'm running Hoary and I was able to reproduce it.

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you still get this bug ?

Revision history for this message
Mike McCabe (mccabemt) wrote :

I can't reproduce it now.

Revision history for this message
Sebastien Bacher (seb128) wrote :

ok, I'm closing it for the moment so. Feel free to reopen if you get the bug again.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.