GNOME Bugzilla – Bug 172324
file-roller crash when extract button is clicked
Last modified: 2005-04-01 05:06:39 UTC
Distribution: SuSE Linux 9.2 (i586) Package: file-roller Severity: normal Version: GNOME2.6. 2.6.1 Gnome-Distributor: SUSE Synopsis: file-roller crash when extract button is clicked Bugzilla-Product: file-roller Bugzilla-Component: general Bugzilla-Version: 2.6.1 BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: file-roller crashed with a "this program has quit unexpectedly" dialog when I clicked the extract button. I had not selected any individual files for extraction. The archive was a tar.bz2 file. Steps to reproduce the crash: 1. see above 2. 3. Expected Results: How often does this happen? Only tried it once. Additional Information: Debugging Information: Backtrace was generated from '/opt/gnome/bin/file-roller' (no debugging symbols found)...Using host libthread_db library "/lib/tls/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)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1088594272 (LWP 8753)] [New Thread 1095035824 (LWP 8768)] [Thread debugging using libthread_db enabled] [New Thread 1088594272 (LWP 8753)] [New Thread 1095035824 (LWP 8768)] [Thread debugging using libthread_db enabled] [New Thread 1088594272 (LWP 8753)] [New Thread 1095035824 (LWP 8768)] [New Thread 1094118320 (LWP 8767)] (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 ?? ()
+ Trace 57583
Thread 1 (Thread 1088594272 (LWP 8753))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-01 00:04 ------- Unknown version 2.6.1 in product file-roller. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "file-roller". 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 tph@bazza.com. 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 particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Matches the stack trace in bug 168073, which has been marked as a duplicate of 151715. *** This bug has been marked as a duplicate of 151715 ***