gnome-shell crashed with SIGABRT at ERROR:../src/st/st-icon-theme.c:3584:st_icon_info_load_icon_finish: assertion failed: (icon_info_get_pixbuf_ready (icon_info))
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This happened under some I/O load, with the laptop in power saver mode.
ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: gnome-shell 45.3-1ubuntu1
ProcVersionSign
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckR
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 12 10:52:57 2024
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2024-02-07 (5 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
JournalErrors:
lut 12 10:52:55 username-laptop systemd[1]: /lib/systemd/
lut 12 10:52:56 username-laptop gnome-shell[6437]: Could not load a pixbuf from icon theme.
lut 12 10:52:57 username-laptop systemd[1]: /lib/systemd/
lut 12 10:52:58 username-laptop systemd[1]: /lib/systemd/
ProcCmdline: /usr/bin/
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, user)
SHELL=/usr/bin/zsh
XDG_RUNTIME_
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageV
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
??? () at /lib/x86_
g_assertion_
st_icon_
??? () at /usr/lib/
??? () at /lib/x86_
Title: gnome-shell crashed with SIGABRT in ???()
UpgradeStatus: Upgraded to noble on 2024-02-07 (5 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
separator:
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 #1959507, 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.