[Unsolved] Screen tearing, slow text input, screen flashing in games

Papapuff · 2024-03-08 21:03:29

Hello guys! This is my second post, after the initial one where I asked for help to install Arch all the way, which I did, congrats to you. Now, my next issue is that, after I entered the desktop environment, I noticed slow typing speeds and it's almost like lagging. Another thing I observed is that, when trying to run, for example, Factorio, black flashes are all over the screen, making any kind of gameplay unplayable and frustrating. Please, could you land me a hand of help and guide me to get through this behavior? I'm day 1 Arch user so please bare with me if I ask for a dumbed down version of how to do some commands or more explicit steps. I will provide any kind of info that is helpful and requested.
AMD Ryzen 3600x
Nvidia 3060
b450 mortar max

Edit: I have two monitors, 1 60hz and 1 144hz. Factorio runs without flicker on the 60hz monitor, so I set the 144hz monitor to 60hz, runs well, no flicker. So I'm not able to run apps using 144hz. But the typing lag/stutter is still present (I checked on Brave browser and on Chrome browser). This could narrow the issue down.
https://media.giphy.com/media/v1.Y2lkPT … -large.gif

Last edited by Papapuff (2024-03-26 10:56:16)

seth · 2024-03-09 15:54:40

We'll first need to know what you're actually running

loginctl session-status

and assuming it'S X11, please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

AaAaAAaaAAaARCH · 2024-03-09 16:41:15

Nvidia Linux drivers are bad at high refresh rates in my experience. Also use displayport, as HDMI seems to run worse than displayport at high refresh rates (if at all). My graphics glitches dissapeared when moving to AMD, although it also has some crashes.

Papapuff · 2024-03-09 17:00:11

Guys, before I tried to gather info using "loginctl session-status" I did a "sudo pacman -Sy" and rebooted. Currently booting stopped at "Terminate Plymouth Boot Screen" and won't proceed further so I need to figure what broke now before continuing with anything else...

Sitting in tty2 and looking at this error after I ran "systemctl status sddm" which says this in orange

https://imgur.com/gallery/jJ1ylHk

Last edited by Papapuff (2024-03-09 17:03:52)

seth · 2024-03-09 17:03:36

First off, disable plymouth.
You'll most likely still be able to boot the multi-user.target (2nd link below)

