Here’s a before and after comparison:
Before there was no box with only a bit of a drop shadow on the filename,
now there’s a dark box around the filenames.
I updated my system and I don’t know what changed, I messed around with the themes for a while but I’m lost as to how to get it looking as it did before.
Where do I change this?
Thanks!
No information given… and my crystal ball is broken.
That does look rather like somethign I haven’t seen since Wayland came along - Compositing. You can find it in your settings (Display maybe).
That means you’re likely using the cursed X11…
Possibly the even more cursed nVidia.
For Bonus points: I’ll say nVidia is a prime suspect too.
kinfo
The bare minimum.
inxi -zv8
The ultimate sysinfo.
When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:
```
pasted text
```
Or three (3) tilde signs, like this:
~~~
pasted text
~~~
Quick Fix:
Sorry about that, I wasn’t sure what would be useful.
kinfo
Operating System: Arch Linux
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.12-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: NVIDIA GeForce GTX 1660
sudo inxi -zv8
System:
Kernel: 7.0.12-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-linux
root=UUID=3b806416-e8ea-44bf-9d2d-572cc27ef0f1 rw loglevel=3 quiet splash
nvidia-drm.modeset=1 nvidia.drm.fbdev=1
Desktop: KDE Plasma v: 6.6.5 tk: Qt v: N/A wm: kwin_x11 with: krunner
dm: SDDM Distro: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: B550 Phantom Gaming 4/ac serial: <filter>
uuid: 3759a1a8-f226-0000-0000-000000000000 Firmware: UEFI vendor: American
Megatrends LLC. v: P2.20 date: 02/24/2022
Battery:
Device-1: hidpp_battery_0 model: Logitech M720 Triathlon Multi-Device Mouse
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
Memory:
System RAM: total: 32 GiB available: 31.26 GiB used: 7.42 GiB (23.7%)
Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
max-module-size: 32 GiB note: est.
Device-1: Channel-A DIMM 0 type: no module installed
Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 16 GiB speed: 2133 MT/s volts: curr: 1.2 min: 1.2
max: 1.2 width (bits): data: 64 total: 64 manufacturer: G.Skill
part-no: F4-3200C16-16GVK serial: N/A
Device-3: Channel-B DIMM 0 type: no module installed
Device-4: Channel-B DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 16 GiB speed: 2133 MT/s volts: curr: 1.2 min: 1.2
max: 1.2 width (bits): data: 64 total: 64 manufacturer: G.Skill
part-no: F4-3200C16-16GVK serial: N/A
PCI Slots:
Slot: 0 type: PCIe status: in use info: J6B2 length: long volts: 3.3
bus-ID: 00:01.0
Slot: 1 type: PCIe status: in use info: J6B1 length: short volts: 3.3
bus-ID: 00:1c.3
Slot: 2 type: PCIe status: in use info: J6D1 length: short volts: 3.3
bus-ID: 00:1c.4
Slot: 3 type: PCIe status: in use info: J7B1 length: short volts: 3.3
bus-ID: 00:1c.5
Slot: 4 type: PCIe status: in use info: J8B4 length: short volts: 3.3
bus-ID: 00:1c.6
Slot: 5 type: PCIe status: in use info: J8D1 length: short volts: 3.3
bus-ID: 00:1c.7
CPU:
Info: model: AMD Ryzen 5 3600 socket: AM4 bits: 64 type: MT MCP arch: Zen 2
gen: 2 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 dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
desc: 6x512 KiB L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 1724 min/max: 558/4208 boost: enabled
base/boost: 3600/4200 scaling: driver: amd-pstate-epp governor: powersave
volts: 1.1 V ext-clock: 100 MHz cores: 1: 1724 2: 1724 3: 1724 4: 1724
5: 1724 6: 1724 7: 1724 8: 1724 9: 1724 10: 1724 11: 1724 12: 1724
bogomips: 86234
Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid
f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs
irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae
pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
pfthreshold pge pni popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a
rdtscp rep_good sep sev sev_es sha_ni skinit smap smca smep ssbd sse sse2
sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext
tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme
vmmcall wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt
xtopology
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: ghostwrite status: Not affected
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: old_microcode status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
protection
Type: spec_rstack_overflow mitigation: Safe RET
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; STIBP:
always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsa status: Not affected
Type: tsx_async_abort status: Not affected
Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
Device-1: NVIDIA TU116 [GeForce GTX 1660] vendor: ZOTAC driver: nvidia
v: 610.43.02 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
status: current (as of 2025-11; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s
lanes: 16 ports: active: none off: DP-1,DP-2 empty: DP-3,HDMI-A-1
bus-ID: 06:00.0 chip-ID: 10de:2184 class-ID: 0300
Display: unspecified server: X.Org v: 21.1.23 with: Xwayland v: 24.1.12
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 4184x2688 s-dpi: 107 s-size: 993x638mm (39.09x25.12")
s-diag: 1180mm (46.47")
Monitor-1: DP-1 mapped: DP-0 note: disabled pos: primary,bottom-r
model: LG (GoldStar) ULTRAGEAR serial: <filter> built: 2021 res:
mode: 2560x1440 hz: 144 scale: 100% (1) dpi: 109 gamma: 1.2 chroma: red:
x: 0.686 y: 0.310 green: x: 0.263 y: 0.671 blue: x: 0.149 y: 0.055 white:
x: 0.314 y: 0.329 size: 597x336mm (23.5x13.23") diag: 685mm (27")
ratio: 16:9 modes: 2560x1440, 1920x1080, 1680x1050, 1600x900, 1280x1024,
1280x800, 1152x864, 1280x720, 1024x768, 800x600, 720x480, 640x480
Monitor-2: DP-2 note: disabled pos: top-left model: ASUS VG289Q1A
serial: <filter> built: 2022 res: mode: 3840x2160 hz: 60
scale: 253% (0.39375) to: 1512x2688 dpi: 157 gamma: 1.2 chroma: red:
x: 0.678 y: 0.314 green: x: 0.271 y: 0.624 blue: x: 0.145 y: 0.055 white:
x: 0.314 y: 0.329 size: 621x341mm (24.45x13.43") diag: 708mm (27.9")
ratio: 16:9 modes: 3840x2160, 2560x1440, 1920x1080, 1680x1050, 1280x1024,
1440x900, 1280x960, 1280x800, 1280x720, 1440x576, 1024x768, 1440x480,
800x600, 720x576, 720x480, 640x480
EDID-Warnings: 1: parse_edid: unhandled CEA mode 96 2: parse_edid:
unhandled CEA mode 97
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: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 610.43.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1660/PCIe/SSE2
memory: 5.86 GiB
API: Vulkan v: 1.4.350 layers: 3 device: 0 type: discrete-gpu
name: NVIDIA GeForce GTX 1660 driver: nvidia v: 610.43.02
device-ID: 10de:2184 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA TU116 High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 06:00.1 chip-ID: 10de:1aeb class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASRock driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 08:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k7.0.12-arch1-1 status: kernel-api
tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.6.6 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASRock driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 05:00.0
chip-ID: 8086:24fb class-ID: 0280
IF: wlp5s0 state: up mac: <filter>
IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
WAN IP: <filter>
Bluetooth:
Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9:3 chip-ID: 8087:0aa7
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: disabled
rfk-block: hardware: no software: yes address: <filter>
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff
link-mode: peripheral accept
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 21.83 TiB used: 14.45 TiB (66.2%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Sabrent model: Rocket 4.0 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: RKT401.3 temp: 34.9 C
scheme: GPT
SMART: yes health: PASSED on: 3y 246d 19h cycles: 2,151
read-units: 723,676,813 [370 TB] written-units: 323,684,843 [165 TB]
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD80EAAZ-00BXBB0 family: Blue (CMR) size: 7.28 TiB block-size:
physical: 4096 B logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD
rpm: 5640 serial: <filter> fw-rev: 1A01 temp: 35 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 44d 10h cycles: 12
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST8000DM004-2U9188
family: BarraCuda 3.5 (SMR) size: 7.28 TiB block-size: physical: 4096 B
logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD rpm: 5400
serial: <filter> fw-rev: 0001 temp: 40 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 14452h+32m+08.539s
cycles: 180 read: 60.68 TiB written: 34.18 TiB Pre-Fail:
attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD6003FZBX-00K5WB0 size: 5.46 TiB block-size: physical: 4096 B
logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: HDD rpm: 7200
serial: <filter> fw-rev: 1A01 temp: 43 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 3y 248d 23h cycles: 2150
ID-5: /dev/sdd maj-min: 8:48 vendor: SanDisk model: Extreme Portable SSD
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 1012 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 300 GiB size: 294.23 GiB (98.08%) used: 71.36 GiB (24.3%)
fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 label: N/A
uuid: 3b806416-e8ea-44bf-9d2d-572cc27ef0f1
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 164 KiB (0.0%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
maj-min: 259:1 label: N/A uuid: 19B6-931E
ID-3: /home raw-size: 615 GiB size: 604.28 GiB (98.26%)
used: 525.07 GiB (86.9%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p3
maj-min: 259:3 label: N/A uuid: 4af1e547-604e-4426-9748-21ac5022af16
ID-4: /media/ReallierBiggerDriver raw-size: 7.28 TiB
size: 7.22 TiB (99.20%) used: 1.93 TiB (26.8%) fs: ext4 block-size: 4096 B
dev: /dev/sda1 maj-min: 8:1 label: yan-big-drive
uuid: 4606d1b8-6753-4576-a301-3512969f9161
ID-5: /media/ReallyBigDrive raw-size: 7.28 TiB size: 7.22 TiB (99.20%)
used: 6.83 TiB (94.7%) fs: ext4 block-size: 4096 B dev: /dev/sdb1
maj-min: 8:17 label: really-big-drive
uuid: eb1f4c30-5c34-4cc9-8174-0825943b8e2e
ID-6: /media/VeryBigDrive raw-size: 5.46 TiB size: 5.41 TiB (99.19%)
used: 5.1 TiB (94.2%) fs: ext4 block-size: 4096 B dev: /dev/sdc1
maj-min: 8:33 label: very-big-drive
uuid: 6bb198da-4acb-4eff-9631-df066c96765c
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: partition size: 16.01 GiB used: 1.39 GiB (8.7%)
priority: -1 dev: /dev/nvme0n1p4 maj-min: 259:4 label: N/A
uuid: f1185a40-c91e-40ed-8f8e-8035d3e6bb6b
Unmounted:
ID-1: /dev/sdd1 maj-min: 8:49 size: 931.51 GiB fs: ntfs label: DataEater
uuid: 2CBCAC6ABCAC2FEE
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 1-5:2 info: Logitech Unifying Receiver type: keyboard,mouse,HID
driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
chip-ID: 046d:c52b class-ID: 0300
Device-2: 1-9:3 info: Intel Wireless-AC 3168 Bluetooth type: bluetooth
driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
mode: 1.1 power: 100mA chip-ID: 8087:0aa7 class-ID: e001
Device-3: 1-10:4 info: ASRock LED Controller type: HID
driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 100mA chip-ID: 26ce:01a2 class-ID: 0300
serial: <filter>
Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-4: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-5: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 5-1:2 info: G.SKILL KM360 MX type: keyboard
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 500mA chip-ID: 28da:1505 class-ID: 0301
Hub-6: 6-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Device-1: 6-3:4 info: Norelsys NS1068/NS1068X SATA Bridge Controller
type: mass storage driver: usb-storage interfaces: 1 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 8mA
chip-ID: 2537:1068 class-ID: 0806 serial: <filter>
Device-2: 6-4:3 info: SanDisk Extreme Portable SSD type: mass storage
driver: uas interfaces: 1 rev: 3.1 speed: 5 Gb/s (596.0 MiB/s) lanes: 1
mode: 3.2 gen-1x1 power: 896mA chip-ID: 0781:558c class-ID: 0806
serial: <filter>
Sensors:
System Temperatures: cpu: 46.6 C mobo: N/A
Fan Speeds (rpm): N/A
Repos:
Packages: 1796 pm: pacman pkgs: 1776 libs: 444 tools: yay pm: rpm pkgs: 0
pm: flatpak pkgs: 20
Active pacman repo servers in: /etc/pacman.d/mirrorlist
(mirrorlist was really long, excluded)
Processes:
CPU top: 5 of 365
1: cpu: 1.4% command: librewolf pid: 308967 mem: 213.4 MiB (0.6%)
2: cpu: 1.2% command: librewolf pid: 304608 mem: 378.9 MiB (1.1%)
3: cpu: 1.1% command: steamwebhelper pid: 99635 mem: 457.3 MiB (1.4%)
4: cpu: 0.9% command: steam pid: 99338 mem: 149.7 MiB (0.4%)
5: cpu: 0.8% command: librewolf pid: 279983 mem: 830.3 MiB (2.5%)
Memory top: 5 of 365
1: mem: 1129.8 MiB (3.5%) command: fsearch pid: 226751 cpu: 0.5%
2: mem: 1058.5 MiB (3.3%) command: librewolf pid: 279724 cpu: 0.7%
3: mem: 830.3 MiB (2.5%) command: librewolf pid: 279983 cpu: 0.8%
4: mem: 784.9 MiB (2.4%) command: baloorunner pid: 11071 cpu: 0.0%
5: mem: 641.0 MiB (2.0%) command: librewolf pid: 298927 cpu: 0.7%
Info:
Processes: 365 Power: uptime: 1d 21h 18m states: freeze,mem,disk
suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 12.42 GiB
services: org_kde_powerdevil,upowerd Init: systemd v: 260
default: graphical tool: systemctl
Compilers: clang: 22.1.6 gcc: 16.1.1 alt: 15 Shell: Sudo (sudo)
v: 1.9.17p2 default: Bash v: 5.3.15 running-in: konsole inxi: 3.3.40
Switching to Wayland did remove the text boxes, so problem solved there. Although, the icons can’t be moved, and there’s no indication that I’m hovering over them, I can’t rename them, and only the folders respond at all by double-clicking. the drop shadows on the icons themselves did not come back either. I was using Wayland before so I think something caused X11 to get re-enabled after I did an update. I’m still not sure what’s configured differently on X11 though to make the black boxes show up, that’s still a mystery to me. Any ideas?
(As a side note, it thinks my vertical monitor is on the right side instead of the left, and the thumbnails for the photos on my desktop disappeared. second monitor is new to me, still working out the problems. I think I still need to configure something to keep it from doing weird things)
Sure, your compositing is off… switching to the more stable Wayland won’t have that issue, Wayland has proved to be super-stable for me since I first tested it.
Not sure how to fix that, I didn’t use either for a long time - I enjoy stable computing 
What’s keeping you on X11?
Just logged out of Wayland switching back to X11 since the icons work, it stalled and I had to do a full reboot. Now logging back in with X11, there are no longer boxes on the filenames. I’m a bit confused but I’ll report back when/how it breaks again. Wayland works great, though I do think I saw the black boxes on the filenames while running Wayland too. Historically I’ve just switched between whatever one works best in the moment.
So I’m thinking, maybe it isn’t a Wayland/X11 problem, just a problem with how something? is initializing. I’m just guessing though because I have no idea how KDE works underneath.
Sorry I don’t understand, I’m not entirely sure what you mean by compositing, can you clarify? I assume are Graphics Platform: X11 and NVIDIA TU116 [GeForce GTX 1660] are fighting each other or something?
X11 is an ancient system.
I remember issues with screen tearing, laggy scrolling, all kinds of things…
So you have a desktop with no ‘compositing’ - every application draws a window directly on the single desktop/screen. When you move a window, that has to be erased and re-drawn… you’re living in the 1980s.
So then compositing takes place - it’s an afterthought bolted on to X11 (which is the original Frankenstein’s monster)… bringing us out of the 1980s.
Compositing sits on the desktop and catches the windows and handles them and passes them to the GPU for rendering. It’s separate and can be toggled.
However, with Wayland, compositing is not an optional extra… it is the core requirement - there is no ‘fallback’ because it’s built into the foundation.
So you’ll have a hard time creating screen tearing and there’s no more choice between either a ‘smooth’ or a ‘responsive’ setup, because it’s both at once.
This is why I asked the question:
This is a nightmare with some nVidia setups that needs sorting, but many nVidia users have no issues with Wayland.
There are one or two other issues which force people to stay with X11…
But unless you have a very good reason to log in X11, you should log in to Wayland, and reserve X11 only for times when you absolutely must use it.