GNOME Bugzilla – Bug 363472
Crash in gtk_file_info_get_is_folder
Last modified: 2013-05-17 01:45:20 UTC
Version: 2.16.1 What were you doing when the application crashed? Editing latex file Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 129789952 vsize: 0 resident: 129789952 share: 0 rss: 39235584 rss_rlim: 0 CPU usage: start_time: 1161243070 rtime: 0 utime: 6958 stime: 0 cutime:6611 cstime: 0 timeout: 347 it_real_value: 0 frequency: 387 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 -1227045200 (LWP 393)] [New Thread -1302602848 (LWP 30277)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 77192
Thread 1 (Thread -1227045200 (LWP 393))
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug. You'll also need to add a better stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance! Moving to gtk+ since it looks a crash in the file chooser.
*** Bug 374655 has been marked as a duplicate of this bug. ***
*** Bug 376306 has been marked as a duplicate of this bug. ***
I'm seeing this one on Fedora Rawhide with GIMP. Package versions: gtk2-2.10.6-3.fc7 gnome-vfs2-2.16.2-2.fc7 glib2-2.12.4-1.fc7 Steps to reproduce: 1. Create a folder and put in some PNGs 2. Open ALL of the PNGs inside this folder with GIMP 3. Attach gdb to GIMPs process 4. From a terminal do "tar -czvf pictures.tar.gz *.png" At this point GIMP crashes. Backtrace with debug symbols will be attached.
Created attachment 76832 [details] Backtrace of the GIMP crash with debug info
I think I've found some related bugs. But I don't know for sure, so I want to hear a second opinion. Here are the bugs: gedit Bug 375496 and Bug 377747 control-center Bug 369211 and Bug 375783 evolution Bug 377752 gnome-utils Bug 377807 I was able to reproduce Bug 377747 with GIMP again on Fedora Rawhide. I've opened the filechooser, changed to a directory, and deleted a file from the displayed directory through a terminal. It seems not to be 100% reproducible. Backtrace should be the same as Bug 377747, and again "No such file or directory":
+ Trace 88473
*** Bug 378126 has been marked as a duplicate of this bug. ***
*** Bug 387292 has been marked as a duplicate of this bug. ***
*** Bug 388444 has been marked as a duplicate of this bug. ***
*** Bug 388977 has been marked as a duplicate of this bug. ***
*** Bug 401614 has been marked as a duplicate of this bug. ***
*** Bug 394352 has been marked as a duplicate of this bug. ***
*** Bug 393467 has been marked as a duplicate of this bug. ***
*** Bug 392485 has been marked as a duplicate of this bug. ***
*** Bug 394711 has been marked as a duplicate of this bug. ***
*** Bug 404114 has been marked as a duplicate of this bug. ***
*** Bug 410607 has been marked as a duplicate of this bug. ***
*** Bug 416641 has been marked as a duplicate of this bug. ***
*** Bug 418402 has been marked as a duplicate of this bug. ***
*** Bug 420808 has been marked as a duplicate of this bug. ***
*** Bug 423248 has been marked as a duplicate of this bug. ***
*** Bug 433199 has been marked as a duplicate of this bug. ***
*** Bug 450847 has been marked as a duplicate of this bug. ***
*** Bug 447661 has been marked as a duplicate of this bug. ***
*** Bug 378764 has been marked as a duplicate of this bug. ***
*** Bug 456226 has been marked as a duplicate of this bug. ***
After I reported bug 456226, I closed all windows and rebooted. After logging on, I received the following error message: X-session-manager: gtk-warning cannot open display. After closing the messagebox, I was returned to the login screen. Logging in with other users yielded the same result, as did the other login options (failsafe GNOME and failsafe Terminal). I was finally able to reboot using the Grub boot selection Ubuntu, 2.6.20-16-server (recovery mode). From there I was able to start GNOME as root, but not as my user. (I forget what command I entered.) The primary error message that I encountered while investigating the problem was: Error after login (gnome-session:xxxx) Gtk-WARNING **: Cannot open session. After two days, I was unsuccessful in correcting the problem, and ended up doing a fresh install of Ubuntu 7.04. I still have the original system on a separate hard drive. However, before doing the fresh install, I unsuccessfully attempted to do a 'apt-get -u dist-upgrade'. Therefore, the original configuration is most likely not intact, although some of the log files may be, if they would be of any use. Regards, Tom PS: I had originally installed 6.06lts in April, and had upgraded to 6.10 about a week before this incident. I had not previously had any problems with GNOME.
*** Bug 456328 has been marked as a duplicate of this bug. ***
*** Bug 492893 has been marked as a duplicate of this bug. ***
See also Mozilla Bug 401801 – Crash in gtk_file_info_get_is_folder using GTK File-Open dialog when desktop contents are changed https://bugzilla.mozilla.org/show_bug.cgi?id=401801 To reproduce: - Move all files/folders off desktop - Create two empty files called "a" and "b" - In a new Firefox or gedit window, press <Ctrl+o> for the GTK Open-File dialog - On the desktop, rename file "a" to "c" ***Crash!*** This is very reproducible on my Ubuntu Gutsy desktop, but not on my Ubuntu Gutsy laptop for some reason. Both machines are up-to-date and have similar packages installed, so I'm not sure what the distinction is.
After many many reports of this bug for around 1 year. They then suddenly stopped with no further activity for 5.5 years now. This bug report should probably be closed.
Thanks, good catch. After moving to GIO, this would have a changed a lot.