MX Linux Forum

Which logs should I be checking to see what's going wrong?

I can double check after the backup but I seriously doubt that is the case

Mx starts but ends up on console without GUI. startx gives back xinit cannot start x server.
I can see all my files (currently doing a backup) but cannot write anything

Honestly it's a really annoying bug which affects the real world usability of MX. I'm thinking of leaving just because of this. Maybe I'll start using the KDE spin.

There is some bug introduced in mx 21 where the lock screen breaks audio of running apps.

Have a look at this: www.reddit.com/r/MXLinux/comments/s9m45 ... &context=3

Also relevant: https://forum.mxlinux.org/viewtopic.php ... 64#p675264

bump

The drop-down terminal (F4) does not follow my cursor on a multi monitor setup. This worked fine in mx19.
It is enabled in the terminal preferences.

Edit->Preferences
Drop-down->Position->Move to monitor with pointer


System: Kernel: 5.15.0-2mx-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 ...

After sleeping/locking the mic is not found by programs that have been left running. eg. Google Chrome/Meet, Slack says "Mic not found".

System: Kernel: 5.15.0-2mx-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/vmlinuz-5.15.0-2mx-amd64
root=UUID=<filter> ro quiet splash ...

Small bug report:
Using F4 for the Drop down terminal only works on the Primary Display. Even though my cursor is on another display, the drop down appears on the primary. Move to monitor with pointer is checked in Preferences -> Drop-down tab -> Position.

Bump.
Anyone experiencing the same?

Small bug report:
Using F4 for the Drop down terminal only works on the Primary Display. Even though my cursor is on another display, the drop down appears on the primary. Move to monitor with pointer is checked in Preferences -> Drop-down tab -> Position.