nemo crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nemo (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
?
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nemo 3.6.5-1
ProcVersionSign
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Fri Apr 13 18:40:19 2018
ExecutablePath: /usr/bin/nemo
InstallationDate: Installed on 2018-03-23 (21 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180322)
ProcCmdline: /usr/bin/nemo --no-default-window
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=de_DE
PATH=(custom, no user)
LANG=de_DE.UTF-8
SegvAnalysis:
Segfault happened at: 0x55ab6f16f780: mov 0x18(%rdi),%rax
PC (0x55ab6f16f780) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nemo
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
g_main_
Title: nemo crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
tags: | removed: need-amd64-retrace |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.