GNOME Bugzilla – Bug 400170
GNOME panel crash after Nautilus entering a bad directory
Last modified: 2007-02-09 14:54:53 UTC
Steps to reproduce: 1. Download http://www.badongo.com/file/2074185 2. Unzip it and it will generate two files: Warcraft III.mdf and Warcraft III.mds 3. Transform these files to a standard ISO file by "Alcohol 120%", named wc3.iso (613.8MB) 4. Extract wc3.iso in Nautilus (Extract files here) 5. Enter the directory which created by Nautilus after extracting wc3.iso 6. Then GNOME panel will CRASH!!! Stack trace: Memory status: size: 163287040 vsize: 163287040 resident: 20701184 share: 13795328 rss: 20701184 rss_rlim: -1 CPU usage: start_time: 1169575976 rtime: 54 utime: 46 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (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) (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 46912590904480 (LWP 5189)] (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) (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) 0x00002aaaacfa5eb5 in waitpid () from /lib/libpthread.so.0
+ Trace 104832
Thread 1 (Thread 46912590904480 (LWP 5189))
Other information: Warcraft III.mdf and Warcraft III.mds are virtual CD image files, so unzip the ISO file transformed from these virtual files will generate bad file sections I think. I can repair this problem with deleting home directory. For instance: mv /home/h45 /home/h45.bak mkdir -p /home/h45 chown h45.h45 /home/h45 After all, GNOME panel will run correctly after cleaning my home directory.
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 358044 ***