MX Linux Forum

I haven't decided by now (mostly due to some changes coming up personally)
- I plan to work in the Debian Qt/KDE Team towards updates of KDE/Plasma. In particular, new versions of plasma (5.21) will got to experimental
- After bullseye release I plan to add the new stable (bullseye) to the OBS repositories and push updates and newer versions to OBS as they come in
- if, at some time in the future, Qt in bullseye will not support newer Plasma anymore, this will probably has to stop

Hope that makes my intention more or less clear.

norbert wrote: Wed Jan 13, 2021 6:12 pm I haven't decided by now (mostly due to some changes coming up personally)
- I plan to work in the Debian Qt/KDE Team towards updates of KDE/Plasma. In particular, new versions of plasma (5.21) will got to experimental
- After bullseye release I plan to add the new stable (bullseye) to the OBS repositories and push updates and newer versions to OBS as they come in
- if, at some time in the future, Qt in bullseye will not support newer Plasma anymore, this will probably has to stop

Hope that makes my intention more or less clear.

KDE users would love to finally see backports for Stable. According to QT Company, QT 5.15 is their last LTS for QT5 series. QT6 is not ready yet and KDE wouldn't jump into it anyway. If there won't be some QT5 community fork I really don't see how Plasma/Applications could become incompatible with minor QT5 updates/backports/fixes.

I cannot provide official backports, I just try to get things compile on different releases. No guarantee, no strings attached.

Alt wrote: Thu Jan 14, 2021 6:28 am KDE users would love to finally see backports for Stable. According to QT Company, QT 5.15 is their last LTS for QT5 series. QT6 is not ready yet and KDE wouldn't jump into it anyway. If there won't be some QT5 community fork I really don't see how Plasma/Applications could become incompatible with minor QT5 updates/backports/fixes.

That's a good point, Qt version should be pretty stable for a couple of years. Maybe MX devs could allow plasma and Qt to track with Debian testing or sid for awhile without breaking their own homemade Qt apps.

MAYBL8 wrote: Tue Jan 12, 2021 12:22 pm I think I had it working before my last rebuild of the repos. And you are correct about bringing in buster packages.
I probably caused some of my own issues before due to being a frankendebian.

I have a stable sid right now so I am not going to rock the boat.

Since things are so stable right now, maybe we should create an MX Sid KDE respin. If we left off the MX Package Installer hopefully most other things would still work. We could try to base it off of MX KDE, change out the repos, remove MXPI, and see if we get an ISO that will actually install for us.

I made a respin, with MX-KDE base, then added Sid and Norbert's repos, and upgraded to plasma 5.20.5. Calling it "MX KDE Sid Respin" for now. Download the ISO from here: https://mega.nz/folder/TNtGURKb#yZKlbP2R9kEIcIQEAWbipw

It's in alpha condition, has a few rough edges. When I tried it as a live ISO in Virtualbox I had to run 'sudo NetworkManager' in a terminal to start up networking. MX Package Installer does not work, and is not likely to work as long as it is using Debian Sid repos. Passwords are the same for the MX Live ISO's - demo/demo, root/root.

Not production ready, not by a long shot. This is just for experimentation. Try it in a vm or as a live usb, but don't install it on a disk where you are keeping important data.

Updated respin ISO is here: https://mega.nz/folder/KUtCmBiY#RtWPSb5OSNYgQADc8ZLibg

Passwords are the same as the MX Live ISO: demo/demo, root/root

Still alpha condition, still not recommended for anything but experimentation. It has a fairly large number of updated packages, with plasma 5.20.5, Frameworks 5.78.0, and Qt 5.15.2

Networking still does not work automatically, you need to run 'sudo NetworkManager' after logging in. Seems to be due to a Sid version of NetworkManager that requires systemd - I'll look into whether I can revert to the MX version of NetworkManager for the next respin.

@andy,
I haven't tried your respin yet but I use CMST conman system tray for my network manager and that works quite well.

on network-manager, its worth just trying the init script from the previous version.

place the script contained in the attached archive into /etc/init.d and then issue
reboot and see if that helps.

dolphin_oracle wrote: Sat Jan 23, 2021 5:25 pm on network-manager, its worth just trying the init script from the previous version.

place the script contained in the attached archive into /etc/init.d and then issue

Code: Select all

sudo update-rc.d network-manager defaults

reboot and see if that helps.

OK, yes, that should do it. I noticed I was missing any reference to network-manager in /etc/init.d. Probably got deleted when I upgraded to the Sid packages. This should probably fix it right up, thank you.