Desktop doesn't work properly after updating kernel

I experience desktop issues after updating kernel through pacman -Syu.

  1. one of multi-displays doesn't show the wallpaper I set the same as other displays. The display's background only show black. (But it shows taskbar and dock)
  2. right-click doesn't work on that black screen.
  3. windows don't disappear after closing. This doesn't happen just after starting os but does after about one hour.

I'll show my desktop running nothing but leaving "ghost windows".


The left screen is the one having wallpaper problem. All windows do not accept any operation and are just remaining there.
Strangely, they look existing there because selection frame by dragging mouse goes under them. But I can't close nor even touch them.
Peek 2021-06-20 16-10

I believe reinstalling Garuda will fix it, but i wanna try to reveal the cause.

Could you give me a hint?
Thanks.

1 Like

Here is my inxi -Fxxxza.

System:    Kernel: 5.12.11-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0  
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=d1c12b10-b3e0-44cf-bf6d-5361465887bc  
rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.22.1 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM  
Distro: Garuda Linux base: Arch Linux  
Machine:   Type: Desktop System: Thirdwave Diginnos product: Diginnos PC v: N/A serial: <filter>  
Mobo: ASRock model: H97 Pro4 serial: <filter> UEFI: American Megatrends v: P2.20Z  
date: 09/25/2015  
CPU:       Info: Quad Core model: Intel Core i7-4790K bits: 64 type: MT MCP arch: Haswell family: 6  
model-id: 3C (60) stepping: 3 microcode: 28 cache: L2: 8 MiB  
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 63853  
Speed: 4335 MHz min/max: 800/4400 MHz Core speeds (MHz): 1: 4335 2: 4391 3: 4391 4: 4390  
5: 4391 6: 4390 7: 4392 8: 4394  
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled  
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable  
Type: mds mitigation: Clear CPU buffers; SMT vulnerable  
Type: meltdown mitigation: PTI  
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp  
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization  
Type: spectre_v2  
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling  
Type: srbds mitigation: Microcode  
Type: tsx_async_abort status: Not affected  
Graphics:  Device-1: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 465.31 alternate: nouveau,nvidia_drm  
bus-ID: 01:00.0 chip-ID: 10de:13c2 class-ID: 0300  
Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver: loaded: nvidia display-ID: :0  
screens: 1  
Screen-1: 0 s-res: 5760x1080 s-dpi: 92 s-size: 1590x292mm (62.6x11.5") s-diag: 1617mm (63.6")  
Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 92 size: 531x299mm (20.9x11.8") diag: 609mm (24")  
Monitor-2: DP-1 res: 1920x1080 dpi: 92 size: 530x290mm (20.9x11.4") diag: 604mm (23.8")  
Monitor-3: DP-3 res: 1920x1080 hz: 60 dpi: 92 size: 531x299mm (20.9x11.8") diag: 609mm (24")  
OpenGL: renderer: NVIDIA GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 465.31 direct render: Yes  
Audio:     Device-1: Intel 9 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel  
bus-ID: 00:1b.0 chip-ID: 8086:8ca0 class-ID: 0403  
Device-2: NVIDIA GM204 High Definition Audio driver: snd_hda_intel v: kernel bus-ID: 01:00.1  
chip-ID: 10de:0fbb class-ID: 0403  
Sound Server-1: ALSA v: k5.12.11-zen1-1-zen running: yes  
Sound Server-2: JACK v: 0.125.0 running: no  
Sound Server-3: PulseAudio v: 14.2 running: yes  
Sound Server-4: PipeWire v: 0.3.30 running: yes  
Network:   Device-1: Intel Ethernet I218-V vendor: ASRock driver: e1000e v: kernel port: f040  
bus-ID: 00:19.0 chip-ID: 8086:15a1 class-ID: 0200  
IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>  
Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8  
bus-ID: 3-2:2 chip-ID: 0a12:0001 class-ID: e001  
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>  
Drives:    Local Storage: total: 2.27 TiB used: 55.39 GiB (2.4%)  
SMART Message: Unable to run smartctl. Root privileges required.  
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT250BX100SSD1 size: 232.89 GiB block-size:  
physical: 512 B logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: MU02  
scheme: GPT  
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM001-1ER164 size: 1.82 TiB  
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter>  
rev: CC25 scheme: GPT  
ID-3: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT240BX500SSD1 size: 223.57 GiB block-size:  
physical: 512 B logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: R022  
scheme: GPT
Partition: ID-1: / raw-size: 223.32 GiB size: 223.32 GiB (100.00%) used: 55.39 GiB (24.8%) fs: btrfs
dev: /dev/sdc2 maj-min: 8:34
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 546 KiB (0.2%) fs: vfat
dev: /dev/sdc1 maj-min: 8:33
ID-3: /home raw-size: 223.32 GiB size: 223.32 GiB (100.00%) used: 55.39 GiB (24.8%) fs: btrfs
dev: /dev/sdc2 maj-min: 8:34
ID-4: /var/log raw-size: 223.32 GiB size: 223.32 GiB (100.00%) used: 55.39 GiB (24.8%)
fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-5: /var/tmp raw-size: 223.32 GiB size: 223.32 GiB (100.00%) used: 55.39 GiB (24.8%)
fs: btrfs dev: /dev/sdc2 maj-min: 8:34
Swap:      Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100)
ID-1: swap-1 type: zram size: 3.91 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0
ID-2: swap-2 type: zram size: 3.91 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1
ID-3: swap-3 type: zram size: 3.91 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2
ID-4: swap-4 type: zram size: 3.91 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3
ID-5: swap-5 type: zram size: 3.91 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram4
ID-6: swap-6 type: zram size: 3.91 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram5
ID-7: swap-7 type: zram size: 3.91 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram6
ID-8: swap-8 type: zram size: 3.91 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram7
Sensors:   System Temperatures: cpu: 40.0 C mobo: N/A gpu: nvidia temp: 66 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 22%
Info:      Processes: 299 Uptime: 3h 35m wakeups: 2 Memory: 31.29 GiB used: 4.12 GiB (13.2%) Init: systemd
v: 248 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.0 Packages: pacman: 1485 lib: 340
Shell: fish v: 3.2.2 running-in: konsole inxi: 3.3.04

Try doing Force Smoothest Animations in KDE Compositor Settings -> Latency drop down.

1 Like

Have you checked that the compositor is up and running?

2 Likes

@ExistingDude
I tried, but it doesn't improve black-bg problem. I will check ghost-window issue later.

@filo
How can I check it? "Enable compositor" in Display and Monitor settings is already checked.

So it is ok, otherwise there would be an error message.
Maybe you could restore the latest snapshot and update again. Just in case something went wrong...
Or maybe you could try reinstalling your Nvidia drivers.

It sounds pretty stupid to re-install an operating system because of a perceived kernel problem without first trying a few other kernels, right?

5 Likes

@filo
I have updated system again and again. So I guess the wrong setting has already persisted. But I will try, thanks.

@c00ter
Maybe you are right. But I prefer remaining on linux-zen because I had some other serious troubles from changing to other kernels before. The issue of this time looks easier then the previous ones. How interesting and exciting using linux is haha.

Garuda comes with a timeshift rollback feature precisely for these types of issues. Simply roll your system back to your pre-update state.

If that doesn't fix things it's a user configuration setting in your home directory causing your issues.

If the issue is corrected with timeshift, then wait a week before trying another update to see if the problem has been resolved. Reinstalling should always be a last resort.

6 Likes

@ExistingDude
Ghost window problem isn't solved even after changing the setting you mentioned.

@tbg
You are right. This is gonna be a very good lesson for me.

So, was it solved with a timeshift restore? If so, please mark it as such.
If not, in the meanwhile, a somewhat similar KDE issue (only a black background there) could be solved creating a new user (timeshift does not backup/restore home configs).
It would be very quick to test it, if you want...

4 Likes

I don't have the timeshift in which everything works correctly any more. It has gone. I left the problem a bit long. This is my fault.

Creating a new user seems to fix the issue. Sometime, while I repeat rebooting as an experiment and for reset system settings, one display randomly shows the same symptom of black background. That monitor is another one from before. But mostly it works.

I'll see whether the problems will happen again or not for a few days. Thanks!

Oh, the new user doesn't have neofetch. So I installed it but it shows old logo, maybe.

How can I bring the new logo from the old user setting? I prefer this.

You really want to waste the valuable time of Garuda staff, forum staff, and people that have other, real problems? Really? Did you do a forum search?

1 Like

Did you try resetting config in Garuda Assistant

1 Like

@c00ter
Sorry for irritating you. Yes I did search forum and couldn't find the direct answer. I didn't think this was intended phenomenon that a new user doesn't have neofetch. If this is a disturbing minor problem, I didn't know that. Sorry, Just leave it.

@SameExpert
Yes and nothing changed.

OK, this is a good lesson. I'll use timeshift function more often.

The latter picture is the output of paleofetch not neofetch, which I think is the default.
Try editing config.fish as follows (ie substituing neofetch with paleofetch in the line before end)

3 Likes

I have the same problem after a recent kernel update. I dont think its related to any settings or multiple monitors. (I run a single monitor and didnt tinker with any settings before or after the update) . just as the gif shows, the windows cannot be selected or closed but when you click on them the click is parsed to the desktop.

I'm going to try and downgrade the kernel (if possible), if I do so do I need to downgrade the kernel headers as well ?

When you file a help request, the proper method is to tell us what you've researched and found, what you've tried and not tried, what the results were, output, journal files, inxi etc., etc.

You waste the valuable time of every developer, team member, or forum helper that responds when you fail to do so.

Those posters who do not follow some semblance of the above are considered Help Vampires.

3 Likes