MX Linux Forum

a mirror sync might probably in-progress, try a different mirror, or wait a bit

also, please remove http://deb.debian.org/debian bullseye-backports , can't be certain, but pretty sure this repo is not enabled by default on antiX
no one should be manually enabling this repo unless they know exactly ...

puddletag is coming from Debian, not MX. When using MXPI it will show under the Stable Repo because it shows what is in Debian Stable and MX Stable, I know its a bit confusing sometimes. :hug:

please try to install the recommends listed for this package (they don't install by default on MX ...

@Staempunk if I remember right there wasn’t anything dodgy with it, it was an issue building properly.

I can’t remember what it was but I can take a look at it sometime next week.

the update for libexpat1 is a security update, so the better question is...

why wouldn't you want to stay updated in the first place anyway?


You're rigth, thank you. I ask because I wanna know more... sorry if that sounded stupid :confused: But I'm very grateful for your feedback, so again ...

Amiga-MX unfortunately tuxmath is coming from Debian's repos and not ours.

But please share your Quick System Info if you want help attempting to see if it can be fixed on MX.

If not, Debian is the best place to report the issue. They will also want system information and probably some logs too ...

the update for libexpat1 is a security update, so the better question is...

why wouldn't you want to stay updated in the first place anyway?

Lvl2u wrote: Sat Feb 12, 2022 2:27 pm ...
Yeah, Im a begginer

You're also a Porygon it seems...

Sorry I couldn't help it

the issue with updating scrcpy for MX-19 is that it may not work unless it is built with a newer version of libc6 than what comes with MX-19.

I looked at updating the version available for MX-21 and it looks possible to update that, when I try it, I can try for MX-19 but there is a good chance its ...

This is really awesome, thanks for sharing.

That is an extremely old article (TechRepublic at that) and it doesn't highlight the root cause of how the compromise occurred, which was through using outdated WordPress at the time.
There were several other issues like some lack of ISO verification methods, etc, etc.

Malicious code or a backdoor ...