Ubuntu
file-roller package

file-roller crashed with SIGSEGV in open_progress_dialog_with_open_destination()

Bug #1200966 reported by Craig Tee
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Using 'Extract to...' from right click menu.
Packages crashes before confirmation of result.
Extraction process is completed without error.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: file-roller 3.8.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Sat Jul 13 17:09:11 2013
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2013-07-07 (5 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130702)
MarkForUpload: True
ProcCmdline: file-roller /media/username/x134/Copy/software/lin/copy_agent-1.32.0471.tgz
SegvAnalysis:
 Segfault happened at: 0x44b3ec: mov 0x2a0(%rax),%edi
 PC (0x0044b3ec) ok
 source "0x2a0(%rax)" (0xaaaaaaaaaaaaad4a) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio backup cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video

Revision history for this message
Craig Tee (captco) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 open_progress_dialog_with_open_destination (window=0x952580) at fr-window.c:2609
 archive_extraction_ready_cb (source_object=0xbf6170, result=0xcbea30, user_data=user_data@entry=0xb84e00) at fr-window.c:6481
 g_simple_async_result_complete (simple=0xcbea30) at /build/buildd/glib2.0-2.37.3/./gio/gsimpleasyncresult.c:777
 complete_in_idle_cb_for_thread (_data=0xc8d4e0) at /build/buildd/glib2.0-2.37.3/./gio/gsimpleasyncresult.c:845
 g_main_dispatch (context=0x7d45c0) at /build/buildd/glib2.0-2.37.3/./glib/gmain.c:3058

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 file-roller (Ubuntu):
importance: Undecided → Medium
summary: - file-roller crashed with SIGSEGV in g_simple_async_result_complete()
+ file-roller crashed with SIGSEGV in
+ open_progress_dialog_with_open_destination()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in file-roller (Ubuntu):
status: New → Confirmed
Sebastien Bacher (seb128)
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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