nemo crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nemo (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I just clicked on it and it closed, simple as that.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nemo 3.6.5-1
ProcVersionSign
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 13 15:10:00 2018
ExecutablePath: /usr/bin/nemo
InstallationDate: Installed on 2018-04-12 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
ProcCmdline: nemo
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fed2e988d76 <__strcmp_
PC (0x7fed2e988d76) ok
source "(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nemo
StacktraceTop:
()
()
() at /usr/lib/
g_signal_
g_signal_emit () at /usr/lib/
Title: nemo crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1679843, 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.