file-roller crashed with SIGSEGV in g_signal_emit_valist()

Bug #1049447 reported by Sebastian Bugiu
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
New
Undecided
Unassigned

Bug Description

Under heavy load tried opening file-roller after archiving a folder and got this.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: file-roller 3.5.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Wed Sep 12 05:53:07 2012
ExecutablePath: /usr/bin/file-roller
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: file-roller --notify --default-dir=file:///home/username/eclipse_workspace --add file:///home/username/eclipse_workspace/Blackhole_Darksun
SegvAnalysis:
 Segfault happened at: 0x4395b7: mov 0x240(%rdx),%rdi
 PC (0x004395b7) ok
 source "0x240(%rdx)" (0xaaaaaaaaaaaaacea) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 ?? () 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
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libnotify.so.4
Title: file-roller crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: Upgraded to quantal on 2012-08-12 (31 days ago)
UserGroups: adm admin cdrom dialout dip lpadmin netdev plugdev sambashare

Revision history for this message
Sebastian Bugiu (sebastian-bugiu) 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 #1038532, 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-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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