nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Nautilus operation is quite slower on Ubuntu 24.04 when changing directories.
While changing directories rapidly with mouse clicks back and forward, nautilus crashed at a point.
And something about Gnome's graphics interface: it feels a bit more cumbersome than in Ubuntu 22.04 when moving the scrollbar for example.
ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: nautilus 1:45.2.1-4ubuntu1
ProcVersionSign
Uname: Linux 6.6.0-14-lowlatency x86_64
NonfreeKernelMo
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckR
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 4 00:05:18 2024
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
b'org.
ProcCmdline: /usr/bin/nautilus --gapplication-
ProcEnviron:
LANG=de_BE.UTF-8
PATH=(custom, user)
SHELL=/bin/bash
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7bfa82441de1 <g_type_
PC (0x7bfa82441de1) ok
source "(%rax)" (0x00000004) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_type_
g_object_ref () from /lib/x86_
g_list_copy_deep () from /lib/x86_
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm dialout libvirt sudo
separator:
usr_lib_nautilus:
file-roller 43.1-1
nautilus-
nautilus-
nautilus-share 0.7.5-0.3
python3-nautilus 4.0-1build2
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 #1813171, 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.