file-roller crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
file-roller (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Something went wrong, I don't know what!
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: file-roller 3.28.0-1ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 19 14:53:03 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2018-03-17 (32 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
ProcCmdline: file-roller /home/username/
SegvAnalysis:
Segfault happened at: 0x5623d8a15c47: mov 0x228(%rax),%eax
PC (0x5623d8a15c47) 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 /usr/lib/
g_main_
?? () from /usr/lib/
g_main_loop_run () from /usr/lib/
Title: file-roller crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Mehdi Abbassi (mehdi-n-abbassi) wrote : | #1 |
information type: | Private → Public |
tags: | removed: need-amd64-retrace |
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.