nautilus crashed with SIGSEGV on 20.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Out of nowhere when restart after installing Ubuntu 20.04 Focal Fossa, and installing some updates, pop gtk theme, pop sound theme, pop shell theme, Minecraft Launcher and GNOME Tweaks. I have set natural scrolling to ON. This is all the information I've.
Oh, this is in VMWare Workstation Pro 15.x virtual machine.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.0-1ubuntu1
ProcVersionSign
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 12 17:34:28 2020
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.
InstallationDate: Installed on 2020-03-12 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
ProcCmdline: /usr/bin/nautilus --gapplication-
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANG=nl_NL.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f6e2a4b9962: mov 0x380(%rax),%rax
PC (0x7f6e2a4b9962) 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 /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
usr_lib_nautilus:
summary: |
- nautilus crashed with SIGSEGV + nautilus crashed with SIGSEGV on VMWare VM |
summary: |
- nautilus crashed with SIGSEGV on VMWare VM + nautilus crashed with SIGSEGV on 20.04 |
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.