MX Linux Forum

fehlix wrote: Sat Dec 07, 2024 12:45 pm Summary of temporary fix...
...

Suppose I decide to do what you describe in the post and the problem is solved.

Is it foreseeable that a package maintainer will fix the problem permanently? If so, would I then have to undo everything possible and do a completely different procedure? What do you think the chances are that the problem will be fixed soon and that it will be possible to install it normally via apt again?

debianix wrote: Sat Dec 07, 2024 1:48 pm

fehlix wrote: Sat Dec 07, 2024 12:45 pm Summary of temporary fix...
...

Suppose I decide to do what you describe in the post and the problem is solved.

Is it foreseeable that a package maintainer will fix the problem permanently? If so, would I then have to undo everything possible and do a completely different procedure? What do you think the chances are that the problem will be fixed soon and that it will be possible to install it normally via apt again?

You either can set chromium on hold - if you still have it installed -, and wait until Debian's maintainer have fixed it,
and you would then remove the hold again to get a newer version.
Or you can upgrade now with the propose fixed, which will get latest installed,
a future updated package will get automatically a higher version, so nothing else todo.
Note: I have adjusted the post, with two additional packages.

I think Debian fixed it now, latest chromium got installed here without any special adjustments.

MadMax wrote: Sat Dec 07, 2024 9:24 am Today's updates from the Debian repos break Chromium's dependencies in a way that will remove Chromium from your system. Re-installation will also be not possible. I just stumbled upon this when I wanted to update my system (which I usually do every Friday and/or Saturday).
If you want to keep using Chromium, wait until this issue is resolved.

Maybe mark this thread as [Solved], if it is solved for you.
And perhaps let us know what TLA this PSA is about, if not a health related issue you have?

In case something got misunderstood: PSA = Public Service Announcement

Eadwine Rose wrote: Sat Dec 07, 2024 5:28 pm In case something got misunderstood: PSA = Public Service Announcement

Ah, good to know, so not
Project Smash Attack
or
Prostate-Specific Antigen

fehlix wrote: Sat Dec 07, 2024 5:40 pm
Prostate-Specific Antigen

fehlix wrote: Sat Dec 07, 2024 4:50 pm I think Debian fixed it now, latest chromium got installed here without any special adjustments.

Code: Select all

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-security bookworm-security/main amd64 Packages
        100 /var/lib/dpkg/status
     130.0.6723.91-1~deb12u1 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages

thank you! installed here as well without any flaws, works as before, thank you so much!

debianix wrote: Sat Dec 07, 2024 5:54 pm

fehlix wrote: Sat Dec 07, 2024 4:50 pm I think Debian fixed it now, latest chromium got installed here without any special adjustments.

Code: Select all

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-security bookworm-security/main amd64 Packages
        100 /var/lib/dpkg/status
     130.0.6723.91-1~deb12u1 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages

thank you! installed here as well without any flaws, works as before, thank you so much!

Hey, did you get offered 3 New library installs version 19 each, with version 16 of each being removed when u upgraded the fixed Chromium? I earlier today (after seeing this post) did nala upgrade just to see the output without going thru with the upgrade, and Chromium was listed as an upgrade but was being kept back. I ran upgrade tonight and now Chromium is freed up to install the upgrade, but it had those 3 libraries too. I was assuming that they were the fix, but maybe just coincidentally came at the same time. Just curious since u didn't mention it. U upgraded the fix much earlier than I, so maybe the 3 libraries weren't offered yet and have nothing to do with Chromium working.

Also, very strangely, while nala upgrade and MX Updater both show what I just said, my apt upgrade output still shows the earlier state, with Chromium being kept back and no 3 libraries. I wish I knew what that was about.

yes, these three libraries that caused the issue have been delivered along with the Chromium update.