nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Cannot reproduce sorry!
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42~rc-1ubuntu1
ProcVersionSign
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 22 22:18:54 2022
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
b'org.
InstallationDate: Installed on 2022-03-18 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
ProcCmdline: /usr/bin/nautilus --gapplication-
SegvAnalysis:
Segfault happened at: 0x7f481af76a88 <gtk_widget_
PC (0x7f481af76a88) ok
source "%rax" ok
destination "(%rbx)" (0xf8f7f7f70000
SegvReason: writing unknown 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 42.0-1
file-roller 3.42.0-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.