Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1834727 - gnome-shell killed by SIGABRT due to _st_theme_resolve_url: assertion failed: (base_file)
Summary: gnome-shell killed by SIGABRT due to _st_theme_resolve_url: assertion failed:...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 32
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:6b2078f60dbccd3f894fcb7ee59...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-12 10:06 UTC by Niko
Modified: 2021-05-25 16:14 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1516633
Environment:
Last Closed: 2021-05-25 16:14:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
journalctl -S "10:34:06" -U "10:36:12" > journal.txt (117.87 KB, text/plain)
2020-05-12 10:06 UTC, Niko 		no flags Details
coredumpctl gdb > coredump.txt (32.12 KB, text/plain)
2020-05-12 10:08 UTC, Niko 		no flags Details
coredump backtrace (3.61 KB, text/plain)
2021-03-02 16:38 UTC, Mateus Rodrigues Costa 		no flags Details
View All

Description Niko 2020-05-12 10:06:13 UTC 
Created attachment 1687629 [details]
journalctl -S "10:34:06" -U "10:36:12" > journal.txt

This is a follow up from my comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1516633#c22

I'm trying to report this crash manually, as abrt considers it a duplicate of 1516633 (which it isn't) and refuses to report it.
The backtrace is here:
https://retrace.fedoraproject.org/faf/reports/2904053/
It seems to come from some JS code calling st_theme_unload_stylesheet when the screen is being locked, but something about the following style changes fails.
This is new since updating to fedora 32 and happens pretty often when locking the screen or suspending.
My syslog says:
--Mai 11 12:38:28 escher gnome-shell[2311]: **
Mai 11 12:38:28 escher gnome-shell[2311]: St:ERROR:../src/st/st-theme.c:1048:_st_theme_resolve_url: assertion failed: (base_file)
Mai 11 12:38:28 escher gnome-shell[2311]: Bail out! St:ERROR:../src/st/st-theme.c:1048:_st_theme_resolve_url: assertion failed: (base_file)
Mai 11 12:38:28 escher gnome-shell[2311]: == Stack trace for context 0x564a37a41480 ==
Mai 11 12:38:28 escher gnome-shell[2311]: #0   564a38d427d8 i   resource:///org/gnome/shell/ui/extensionSystem.js:107 (2936af068358 @ 467)
Mai 11 12:38:28 escher gnome-shell[2311]: #1   564a38d42748 i   resource:///org/gnome/shell/ui/extensionSystem.js:593 (2936af06a538 @ 15)
Mai 11 12:38:28 escher gnome-shell[2311]: #2   7ffd42f6f5a0 b   self-hosted:266 (2e7975face20 @ 259)
Mai 11 12:38:28 escher gnome-shell[2311]: #3   564a38d426b8 i   resource:///org/gnome/shell/ui/extensionSystem.js:592 (2936af06a4c0 @ 98)
Mai 11 12:38:28 escher gnome-shell[2311]: #4   564a38d42628 i   resource:///org/gnome/shell/ui/extensionSystem.js:610 (2936af06a5b0 @ 82)
Mai 11 12:38:28 escher gnome-shell[2311]: #5   7ffd42f70830 b   self-hosted:1009 (1d8d6269e358 @ 423)
Mai 11 12:38:28 escher gnome-shell[2311]: #6   7ffd42f70930 b   resource:///org/gnome/gjs/modules/core/_signals.js:133 (2e7975fac880 @ 427)
Mai 11 12:38:28 escher gnome-shell[2311]: #7   7ffd42f71850 b   resource:///org/gnome/shell/ui/sessionMode.js:195 (1d8d62624d30 @ 286)
Mai 11 12:38:28 escher gnome-shell[2311]: #8   564a38d423c8 i   resource:///org/gnome/shell/ui/sessionMode.js:156 (1d8d62624b50 @ 40)
Mai 11 12:38:28 escher gnome-shell[2311]: #9   564a38d42310 i   resource:///org/gnome/shell/ui/screenShield.js:571 (1d8d6260fd30 @ 191)
Mai 11 12:38:28 escher gnome-shell[2311]: #10   564a38d42250 i   resource:///org/gnome/shell/ui/screenShield.js:620 (1d8d6260fda8 @ 419)
Mai 11 12:38:28 escher gnome-shell[2311]: #11   564a38d421b8 i   resource:///org/gnome/shell/ui/shellDBus.js:378 (1d8d626158f8 @ 67)
Mai 11 12:38:28 escher gnome-shell[2311]: #12   564a38d420d0 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:371 (2e7975f9c1f0 @ 949)
Mai 11 12:38:28 escher gnome-shell[2311]: #13   564a38d42018 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404 (2e7975f9c3d0 @ 34)
--

When I try to report it via abrt, I get the following output:
Generating backtrace
Backtrace is too big (545384 bytes), reducing depth to 512
Backtrace is too big (543322 bytes), reducing depth to 256
Backtrace is too big (543322 bytes), reducing depth to 128
Backtrace is too big (543322 bytes), reducing depth to 64
Backtrace is generated and saved, 98528 bytes
Looking for similar problems in bugzilla
Duplicate bugzilla bug '#1516633' was found
Searching for updates
No updates for this package found

Followed by the message:
Reporting is disabled because the generated backtrace is of low informational value.


I don't see anything extension-related in the trace, so I guess this is a bug in the shell itself. I have these extensions installed on GNOME Shell 3.36.2:
$ gnome-extensions list
windowoverlay-icons.cz
disconnect-wifi
refresh-wifi
caffeine
gTile@vibou
gsconnect.io
appindicatorsupport.com
drive-menu.github.com
apps-menu.github.com
background-logo
horizontal-workspaces.github.com
launch-new-instance.github.com
places-menu.github.com
window-list.github.com
user-theme.github.com
GPaste.org
Comment 1 Niko 2020-05-12 10:08:32 UTC 
Created attachment 1687630 [details]
coredumpctl gdb > coredump.txt
Comment 2 Mateus Rodrigues Costa 2021-03-02 16:37:39 UTC 
Just got this yesterday on Fedora 33 and gnome-shell 3.38.3-1.fc33.x86_64

My extensions, in case it's useful:

sound-output-device-chooser
dim-on-battery.com
caffeine
background-logo
gamemode.me
user-theme.github.com
workspace-indicator.github.com
drive-menu.github.com
dash-to-dock.com
appindicatorsupport.com
windowoverlay-icons.cz
system-monitor.gmail.com

I will send my backtrace shortly
Comment 3 Mateus Rodrigues Costa 2021-03-02 16:38:42 UTC 
Created attachment 1760263 [details]
coredump backtrace
Comment 4 Fedora Program Management 2021-04-29 16:25:27 UTC 
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Ben Cotton 2021-05-25 16:14:37 UTC 
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.