[SOLVED] Screen tearing issues out of the blue

radumitrescu · 2023-05-11 10:09:17

seth wrote:

Thats not gnome but GDM and you can select a different session there type there.
And it is very much so archlinux.
And you've still no idea about the most basic stuff.

Perhaps... but why do I get the feeling that you're somehow taking this personally? It almost seems like you're offended by my cluelessness.

The way I see it, you either help me or you don't, and I do appreciate your input thus far, but right now, frankly speaking, you're coming across as elitist and condescending.

Last edited by radumitrescu (2023-05-11 11:38:24)

Fuxino · 2023-05-11 11:13:59

radumitrescu wrote:

Uhm... OK... I'm still confused, because I don't ever start gnome. I just turn on my computer and gnome is there... How, specifically, do I start openbox instead of gnome?

First you have to install it. Then you select it in your display manager instead of Gnome. Or you start it with xinit. See: https://wiki.archlinux.org/title/Openbox

radumitrescu · 2023-05-11 11:37:28

Fuxino wrote:

radumitrescu wrote:
Uhm... OK... I'm still confused, because I don't ever start gnome. I just turn on my computer and gnome is there... How, specifically, do I start openbox instead of gnome?
First you have to install it. Then you select it in your display manager instead of Gnome. Or you start it with xinit. See: https://wiki.archlinux.org/title/Openbox

Oh, so it's a session, kind of like X, or Wayland? I thought it was another desktop environment entirely.

Fuxino · 2023-05-11 11:40:26

It's a window manager.

radumitrescu · 2023-05-14 10:58:35

OK, a bit of an update. FWIW...

While I haven't been able to fix this, I am confident enough to say that I narrowed it down to the culprit being either or both Gnome 44/Kernel 6.3.1. But my money's on Gnome 44.

Let me explain how I came to this conclusion. I installed the latest Manjaro Gnome image which ships with Gnome 43, kernel 6.1, and nvidia-530. I tested my game and it ran just fine. I then updated the kernel to 6.3.0 and yet again, the game ran just fine. I then updated to the testing branch which installed Gnome 44 and kernel 6.3.1 and sure enought it's now that the issues starting manifesting.

Because I don't really like anything Manjaro do and stand for, I ditched it in favour of Nobara Project, which still uses Gnome 43, kernel 6.2.14. My plan is to wait out until the Gnome 44 and kernel 6.3.1 makes it to Nobara and if the issues don't start here I'll try Arch again.

Sorry I'm being such a noob and that I can't go through some of the stuff it's been suggested here. I do appreciate everyone's help, despite some elitist and condescending attitudes that have surfaced here.

seth · 2023-05-14 14:54:29

radumitrescu wrote:

Perhaps... but why do I get the feeling that you're somehow taking this personally? It almost seems like you're offended by my cluelessness.
The way I see it, you either help me or you don't, and I do appreciate your input thus far, but right now, frankly speaking, you're coming across as elitist and condescending.

I don't take anything here personally, I'm not offended by your cluelessnes but don't believe that you're using archlinux - or at least you didn't install that yourself (because the *extreme* cluelessnes would preclude that)

You might find that condescending, but picture yourself trying to explain details of perspective, shade and colors to then find the person you're talking to and who claims to hold a MFA being concerned with eating their brush. Sounds funny? Sounds frustrating?
There's a certain expectation when talking to archlinux users, notably that you can expect some minimal understanding of the system.

Back on topic: did you meanwhile figure how to run a different session from GDM?
There're currently too many variables:
1. X11 ./. wayland (did you inspect the display server on manjaro/nobara?)
2. GDM (and also whether GDM runs on X11 or wayland - which is different from gnome)
3. The kernel (6.3.0 ./. 6.3.1)
4. The nvidia driver version (undocumented)
5. The prime situation
6. xf86-video-intel ./. the modesetting driver