But "sudo pacman -Sy" is inert, it sets you up for partial updates (don't) but will in and by itself not change anything about your system.

Papapuff · 2024-03-09 17:07:09

I'm still in tty but I can't figure out how to remove Plymouth for good, I'm a bit dumb I'm afraid Seth

seth · 2024-03-09 17:13:06

https://wiki.archlinux.org/title/Plymou … parameters

Papapuff · 2024-03-09 17:16:28

I ran plymouth.enable=0 disablehooks=plymouth and the output of that is: -bash: plymouth.enable=0: command not found

seth · 2024-03-09 17:36:21

That's not a command but a kernel parameter.
Do not just copy bluebox text into an interactive shell, that's recipe for a disaster.

Papapuff · 2024-03-09 18:42:10

Well would you be kind to tell me what is the correct command to remove Plymouth ?

Last edited by Papapuff (2024-03-09 20:17:22)

seth · 2024-03-09 21:35:07

"pacman -Rs plymouth" but you really only have to apply the https://wiki.archlinux.org/title/Kernel_parameters

Papapuff · 2024-03-10 12:19:56

So good morning again Seth. Here I come with what I learned and tried. I also reinstalled Arch Linux as I nuked it by mistake. I learned I can enter Kernel parameters by going into my live USB key install, nano /etc/default/grub and typed the lines plymouth.enable=0 disablehooks=plymouth in between the quotes of GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" as per wiki example. Next wiki says:
And then automatically re-generate the grub.cfg file with:
# grub-mkconfig -o /boot/grub/grub.cfg

Now here is what next problem rises: when I hit enter this comes
/usr/bin/grub-probe: error: failed to get canonical path of 'airootfs'

Please tell me if I did anything wrong until this point as I'm learning while walking instructions.

seth · 2024-03-10 14:18:42

Don't edit the grub config of the install iso, that's not going to survive a reboot anyway.
If you want to pass kernel parameters to the install iso, edit the kernel commandline in the grub menu.

However, since you re-installed arch(?) is the plymouth problem still there?
Why did you (re)install plymouth itfp?

Papapuff · 2024-03-10 14:25:11

So the reason I try to enter grub parameters on the install iso on USB key is that I understood I can't enter grub without iso USB key. How can I enter my grub without the iso, on my live arch (not desktop environment but you get what I mean, Im just dumb to know how to express specifically) to get rid of Plymouth and solve my graphical issues for good.

Why I reinstalled arch? Because I tried what I told you before and then encountered another issue at boot "arch linux stopped at reached target graphical interface" and I preferred to reinstall instead of dealing with issue number 1000.

Since I reinstalled which took a bit, hence my slow response, Plymouth is still a problem if I want to get rid of screen tearing, graphical issues, as you said, I gotta disable it.

Note: After Linux reinstall, my system is live, I can use it, but can't play anything due to the graphical issues

Last edited by Papapuff (2024-03-10 14:29:49)

seth · 2024-03-10 14:32:01

I understood I can't enter grub without iso USB key.

That's nonsense.
You're not "entering" grub for this and you most certainly don't need to do it offline.

Start the system normally, when grub appears, select the Arch entry, press "e", find the line that has vmlinuz-linux in it and append the plymouth parameters there.
If you want to disable it with a non-volatile config and cannot boot the installed system because of plymouth, you can edit the grub config after booting the iso, but you'll first have to "arch-chroot /mnt" into the installed system.

Edit: … and in that case, don't forget to mount the /boot partition before. But in doubt just edit the kernel commandline in the grub menu

Last edited by seth (2024-03-10 14:36:34)

Papapuff · 2024-03-10 14:34:59

As I assumed, yes, you're right, I'm doing nonsense, but I gotta ask you something first before doing what you told me.
My system boots (without the iso USB key in pc) in like 10 seconds, in this time I see no grub, it's just lines of code going down then log in screen appears. Could you tell me, please, what am I missing here?

seth · 2024-03-10 14:41:42

Grub is the thing you get before the system boots, provided you installed it as bootloader. Did you? (Because otherwise this is all irrelevant, you'll have to edit the kernel parameters according to the bootloader you actually use)

Papapuff · 2024-03-10 16:35:06

Well, have a look at this and tell me if it is indeed grub or not
https://www.youtube.com/shorts/QqGpk1C9tOY

This is how my system boots everytime

Last edited by Papapuff (2024-03-10 16:56:48)

seth · 2024-03-10 18:04:11

Portrait mode, really?
I can see "something" in probably the center of the screen, but can't make out what that is, then, probably after the KMS switch, boot messages appear, plymouth isn't used, it seems.
The system then seems to boot and the GUI shows up on the monitor to the left?

You wrote:

Guys, before I tried to gather info using "loginctl session-status" I did a "sudo pacman -Sy" and rebooted. Currently booting stopped at "Terminate Plymouth Boot Screen" and won't proceed further so I need to figure what broke now before continuing with anything else...

is this actually still the case?

Papapuff · 2024-03-10 21:47:05

So Seth, I tried to film the whole booting process in slow motion because the lines of text were going too fast. Ianaged to get all the booting text here in 4 images:
https://imgur.com/gallery/cJvEG39

Also, the output of "loginctl session-status" is:
https://imgur.com/gallery/uN2i7re

The thing in the middle that you saw was the AMD "Arsenal Gaming" motherboard logo.

seth · 2024-03-10 22:19:42

Why are you posting photos of text?
Afaict the problem where you couldn't boot at all is gone?

You're in a plasma/wayland session, started by sddm.

So returning to the original problem: do you encounter that when starting an X11 KDE session?
(Afaiu you can select the session in the lower right corner of the SDDM login screen)
What's the ouptut of "qdbus org.kde.KWin /KWin supportInformation"?
(Don't post a picture, you can just upload that following the tip in the first link below.)

Papapuff · 2024-03-10 23:27:55

The problem where I couldn't boot at all it's solved Seth, as I said, because I reinstalled Linux again so that's no more worries. And the photos I showed you are related to the video from which you couldn't figure out what bootloader I have.
Also the output of "qdbus org.kde.KWin /KWin supportInformation" is:

[submuffin@papapuff ~]$ qdbus org.kde.KWin /KWin supportInformation
KWin Support Information:
The following information should be used when requesting support on e.g. https://discuss.kde.org.
It provides information about the currently running instance, which options are used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a paste bin service
like https://paste.kde.org instead of pasting into support threads.

==========================

Version
=======
KWin version: 6.0.1
Qt Version: 6.6.2
Qt compile version: 6.6.2
XCB compile version: 1.16.1

Operation Mode: Xwayland

Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_X11_XCB: yes
HAVE_GLX: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 12302004
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==========
Plugin: org.kde.breeze
Theme: 
Plugin recommends border size: None
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,0,400,0,0,0,0,0,0,0,0,0,0,1
smallSpacing: 2
largeSpacing: 10

Output backend
==============
Name: DRM
Atomic Mode Setting on GPU 0: true

Cursor
======
themeName: breeze_cursors
themeSize: 24

Options
=======
focusPolicy: ClickToFocus
xwaylandCrashPolicy: 1
xwaylandMaxCrashCount: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
activeMouseScreen: true
placement: 5
activationDesktopPolicy: SwitchToOtherDesktop
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: false
focusStealingPreventionLevel: 1
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: MouseRaise
commandActiveTitlebar2: MouseNothing
commandActiveTitlebar3: MouseOperationsMenu
commandInactiveTitlebar1: MouseActivateAndRaise
commandInactiveTitlebar2: MouseNothing
commandInactiveTitlebar3: MouseOperationsMenu
commandWindow1: MouseActivateRaiseAndPassClick
commandWindow2: MouseActivateAndPassClick
commandWindow3: MouseActivateAndPassClick
commandWindowWheel: MouseNothing
commandAll1: MouseUnrestrictedMove
commandAll2: MouseToggleRaiseAndLower
commandAll3: MouseUnrestrictedResize
keyCmdAllModKey: 16777250
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
compositingMode: 1
useCompositing: true
hiddenPreviews: 1
glSmoothScale: 2
glStrictBinding: true
glStrictBindingFollowsDriver: true
glPreferBufferSwap: AutoSwapStrategy
glPlatformInterface: 2
windowsBlockCompositing: true
allowTearing: true

Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 75
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
=======
Active screen follows mouse:  yes
Number of Screens: 2

Screen 0:
---------
Name: HDMI-A-1
Enabled: 1
Geometry: 0,0,1920x1080
Scale: 1
Refresh Rate: 60000
Adaptive Sync: incapable
Screen 1:
---------
Name: DP-1
Enabled: 1
Geometry: 1920,0,1920x1080
Scale: 1
Refresh Rate: 144001
Adaptive Sync: never

Compositing
===========
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 3060/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 550.54.14
OpenGL platform interface: EGL
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 550.54.14
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
X server version: 1.23.2
Linux kernel version: 6.7.9
Direct rendering: Requires strict binding: no
Virtual Machine:  no
OpenGL 2 Shaders are used

Loaded Effects:
---------------
screenshot
outputlocator
colorpicker
zoom
screenedge
blur
contrast
login
sessionquit
logout
slidingpopups
windowaperture
slide
scale
fadingpopups
maximize
squash
morphingpopups
frozenapp
fullscreen
dialogparent
windowview
tileseditor
overview
highlightwindow
blendchanges
startupfeedback
screentransform
kscreen

Currently Active Effects:
-------------------------
blur
contrast

Effect Settings:
----------------
screenshot:

outputlocator:

colorpicker:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
focusTrackingEnabled: false
textCaretTrackingEnabled: false
focusDelay: 350
moveFactor: 20
targetZoom: 1

screenedge:

blur:

contrast:

login:
pluginId: login
isActiveFullScreenEffect: false

sessionquit:
pluginId: sessionquit
isActiveFullScreenEffect: false

logout:
pluginId: logout
isActiveFullScreenEffect: false

slidingpopups:
slideInDuration: 150
slideOutDuration: 250

windowaperture:
pluginId: windowaperture
isActiveFullScreenEffect: false

slide:
horizontalGap: 45
verticalGap: 20
slideBackground: true

scale:
pluginId: scale
isActiveFullScreenEffect: false

fadingpopups:
pluginId: fadingpopups
isActiveFullScreenEffect: false

maximize:
pluginId: maximize
isActiveFullScreenEffect: false

squash:
pluginId: squash
isActiveFullScreenEffect: false

morphingpopups:
pluginId: morphingpopups
isActiveFullScreenEffect: false

frozenapp:
pluginId: frozenapp
isActiveFullScreenEffect: false

fullscreen:
pluginId: fullscreen
isActiveFullScreenEffect: false

dialogparent:
pluginId: dialogparent
isActiveFullScreenEffect: false

windowview:
activeView: 
delegate: 
animationDuration: 300
layout: 1
ignoreMinimized: false
mode: 
partialActivationFactor: 0
gestureInProgress: false
searchText: 
selectedIds: 

tileseditor:
activeView: 
delegate: 
animationDuration: 200

overview:
activeView: 
delegate: 
animationDuration: 300
layout: 1
ignoreMinimized: false
filterWindows: true
organizedGrid: true
overviewPartialActivationFactor: 0
overviewGestureInProgress: false
transitionPartialActivationFactor: 0
transitionGestureInProgress: false
gridPartialActivationFactor: 0
gridGestureInProgress: false
desktopOffset: 
searchText: 

highlightwindow:

blendchanges:

startupfeedback:
type: 1

screentransform:

kscreen:


Loaded Plugins:
---------------
BounceKeysPlugin
StickyKeysPlugin
buttonsrebind
krunnerintegration
nightcolor
screencast

Available Plugins:
------------------
BounceKeysPlugin
StickyKeysPlugin
buttonsrebind
krunnerintegration
nightcolor
screencast

.

Update: Reinstalled 3rd time Linux, installed GRUB as bootloader and I nano the /etc/default/grub to insert the kernel parameters (I inserted GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet nvidia-drm.modeset=1 plymouth.enable=0 disablehooks=plymouth i915.enable_psr=0 i915.enable_fbc=0" these parameters)
So the parameters had no effect on the tearing/flickering problem which still occurs.

Last edited by Papapuff (2024-03-11 17:00:32)

seth · 2024-03-11 17:18:54

This has nothing to do w/ plymouth anymore.
Plymouth was only what apparently at some point prevented the boot completion.

The i915 parameters should™ be moot, too, since you're running X11 on nvidia.
Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

You've two outputs, 60Hz and 144Hz, the latter not on VRR.
Does the flicker/tearing remain if you
1. disable the compositor (SHIFT+Alt+F12)
2. set the 144Hz output to 60Hz
3. Remove one of the outputs
4. Enable VRR for the 144Hz output, https://wiki.archlinux.org/title/Variab … _on_NVIDIA
5. Run KDE on wayland?

Lastly: does the flicker and tearing happen on both monitors or only one of them? Which?

Papapuff · 2024-03-11 18:53:28

Excuse me as I forgot to add basic information about the problem such as: Both monitors had the flicker problem, doesn't matter if I game or watch a video. Refresh rate didn't fixed the problem. It occurred on both monitors, both 60hz, or one monitor 60hz.
Again, my apology as maybe I misinterpreted but I assumed you wanted me to post the Xorg log, so I have to install Xorg effectively, which I did and now the flickering is not present anymore after I executed "sudo startx" in Konsole saw blackscreen, rebooted and flicker was gone. I tested Factorio to see if flicker is still present and it's not.

Only major lag is present now on desktop animations/when moving windows, bringing windows from background to foreground and vice versa. I'm trying to deal with this issue now. I enabled VRR, disabled/enabled compositor but didn't helped.
I am running KDE wayland since the begining of the issue, at least that's what it says when I choose it in the log in window from upper left corner but now chose X11 to proceed further as you said.
I removed the plymouth parameters from /etc/default/grub as you said it no longer helps to resolve a solved issue.
Also, if by "post your xorg log" you mean "run this command in konsole: tail -f ~/.local/share/xorg/Xorg.0.log | ts which outputs

bash: ts: command not found
tail: cannot open '/home/submuffin/.local/share/xorg/Xorg.0.log' for reading: No such file or directory
tail: no files remaining
.

Edit: Nevermind, it's still present, haven't done anything but search the web to fix another problem and tried Factorio again, just to see the graphical tearing/flicker again...idk at this point what causes it. But on X11 it seems after a restart, my sudo nvidia-settings display all the proper setting tabs without any Konsole error as it does on Wayland.
If it helps sometimes I don't have this errors when I'm doing sudo nvidia-settings, sometimes it works, I don't know why it fails

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.276: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(nvidia-settings:1606): Gtk-CRITICAL **: 21:32:58.294: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed

(nvidia-settings:1606): Gtk-CRITICAL **: 21:32:58.295: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.295: invalid (NULL) pointer instance

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.295: g_signal_handlers_block_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(nvidia-settings:1606): Gtk-CRITICAL **: 21:32:58.295: gtk_toggle_button_get_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.295: invalid (NULL) pointer instance

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.295: g_signal_handlers_unblock_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.295: invalid (NULL) pointer instance

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.295: g_signal_handlers_block_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(nvidia-settings:1606): Gtk-CRITICAL **: 21:32:58.295: gtk_toggle_button_get_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.295: invalid (NULL) pointer instance

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.295: g_signal_handlers_unblock_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(nvidia-settings:1606): Gtk-CRITICAL **: 21:32:58.295: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed

(nvidia-settings:1606): Gtk-CRITICAL **: 21:32:58.295: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.296: invalid (NULL) pointer instance

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.296: g_signal_handlers_block_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(nvidia-settings:1606): Gtk-CRITICAL **: 21:32:58.296: gtk_toggle_button_get_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.296: invalid (NULL) pointer instance

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.296: g_signal_handlers_unblock_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.297: invalid (NULL) pointer instance

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.297: g_signal_handlers_block_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(nvidia-settings:1606): Gtk-CRITICAL **: 21:32:58.297: gtk_toggle_button_get_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.297: invalid (NULL) pointer instance

(nvidia-settings:1606): GLib-GObject-CRITICAL **: 21:32:58.297: g_signal_handlers_unblock_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(nvidia-settings:1606): Gtk-CRITICAL **: 21:32:58.297: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed

(nvidia-settings:1606): Gtk-CRITICAL **: 21:32:58.297: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed
.

Last edited by Papapuff (2024-03-11 20:42:05)

seth · 2024-03-11 23:47:22

Operation Mode: Xwayland

When you called "qdbus org.kde.KWin /KWin supportInformation" you were running KDE on X11 - also you cannot suspend the compositor on wayland, the wayland compositor is the wayland display server.

after I executed "sudo startx" in Konsole

Don't sudo that. Also "startx" will just get you a simple X11 server at best (trying to start xterm and twm) and then immediately terminate. (And quite possibly X11 won't start at all out of the wayland context)
You'd rather select KDE on X11 in your DM (SDDM, I assume)

The position of your Xorg log depends on how X11 is started, https://wiki.archlinux.org/title/Xorg#General
Most likely /var/log/Xorg.0.log

cat /var/log/Xorg.0.log | curl -F 'file=@-' 0x0.st

my sudo nvidia-settings

Do not sudo that either! In general, stop prepending sudo to things unless you *know* that you need to run something as root, and the rule of thumb is that you don't run GUI as root, period.

Arch Linux

#1 2024-03-08 21:03:29

[Unsolved] Screen tearing, slow text input, screen flashing in games

#2 2024-03-09 15:54:40

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#3 2024-03-09 16:41:15

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#4 2024-03-09 17:00:11

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#5 2024-03-09 17:03:36

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#6 2024-03-09 17:07:09

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#7 2024-03-09 17:13:06

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#8 2024-03-09 17:16:28

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#9 2024-03-09 17:36:21

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#10 2024-03-09 18:42:10

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#11 2024-03-09 21:35:07

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#12 2024-03-10 12:19:56

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#13 2024-03-10 14:18:42

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#14 2024-03-10 14:25:11

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#15 2024-03-10 14:32:01

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#16 2024-03-10 14:34:59

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#17 2024-03-10 14:41:42

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#18 2024-03-10 16:35:06

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#19 2024-03-10 18:04:11

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#20 2024-03-10 21:47:05

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#21 2024-03-10 22:19:42

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#22 2024-03-10 23:27:55

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#23 2024-03-11 17:18:54

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#24 2024-03-11 18:53:28

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

#25 2024-03-11 23:47:22

Re: [Unsolved] Screen tearing, slow text input, screen flashing in games

Board footer