Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#74388 - [gnome-control-center 42.0-1] Clicking on Notifications or Applications freezes the settings app
Attached to Project:
Arch Linux
Opened by Aaron (aaronrancsik) - Thursday, 07 April 2022, 14:03 GMT
Last edited by Toolybird (Toolybird) - Monday, 29 May 2023, 00:46 GMT
Opened by Aaron (aaronrancsik) - Thursday, 07 April 2022, 14:03 GMT
Last edited by Toolybird (Toolybird) - Monday, 29 May 2023, 00:46 GMT
|
DetailsDescription:
- Clicking on Notifications or Applications freezes the settings app - Only on wayland. On X11 session it works fine. - After it freeze clicks has no visual affect, only the close button is working, but when I reopen it will start in the last click's category. Additional info: * package version(s) 42.0-1] * config and/or log files etc. - no relevant `journalctl -f` log. Steps to reproduce: Just click the Applications or the Notifications category from |
This task depends upon
Closed by Toolybird (Toolybird)
Monday, 29 May 2023, 00:46 GMT
Reason for closing: Upstream
Additional comments about closing: See comments
Monday, 29 May 2023, 00:46 GMT
Reason for closing: Upstream
Additional comments about closing: See comments
So I would say the transition in and out with these specific categories makes the freeze.
EDIT: Also this is just a visual freeze the settings is looks like functioning underneath. (I think because the logs show the switches between the categories, that I can't see visually)
GSK_RENDERER=cairo gnome-control-center
If that works it's likely this one: https://gitlab.gnome.org/GNOME/gtk/-/issues/4773
EDIT:
From the linked issue I tried MESA_DEBUG=1.
And I've got this:
Mesa: User error: GL_INVALID_OPERATION in glGetFramebufferAttachmentParameteriv(invalid pname GL_FRAMEBUFFER_ATTACHMENT_RED_SIZE)
Mesa: User error: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)
Mesa: User error: GL_INVALID_FRAMEBUFFER_OPERATION in glDrawArrays
So yeah this is definitely the upstream issue for me, thanks nice finding.