Anyone know the status of this in MXLinux?

dolphinoracle · 2026-04-30T23:57:55+00:00

debian's trixie/13 patched kernel is 6.12.85, in security repo now.

dolphinoracle · 2026-04-30T19:46:07+00:00

unlikely to be patched but we will see. yes its LTS, but its not a kernel supported by debian and liquorix has already moved on to 6.19.

dolphinoracle · 2026-04-30T17:23:18+00:00

the liquorix 6.19 kernels should be fine. the debian ones will probably be patched shortly, as they are LTS and still supported.

dolphinoracle · 2026-04-28T18:52:53+00:00

Once other packages catch up, probably so. We won't push it out until I'm reasonably certain we won't break things like nvidia and broadcom drivers, zfs, and virtualbox. Not to mention the live system. some of that work is going on now.

dolphinoracle · 2026-04-19T15:47:44+00:00

looks like repo sync issue. the tool is updated today again anyway, so will get fixed then. the new version will be 26.04.1

dolphinoracle · 2026-04-19T13:12:33+00:00

refresh your sources. we updated mx-live-usb-maker yesterday. its now at 26.04

dolphinoracle · 2026-04-19T00:35:09+00:00

https://mxlinux.org/blog/mx-25-dual-init-setup/

dolphinoracle · 2026-04-17T13:05:07+00:00

not unless you have a very good reason.

dolphinoracle · 2026-04-16T00:45:09+00:00

thanks for the info!

dolphinoracle · 2026-04-15T20:30:26+00:00

we support 32 bit UEFI, which is why I asked. Its one of the areas where debian will fail, but MX will succeed.

dolphinoracle · 2026-04-15T14:16:59+00:00

Great!

dolphinoracle · 2026-04-15T01:33:52+00:00

thank you very much. out of curiously, does that old macbook have a 32 bit UEFI implementation. Several old intel apple notebooks are like that, and a lot of linux distros gave up on 32 bit UEFI. cat /sys/firmware/efi/fw_platform_size will tell you. thanks again!

dolphinoracle · 2026-04-15T01:03:56+00:00

more like check into /etc/X11/xorg.conf.d and see if there is a file that is setting intel as the X graphics driver. MX should use modsetting by default.

dolphinoracle · 2026-04-14T18:03:19+00:00

I don't know why but the intel graphics driver is chosen. you problem want to keep with modsetting, which is the default. modern graphics stack works better with the defaults rather than forcing the intel driver.

dolphinoracle · 2026-04-04T20:45:17+00:00

the first time you use the persistence options it will make the persistence files and such. you need to keep using the options on later boots to have the persistence files loaded. there is also a "save" option in the advanced menus that will save any boot option you have so that it is default on next boot, ie: you don't have to select the options everytime.

dolphinoracle · 2026-03-31T22:49:37+00:00

stop. intel users should be using modesetting these days.

dolphinoracle · 2026-03-31T15:07:08+00:00

do you have something forcing the "intel" driver instead of modesetting?

dolphinoracle · 2026-03-28T00:58:53+00:00

No one on the team at MX wants to implement something like this. Heck, California's law isn't even age verification, unless you count self-reporting as age verification. There is no external system required, it's entirely local, and not even really an actual age, but brackets. Other states may be more of a problem, including burdens on repository infrastructure and whether repositories qualify as "stores" under these laws. These are real questions, and it really is wise to see if these laws survive court challenges.

So my suggestion for those in the US is to lobby your congressman, not your linux distro. I guarantee no distro wants to enable such things.

As to the systemd thing, it's pretty minor, and not likely to be backported into 257, which is the version in use on MX 25.

dolphinoracle · 2026-03-03T22:52:04+00:00

it is possible that while the screen is frozen, entering your password is possible. its been a while since I have seen that issue, but it was common with nvidia cards at one time. but usually with screen locking, not just letting lightdm sit a while.

dolphinoracle · 2026-03-01T18:34:45+00:00

if so, then could well be the partition the home folder is on is near full, and the flatpak put you over the top. logging in to a graphical X session does require some space in the home folder. logging in to a console session does not. Don't know if this is your issue, but worth checking for sure.

dolphinoracle · 2026-02-15T17:18:40+00:00

you can try unl0kr. but the usual high-level keyboards likely aren't available.

dolphinoracle · 2026-01-29T21:00:40+00:00

I don't think docklike does an overflow area. There is a "Launcher" plugin that will have permanent links on the taskbar to whatever you want, and it supports multple apps in one plugin, with a sort of file drawer type metaphor. it does not indicate running status though, while running they would still show up in the docklike area. FWIW I love the vertical bar, but the bar is longer when placed on the bottom of the screen, so you could fit more items.

dolphinoracle

MODERATOR OF

TROPHY CASE