MX Linux Forum

As a KDE user, who used sysV and X11 all the time with MX23, is there a way i can find out if systemd and Wayland with MX25 KDE will work for my use case, other than trying it out and „learn the hard way“ that it does not? :-)

alright thank you so much! Then I will leave virtualbox as it is for now, I was so used to having "splash" and "quiet" activated that I didnt even consider that as an option...
So I replaced those words with "nosplash" and planning to do nothing more right now... just wait till the problem occurs ...

Thanks again to all of you for your detailed replies – it really helps to get different perspectives on the issue.

Here's what I'll do next, based on your input / what I have understood so far:

Step 1: Remove VirtualBox completely
Since I currently don't need it, and there's a chance it might ...

Right now I use Kernel 6.1.0-37-amd64 [6.1.140-1] and everything fine so far except that boot thing that happens occasionally (about every 20th boot or so, but still annoying)

Until now I had always installed VirtualBox over MXPI, because I thought this is always the preferred way within the MX ...

Hi everyone,

I'm using MX Linux with a fully encrypted root partition, and I’ve been running into the following issue:

=== The Problem ===
Roughly 1 out of every 20 boots, the system freezes right after decrypting the root partition. I see the usual message:

cryptsetup: cryptsetup successfully ...

Strawberry :-)

Hello!

Hello!

I have recently installed a new graphics card, see here https://forum.mxlinux.org/viewtopic.php?t=82841


Now the night colors in KDE are no longer activated automatically at system startup, although I have selected “always on”.


When I restart, the night colors are no longer active ...

At boot the kernel chooses the driver automatically after detecting the hardware. Usually radeon is for older cards and amdgpu for the newer ones (probably including yours).
To check which driver is used run lspci with the -k flag.

lspci -k



finally installed the card and it works so far ...

I think Debian fixed it now, latest chromium got installed here without any special adjustments.
apt policy chromium
chromium:
Installed: 131.0.6778.108-1~deb12u1
Candidate: 131.0.6778.108-1~deb12u1
Version table:
*** 131.0.6778.108-1~deb12u1 500
500 http://security.debian.org/debian ...

CharlesV wrote: Sat Dec 07, 2024 12:29 pm Das Problem wird hier beschrieben, zusammen mit einigen Methoden, um es vorübergehend zu beheben.

viewtopic.php?p=800655#p800655

Danke, das habe ich übersehen, jetzt verstehe ich :-)