GNOME Bugzilla – Bug 167851
File-roller crashes when openeing a PowerPoint file contained in a ZIP file
Last modified: 2005-02-19 00:40:33 UTC
Distribution: Debian 3.1 Package: file-roller Severity: normal Version: GNOME2.8.1 2.8.3 Gnome-Distributor: Debian Synopsis: File-roller crashes when openeing a PowerPoint file contained in a ZIP file Bugzilla-Product: file-roller Bugzilla-Component: general Bugzilla-Version: 2.8.3 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Steps to reproduce the crash: 1. Open a .zip file which was attached to a message recieved in Gmail. 2. Double-clicked on a .pps (MS PowerPoint) file to open it with OpenOffice. (only file in it) 3. File-roller reported crash Expected Results: Open the contained file with OpenOffice How often does this happen? First time Additional Information: Debian testting on AMD Athlon, KDE environment but with GNOME installed. Kernel is Debian Testting's latest: 2.6.8-2-k7 Debugging Information: Backtrace was generated from '/usr/bin/file-roller' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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) [Thread debugging using libthread_db enabled] [New Thread 1087244864 (LWP 7488)] (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) 0x4094b4ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 55861
Thread 1 (Thread 1087244864 (LWP 7488))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-18 17:25 ------- Unknown version 2.8.3 in product file-roller. Setting version to "2.8.x". 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 bugbuddy@amos.mailshell.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 166095, which has been marked as a duplicate of 164894. *** This bug has been marked as a duplicate of 164894 ***