GNOME Bugzilla – Bug 436019
crash in Archive Manager: Extract a pile of zipped...
Last modified: 2007-05-05 16:56:09 UTC
Version: 2.16.1 What were you doing when the application crashed? Extract a pile of zipped files on the laptop HD onto a barick-media folder. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 67731456 vsize: 0 resident: 67731456 share: 0 rss: 16052224 rss_rlim: 0 CPU usage: start_time: 1178333000 rtime: 0 utime: 788 stime: 0 cutime:758 cstime: 0 timeout: 30 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/file-roller' (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 -1224730960 (LWP 22122)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 132480
Thread 1 (Thread -1224730960 (LWP 22122))
The hard drive on which the files in question were located is, or the last time I had it, was, a properly operational hard drive on a Toshiba laptop, running Windows XP. That laptop PC is, at the moment, gone to visit a doctor for problems other than those associated with the hard drive. I was trying to extract some 41 sipped files from a folder on the drive, and place them onto a local file server when the incident precipitating this failure occurred. Ordinarily, I would have had the hard drive in an enclosure plugged into a USB port on my windows PC, but that PC would mot allow me access to the drive's contents. On a whim, I thought I'd see if I could see the drive any better on the linux-based PC. That PC had no trouble at all in seeing the drive, as well as its contents, much to my surprise after the experience on the Windows PC. Earlier in the evening, I made a visit to a Geek Squad guru(?) at the Best Buy store where I purchased the laptop PC almost three years ago, to inquire as to the state of the source drive under consideration. He only confirmed my own experience with the drive, but assured me that, were the drive mounted anew in the PC from which it had been dismounted, it would probably prove quite properly functional. I was not willing to wait for the laptop to return from the doctor's visit. Hence, my attempt to see its contents on the linux machine, and the precipitation of this incident. I have, however, circumvented the problem. I extracted all the files destined for the file server to the desktop of the linux user, then copied them onto the file server and moved them off the desktop to the trash can. Consequently, any repair to the tools in use at the time of the failure are, at the moment, of relatively small import to me. But, since we all want our software to be properly functional, I dare say those repairs will be accomplished in due course. Thank you! Bruce Barick
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 357188 ***