Screen glitch/blur away

Hi everybody!
For like 1 month I have a problem with Garuda Linux. My screen is randomly blurring away.
Randomly my screen goes away, it will not be black, it will be blurry, but very - very blurred, I am just seeing the main colors of what would be on the screen.
I don't have a picture about it, but if It will happen next time, I am going to take a picture.
If this glitch happens, I can control the PC but I can't really see much, so I just hard reset my PC.
I just updated my system too!
What would be the solution for this? Or is there like a key bind for refreshing drivers, like Windows has? It would maybe a kind of half solution for my problem - it is really annoying.

My inxi -Faz output:

System:    Kernel: 5.15.7-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=e1fd8aa5-3909-4e25-beac-5e11b1b3a928
rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.23.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:   Type: Desktop Mobo: ASUSTeK model: STRIX B250G GAMING v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 0809 date: 07/07/2017
CPU:       Info: Quad Core model: Intel Core i5-7500 bits: 64 type: MCP arch: Kaby Lake family: 6
model-id: 9E (158) stepping: 9 microcode: EA cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 27199
Speed: 3637 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 3637 2: 3708 3: 3734 4: 3692
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: ASUSTeK driver: nvidia v: 495.46
alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1c03 class-ID: 0300
Display: x11 server: X.Org 1.21.1.1 compositor: kwin_x11 driver: loaded: nvidia
unloaded: modesetting alternate: fbdev,nouveau,nv,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 5520x1163 s-dpi: 88 s-size: 1594x335mm (62.8x13.2") s-diag: 1629mm (64.1")
Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") diag: 686mm (27")
Monitor-2: HDMI-1 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") diag: 686mm (27")
Monitor-3: DP-1 res: 1680x1050 dpi: 91 size: 470x300mm (18.5x11.8") diag: 558mm (22")
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:     Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
Device-2: NVIDIA GP106 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 01:00.1 chip-ID: 10de:10f1 class-ID: 0403
Device-3: Kingston HyperX Cloud II Wireless type: USB driver: hid-generic,snd-usb-audio,usbhid
bus-ID: 1-7:3 chip-ID: 0951:1718 class-ID: 0300 serial: <filter>
Sound Server-1: ALSA v: k5.15.7-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.41 running: yes
Network:   Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    Local Storage: total: 1.02 TiB used: 43.36 GiB (4.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SUV400S37120G size: 111.79 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 87RA
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD10EZRZ-00HTKB0 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400
serial: <filter> rev: 1A01 scheme: GPT
Partition: ID-1: / raw-size: 111.53 GiB size: 111.53 GiB (100.00%) used: 41.66 GiB (37.3%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%) used: 562 KiB (0.2%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 111.53 GiB size: 111.53 GiB (100.00%) used: 41.66 GiB (37.3%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 111.53 GiB size: 111.53 GiB (100.00%) used: 41.66 GiB (37.3%)
fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 111.53 GiB size: 111.53 GiB (100.00%) used: 41.66 GiB (37.3%)
fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.57 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 55 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:      Processes: 270 Uptime: 17m wakeups: 1 Memory: 15.57 GiB used: 4.36 GiB (28.0%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 Packages: 1456 pacman: 1449 lib: 334 snap: 7
Shell: fish v: 3.3.1 default: Bash v: 5.1.12 running-in: konsole inxi: 3.3.09

Thanks if your read it all! I hope, that someone can help me.

Before providing any help, we need to know something more about your system.
According to the new topic template, you should have included the output of inxi -Faz, as text, formatted with ~~~ before and after that text block.

2 Likes

Okay, sorry. Correcting it right now.

The next time it happens you could give a look at the "compositor".
Sometimes when you open its settings there's a message saying that it crashed and offering to reset it. Also there you'll find some settings to play with and see if it works better. Take notes of what you change...

1 Like

Okay, then I am going to do that for sure.

Do you have Garuda installed to a Virtual Machine?

3 Likes

Garuda Linux is not running on a virtual machine. But I am back with updates - it happened again.
I have 3 monitors, two of them were black and one of them showed this:

The blurred boxes are created with right clicks (they are the menu on the desktop).
I could move my mouse but my screen was trash.
I hard restarted my PC, I went into the Compositor, it did not say any crash.
After like one minute, I started discord, and my PC just froze down, so I had to hard restart again.
Now it is good...for now. :smiley:

I did not change any settings in the compositor, ever!

Have you ever tried to narrow down a little bit your setup?
Starting with one monitor only and see if the problem persists, so it's not due to the multi head configuration.
If all is well, you could try to add the second monitor, and so on.
If you have the problem with only one monitor, I'd also consider downgrading the driver to a previous version, since I've seen a bit too many users with your version complaining...
I'm not a Nvidia expert but I think it's feasible.

2 Likes

I’m not a dick, just trying to point-out that everytime I hear a graphics problem with Linux 99.999% of it the case involves Nvidia GPU.

The father of Linux made it public how bad Nvidia is 9-years ago: https://www.youtube.com/watch?v=IVpOyKCNZYw

Nvidia GPU & Linux really do not belong in the same sentence, the workaround is to download the proprietary driver but doing so it is still YMMV.

2 Likes

I believe a Subforum dealing specifically with nVidia problems may be helpful to others. Should we create one?

So you're meaning to say, create a sub-forum equivalent of purgatory. This could be an area for all the Nvidia and Windows dual boot users before they are permanently dispatched to hell. :rofl:

1 Like

Ooh, ooh, ooh! Hey, yeah, send 'em to the online equivalent of Dante's 9 circles of hell! :rofl:

Nah, I meant where nVidia users can help each other since we are sometimes talking about proprietary drivers. There's not much Garuda can do about them. But I would expect there might be some moderator or otherwise motivated nVidia aficionado that would drop in from time-to-time.

I come from a place where those making such suggestions are usually the ones that others say "fine, you do it," but I am least prepared as I haven't had anything nVidia for a couple decades, anyway. That's why I said "may be helpful" since it's another job that a limited-resources distribution would have to find the man/womanpower to do in a supportive, full-fledged way. And not in a lackadaisical manner.

It's obvious that experience with nVidia leaves a bad taste in some Linux users mouths, and I don't blame them. When I completed the transition to Linux I remember having to make a choice between it and a pair of 3Dfx Voodoo cards running in SLI, because there was no help. That's a horrible choice to be forced to make, and if we can help I am of the opinion we should help. Anyway, you have a better idea of its feasibility than I do.
:upside_down_face:

If the dirty finger of Linus Torvalds didn't shoke Nvidia's ass, I don't think a dedicated Garuda forum section will.

Again, we Linux enthusiast should just discourage people with Nvidia from switching. It really is just asking for trouble. If you have Nvidia graphics, stay with Windows.

2 Likes

Somebody knows their corporate CEO and CFO, board members and chair, stockholders--somebody that should be notified that Linux is a thing now, and it might be worthwhile supporting their Linux drivers.

(I'll leave it at that. It's been a long day. But, gosh, "we" are now heading towards 54 days tobacco-free. I wish you and yours a peaceful Christmas. Kick your feet up and set a spell.)
:smiley:

5 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.