-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extensions settings window do not open in Wayland #413
Comments
Update: it only happens on Wayland. |
App crashes on Wayland only, workaround: |
Thanks but that does not work:
|
Hmmm, this is not the stock Extensions app (it comes from a deb package), this app is something else available in Flathub, so not related to Pop!_OS. The stock Extensions app (gnome-extensions-app) works fine using the environment variable as explained. |
Actually it seems to be a problem between GTK and Nvidia proprietary drivers, it works fine here (Pop 22.04/Wayland on AMD). I can get the app to launch on Nvidia using the command above, but all settings windows crash. No luck changing the renderer either, with or without forcing it to use Xwayland:
|
NVIDIA Wayland isn't supported so if that's the only issue I think we can close this. |
If you have hybrid graphics with AMD, try:
or 0 instead of 1 (to use iGPU). |
So the first one must be AMD, but both are not working.
This must be an AMD driver issue, hopefully I'll receive some fixes with HWE updates. Anywy @lfom thank you for help! |
@komorebithrowsatable Are you using Wayland with AMD? The command below also fails? If yes, stock Pop installation?
|
How did you upgrade to 22.04? (Fresh install / Upgrade)
Upgraded from 21.10. Deleted old extensions. Just the system extensions are installed.
Related Application and/or Package Version (run
apt policy $PACKAGE NAME
):gnome-shell
Issue/Bug Description:
Attempting to open the settings window of any extension fails.
Relevant journal logs:
Steps to reproduce (if you know):
Expected behavior:
The settings window should open.
Other Notes:
As it might be related to the GPU, I'll leave the driver versions I'm using.
The text was updated successfully, but these errors were encountered: