squeeze crashed with SIGSEGV in lsq_archive_iter_ref()

Bug #1220902 reported by Jackson Doak
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
squeeze (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When clicking "extract" while only some files in an archive are selected, squeeze crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: squeeze 0.2.3-12build1
ProcVersionSignature: Ubuntu 3.11.0-5.10-generic 3.11.0
Uname: Linux 3.11.0-5-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Thu Sep 5 06:36:39 2013
ExecutablePath: /usr/bin/squeeze
InstallationDate: Installed on 2013-08-17 (18 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130816)
MarkForUpload: True
ProcCmdline: squeeze /home/username/packaging/qt/PyQt-x11-gpl-4.10.3.tar.gz
SegvAnalysis:
 Segfault happened at: 0x7f6ad97eabc0 <lsq_archive_iter_ref>: mov 0x18(%rdi),%edx
 PC (0x7f6ad97eabc0) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: squeeze
StacktraceTop:
 lsq_archive_iter_ref () from /usr/lib/x86_64-linux-gnu/libsqueeze-0.2.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: squeeze crashed with SIGSEGV in lsq_archive_iter_ref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Jackson Doak (noskcaj) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in squeeze (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libexpat1: package version 2.1.0-4 dbgsym version 2.1.0-2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.