nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
lsb_release -rd
Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04
nautilus:
Installed: 1:42~beta-1ubuntu1
Candidate: 1:42~beta-1ubuntu1
Version table:
*** 1:42~beta-1ubuntu1 500
500 http://
100 /var/lib/
The crashed happened opening "Files" from the side application bar
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42~beta-1ubuntu1
ProcVersionSign
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 5 20:29:23 2022
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.
InstallationDate: Installed on 2022-02-13 (19 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220116)
ProcCmdline: /usr/bin/nautilus --gapplication-
SegvAnalysis:
Segfault happened at: 0x7f24ab2db9a8 <gtk_widget_
PC (0x7f24ab2db9a8) ok
source "%rax" ok
destination "(%rbx)" (0x00000090) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
gtk_widget_
?? ()
g_closure_invoke () from /lib/x86_
?? () from /lib/x86_
g_signal_
Title: nautilus crashed with SIGSEGV in gtk_widget_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
usr_lib_nautilus:
evince 41.3-3
file-roller 3.41.90-1
nautilus-
nautilus-share 0.7.3-2ubuntu4
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 #1962761, 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.