file-roller crashed with SIGSEGV in extraction_is_finished()

Bug #1431617 reported by ROCHE
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Confirmed
High
Unassigned

Bug Description

By extract an apk file and copiing on a smartphone

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: file-roller 3.14.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Mar 13 00:16:36 2015
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2015-02-28 (12 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
ProcCmdline: file-roller /media/username/6CBE6A300BA189D3/Prg/apk/Sygic/Apk\ orig/Sygic_14.7.0_crk_151.apk
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4396d7: mov 0x228(%rax),%eax
 PC (0x004396d7) ok
 source "0x228(%rax)" (0x00000228) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-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
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: file-roller crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
ROCHE (guyroche08-6) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 extraction_is_finished (data=0x7ffcf95dfd90, data@entry=<error reading variable: value has been optimized out>) at fr-window.c:4325
 g_timeout_dispatch (source=0x10c97d0, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.43.91/./glib/gmain.c:4545
 g_main_dispatch (context=0x8f7cd0) at /build/buildd/glib2.0-2.43.91/./glib/gmain.c:3122
 g_main_context_dispatch (context=context@entry=0x8f7cd0) at /build/buildd/glib2.0-2.43.91/./glib/gmain.c:3737
 g_main_context_iterate (context=0x8f7cd0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.43.91/./glib/gmain.c:3808

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_main_context_dispatch()
+ file-roller crashed with SIGSEGV in extraction_is_finished()
tags: removed: need-amd64-retrace
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.

information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in file-roller (Ubuntu):
importance: Medium → High
status: New → Confirmed
tags: added: artful
tags: added: bionic
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.