file-roller crashed with SIGSEGV in g_main_context_dispatch()

Bug #1724632 reported by Lê Chương on 2017-10-18
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Undecided
Unassigned

Bug Description

I open font svg file, try to zoom in and zoom out (by rolling mouse), then this error occur

There is other report but too old (2010 and earlier), so I'm open new thread.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: file-roller 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 00:14:52 2017
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2017-08-22 (57 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
ProcCmdline: file-roller /home/username/Downloads/entypo.zip
SegvAnalysis:
 Segfault happened at: 0x55f76a5c3087: mov 0x228(%rax),%eax
 PC (0x55f76a5c3087) 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 docker lpadmin plugdev sambashare sudo

Lê Chương (ko-co-ten-1992) wrote :

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 #1431617, 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  Edit
Everyone can see this information.

Other bug subscribers