nautilus crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I don't have further information.
Sometimes, after system start gives this crash error.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSign
Uname: Linux 5.4.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckR
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 5 21:37:58 2020
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2014-03-19 (2362 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: /usr/bin/nautilus --gapplication-
SegvAnalysis:
Segfault happened at: 0x7fcc28d93ac2: mov 0x380(%rax),%rax
PC (0x7fcc28d93ac2) 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:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to focal on 2020-08-06 (30 days ago)
UserGroups: adm audio cdrom dialout dip lp lpadmin plugdev sambashare sudo
modified.
mtime.conffile.
separator:
usr_lib_nautilus:
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.