If you suspect the cause to be mutter (gnome compositor) the easiest way to confirm that is to start a different session (openbox) on the same, malfunctioning setup.

radumitrescu · 2023-05-14 15:39:42

seth wrote:

I don't take anything here personally, I'm not offended by your cluelessnes but don't believe that you're using archlinux - or at least you didn't install that yourself (because the *extreme* cluelessnes would preclude that)

You can believe whatever you want. The truth remains the same. I AM (well, rather was) using Arch Linux. And I DID install it myself. The archinstall script is pretty easy even for a clueless noob like myself.

seth wrote:

Back on topic: did you meanwhile figure how to run a different session from GDM?
There're currently too many variables:
1. X11 ./. wayland (did you inspect the display server on manjaro/nobara?)

Yes. It's X11. I check in the about section of Gnome. I chose it specifically when logging into the OS. It's stated clearly by mangohud. All these were the case when I used Arch.

There was that confusion about wayland, but I think I addressed that and that we should move on. It's a non issue by now. Everything is to do with X11.

seth wrote:

2. GDM (and also whether GDM runs on X11 or wayland - which is different from gnome)

Yes. I was using GDM on X11.

seth wrote:

3. The kernel (6.3.0 ./. 6.3.1)

I have a strong hunch it's not the kernel, but Gnome 44 that is the culprit. However, it's just a hunch.

seth wrote:

4. The nvidia driver version (undocumented)

It's in the inxi output. 530.41.03

seth wrote:

5. The prime situation

What about it? I run games with prime-run in Steam.

seth wrote:

6. xf86-video-intel ./. the modesetting driver

I normally never install that. I just did it as a Hail Mary, but it didn't do anything... good or bad.

seth wrote:

If you suspect the cause to be mutter (gnome compositor) the easiest way to confirm that is to start a different session (openbox) on the same, malfunctioning setup.

I did install and log into openbox and I couldn't find a way to run the game from within it. And by then, I was so frustrated with this whole issue that I just didn't have it in me to research that. So I just installed Nobara so I can actually use my computer... I've been troubleshooting this for a full seven days with no succes.

Thank you for your continued input.

radumitrescu · 2023-05-16 13:02:31

As per this reddit comment there seems to have been a regression when Gnome moved to 44. However, the merge request linked as a temporary solution left me baffled. I have no idea if and how I can fix this.

Any help?

Last edited by radumitrescu (2023-05-16 13:04:47)

seth · 2023-05-16 15:41:33

You'll have to rebuild mutter and apply the suggested patch, https://wiki.archlinux.org/title/Arch_Build_System
Or you wait until upstream has fixed their stuff - there's quite some debate on the patch and it's open for a month - so probably not a silver bullet solution.

radumitrescu · 2023-05-17 05:09:37

On first glance, installing https://aur.archlinux.org/packages/mutter-performance and https://aur.archlinux.org/packages/gnom … erformance seems to have solved the issue.

Arch Linux

#26 2023-05-11 10:09:17

Re: [SOLVED] Screen tearing issues out of the blue

#27 2023-05-11 11:13:59

Re: [SOLVED] Screen tearing issues out of the blue

#28 2023-05-11 11:37:28

Re: [SOLVED] Screen tearing issues out of the blue

#29 2023-05-11 11:40:26

Re: [SOLVED] Screen tearing issues out of the blue

#30 2023-05-14 10:58:35

Re: [SOLVED] Screen tearing issues out of the blue

#31 2023-05-14 14:54:29

Re: [SOLVED] Screen tearing issues out of the blue

#32 2023-05-14 15:39:42

Re: [SOLVED] Screen tearing issues out of the blue

#33 2023-05-16 13:02:31

Re: [SOLVED] Screen tearing issues out of the blue

#34 2023-05-16 15:41:33

Re: [SOLVED] Screen tearing issues out of the blue

#35 2023-05-17 05:09:37

Re: [SOLVED] Screen tearing issues out of the blue

Board footer