nautilus crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
nautilus crashed with SIGSEGV
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.2-0ubuntu2.1
ProcVersionSign
Uname: Linux 5.19.0-38-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 18 06:30:50 2023
ExecutablePath: /usr/bin/nautilus
ExecutableTimes
GsettingsChanges:
InstallationDate: Installed on 2023-04-08 (9 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
ProcCmdline: /usr/bin/nautilus --gapplication-
ProcCwd: /home/idmbe
SegvAnalysis:
Segfault happened at: 0x7fdede5b2848: mov 0x380(%rax),%rax
PC (0x7fdede5b2848) 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:
evince 42.3-0ubuntu3
file-roller 3.42.0-1
nautilus-
nautilus-share 0.7.3-2ubuntu6
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.