file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

Bug #1502616 reported by Matthias Andree
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

crash when double-clicking a folder inside a .zip archive
to be downloaded here
http://dl.cdn.chip.de/downloads/18172013/omegavesko-SimpleADBBackup-0790701.zip?1443965445-1443972945-b4a315-B-8bac46d6bcd66c375e5a8c6c5b0fcfa2

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: file-roller 3.10.2.1-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 4 15:26:57 2015
ExecutablePath: /usr/bin/file-roller
ProcCmdline: file-roller /home/username/Downloads/omegavesko-SimpleADBBackup-0790701.zip
SegvAnalysis:
 Segfault happened at: 0x41c4f0: mov (%rbx),%rsi
 PC (0x0041c4f0) ok
 source "(%rbx)" (0x10000000006) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke (closure=0xde36d0, return_value=0x7ffcde85e440, n_param_values=2, param_values=0x7ffcde85e4f0, invocation_hint=0x7ffcde85e490) at /build/buildd/glib2.0-2.40.2/./gobject/gclosure.c:768
 signal_emit_unlocked_R (node=node@entry=0x8d1aa0, detail=detail@entry=0, instance=instance@entry=0xa8e4b0, emission_return=emission_return@entry=0x7ffcde85e5c0, instance_and_params=instance_and_params@entry=0x7ffcde85e4f0) at /build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:3551
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffcde85e688) at /build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:3317
Title: file-roller crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to trusty on 2014-08-29 (400 days ago)
UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse kvm libvirtd lpadmin netdev plugdev pulse sambashare saned tape vboxusers video

Revision history for this message
Matthias Andree (matthias-andree) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 _gtk_marshal_BOOLEAN__BOXED (closure=0xde36d0, return_value=0x7ffcde85e440, n_param_values=<optimized out>, param_values=0x7ffcde85e4f0, invocation_hint=<optimized out>, marshal_data=<optimized out>) at gtkmarshalers.c:85
 g_closure_invoke (closure=0xde36d0, return_value=0x7ffcde85e440, n_param_values=2, param_values=0x7ffcde85e4f0, invocation_hint=0x7ffcde85e490) at /build/buildd/glib2.0-2.40.2/./gobject/gclosure.c:768
 signal_emit_unlocked_R (node=node@entry=0x8d1aa0, detail=detail@entry=0, instance=instance@entry=0xa8e4b0, emission_return=emission_return@entry=0x7ffcde85e5c0, instance_and_params=instance_and_params@entry=0x7ffcde85e4f0) at /build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:3551
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffcde85e688) at /build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:3317

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.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_closure_invoke()
+ file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
tags: removed: need-amd64-retrace
information type: Private Security → Public
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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