MX-21 KDE/plasma RC1 feedback

[Gerson]

@rainfox; To permanently disable bluetooth and use it only when required, from System Preferences > Startup and Shutdown > Background Services; uncheck the box, that's it.

[jackdotnet]

@Adrian @SwampRabbit @dolphin_oracle
More on KDE RC1 slow as molasses...made live usb 3.0...took over 20 minutes to shutdown w/persist-save.
Following (hopefully code tagged properly) is MX-19.4 and MX-21 KDE RC1 and Mx-21 ahs rc1 Graphics sections of QSI.

Code: Select all

           Distro: MX-19.4_x64 patito feo November 11  2020
 Graphics: Device-1: AMD Picasso vendor: Gigabyte driver: N/A bus ID: 06:00.0 chip ID: 1002:15d8 
           Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1920x1080~N/A 
           OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1 
           direct render: Yes 
           
           Distro: MX-21_ahs_rc1_x64 Wildflower October 10  2021
 Graphics: Device-1: AMD Picasso vendor: Gigabyte driver: amdgpu v: kernel bus ID: 06:00.0 chip ID: 1002:15d8 
           Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.42.0 5.14.0-2mx-amd64 LLVM 12.0.1) 
           v: 4.6 Mesa 21.2.1 direct render: Yes 
           
           Distro: MX-21_KDE_RC1_x64 Wildflower October 5  2021 
 Graphics: Device-1: AMD Picasso vendor: Gigabyte driver: amdgpu v: kernel bus ID: 06:00.0 chip ID: 1002:15d8 
           Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,vesa compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.10.0-8-amd64 LLVM 12.0.1) 
           v: 4.6 Mesa 21.2.1 direct render: Yes

I have no clue why KDE RC1 is slow and non-responsive while MX-21_ahs_rc1 and my daily driver MX-19.4 are problem free (all running on the same box)

[rainfox]

@Gerson thanks for this, havent found this setting yet.

[baldyeti]

I sent up an updated kimageannotator 0.5.2-1, hopefully it fixes this segfault, if you get this update can you verify if it's fixed or not? Thanks

spectacle does not crash anymore indeed, thanks !

---

with the latest wave of updates building (wireless?) DKMS drivers took quite a while even though i don't own the corresponding HW, i hope it's a one-time thing ...

[danielson]

Wanted to report sooner but...

Anyhow, EMOJI Selector does not show all "icons":
https://i.imgur.com/YM1mJEV.png


On the bright side of things, CPU and Memory usage are usually pretty low.

Go KDE go!

[Adrian]

I sent up an updated kimageannotator 0.5.2-1, hopefully it fixes this segfault, if you get this update can you verify if it's fixed or not? Thanks

spectacle does not crash anymore indeed, thanks !

I tested and can confirm, I replaced ksnip with spectacle for the final because spectacle interface is a bit better integrated in Plasma I think.

BTW, Final will be released shortly, new bug reports will probably not make any difference.

[SwampRabbit]

spectacle does not crash anymore indeed, thanks !

---

with the latest wave of updates building (wireless?) DKMS drivers took quite a while even though i don't own the corresponding HW, i hope it's a one-time thing ...

Thanks for confirming that big is fixed, as Adrian said it’ll be added by default on final.

You can remove the dkms you don’t need if you want to.

[rainfox]

@rainfox; To permanently disable bluetooth and use it only when required, from System Preferences > Startup and Shutdown > Background Services; uncheck the box, that's it.

This did not fix it. The Bluetooth device still was turned on after reboot and with this service disabled. bluetoothd was still running.

What did help was executing "sudo systemctl disable bluetooth"

After that I reenabled the Bluetooth setting in the System Preferences > Startup and Shutdown > Background Services. It did not start Bluetooth. Looks like this setting is not connected to the bluetooth service.
Can anyone check or confirm this?

[markol]

@rainfox; To permanently disable bluetooth and use it only when required, from System Preferences > Startup and Shutdown > Background Services; uncheck the box, that's it.

This did not fix it. The Bluetooth device still was turned on after reboot and with this service disabled. bluetoothd was still running.

What did help was executing "sudo systemctl disable bluetooth"

After that I reenabled the Bluetooth setting in the System Preferences > Startup and Shutdown > Background Services. It did not start Bluetooth. Looks like this setting is not connected to the bluetooth service.
Can anyone check or confirm this?

I can confirm that this "fix" did not work. Bluetooth still enabled after reboot.

[SwampRabbit]

@rainfox and @markol this has to be because you’re using systemd then.

Because systemctl is a systemd command.