Desktop doesn't load sometimes

anon25081990 · 29 May 2022 13:20

Hey, i've got the issue that my desktop doesn't load sometimes, which means sometimes i need to reboot directly after i started the computer in order for me to use my main display ( i got two )
There was a post that kinda had the same problem, but as far as i've read it was resolved after restoring via timeshift ( or now btrfs assistant ), but the problem always has been there for me, just recently it became much more common and now i've already restarted my pc before i've gone to the garuda forum, and i'm annoyed about it not starting; the "broken" desktop does not feature any click-feedback, the files that are on the "broken" desktop don't appear on the second one, but on the folder "Desktop" they're still there, there's a photo of both my displays:

inxi follows:

System:
  Kernel: 5.18.0-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=59fb3e2d-83c0-4365-a80b-433fb57039f2 rw rootflags=subvol=@
    rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=07dd9dba-6b0e-4958-8a6d-b047eca29fdd loglevel=3
  Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 info: latte-dock
    wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: B450-A PRO MAX (MS-7B86) v: 4.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: M.F1
    date: 03/22/2022
CPU:
  Info: model: AMD Ryzen 5 5500 bits: 64 type: MT MCP arch: Zen 3
    family: 0x19 (25) model-id: 0x50 (80) stepping: 0 microcode: 0xA50000C
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 2591 high: 2995 min/max: 1400/4268 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2809 2: 2560
    3: 2391 4: 2394 5: 2991 6: 2398 7: 2994 8: 2389 9: 2394 10: 2394 11: 2995
    12: 2393 bogomips: 86246
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  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: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 515.43.04
    alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-05) arch: Maxwell pcie: gen: 3 speed: 8 GT/s
    lanes: 16 bus-ID: 10:00.0 chip-ID: 10de:13c2 class-ID: 0300
  Device-2: Logitech Webcam B500 type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-1:2 chip-ID: 046d:0807 class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.2
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 93 s-size: 1049x292mm (41.30x11.50")
    s-diag: 1089mm (42.87")
  Monitor-1: DVI-I-1 pos: right res: 1920x1080 hz: 60 dpi: 102
    size: 477x268mm (18.78x10.55") diag: 547mm (21.54") modes: N/A
  Monitor-2: HDMI-0 pos: primary,left res: 1920x1080 hz: 60 dpi: 94
    size: 521x293mm (20.51x11.54") diag: 598mm (23.53") modes: N/A
  OpenGL: renderer: NVIDIA GeForce GTX 970/PCIe/SSE2
    v: 4.6.0 NVIDIA 515.43.04 direct render: Yes
Audio:
  Device-1: NVIDIA GM204 High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 10:00.1
    chip-ID: 10de:0fbb class-ID: 0403
  Device-2: AMD Renoir Radeon High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-3: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Device-4: Logitech Webcam B500 type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-1:2 chip-ID: 046d:0807 class-ID: 0102 serial: <filter>
  Device-5: JMTek LLC. USB PnP Audio Device type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-1:2 chip-ID: 0c76:161e
    class-ID: 0300
  Sound Server-1: ALSA v: k5.18.0-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 3.64 TiB used: 760.2 GiB (20.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT240BX500SSD1
    size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 041 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Silicon Power
    model: SPCC Solid State Disk size: 238.47 GiB block-size: physical: 512 B
    logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 9A0
    scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST500LX005-1CW162
    size: 465.76 GiB block-size: physical: 4096 B logical: 512 B
    speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: LVD1
    scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST2000DM008-2FR102
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: 0001 scheme: MBR
  ID-5: /dev/sde maj-min: 8:64 vendor: Western Digital
    model: WD10EZEX-00WN4A0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1A01 scheme: MBR
Partition:
  ID-1: / raw-size: 221.04 GiB size: 221.04 GiB (100.00%)
    used: 59.76 GiB (27.0%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
  ID-3: /home raw-size: 221.04 GiB size: 221.04 GiB (100.00%)
    used: 59.76 GiB (27.0%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
  ID-4: /var/log raw-size: 221.04 GiB size: 221.04 GiB (100.00%)
    used: 59.76 GiB (27.0%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
  ID-5: /var/tmp raw-size: 221.04 GiB size: 221.04 GiB (100.00%)
    used: 59.76 GiB (27.0%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.58 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 17.13 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sdb3 maj-min: 8:19
Sensors:
  System Temperatures: cpu: 25.0 C mobo: 28.0 C gpu: nvidia temp: 37 C
  Fan Speeds (RPM): fan-1: 0 fan-2: 1341 fan-3: 1628 fan-4: 1142
    fan-5: 1027 fan-6: 0 gpu: nvidia fan: 50%
Info:
  Processes: 312 Uptime: 11m wakeups: 0 Memory: 15.58 GiB
  used: 3.81 GiB (24.5%) Init: systemd v: 251 tool: systemctl Compilers:
  gcc: 12.1.0 clang: 13.0.1 Packages: pacman: 1361 lib: 339 Shell: Bash
  v: 5.1.16 running-in: konsole inxi: 3.3.16
e[1;34mGaruda (2.6.3-2):e[0m
e[1;34m  System install date:e[0m     2022-04-20
e[1;34m  Last full system update:e[0m 2022-05-29
e[1;34m  Is partially upgraded:  e[0m No
e[1;34m  Relevant software:      e[0m NetworkManager
e[1;34m  Windows dual boot:      e[0m No/Undetected
e[1;34m  Snapshots:              e[0m Snapper
e[1;34m  Failed units:           e[0m bluetooth-autoconnect.service

tbg · 29 May 2022 14:44

Firstly let me state, I am a dinosaur. I actually use computers with only one monitor attached. IMO, most people's expectation that Linux should run 2, 3, or even more monitors without any issues (just like Windows) is not realistic. There are many outstanding bugs with trying to get multi-monitor support working properly. Sadly that is just reality. Linux does not have billions of dollars at their disposal like M$, with teams of thousands of paid devolopers on staff. Linux does lots of things well, but multi-monitor support is currently not one of its better supported features. IMO, If you wish to get a multi-monitor setup working properly, then be prepared to expend a lot of elbow grease.

anon25081990 · 29 May 2022 16:28

in english "there is nothing we can do about it" ?

SGS · 29 May 2022 16:31

We don't, but you do.

anon25081990 · 29 May 2022 16:32

what could i do against it if i want to keep the second display?

BluishHumility · 29 May 2022 20:19

Hi @anon25081990, can you try making a new user on your system and see if you can reproduce this problem?

petsam · 29 May 2022 22:28

I respectfully disagree with this personal opinion It’s a real misunderstanding IMHO.
There is only one case/condition that I would agree. If you say this for KDE/Plasma.

I think that says it all. Systems based on Window Managers, like BSPWM that I use, are fluent in multi-monitoring . The same system with KDE is a nightmare.

So, I would suggest OP to test other DEs, or WMs and report about multi-monitor problems.

Nevertheless, a common workaround for such KDE issues, is/was to restart Plasma and/or kWin using a shortcut. Not always succesful, but worth a try.
Also, switch to TTY and back (actually shaking Xorg) might help.

tbg · 30 May 2022 03:38

Yes, you are correct @pstsam. It is mostly a KDE issue, however most Garuda users tend to install KDE (not WM's).

anon25081990 · 30 May 2022 19:26

i already have multiple users on my system, it's a systemwide-problem

anon25081990 · 30 May 2022 19:30

which other window managers do you recommend which do not require that much setting them up, and if you could provide me with the path to the service which needs to be restarted in order for the desktop to reload i'd be grateful, i can't find the name of it myself

petsam · 30 May 2022 19:33

You probably misunderstood. A new user might confirm failure or success, because there is no cached info, or configuration is pure and the latest (no old configuration settings).

As for your issue, it is sometimes solved, so we are looking for the rest of the times that it is not.

Until you find a stable sequence that always reproduces this bug, there is no general solution. Test several ideas, like restart shortcuts, that you have probably missed.

Or just report upstream.

anon25081990 · 31 May 2022 07:00

i would, but as stated

i did not find a shortcut etc. to restart, do you know where it is?

petsam · 31 May 2022 21:23

They don't exist by default. You need to create them as custom shortcuts.
Restart Plasma command/action

kquitapp5 plasmashell && kstart5 plasmashell

Restart kWin command/action

qdbus org.kde.KWin /KWin reconfigure

anon25081990 · 2 June 2022 15:16

thank you c:

petsam · 2 June 2022 18:54

Do those work with your original issue?
Which one and how?

anon25081990 · 3 June 2022 17:24

to be honest i haven't encountered a issue like that since then, last time i had a issue i used both of those commands in a little script and it works fine

system · 5 June 2022 17:24

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