GNOME Bugzilla – Bug 129794
file-roller 2.4.1.1 crashes upon LZH file opening
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Unknown Package: file-roller Severity: normal Version: GNOME2.4.0 2.4.1.1 Gnome-Distributor: Gentoo Linux Synopsis: file-roller 2.4.1.1 crashes upon LZH file opening Bugzilla-Product: file-roller Bugzilla-Component: general Bugzilla-Version: 2.4.1.1 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: file-roller will crash when opening regular LZH files (link below). All the LZH files that cause the problem can be correctly opened using the "lha" command line tool. I didn't manage to find a LZH file that can be opened with file-roller. Steps to reproduce the crash: 1. Download TZNOW.LZH from this link: ftp://grunny.demon.nl/challenge/snow/TZNOW.LZH (as far as I tried, any LZH file will trigger the crash) 2. Start file-roller and open TZNOW.LZH 3. Watch it crash :( Expected Results: Contents of LZH files should be listed in file-roller window and be available for decompression. How often does this happen? Always. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/file-roller' (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)...[New Thread 16384 (LWP 5353)] (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)...0x40550f67 in waitpid () from /lib/libpthread.so.0
+ Trace 42826
Thread 1 (Thread 16384 (LWP 5353))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-12-21 15:17 ------- Unknown version 2.4.1.1 in product file-roller. Setting version to the default, "unspecified". The original reporter (l.mancini@oltrelinux.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, paolo.bacch@tin.it.
Thanks for the bug report. This appears to be a unique stack trace according to the simple-dup-finder. For what it's worth, I can reproduce this on Fedora using your instructions. I'm setting some fields appropriately and adding the bugsquad keyword.