You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried asking on Slack (especially for configuration related issues)
Thank you to develop and maintain Regolith, It is awesome!
Describe the bug
I've just reinstalled my laptop with Ubuntu 24.04 and regolith 3.2 beta 2. Picom is regularly crashing on workspace/window switching with the following error:
It seems to be linked to this Picom's issue which is fixed on the last Picom release (v11.2) and Regolith is using Picom v10 for now.
To Reproduce
Steps to reproduce the behavior:
Default regolith 3.2 beta 2 installation with ubuntu 24.04, X11 and Picom as compositor.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Configuration file(s)
Please attach or mention any customization you've done to configuration files which might have an impact on the bug you are describing. It'll help us determine the root cause of your issue.
Installation Details
Regolith Install Type: PPA
Regolith Version: 3.2 beta 2
PPA url: [default: ppa:regolith-linux/release]
Host OS (for PPA): Ubuntu 24.04
Additional context
The text was updated successfully, but these errors were encountered:
Thank you to develop and maintain Regolith, It is awesome!
Describe the bug
I've just reinstalled my laptop with Ubuntu 24.04 and regolith 3.2 beta 2. Picom is regularly crashing on workspace/window switching with the following error:
It seems to be linked to this Picom's issue which is fixed on the last Picom release (v11.2) and Regolith is using Picom v10 for now.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Configuration file(s)
Please attach or mention any customization you've done to configuration files which might have an impact on the bug you are describing. It'll help us determine the root cause of your issue.
Installation Details
Additional context
The text was updated successfully, but these errors were encountered: