nautilus crashed with SIGSEGV

Bug #2017406 reported by Meshari E
10
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 18 06:30:50 2023
ExecutablePath: /usr/bin/nautilus
ExecutableTimestamp: 1672766988
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-service
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_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
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-extension-gnome-terminal 3.44.0-1ubuntu1
 nautilus-share 0.7.3-2ubuntu6

Revision history for this message
Meshari E (idmbe) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.