MX Modified - Latest MX KDE 5.22 Using MX21 beta

[MAYBL8]

At this point my system is running fine.
If you want just let me know when it is good to upgrade.

[MAYBL8]

On this system I am having an issue saving ,modifying documents on my NAS drive.
I have determined that it is this system that is the issue not the NAS drive.
Other installs of MX work just fine with the NAS drive.

So I am going to reinstall this system and bring it up to the latest KDE plasma at the moment of 5.23
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.0-2-amd64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

I will document my steps as I go. I will modify this post with the steps.
First step will be overwriting this partition with the MX 21 kde standard edition.
I have to do some documenting what I have installed since I started.

Reinstalled the /root partition and left /home and reused it. System can now save changes to the NAS drive.
On this system the first change I made is the screen resolution. I had to reduce it to 1920x1080 so I could read the screen.
The login screen is still small. I need to find where to change that.
Now to add my apps back in and then change to sid and npreinings repos

[markol]

So I upgraded a clean install of MX21 to Plasma 5.22 :)
Looks like everything is working (at least after an hour of playing around)

I wanted to try the new Kalendar app from kde.org but could not install it via appstream/Discover ("Could not open appstream://org.kde.kalendar"). I tried several other applications but no success.
appstream is still version 0.14.4-1 (bullseye), however bookworm and sid have 0.15.1. Could this be the problem?
I installed Kalendar smoothly in the latest KDE Neon

And another thing... KDE Connect still slows down (cca 9 seconds) the reboot/shutdown (I mentioned it in the KDE section of the forum):

Code: Select all

Dec 25 21:56:52 testix dbus-daemon[1171]: [session uid=1000 pid=1169] Activating service name='org.kde.Shutdown' requested by ':1.16' (uid=1000 pid=1583 comm="/usr/bin/ksmserver ")
Dec 25 21:56:52 testix dbus-daemon[1171]: [session uid=1000 pid=1169] Successfully activated service 'org.kde.Shutdown'
Dec 25 21:56:53 testix dbus-daemon[1171]: [session uid=1000 pid=1169] Activating service name='org.kde.kdeconnect' requested by ':1.21' (uid=1000 pid=1665 comm="/usr/bin/plasmashell ")
Dec 25 21:56:53 testix dbus-daemon[1171]: [session uid=1000 pid=1169] Successfully activated service 'org.kde.kdeconnect'
Dec 25 21:56:53 testix org.kde.kdeconnect[10480]: kdeconnect.core: Could not query capabilities from notifications server
Dec 25 21:57:02 testix org.kde.kdeconnect[10480]: ICE default IO error handler doing an exit(), pid = 10480, errno = 11

[markol]

Plasma 5.23 (with apps 2112) running just fine in my VBox

There was a problem with DIgikam when I tried to install from PXPI popular apps.
I uninstalled it, then sudo apt update and sudo apt upgrade
Rebooted
MX updater suggested 40 more packages so I let it do the job
Rebooted again just to be sure

I did setup environment identical to my machine and everything works without glitches.

[baldyeti]

There is one thing i'd like to ask to those running a post 5.20 plasma: are you affected by this kdeconnect bug ?
You have to have kdeconnect installed, and then you'd notice if terminating a session incurs an odd delay or not.

If (and only if) i was sure this has been fixed i'd then request a backport of the current version of kdeconnect to MX21.
If i am reading correctly the bug report referenced in the above link, this issue would have been fixed in late 2021 so i am not sure if it is included in the current 5.23 version already.

[markol]

There is one thing i'd like to ask to those running a post 5.20 plasma: are you affected by this kdeconnect bug ?
You have to have kdeconnect installed, and then you'd notice if terminating a session incurs an odd delay or not.

If (and only if) i was sure this has been fixed i'd then request a backport of the current version of kdeconnect to MX21.
If i am reading correctly the bug report referenced in the above link, this issue would have been fixed in late 2021 so i am not sure if it is included in the current 5.23 version already.

I'm running 5.23 from Norbert's repo and the bug is still there.

[baldyeti]

I'm running 5.23 from Norbert's repo and the bug is still there.

Oh that is too bad but thanks for checking. Please let us know when it gets fixed in a future version (or perhaps it'll be backported by the debian maintainers themselves).

[markol]

@norbert is there a chance you could do a backport for KDE Connect regarding this bug: https://bugs.kde.org/show_bug.cgi?id=432643
I can test it in 5.23

[norbert]

@markol
I can try later on, best if someone could send me an email with the patch, do that I don't forget ;-) Still busy with family time.

[norbert]

Ok, I sent plasma-workspace 5.23.5-1~np2 to the OSC servers. Should be rebuilt in reasonable time.

Please test.