nemo crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nemo (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
nemo was in the background with an open sftp-connection and chaneing it into the front produced a crash
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nemo 3.6.5-1
ProcVersionSign
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 11 10:24:50 2018
ExecutablePath: /usr/bin/nemo
InstallationDate: Installed on 2017-04-07 (368 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcCmdline: nemo
SegvAnalysis:
Segfault happened at: 0x7f8b205eed76 <__strcmp_
PC (0x7f8b205eed76) ok
source "(%rdi)" (0x796e616567) not located in a known VMA region (needed readable region)!
destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nemo
StacktraceTop:
()
()
() at /usr/lib/
g_signal_
g_signal_emit () at /usr/lib/
Title: nemo crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2018-03-29 (12 days ago)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
| Johannes Kalliauer (jokalliauer1989) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| 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 #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.