nautilus crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I don't know what happened.
ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: nautilus 1:3.37.1.1-1ubuntu1
Uname: Linux 5.6.11-
ApportVersion: 2.20.11-0ubuntu33
Architecture: amd64
CasperMD5CheckR
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu May 7 15:40:35 2020
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2018-12-02 (524 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: /usr/bin/nautilus --gapplication-
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANGUAGE=es_CL:es
LANG=es_CL.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fb39cdedac2: mov 0x380(%rax),%rax
PC (0x7fb39cdedac2) ok
source "0x380(%rax)" (0x00000380) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom chrome-
separator:
usr_lib_nautilus:
| El jinete sin cabeza (ejsc) 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 #1857539, 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.