Visual bugs

Issues & Assistance KDE
1

Is experiencing visual bugs normal? I haven’t opened windows, it’s erased, but my other drives are ntfs which I wish to format soon.

System:
Kernel: 6.7.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=6f7ae3fc-7e25-4c8c-8419-89e325646b4c rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.1 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: B550 AORUS ELITE v: N/A serial: N/A
Mobo: Gigabyte model: B550 AORUS ELITE v: x.x serial: N/A
uuid: 032e02b4-0499-05ef-1806-910700080009 BIOS: American Megatrends v: F10
date: 09/18/2020
CPU:
Info: model: AMD Ryzen 7 3700X socket: AM4 bits: 64 type: MT MCP arch: Zen 2
gen: 3 level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 3600 min/max: 2200/4426 boost: enabled
base/boost: 3600/4400 scaling: driver: acpi-cpufreq governor: performance
volts: 1.1 V ext-clock: 100 MHz cores: 1: 3600 2: 3600 3: 3600 4: 3600
5: 3600 6: 3600 7: 3600 8: 3600 9: 3600 10: 3600 11: 3600 12: 3600
13: 3600 14: 3600 15: 3600 16: 3600 bogomips: 114972
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: eVga.com.
driver: nvidia v: 550.54.14 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2024-02; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s
lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: none off: DP-3
empty: DP-1, DP-2, HDMI-A-1, Unknown-2 bus-ID: 0a:00.0 chip-ID: 10de:1e84
class-ID: 0300
Display: server: X.Org v: 23.2.4 with: Xwayland v: 23.2.4
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :1 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: DP-3 note: disabled model: Acer XF243Y serial: <filter>
built: 2020 res: 1920x1080 hz: 144 dpi: 92 gamma: 1.2
size: 530x300mm (20.87x11.81") diag: 604mm (23.8") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: zink
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.54.14
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2070
SUPER/PCIe/SSE2 memory: 7.81 GiB
API: Vulkan v: 1.3.279 layers: 7 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 2070 SUPER driver: nvidia v: 550.54.14 device-ID: 10de:1e84
surfaces: xcb,xlib
Audio:
Device-1: NVIDIA TU104 HD Audio vendor: eVga.com. driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 0a:00.1
chip-ID: 10de:10f8 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: HP HyperX SoloCast driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3:3
chip-ID: 03f0:078b class-ID: 0300
Device-4: Razer USA BlackShark V2 Pro
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-9:9 chip-ID: 1532:0528 class-ID: 0300
API: ALSA v: k6.7.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.3 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 08:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Drives:
Local Storage: total: 1.36 TiB used: 274.68 GiB (19.7%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 3B2QGXA7 temp: 46.9 C
scheme: MBR
SMART: yes health: PASSED on: 127d 15h cycles: 1,522
read-units: 40,718,316 [20.8 TB] written-units: 14,520,006 [7.43 TB]
ID-2: /dev/nvme1n1 maj-min: 259:2 vendor: Samsung
model: SSD 970 EVO Plus 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 2B2QEXM7 temp: 51.9 C scheme: GPT
SMART: yes health: PASSED on: 221d 9h cycles: 1,880
read-units: 33,951,135 [17.3 TB] written-units: 9,590,178 [4.91 TB]
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 500GB
family: based SSDs size: 465.76 GiB block-size: physical: 512 B
logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: SSD serial: <filter>
fw-rev: 4B6Q temp: 34 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 1y 172d 19h cycles: 2278
written: 33 TiB
Partition:
ID-1: / raw-size: 465.76 GiB size: 465.76 GiB (100.00%)
used: 54.34 GiB (11.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p1
maj-min: 259:1
ID-2: /home raw-size: 465.76 GiB size: 465.76 GiB (100.00%)
used: 54.34 GiB (11.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p1
maj-min: 259:1
ID-3: /var/log raw-size: 465.76 GiB size: 465.76 GiB (100.00%)
used: 54.34 GiB (11.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p1
maj-min: 259:1
ID-4: /var/tmp raw-size: 465.76 GiB size: 465.76 GiB (100.00%)
used: 54.34 GiB (11.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p1
maj-min: 259:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.28 GiB used: 2.8 MiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 61.6 C mobo: 43.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.28 GiB used: 11.24 GiB (35.9%)
Processes: 444 Power: uptime: 2h 7m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.47 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: 1955 pm: dpkg pkgs: 1 tools: apt,apt-get pm: pacman pkgs: 1954
libs: 542 tools: octopi,paru Compilers: clang: 17.0.6 gcc: 13.2.1
Shell: garuda-inxi (sudo) default: Bash v: 5.2.26 running-in: konsole
inxi: 3.3.33
Garuda (2.6.23-1):
System install date:     2024-03-10
Last full system update: 2024-03-10 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:
2

What’s the problem with not posting garuda-inxi?
It contains additional, useful information about the status of your system.

:warning: Missing information requested in the template may result in not receiving assistance

Make sure you have done the following before you post:

Issue still unresolved? Then:

  • ONE issue per topic.
  • Describe your issue in detail. The more we know, the better we can help
  • Show us the results of your searches, and what you’ve tried
  • After rebooting, post the FULL output of garuda-inxi in the body of the post (not linked externally, or collapsed with the “hide details” feature)
  • Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>) , or put three tildes (~) above and below the text

Without garuda-inxi this request will be moved to 412 Precondition Failed

2 Likes
4

Yes. It is normal, due to the recent KDE6 migration.
There are (too) many topics about it.
I’m just linking one

We will all have to wait.

3 Likes
5

Open Kvantum Manager and explore it.
Maybe with the help of some tutorial from the internet.
Just linking the first one listed in my search (not necessarily the best article).

3 Likes
6

I updated kvantum-git yesterday and we have the blur working here. Might be a temporary workaround until the Arch version gets updated (there is no tag on the repo yet).

3 Likes
7

By-the-way, this means that a reboot is pending after an update. And this is particularly important for the KDE 6 migration.

6 Likes
8

True true! I have updated something like 8 machines for a total of over 20 times on Plasma 6.0.1 and ALL attempts caused navigation or visual issues until I rebooted. For example, the SHUTDOWN and RESTART buttons were just doing nothing and I had to reboot from CLI every time. Other serious visual/user experience issues occurred as well.

Anyone updating to Plasma 6 MUST reboot immediately before something gets possibly corrupted, who knows.

4 Likes
9

And the instructions were very clear about it.

** It is extremely highly recommended to reboot immediately after performing the upgrade! It is possible your usual GUI Logout, Restart, and Shutdown buttons won’t work. Don’t panic, all you have to do is open up a Terminal window (which may well still be opened after your garuda-update) and type in

systemctl reboot

By-the-way, extremely highly recommended is lovely! :muscle::wink:

5 Likes
10

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