Bug 489385

Summary: Moving Windows to virtual desktops results in a hard crash.
Product: [Plasma] kwin Reporter: Elite <eliteamdgaming>
Component: generic-crashAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: kdedev
Priority: NOR    
Version First Reported In: 6.1.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Elite 2024-06-28 16:30:38 UTC 
When you click to drag a window to a virtual desktop. When the setting " Switch desktop on edge: Only when moving the window". An you drag the window in my case up or down since im using a ultrawide it makes the most sense.  The system Will hard lock up.  Requiring a power buton  hold restart. 
From a little testing I cant reproduce it from an new user. Though in a new user there is its own bug of not letting you drag the window down it just goes up. 

1. Have " Switch desktop on edge: Only when moving the window: " set 
2. Have ta least 4 virtual desktops in "individual rows"
3. Drag any window up  to the top  of the screen so it will change Virt desktops

I've included some poorly taken videos here since I cant use desktop capture to record the freeze.

Main user:   https://www.youtube.com/watch?v=b0wWSaY5wEQ
New user: https://www.youtube.com/watch?v=BdxAKONiOYI

If there are any other commands I could run to give more info please let me know. 

Operating System: Garuda Linux 
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.7-1-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 GRE



```garuda-inxi
System:
  Kernel: 6.9.7-1-cachyos arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-cachyos
    root=UUID=ed618e85-c1b1-4a62-9eef-7263837ec30d rw rootflags=subvol=@
    resume=UUID=9e39bce2-8148-4e68-83a2-8185da8c85fb loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.1.1 tk: Qt v: N/A info: frameworks v: 6.3.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    UEFI: American Megatrends v: 4802 date: 06/15/2023
CPU:
  Info: model: AMD Ryzen 7 3700X 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: 0x8701030
  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: 2216 high: 3975 min/max: 550/4426 boost: enabled
    scaling: driver: amd-pstate-epp governor: powersave cores: 1: 3975 2: 3973
    3: 550 4: 550 5: 3795 6: 550 7: 3686 8: 550 9: 550 10: 3975 11: 3975
    12: 550 13: 550 14: 550 15: 3974 16: 3711 bogomips: 115201
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M] vendor: Sapphire
    driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x process: TSMC n5 (5nm)
    built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1
    empty: DP-2, HDMI-A-1, HDMI-A-2, Writeback-1 bus-ID: 0c:00.0
    chip-ID: 1002:744c class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: 0
  Monitor-1: DP-1 res: 3127x1309 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.0-devel
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 GRE (radeonsi
    navi31 LLVM 17.0.6 DRM 3.57 6.9.7-1-cachyos) device-ID: 1002:744c
    memory: 15.62 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 12 device: 0 type: discrete-gpu name: AMD
    Radeon RX 7900 GRE (RADV NAVI31) driver: mesa radv
    v: 24.2.0-devel (git-a3f35964ba) device-ID: 1002:744c
    surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
    17.0.6 256 bits) driver: mesa llvmpipe v: 24.2.0-devel (git-a3f35964ba)
    (LLVM 17.0.6) device-ID: 10005:0000 surfaces: xcb,xlib,wayland
Audio:
  Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0c:00.1 chip-ID: 1002:ab30
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0f:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Texas Instruments PCM2900C Audio CODEC
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 5-2:3 chip-ID: 08bb:29c0 class-ID: 0300
  API: ALSA v: k6.9.7-1-cachyos status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: PipeWire v: 1.0.7 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 7260 driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:08b1 class-ID: 0280
  IF: wlp5s0 state: down mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: 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-6:4 chip-ID: 8087:07dc
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
    lmp-v: 6 sub-v: e00 hci-v: 6 rev: e00 class-ID: 6c0104
  Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff
    link-mode: peripheral accept service-classes: rendering, capturing, audio,
    telephony
Drives:
  Local Storage: total: 6.5 TiB used: 3.19 TiB (49.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: HP model: SSD EX920 1TB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 32A0T2IA temp: 42.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 46.9 C
    scheme: GPT
  ID-3: /dev/nvme2n1 maj-min: 259:11 vendor: Western Digital
    model: WD BLACK SN770 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 731100WD temp: 49.9 C scheme: GPT
  ID-4: /dev/sda maj-min: 8:0 vendor: OCZ model: VERTEX3 size: 111.79 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
    serial: <filter> fw-rev: 2.22 scheme: GPT
  ID-5: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD20EZAZ-00L9GB0 size: 1.82 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 0A80 scheme: GPT
Partition:
  ID-1: / raw-size: 1.8 TiB size: 1.8 TiB (100.00%) used: 1023.59 GiB (55.5%)
    fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 27.6 MiB (9.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:2
  ID-3: /home raw-size: 1.8 TiB size: 1.8 TiB (100.00%)
    used: 1023.59 GiB (55.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
  ID-4: /var/log raw-size: 1.8 TiB size: 1.8 TiB (100.00%)
    used: 1023.59 GiB (55.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
  ID-5: /var/tmp raw-size: 1.8 TiB size: 1.8 TiB (100.00%)
    used: 1023.59 GiB (55.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.53 GiB used: 2.06 GiB (13.3%)
    priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 17.07 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme1n1p3 maj-min: 259:4
Sensors:
  System Temperatures: cpu: 42.0 C mobo: 42.0 C gpu: amdgpu temp: 54.0 C
    mem: 72.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 598
Info:
  Memory: total: 16 GiB available: 15.53 GiB used: 5.24 GiB (33.7%)
  Processes: 418 Power: uptime: 28m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.18 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Packages: 2569 pm: pacman pkgs: 2540 libs: 625 tools: octopi,pacseek,paru
    pm: flatpak pkgs: 29 Compilers: clang: 17.0.6 gcc: 14.1.1 Shell: garuda-inxi
    default: fish v: 3.7.1 running-in: kitty inxi: 3.3.35
Garuda (2.6.26-1):
  System install date:     2024-05-15
  Last full system update: 2024-06-28
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            
```
Comment 1 Vlad Zahorodnii 2024-10-01 09:40:37 UTC 
I cannot reproduce the issue. Can you check kwin's logs when the hard freeze occurs? 

  journalctl --boot --user-unit plasma-kwin_wayland > log.txt

also, is there any chance that you could retrieve kwin's backtrace when the hard freeze occurs? You would need to ssh from another computer and attach a debugger to kwin process, e.g.

  sudo gdb -p $(pidof kwin_wayland)

then type

  bt

and paste the output here

https://community.kde.org/KWin/Debugging contains more details
Comment 2 Bug Janitor Service 2024-10-16 03:47:42 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Elite 2024-10-16 20:44:52 UTC 
(In reply to Vlad Zahorodnii from comment #1)
> I cannot reproduce the issue. Can you check kwin's logs when the hard freeze
> occurs? 
> 
>   journalctl --boot --user-unit plasma-kwin_wayland > log.txt
> 
> also, is there any chance that you could retrieve kwin's backtrace when the
> hard freeze occurs? You would need to ssh from another computer and attach a
> debugger to kwin process, e.g.
> 
>   sudo gdb -p $(pidof kwin_wayland)
> 
> then type
> 
>   bt
> 
> and paste the output here
> 
> https://community.kde.org/KWin/Debugging contains more details

It seems to have been fixed since 6.2. If the bug comes back ill report it again. With the journal and backtrace if i can manage that one.