GNOME Bugzilla – Bug 151715
Gedit Crash after opening a second tab
Last modified: 2011-02-04 16:16:24 UTC
Distribution: Debian 3.1 Package: gedit Severity: normal Version: GNOME2.6.1 2.6.2 Gnome-Distributor: Debian Synopsis: Gedit Crash after opening a second tab Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.6.2 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: Always crashes after open a second file on a diferent tab Steps to reproduce the crash: 1. open a file 2. open another file 3. crash Expected Results: How often does this happen? Always this session. Never in other sessiones. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found)...Using host libthread_db library "/lib/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)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 1569)] [New Thread 32769 (LWP 1570)] [New Thread 16386 (LWP 1571)] [New Thread 32771 (LWP 1572)] (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)...(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)...0x4092bc0b in waitpid () from /lib/libpthread.so.0
+ Trace 49849
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-02 17:16 ------- Unknown version 2.6.2 in product gedit. Setting version to "0.5.1". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gedit". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was jorge.gonzález.gonzález@hispalinux.es. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. This seems a crash in the new gtk+ file chooser. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please, update your version of gtk+ and gedit and let us know if you are still able to reproduce it. If you are still able to reproduce this crash, please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces.
Same bug reported in the Debian BTS: http://bugs.debian.org/268326 According to the submitter it happens with eog too, so apparently a gtk+ problem ...
*** Bug 151560 has been marked as a duplicate of this bug. ***
We also need to know the libgnomeui version, since this crash involves gtkfilesystemgnomevfs, which lives in libgnomeui.
details in the link to the debian BTS (Comment #2): ii libgnomeui-0 2.6.1.1-4 The GNOME 2 libraries
Does this still occur with a more recent libgnomeui ?
*** Bug 153084 has been marked as a duplicate of this bug. ***
*** Bug 153308 has been marked as a duplicate of this bug. ***
*** Bug 153528 has been marked as a duplicate of this bug. ***
Ok, I've managed to get more details on this problem. It seems to be reproducible without any problem on a Debian unstable without any problem: * gtk+ 2.4.10 * libgnomeui 2.6.1.1 * gnome-vfs 2.6.2 To reproduce: * cd /tmp * mkdir src * touch src/media.cpp * gedit src/media.cpp * click on open => crash Some indications: * If you select "save as" and expand the folder list you can note that media.cpp is listed 2 times in the list of files The crash is due to this stack of functions: gtk_file_chooser_default_set_current_folder -> set_list_model -> name_sort_func Since "media.cpp" is listed 2 times in the save mode perhaps that crashes name_sort_func ... With GNOME 2.8 and gtk+ 2.4.10 the file is not listed 2 times and it doesn't crash. I've made a little test case: #include <gtk/gtk.h> int main(int argc, char *argv[]) { GtkWidget *fs; gtk_init(&argc, &argv); fs = gtk_file_chooser_dialog_new ("Select files", NULL, GTK_FILE_CHOOSER_ACTION_OPEN, GTK_STOCK_CANCEL, GTK_RESPONSE_CANCEL, GTK_STOCK_OPEN, GTK_RESPONSE_ACCEPT, NULL); gtk_dialog_set_default_response (GTK_DIALOG (fs), GTK_RESPONSE_ACCEPT); gtk_file_chooser_set_select_multiple (GTK_FILE_CHOOSER (fs), TRUE); gtk_file_chooser_set_local_only (GTK_FILE_CHOOSER (fs), FALSE); gtk_file_chooser_set_current_folder_uri(GTK_FILE_CHOOSER (fs), "file:///tmp/src/"); gtk_widget_show_all(fs); gtk_main(); return 0; } The backtrace:
+ Trace 50516
Thread 1082073760 (LWP 912)
*** Bug 154314 has been marked as a duplicate of this bug. ***
*** Bug 154348 has been marked as a duplicate of this bug. ***
This is fixed in the latest versions of GTK+ 2.4.x and libgnomeui 2.6.x. I guess Debian has older versions of either.
Yeah, the bug is still in libgnomeui-2.6.1.1. With the latest from CVS in the gnome-2-6 branch, the bug is gone. I guess someone needs to cook a libgnomeui-2.6.2 tarball.
*** Bug 152544 has been marked as a duplicate of this bug. ***
*** Bug 156407 has been marked as a duplicate of this bug. ***
*** Bug 156095 has been marked as a duplicate of this bug. ***
*** Bug 156468 has been marked as a duplicate of this bug. ***
Yes! After running "update" for Debian system and installing newer libraries today the bug does not exist anymore. :-)
*** Bug 156537 has been marked as a duplicate of this bug. ***
*** Bug 156195 has been marked as a duplicate of this bug. ***
*** Bug 156183 has been marked as a duplicate of this bug. ***
*** Bug 154986 has been marked as a duplicate of this bug. ***
*** Bug 156560 has been marked as a duplicate of this bug. ***
*** Bug 156708 has been marked as a duplicate of this bug. ***
*** Bug 156113 has been marked as a duplicate of this bug. ***
*** Bug 155275 has been marked as a duplicate of this bug. ***
*** Bug 157086 has been marked as a duplicate of this bug. ***
*** Bug 157169 has been marked as a duplicate of this bug. ***
*** Bug 157232 has been marked as a duplicate of this bug. ***
*** Bug 157308 has been marked as a duplicate of this bug. ***
*** Bug 157372 has been marked as a duplicate of this bug. ***
*** Bug 157481 has been marked as a duplicate of this bug. ***
*** Bug 157825 has been marked as a duplicate of this bug. ***
*** Bug 157869 has been marked as a duplicate of this bug. ***
*** Bug 158014 has been marked as a duplicate of this bug. ***
*** Bug 158026 has been marked as a duplicate of this bug. ***
*** Bug 158042 has been marked as a duplicate of this bug. ***
*** Bug 158320 has been marked as a duplicate of this bug. ***
*** Bug 158471 has been marked as a duplicate of this bug. ***
*** Bug 158543 has been marked as a duplicate of this bug. ***
*** Bug 158739 has been marked as a duplicate of this bug. ***
*** Bug 158743 has been marked as a duplicate of this bug. ***
*** Bug 158783 has been marked as a duplicate of this bug. ***
*** Bug 159030 has been marked as a duplicate of this bug. ***
*** Bug 159402 has been marked as a duplicate of this bug. ***
*** Bug 159567 has been marked as a duplicate of this bug. ***
*** Bug 159791 has been marked as a duplicate of this bug. ***
*** Bug 159961 has been marked as a duplicate of this bug. ***
*** Bug 160369 has been marked as a duplicate of this bug. ***
*** Bug 160440 has been marked as a duplicate of this bug. ***
*** Bug 160499 has been marked as a duplicate of this bug. ***
*** Bug 160610 has been marked as a duplicate of this bug. ***
*** Bug 160741 has been marked as a duplicate of this bug. ***
*** Bug 160771 has been marked as a duplicate of this bug. ***
Wow, we still continue to have a lot of duplicates of this bug. Do you guys know if this bug has been already fixed in FC and/or Debian updates?
It's fine in FC3, but FC2 still will have the problem. We'll do a libgnomeui update for FC2 for this.
*** Bug 160805 has been marked as a duplicate of this bug. ***
It goes like this: 1. Distros which use GNOME 2.6 are using libgnomeui 2.6.0 or 2.6.1.1 2. The last tarball of libgnomeui under the 2.6 series is 2.6.1.1 3. The fix for this bug went into CVS after that. 4. No one ever made a 2.6.2 release because GNOME 2.8 branched at that point. 5. Distros need to cook a diff from 2.6.1.1 to the latest in the gnome-2-6 branch. You can grab such a SRPM of libgnomeui here: http://primates.ximian.com/~federico/misc/gtk+/SRPMS (That package will go into the first service pack for Novell Linux Desktop, or something like that)
*** Bug 161493 has been marked as a duplicate of this bug. ***
*** Bug 162325 has been marked as a duplicate of this bug. ***
*** Bug 164009 has been marked as a duplicate of this bug. ***
*** Bug 146291 has been marked as a duplicate of this bug. ***
*** Bug 164647 has been marked as a duplicate of this bug. ***
*** Bug 165133 has been marked as a duplicate of this bug. ***
*** Bug 166335 has been marked as a duplicate of this bug. ***
*** Bug 166356 has been marked as a duplicate of this bug. ***
*** Bug 166656 has been marked as a duplicate of this bug. ***
*** Bug 166945 has been marked as a duplicate of this bug. ***
*** Bug 167654 has been marked as a duplicate of this bug. ***
*** Bug 167691 has been marked as a duplicate of this bug. ***
*** Bug 168073 has been marked as a duplicate of this bug. ***
*** Bug 168591 has been marked as a duplicate of this bug. ***
*** Bug 168594 has been marked as a duplicate of this bug. ***
*** Bug 169934 has been marked as a duplicate of this bug. ***
*** Bug 169993 has been marked as a duplicate of this bug. ***
*** Bug 170548 has been marked as a duplicate of this bug. ***
*** Bug 172324 has been marked as a duplicate of this bug. ***
*** Bug 300097 has been marked as a duplicate of this bug. ***
*** Bug 301395 has been marked as a duplicate of this bug. ***
*** Bug 302431 has been marked as a duplicate of this bug. ***
*** Bug 302724 has been marked as a duplicate of this bug. ***
*** Bug 302725 has been marked as a duplicate of this bug. ***
*** Bug 303565 has been marked as a duplicate of this bug. ***
*** Bug 306799 has been marked as a duplicate of this bug. ***
*** Bug 310557 has been marked as a duplicate of this bug. ***
*** Bug 316751 has been marked as a duplicate of this bug. ***