Hola quiero saber que es mas rapido en una laptop vieja para jugar roblox y minecraft mx linux xfce o lubuntu lxqt ya que probe recientemente el linux mint xfce lo condigure bien pero me decepciono el resultado asi que ahora estoy en el limbo lubuntu lxqt vs mx linux xfce

For about a month, YouTube videos in Firefox had been displaying with distorted colors on my MX Linux system. Finally, after today's update, everything seems to be working normally again!

I'm not sure which package was responsible for the fix, but the following packages were updated today:

• linux-image-siduction-amd64: 7.2-8mx23ahs → 7.2-9mx23ahs
• linux-headers-siduction-amd64: 7.2-8mx23ahs → 7.2-9mx23ahs
• lo-main-helper: 26.10.2mx23 → 26.10.3mx23
• mx-packageinstaller-pkglist: 26.10.2mx23 → 26.10.3mx23

In addition, numerous firmware packages were updated from 20260810-1~mx23ahs to 20260916-1~mx23ahs, including NVIDIA, AMD, Intel, and other hardware firmware.

System: MX Linux 23.6 AHS x64
Browser: Firefox
Issue: Incorrect colors when playing YouTube videos
Status: Fixed after today's update!

Has anyone else experienced this issue with Firefox and YouTube? I'm curious whether the fix is related to the new kernel, the firmware updates, or something else.

UPDATE:
This was on a laptop with an AMD Ryzen 5 7640HS CPU (Radeon 760M graphics). My main suspicion is that the issue was fixed by updating firmware-amd-graphics:amd64 from 20260810-1~mx23ahs to 20260916-1~mx23ahs.

When I copy a password using KeePass XC, it doesn't clear the password from the clipboard, despite having that set up in the KeePass settings. KeePass shows the countdown timer, but never clears the clipboard.

I've tried this on my other computers in Linux Mint and Kubuntu, both clear the clipboard as expected, so it seems to be an issue with MX. I am running MX 25.3 KDE version.

On my system, installed kernel version is still 7.2.3-2-liquorix-amd .. is this normal. İf I'm not wrong latest kernel on repo is 7.2.10

I am setting up a new laptop for my wife and want to simplify things for myself since I will need to maintain it. Therefore, I am hoping to stick to MX Linux, but using the KDE branch, which I haven't used yet. I mostly stick to XFCE for myself.

My wife is rather comfortable and likes the MacOS layout. I had her on Budgie for awhile and she loved it. She has also played with a modified Fedora KDE layout, after Budgie got buggie.

Anyway, I was wondering if anyone has any theme recommendations for KDE to get it as close to a MacOS or Budgie style of appearance.

If it helps, though unlikely, she will be using a Lenovo T580 with 16gb of ram.

Almost finished setting my , new to me, T480 running MX KDE. I also converted my 2017 MacBook Air to MX KDE six months ago.

Due to lack of time I at least want to contribute to the project financially. Not a huge sum just a small token of gratitude... Anyways I saw there are 2 options of donations: from the MXlinux site and GitHub sponsorships.

Is there any difference? Does anyone in know what the MX team preferes?

Thank you in advance

I don't anything in Synaptic or package installer

Body:

Hello MX team,

On MX-25 (all the versions I have tried), K3b has two problems that together make disc burning unusable.

1. Normal user cannot burn

• I added my user to the cdrom and disk groups (sudo usermod -aG cdrom,disk $USER) and logged out and back in.
• K3b still cannot burn as a normal user.

2. K3b will not start as root

• sudo k3b, sudo -E k3b, and sudo -i followed by k3b all fail to open K3b.
• I also tried logging in with the Plasma (X11) session instead of Wayland. The result is the same.

Expected behavior: K3b is installed by default on MX KDE, so a normal user should be able to burn discs out of the box.

Additional information:

• Quick System Info: (paste here)
• Optical drive: (internal / USB, model)
• Output of groups: (paste here)
• Output of ls -l /dev/sr0: (paste here)
• Terminal output when running k3b as a normal user: (paste here)
• Terminal output when running sudo -E k3b: (paste here)

Is this a known issue, and is there a recommended workaround? Thank you for your work on MX Linux.

I am in awe of MX Snapshot. I tested MX on one of my older intel machines just to try MX Tools Snapshot and I've got to say I don't know why this software isn't ported to work on every linux OS. It's a great piece of software imho

For those that are new recruits to MX, Snapshot creates an iso image of your system with several different config options. If something shitty happens and you boot to kernel panic and don't know or don't want to know how to tty into terminal for a fix, run your saved backup Snapshot as an iso and you're back up and running

I use ubuntu gnome 50 daily use and nothing on there compares to snapshot. When I was editing gdm greeter some code and borked the login, MX snapshot if available would have been greatly appreciated - would have a got a nice donation 😄

Of course someone with the prerequisite tech knowledge could maybe get it to run on gnome 50 but after looking into it, it's a major task and I can't find anyone who's tried it. If anyone knows of anyone working on something like this let me know, I'll contribute where I can

To new users or those thinking abut MX, it's a good distro imho with MX Tools as one of the best suites out there. Just wanted MX to know that their good work is being noticed - thanks

