Skip to content
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

X11 GNOME broken on accelerated GPU drivers #184

Closed
JamiKettunen opened this issue Jun 10, 2023 · 3 comments
Closed

X11 GNOME broken on accelerated GPU drivers #184

JamiKettunen opened this issue Jun 10, 2023 · 3 comments

Comments

@JamiKettunen
Copy link
Contributor

Upon launching GNOME on Xorg from GDM for example on my RX 6600 pointer follows mouse movement but the desktop rendering itself doesn't go further than a single frame which can be advanced by switching to another TTY and back again to get the next one.

A workaround may be the following as /usr/share/X11/xorg.conf.d/99-kms-no-pageflip.conf for example:

Section "Device"
       Identifier "kms"
       Driver "modesetting"
       Option "PageFlip" "off"
EndSection

Keep in mind this may cause problems such as screen tearing etc.

Reportedly @q66 also tested Enlightenment (X11) without the above workaround and it worked fine.

Upstream report: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9152

q66 added a commit that referenced this issue Sep 10, 2023
It seems the issue was caused by me having a leftover compiled
glib schema in /usr/local, probably from when trying to figure
out #184 and was
trying older versions of mutter in the process.
@q66
Copy link
Contributor

q66 commented Sep 19, 2023

This will probably be wontfix, it seems Fedora might drop X11 session support in GNOME relatively soon (https://www.phoronix.com/news/Fedora-40-Eyes-No-X11-Session) which means it should become possible in upstream to disable it - Chimera will probably follow suit here shortly (AFAICT there is practically no benefit to running X11 GNOME)

@q66
Copy link
Contributor

q66 commented Oct 14, 2023

well, i just tried it again and... it wroks for me now?

@q66
Copy link
Contributor

q66 commented Oct 14, 2023

@nekopsykose confirmed this also works on amd, so i guess it's fine now

@q66 q66 closed this as completed Oct 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants