Page 7 of 17

Re: Responses to Coming changes in impending MX 25 release.

Posted: Tue Aug 05, 2025 5:03 pm
by siamhie
rambo919 wrote: Tue Aug 05, 2025 4:26 pm
siamhie wrote: Tue Aug 05, 2025 3:24 pm @LU344928 You do have another choice.
You could try installing the sysVinit MX-25 XFCE ISO and add kde-full from the enabled tab in MX Package Installer.
You will still have access to all of the MX Tools. I've done this in the past.
The problem is that KDE is progressively dropping support for sysv simply by ignoring it exists. Already in KDE5 you have to boot into systemd for the firewall settings to actually function (it works fine with sysv you just can't change anything) and the system monitor has missing tabs unless you run systemd. I don't even know yet what else broke in KDE6 on sysv but it can't be pretty.
I believe you're right. I just read this KDE ArchWiKi that stated this
3.10 systemd startup

Plasma uses a systemd user instance to launch and manage all the Plasma services. This is the default startup method since Plasma 5.25, but can be disabled to use boot scripts instead with the following command (however this may stop working in a future release):

$ kwriteconfig6 --file startkderc --group General --key systemdBoot false

More details about the implementation can be read in Edmundson's blog: Plasma and the systemd startup.
https://wiki.archlinux.org/title/KDE#systemd_startup

Re: Responses to Coming changes in impending MX 25 release.

Posted: Tue Aug 05, 2025 5:10 pm
by DukeComposed
autumn wrote: Tue Aug 05, 2025 4:56 pm Thanks for posting this @Markus85. That was my concern, regarding mullvad installer also.
I'm running the sysvinit-only MX-23 respin and have had no problems running Lutris, WINE, or the Mullvad VPN software on it. I believe the mullvad-vpn package offered in the repos is 2025.05 and it complained that I should upgrade to 2025.07, so last weekend I tried installing that by adding the official Mullvad repo and key manually and that install barfed on trying to install the systemd service unit file. So I did some very basic repair actions, then an uninstall and reinstall, and a restart. Now, so far as I can tell, I'm using the official 2025.07 package with the MX 2025.05 startup script. No complaints. If running "apt-get install -f" sounds scary to you, maybe think twice before installing anything outside of the MXPI guardrails. Personally, I suspect MX-25 will have a newer Mullvad package by default and, to be honest with myself, there wasn't anything wrong or defective about the functionality of 2025.05 version I'd had. Both versions work more or less equally well, but it reminded me that I live perhaps too comfortable a life inside the MX-only, sysvinit-only walled garden.

Re: Responses to Coming changes in impending MX 25 release.

Posted: Tue Aug 05, 2025 5:10 pm
by siamhie
FullScale4Me wrote: Tue Aug 05, 2025 4:22 pm
uncle mark wrote: Tue Aug 05, 2025 3:54 pm I get nothing.

Code: Select all

mark@MX-KDE:~
$ swapon --show
mark@MX-KDE:~
$ sudo swapon --show
[sudo] password for mark: 
mark@MX-KDE:~
$ swapon --show
mark@MX-KDE:~
This is mine with a swap file enabled:

Code: Select all

mike@dell-lt:~
$ swapon --show
NAME       TYPE SIZE USED PRIO
/swap/swap file   3G   0B   -2
and this is mine with a partition.

Code: Select all

swapon --show
NAME      TYPE      SIZE USED PRIO
/dev/sdb2 partition  64G   0B   -2

Re: Responses to Coming changes in impending MX 25 release.

Posted: Tue Aug 05, 2025 5:53 pm
by Adrian
@uncle mark I'm glad I asked because you have that partition for nothing, you probably just need to add in /etc/fstab an entry like:
UUID=.... none swap defaults 0 0

Where UUID is the uuid for you swap partition, use blkid to get the uuid.

Re: Responses to Coming changes in impending MX 25 release.

Posted: Tue Aug 05, 2025 6:25 pm
by autumn
DukeComposed wrote: Tue Aug 05, 2025 5:10 pm
autumn wrote: Tue Aug 05, 2025 4:56 pm Thanks for posting this @Markus85. That was my concern, regarding mullvad installer also.
I'm running the sysvinit-only MX-23 respin and have had no problems running Lutris, WINE, or the Mullvad VPN software on it ... Now, so far as I can tell, I'm using the official 2025.07 package with the MX 2025.05 startup script. ... Personally, I suspect MX-25 will have a newer Mullvad package by default and, to be honest with myself, there wasn't anything wrong or defective about the functionality of 2025.05 version I'd had ... I live perhaps too comfortable a life inside the MX-only, sysvinit-only walled garden.
Thanks for assurances; great to know. Hadn't upgraded mullvad yet, as, yes, 2025.5 works fine. And I don't think there's anything wrong with being in the walled garden tbh, as everything works better when there's good stability and compatability ... can get a lot more done, and without added stress tech stuff increasingly seems to bring.

Re: Responses to Coming changes in impending MX 25 release.

Posted: Tue Aug 05, 2025 6:26 pm
by uncle mark
Adrian wrote: Tue Aug 05, 2025 5:53 pm @uncle mark I'm glad I asked because you have that partition for nothing, you probably just need to add in /etc/fstab an entry like:
UUID=.... none swap defaults 0 0

Where UUID is the uuid for you swap partition, use blkid to get the uuid.
Well I'll be damned. You were right. No swap shown in fstab. Would have been that way since I installed I guess. Never had an issue, though. <shrug>

Thanks for the assist.

Code: Select all

mark@MX-KDE:~
$ swapon --show
NAME      TYPE      SIZE USED PRIO
/dev/sda2 partition 9.8G   0B   -2
mark@MX-KDE:~

Re: Responses to Coming changes in impending MX 25 release.

Posted: Tue Aug 05, 2025 6:29 pm
by AVLinux
Slightly OT...

I've never really understood the case for SWAP greater than 1 or 2 Gb, if your system is out of memory it's going to be a downward spiral and all kind of weird stuff is going to be going on in which case you'll reboot anyway or at least you'd want to on old mechanical HDD systems. I don't know if I've ever run out of memory even on my older computers. Maybe I'm stingy but I want that 10Gb for Data not for unlikely emergencies...lol

Re: Responses to Coming changes in impending MX 25 release.

Posted: Tue Aug 05, 2025 6:40 pm
by Adrian
AVLinux wrote: Tue Aug 05, 2025 6:29 pm Slightly OT...

I've never really understood the case for SWAP greater than 1 or 2 Gb, if your system is out of memory it's going to be a downward spiral and all kind of weird stuff is going to be going on in which case you'll reboot anyway or at least you'd want to on old mechanical HDD systems. I don't know if I've ever run out of memory even on my older computers. Maybe I'm stingy but I want that 10Gb for Data not for unlikely emergencies...lol
I think 1-2GB should cover accidental need, if it's a runaway process it will fill the swap quickly too, the only reason to have larger swap is only if you want to use for hibernation.

Re: Responses to Coming changes in impending MX 25 release.

Posted: Tue Aug 05, 2025 7:11 pm
by RedGreen925
rambo919 wrote: Tue Aug 05, 2025 12:42 pm
RedGreen925 wrote: Tue Aug 05, 2025 10:44 am The devs are the normal Gnome morons who have been like that for the entire 26 years I have used GNU/Linux.
They used to be more reasonable... then with Gnome 3 they basically stuck their heads up their own.... and kept them there.

Takes all sorts I guess.
I just remember the lies and BS they used to spread about KDE/Trolltek way back then because they had the audacity to dual license the QT toolkit for paying and free uses. Meanwhile their beloved Redhat launched as a for profit company for insane valuation in the .com bubble at the same time, hypocrites every one of them. As far as I can see nothing has changed with them in all of these years since I first started using this in 1999, as they say you do not get a second chance to make a first impression. And the one they made on me has been proven true for going on decades now.

Re: Responses to Coming changes in impending MX 25 release.

Posted: Tue Aug 05, 2025 7:21 pm
by AVLinux
Well, I don't pretend to know all the details and Gnome 2 was on it's way out when I got onboard but certainly RedHat seems to call the tune and what Fedora gets first (usually in an early beta state) we all get later. It's always puzzled me how Debian is often the cautious voice of choice and reason and the foundation of most popular Distros yet they seem to carry no weight in 'big Linux' decisions..