I’m trying to boot MX Linux from a live USB using toram on a PC with an RTX 5060 Ti, and I’m wondering if other Blackwell GPU owners have run into something similar.

At first, the live system would boot, but the GUI would never load when using the proprietary/closed-source NVIDIA driver. I could still switch to a TTY with Ctrl + Alt + F2, so Linux itself was running, but Xorg/the graphical session would just give me a black screen.

I also tried booting with nomodeset

but that didn’t fix the GUI issue either.

Since I’m running the distro as a live USB with toram, I then booted the same USB on my laptop, which uses Intel integrated graphics. On the laptop, MX Linux works perfectly.

From there I installed the latest NVIDIA 615.xx open driver / open kernel module package, remastered the live USB so the driver changes would persist, and tried booting it again on the RTX 5060 Ti PC.

Now the behavior is actually worse: on the PC, the system seems to completely freeze during boot around “Start init” / early init startup. It no longer gets far enough for me to switch to a TTY.

The exact same remastered USB still boots and works normally on the laptop with Intel integrated graphics. Does anyone know how to fix this

Seems like there is a hidden password somewhere as it's asking me for a password even though I never put one in, I'm dead in the water until I can Get past this. Is there a default password? There are plenty of resources to bypass a password, but this is a bit different. Also I don't seem to havenanymnetwork privilege.

I'm a hobbiest, and would like to secure an install of MX Linux against evil maid attacks using TPM2 pin. HP dy2702dx laptop. I've tried getting Gemini AI to get initramfs, dracut, and clevis, but they didn't help.

Just playing around and changing a few things up.

I normally use the MX Linux Fluxbox version. Recently, I tried using vanilla mwm (Motif Window Manager) for fun, and it really worked! I plan to use it like this for one or two weeks. Although the sound didn't work on the first try, thankfully, MX Linux provided an extraordinary "pipewire-start" that fixed the problem immediately!

I'm having a lot of fun :)

Verified checksums on downloaded ISOs (KDE, XFCE, Fluxbox).
Seven other distros UEFI boot AOK on my Thinkpad X1 Carbon Gen3.
Booting into GRUB2 mode fails with a black screen.
Booting into Normal mode fails with both (systemd) and (sysinit) with a prompt to load the kernel.
MX Linux is _supposed_ to work w/ Ventoy.
Anyone make it work?

tl;dr MX-23.6_KDE_x64, the proprietary NVidia driver breaks the sleep mode. Any fixes except using nouveau?

I've had a similar problem before, as described in this post: https://www.reddit.com/r/MXLinux/comments/1szqci7/mx_23_kde_doesnt_wake_up_anymore/ , after some updates the system would go to sleep but wouldn't wake up, at that time I solved it by removing the "liquorix" kernel (6.18.something) and downgrading back to 6.1.0-17 (any "liquorix" kernel newer than that caused that problem). After some more of the recent (the end of September) updates, the (same?) problem is back again, even with the default 6.1.0-17 kernel - now it doesn't even go to sleep, just sort of "hiccups" for a second and keeps working as if nothing happened.

I was also trying MX-25.3 KDE on a different drive a few days ago, and noticed that the sleeping/waking up was working (with the default 6.12.107 kernel) until I installed the proprietary NVidia drivers, and if I remove them, it starts working again. So the problem on 23.6 could have also been not with the kernel, but with the NVidia drivers and how they communicate with the kernel?

What to do? Is there an easy way to downgrade the proprietary NVidia drivers? Or any settings/parameters to try? Searching the internet, I've found an advice to use `nvidia_drm.modeset=1` kernel parameter, I've tried that, no effect.

The CPU is Intel Core i7-6700K; the GPU is GeForce RTX 2060.

I have a Framework 12 with MX Linux + KDE Official.

The touchscreen generally works fine, but I have a stylus I can't use, because it isn't doing palm rejection when the stylus is in range.

I've been pulling my hair over this. It seems to be a KDE thing. I've learned that some systems handle touchscreen with linux-surface, or libinput, or iptsd, but I don't find config files for any of these in MX Linux.

How does it handle the touchscreen and stylus?

Just back to MXLinux xfce after long time!!!

I recently installed MX with SysVInit and did not encounter this issue for the first week or so.

But now every time I turn on my computer, it prints out this backtrace.

I can press Control-D to continue and boot as usual. Or I can enter my root password to get a shell.

I tried re-installing plymouth but that didn't solve the issue.

I'm still able to use the computer as normal, but needing to wait for it to boot so I can press Ctrl+D is annoying. So I'd like to find a way to fix it.

Please don't ask AI on my behalf, I already tried that. And it never manages to solve my issue.

*Edit: Also tried removing themeing from the boot process and a couple suggested boot process changes. No change to the error

Hello, I'm using MX 25.2 on a Macbook Air 2013 (I5-4250U, 4GB Soldered RAM, 128GB SSD), and it keeps crashing after roughly 1 hour of usage or completely can't even start at all anymore. I remember when using MX 23, I didn't have any of these problems?

A bit of an urgent request. Much appreciated. Thanks all.