file-roller crashed with SIGSEGV in g_simple_async_result_complete()

Bug #1063020 reported by mathis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
New
Undecided
Unassigned

Bug Description

version is 12.10 beta2

file-roller crashes when trying to open a .zip file by right-clicking in nautilus. when opening file-roller first, the crash does not occur.
so maybe its a nautilus tthing?

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: file-roller 3.6.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sat Oct 6 22:38:01 2012
ExecutablePath: /usr/bin/file-roller
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcCmdline: file-roller /media/username/859E-615F/theater/NeuesEnsemblE/daria/Mathias.zip
SegvAnalysis:
 Segfault happened at: 0x809d472: mov 0x8(%eax),%eax
 PC (0x0809d472) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to quantal on 2012-09-26 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
mathis (mathiswendel) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1060506, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-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.