'Fall Apart' Broken After Update

Hi everyone.. after doing a system update today I was horrified to see my favorite KDE desktop effect "fall apart" has now stopped working :scream: :scream: :scream:

All other desktop effects appear to be fine. Only Fall Apart is broken.
I have tried disabling and re-enabling the effect, and obviously rebooting.

Can someone please help me fix it. Thanks!

Kernel: 5.16.8-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=d5af581e-eff8-4b35-b8db-4838c1055d5d rw [email protected]
cryptdevice=UUID=46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757:luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757
root=/dev/mapper/luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757 quiet splash
rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
Desktop: KDE Plasma 5.24.0 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: Razer product: Blade v: 2.04
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Razer model: Razer CH20 serial: <superuser required> UEFI: Razer
v: 1.05 date: 05/16/2019
Battery:
ID-1: BAT0 charge: 82.1 Wh (99.9%) condition: 82.2/80.2 Wh (102.5%)
volts: 17.2 min: 15.4 model: Razer Blade type: Unknown serial: <filter>
status: Full
Device-1: hid-10:94:bb:bb:a8:91-battery
model: Magic Keyboard with Numeric Keypad serial: N/A charge: N/A
status: Discharging
CPU:
Info: model: Intel Core i7-8750H bits: 64 type: MT MCP arch: Coffee Lake
family: 6 model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xEC
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 9 MiB desc: 1x9 MiB
Speed (MHz): avg: 4062 high: 4101 min/max: 800/4100 scaling:
driver: intel_pstate governor: performance cores: 1: 4046 2: 4028 3: 4078
4: 4067 5: 4101 6: 4037 7: 4100 8: 4100 9: 4086 10: 4001 11: 4059
12: 4044 bogomips: 52799
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
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: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Razer USA
driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
Device-2: NVIDIA TU104M [GeForce RTX 2080 Mobile] vendor: Razer USA
driver: nvidia v: 510.47.03 alternate: nouveau,nvidia_drm bus-ID: 01:00.0
chip-ID: 10de:1e90 class-ID: 0300
Device-3: Microdia NexiGo HD Webcam type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-2.1.4:13 chip-ID: 0c45:2690
class-ID: 0102 serial: <filter>
Device-4: IMC Networks Integrated Camera type: USB driver: uvcvideo
bus-ID: 1-7:7 chip-ID: 13d3:56d5 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
loaded: modesetting,nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1015x285mm (40.0x11.2")
s-diag: 1054mm (41.5")
Monitor-1: HDMI-0 res: 1920x1080 hz: 120 dpi: 30
size: 1600x900mm (63.0x35.4") diag: 1836mm (72.3")
Monitor-2: DP-1 res: 1920x1080 hz: 120 dpi: 30
size: 1600x900mm (63.0x35.4") diag: 1836mm (72.3")
OpenGL: renderer: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2
v: 4.6.0 NVIDIA 510.47.03 direct render: Yes
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Razer USA
driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA TU104 HD Audio vendor: Razer USA driver: snd_hda_intel
v: kernel bus-ID: 01:00.1 chip-ID: 10de:10f8 class-ID: 0403
Device-3: XMOS JDS Labs UAC2 DAC (XU208) type: USB driver: snd-usb-audio
bus-ID: 1-2.1.1:10 chip-ID: 20b1:30da class-ID: fe01
Device-4: Microdia NexiGo HD Webcam type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-2.1.4:13 chip-ID: 0c45:2690
class-ID: 0102 serial: <filter>
Sound Server-1: ALSA v: k5.16.8-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.45 running: yes
Network:
Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
IF: wlo1 state: up mac: <filter>
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB
driver: btusb v: 0.8 bus-ID: 1-14:14 chip-ID: 8087:0aaa class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 11.38 TiB used: 172.1 GiB (1.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVLB512HAJQ-00000 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: EXA7301Q temp: 49.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Western Digital
model: WD20NMVW-11EDZS3 size: 1.82 TiB block-size: physical: 512 B
logical: 512 B type: HDD rpm: 5200 serial: <filter> rev: 1072 scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Western Digital
model: WD Game Drive size: 4.55 TiB block-size: physical: 4096 B
logical: 512 B type: N/A serial: <filter> rev: 5002 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Western Digital
model: WD Game Drive size: 4.55 TiB block-size: physical: 4096 B
logical: 512 B type: N/A serial: <filter> rev: 5002 scheme: GPT
Partition:
ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 172.1 GiB (36.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 720 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 172.1 GiB (36.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757
ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 172.1 GiB (36.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757
ID-5: /var/tmp raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 172.1 GiB (36.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-46b8c56b-d7cf-4e46-a6d9-d6ac2ee0a757
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.52 GiB used: 2.2 MiB (0.0%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 67.0 C pch: 68.0 C mobo: N/A gpu: nvidia
temp: 59 C
Fan Speeds (RPM): N/A
Info:
Processes: 332 Uptime: 26m wakeups: 2 Memory: 15.52 GiB
used: 3.1 GiB (19.9%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 clang: 13.0.1 Packages: pacman: 1956 lib: 565 Shell: fish
v: 3.3.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.12
Garuda (2.5.4-2):
System install date:     2022-02-01
Last full system update: 2022-02-12
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:

KDE has already dropped some other "movements" in the past, have you ever searched for them on the net? :slight_smile:

1 Like

Similar to SGS' post, it is not uncommon for these effects to fail from time to time, as both KDE & local & upstream developers make changes that can impact them. It is nothing new.

I think I have seen a forum post concerning this or another effect. Search the forum, then Google, and look for bug reports.

And, of course, you have an nVidia chipset. That could be the culprit, right there. :frowning:

Just some info because I can't seem to reply on "412" category: ( feel free to move it there )

On the 'fall apart' topic:

there has been some bugfixs in the last few days:

with 449844 โ€“ Fall Apart effect in new overview

and fix:

I just tested, since I am on kde git edition, and fall apart effect works perfectly

3 Likes

sorry for creating this topic... but I just didn't knew how or where to reply!

mentioning @NovaCore

2 Likes

I appreciate the effort to reply, thank you!

I saw these fixes for 5.24.1 already so my mind was at ease :slightly_smiling_face:
I was panicking since fall apart is clearly the best desktop effect ever :wink:

How long does it normally take for the fixes to be applied to the master?

Thanks again!

Well... next tuesday should be 5.24.1 release, should have it. ( maybe give 1 day or so for packages to arrive )

2 Likes

I moved it to the 412 section because we ask that you first look for the cause yourself on the net before opening a topic.
It only unnecessarily inflates the forum, and everyone is against bloat.

When something will be ready is purely speculative, one can hope but nothing is certain.
Just wait and see.
Not making a statement saves you from being reproached afterwards, but you did say that ... (For your own spin as sample :slight_smile: )

2 Likes

well... i wasn't mentioning as to why it was moved ... I just wanted to give out that info.

I remembered seeing a bugfix on kwin commits about fallapart effect.
and I tested it on kde git.
Also I double checked that the fix was included on 5.24 branch.

Anyway, If by any way I am wrong, so be it! it wouldn't be the first time!

EDIT: clarification.... honestly, I am predicting that I think it should be, but obviously, cannot be completly sure. Things can be reverted, for example.
What I meant was ... "If by any way my prediction is wrong, so be it, since there are a lot of things (almost everything) that I predict and then am wrong" :stuck_out_tongue:

4 Likes

@SGS I apologize for the original post, I was panicking because it's my favorite effect :smile: I'm still learning how to troubleshoot Arch Linux in general.

I now know to keep an eye on the KDE blog/git for KDE related bugs in the future.

3 Likes

Threads merged and moved. There's a problem and a solution. :grin:

4 Likes

Discourse stress testing: actually two solutions for a topic, although only the first one linked in the initial post. Fantastic. :stuck_out_tongue:

2 Likes

Just a tip for anyone having trouble getting 'fall apart' to work again after updating Plasma to 5.24.1.

Go to the desktop effects settings and find the section at the bottom for "Window Open/Close Animation" where the options are Fade, Glide, and Scale. Change the setting there... then go the Compositor and change the setting for "Scale Method", the options being Smooth or Accurate.

After messing with those settings, fall apart should be working again.
Feel free to change the settings back to what you had originally, for some reason just messing with them once causes the stubborn 'fall apart' effect to come back to life :laughing: :man_shrugging: