You are not logged in.
Hi everyone,
I have problems configuring compton (compton-tryone-git package from AUR). I found a configuration where I have no screen tearing, but I have other problems that disappear as soon as I turn compton off.
Please see what the problem looks like here:
https://gfycat.com/DifficultDeafeningKinglet
Sorry for the low quality gif. I tried to make a proper screencast, but failed miserably after trying for 30 minutes. I tried with ffmpeg, but whatever framerate I use, it did not record the blinking, so I filmed my screen with my phone...
You can however see what the problem is: in the gif, I'm simply scrolling through a list in pamac. There are some sort of shadow images appearing and flashing. A window refresh problem?
Can you help me sort this out? I tried changing my compton configuration, but nothing seemed to work.
I have no DE, just BSPWM as a WM.
Last edited by neopium (2019-08-12 19:22:59)
Offline
Try running compton with the flag --no-fading-open-close.
If this does not help, then you can switch to the modesetting driver: https://wiki.archlinux.org/index.php/In … _early_KMS
Offline
Thanks for your answer.
Unfortunately, the --no-fading-open-close frag did not change anything.
I don't really understand what the "modesetting driver" means, sorry. Your link to the Arch wiki points to the Intel graphics page, but I have an AMD processor with no integrated graphics and an NVidia card with proprietary drivers installed.
Should I follow this instead? https://wiki.archlinux.org/index.php/NV … de_setting
Offline
Your config has "glx-swap-method = "buffer-age";" - I'd try using the default here and please post your xorg.conf (for driver H/W config - if you're using the nvidia blob, the modesetting driver will NOT work!)
Offline
Here is my xorg.conf file:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 430.34
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce RTX 2070 Super"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSectionRegarding the glx-swap-method, I chose the buffer-age method because this helped me get rid of screen tearing (or so I thought).
I changed to the default (undefined) and it seems to work. I have to go to work however so I don't have time to test it for too long.
I'll update the post tonight (an maybe mark it SOLVED).
Thanks both for your help
Offline
Remove that file (see the Xorg wiki page on why static xorg configs are stupid)
What you could try was
/etc/X11/xorg.conf.d/20-nvidia.conf
Section "Device"
Identifier "Default nvidia Device"
Driver "nvidia"
Option "NoLogo" "True" # no ads
Option "CoolBits" "24" # possibly more options in nvidia-settings
Option "TripleBuffer" "True" # 1st important setting
Option "UseNvKmsCompositionPipeline" "false" # https://devtalk.nvidia.com/default/topic/1029484/-various-all-distros-numerous-performance-amp-rendering-issues-on-390-25/?offset=110#reply
EndSectionAnd whether that works better along the buffer-age usage. If TripleBuffer cuts it, rather comment the other value.
Offline
OK, I have deleted my xorg.conf file and added the /etc/X11/xorg.conf.d/20-nvidia.conf you suggested.
Everything is working fine: no blinking, not screen tearing.
Buffer-age still doesn't work however.
I don't understand what you mean by "If TripleBuffer cuts it, rather comment the other value." You mean I should comment "UseNvKmsCompositionPipeline"? Which "other value" are you refering to?
Offline
You mean I should comment "UseNvKmsCompositionPipeline"?
This. It activates a deprecated legacy path in the driver.
Offline
Did comment the line. Works great without buffer-age, blinks with it.
I guess I'll keep the default, then.
Offline