file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()

Bug #1440386 reported by origpumu
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

reactivated from standby. Logged in and the error occured.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: file-roller 3.14.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Apr 4 18:39:05 2015
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2014-09-27 (188 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
ProcCmdline: file-roller /home/username/Downloads/77.zip
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4436dd: mov %esi,0x170(%rax)
 PC (0x004436dd) ok
 source "%esi" ok
 destination "0x170(%rax)" (0x00000170) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__STRINGv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.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
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()
UpgradeStatus: Upgraded to vivid on 2015-04-03 (0 days ago)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo

Revision history for this message
origpumu (originalpumuckl-5) 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 #1438670, 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.

information type: 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.