file-roller crashed with SIGSEGV in find_image_offset()

[Iain Lane]

Binary package hint: file-roller

Crashes reliably when picking "open with" on files inside a tarball.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/file-roller
NonfreeKernelModules: fglrx
Package: file-roller 2.23.6-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: file-roller file:///tmp/bdb1-0.2.3.tar.gz
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? ()
Title: file-roller crashed with SIGSEGV
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse kqemu kvm lpadmin netdev plugdev powerdev sambashare scanner vboxusers video www-data

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Iain Lane (laney)]

Pedro Villavicencio wrote:
> Thanks for your bug report. Please try to obtain a backtrace
> http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
> bug report. This will greatly help us in tracking down your problem.
>
> ** Changed in: file-roller (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
> Status: New => Incomplete
>
> ** Attachment removed: "CoreDump.gz"
>
> http://launchpadlibrarian.net/16944096/CoreDump.gz
>
> ** Visibility changed to: Public
>

 status new

Hi Pedro,

Thanks for triaging. Here's the trace and valgrind log for bonus info.

Iain

[Sebastien Bacher (seb128)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=548615