Desktop Cube Skybox background not working

In plasma 6 wayland (nvidia), desktop cube effect’s skybox background is not working, tried all extensions .hdr .exr .jpeg .png but none worked

Am talking about :
Desktop Effects > Cube > Skybox local path

Please help

garuda-inxi : (partially updated - yes but due to installing one software only, no issues of upgrading, system updated recently)

System:
  Kernel: 6.10.3-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=994440bb-4224-4ac7-bc5d-6f26fb2e7d1c rw rootflags=subvol=@
    quiet loglevel=3 nvidia_drm.modeset=1 nvidia_drm.fbdev=1 ibt=off
  Desktop: KDE Plasma v: 6.1.3 tk: Qt v: N/A info: frameworks v: 6.4.0
    wm: kwin_wayland with: Docker,krunner tools: avail: xautolock vt: 1 dm:
    1: LightDM v: 1.32.0 note: stopped 2: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: G751JL v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: G751JL v: 1.0 serial: <superuser required>
    part-nu: ASUS-NotebookSKU uuid: <superuser required>
    UEFI: American Megatrends v: G751JL.205 date: 11/02/2015
Battery:
  ID-1: BAT0 charge: 44.9 Wh (95.9%) condition: 46.8/66.0 Wh (70.9%)
    volts: 15.0 min: 15.0 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: not charging
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: Intel Core i7-4720HQ bits: 64 type: MT MCP arch: Haswell
    gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
    family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 2443 high: 3539 min/max: 800/3600 scaling:
    driver: intel_cpufreq governor: schedutil cores: 1: 800 2: 3410 3: 3510
    4: 800 5: 3258 6: 3434 7: 800 8: 3539 bogomips: 41501
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GM204M [GeForce GTX 965M] vendor: ASUSTeK driver: nvidia
    v: 555.58.02 alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current
    (as of 2024-06; EOL~2026-12-xx) arch: Maxwell code: GMxxx
    process: TSMC 28nm built: 2014-2019 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none off: eDP-1 empty: DP-1,HDMI-A-1,VGA-1 bus-ID: 01:00.0
    chip-ID: 10de:13d9 class-ID: 0300
  Device-2: Chicony USB2.0 HD UVC WebCam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-7:5 chip-ID: 04f2:b414
    class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: 0
  Monitor-1: eDP-1 res: 1920x1080 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: zink inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58.02
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 965M/PCIe/SSE2
    memory: 1.95 GiB display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 3 device: 0 type: discrete-gpu
    name: NVIDIA GeForce GTX 965M driver: nvidia v: 555.58.02
    device-ID: 10de:13d9 surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
    class-ID: 0403
  Device-2: NVIDIA GM204 High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:0fbb class-ID: 0403
  API: ALSA v: k6.10.3-zen1-2-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.2.2 status: active 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: Intel Wireless 7265 driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 3b:00.0 chip-ID: 8086:095a class-ID: 0280
  IF: wls1 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8168 v: 8.053.00-NAPI modules: r8169 pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 3c:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp60s0 state: down mac: <filter>
  IF-ID-1: wlp0s20u4i2 state: up mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Realtek 802.11ac NIC driver: btusb,rtw_8821cu type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-4:9 chip-ID: 0bda:c820
    class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 4 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 4.2 lmp-v: 8
    status: discoverable: no pairing: no
  Device-2: Intel Bluetooth wireless interface driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-5:4
    chip-ID: 8087:0a2a class-ID: e001
  Report: ID: hci1 rfk-id: 1 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 4.2 lmp-v: 8
    status: discoverable: no pairing: no
Drives:
  Local Storage: total: 1.38 TiB used: 103.51 GiB (7.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: HGST (Hitachi) model: HTS721010A9E630
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: A3J0 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: A-Data model: SU630 size: 447.13 GiB
    block-size: physical: 512 B logical: 512 B speed: 1.5 Gb/s tech: SSD
    serial: <filter> fw-rev: 4c21 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Generic model: STORAGE DEVICE
    size: 29.83 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: 0819 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 97 GiB size: 97 GiB (100.00%) used: 29.87 GiB (30.8%)
    fs: btrfs dev: /dev/sdb4 maj-min: 8:20
  ID-2: /boot/efi raw-size: 615.8 MiB size: 614.6 MiB (99.80%)
    used: 584 KiB (0.1%) fs: vfat dev: /dev/sdb7 maj-min: 8:23
  ID-3: /home raw-size: 146.53 GiB size: 146.53 GiB (100.00%)
    used: 73.64 GiB (50.3%) fs: btrfs dev: /dev/sdb5 maj-min: 8:21
  ID-4: /var/log raw-size: 97 GiB size: 97 GiB (100.00%)
    used: 29.87 GiB (30.8%) fs: btrfs dev: /dev/sdb4 maj-min: 8:20
  ID-5: /var/tmp raw-size: 97 GiB size: 97 GiB (100.00%)
    used: 29.87 GiB (30.8%) fs: btrfs dev: /dev/sdb4 maj-min: 8:20
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 23.42 GiB used: 2.21 GiB (9.4%)
    priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 8 GiB used: 2.2 MiB (0.0%) priority: -2
    dev: /dev/sdb6 maj-min: 8:22
Sensors:
  System Temperatures: cpu: 56.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 2300
Info:
  Memory: total: 24 GiB available: 23.42 GiB used: 7 GiB (29.9%)
  Processes: 371 Power: uptime: 7h 43m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 9.31 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 2065 libs: 467 tools: octopi,pamac,paru
    pm: flatpak pkgs: 0 Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi
    default: fish v: 3.7.1 running-in: yakuake inxi: 3.3.35
Garuda (2.6.26-1):
  System install date:     2024-05-28
  Last full system update: 2024-08-08
  Is partially upgraded:   Yes
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            evdev-rce.service nvidia-powerd.service

Could you provide any more details on how it isn’t working (like… is the effect messing up? slows and fails to load image?). Take a look at these reports as this might be related to one or both of these bugs:
https://bugs.kde.org/show_bug.cgi?id=483480

https://bugs.kde.org/show_bug.cgi?id=490906
Both talk about issues using high quality images.

1 Like

I went through it earlier, I also used less than 500kb images but images fail to load and black background is shown

I say try jpeg keep the name short. I just give it a number. I’ve had luck up to 5120x2880.

This is the image i got it working with.

1 Like

Not working @elite
I tried doing so with name 1.jpeg of res about 2000 and size under 500kb still black bg

might be best to change the image your using ive found its super picky. I had it work up to 8MiB files but not all work. Even if they are jpegs.

1 Like

Is kimageformats installed? I recently discovered that this package was not in the recent package list. My machine that was upgraded from KDE 5 to KDE 6 did not have it either:

1 Like

I checked it but I recently found out this is the issue of Wayland sessions, after so many time, I switched to Xorg session to check and found it is working properly in X session, hdr, jpeg working atleast, but in Wayland it is not working somehow

Any suggestions to make it work on Wayland?

There are a few issues open reguarding image use that are still open like this one Custom skybox is weird · Issue #7 · zzag/kwin-effects-cube · GitHub
Although I haven’t seen something that is like the issue you are reporting with it being specifically a Wayland session issue.

If the issue only happens in Wayland as you say, I would open up an issue there and be as detailed as you can in the report with the images you are trying to use. Maybe the developer or other users can help pin down what exactly is causing the issues in a Wayland session and eventually fix it.

2 Likes

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