nautilus crashed with SIGSEGV

Bug #2029264 reported by Anas
This bug report is a duplicate of:  Bug #2029151: nautilus crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

crash after choosing files on VLC Snap Version

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: nautilus 1:44.2.1-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 1 15:47:29 2023
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2023-07-29 (3 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230729)
JournalErrors:
 août 01 15:47:23 hostname gnome-shell[3164]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
 août 01 15:47:28 hostname (udev-worker)[32242]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x5646d257f40a: mov 0x18(%r12),%rdi
 PC (0x5646d257f40a) ok
 source "0x18(%r12)" (0xfffffffffffffeb8) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

usr_lib_nautilus: nautilus-extension-gnome-terminal 3.48.1-1ubuntu1

Revision history for this message
Anas (anas-blinux) wrote :
information type: Private → Public
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 #2029151, 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.

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.