MX Linux Forum

I'm at a loss. Although I think I've seen something similar when policykit was acting up.

How about

Done. ...

chandler wrote: Sun Jul 07, 2019 7:38 pmDone. ...

MX18 is based on stretch, which is now oldstable.
You have manually Debian stable repo enabled, which are now "buster", hence the buster upgrade have broken your system, I guess.

fehlix wrote: Sun Jul 07, 2019 9:21 pm

chandler wrote: Sun Jul 07, 2019 7:38 pmDone. ...

MX18 is based on stretch, which is now oldstable.
You have manually Debian stable repo enabled, which are now "buster", hence the buster upgrade have broken your system, I guess.

good eye.

Yep, a dist-upgrade to buster is not a good idea, and buster became the new stable yesterday.

upgrade issues are why we use the distro name versions of the repo definitions.

I see a Jessie Main repo, plus something about "wire-app" (PPA?) but nothing about Buster in his pictures of his inxi output in the first post. Having a Debian Jessie repo enabled on a Stretch-based system might have been what broke it after the last update. Fehlix must have better eyes than I do (I'm half-blind, actually.)

Edit: never mind, I see it now. "Debian Stable" repos, which are Buster repos now, instead of "Debian Stretch". So he actually has repos for three different versions of Debian stable branch enabled at the same time.

dolphin_oracle wrote: Sun Jul 07, 2019 9:25 pm upgrade issues are why we use the distro name versions of the repo definitions.

Question: has MX done this all along, or did it ever just name the repos "Debian Stable"? Since we suddenly have two cases of lightdm/X11 issues after an update since Buster was released, I'm wondering if people who originally installed an older version of MX, like 17, still have repos named Debian Stable instead of Debian Stretch and that's what's causing the issues.

JayM wrote: Sun Jul 07, 2019 9:30 pm Edit: never mind, I see it now. "Debian Stable" repos, which are Buster repos now, instead of "Debian Stretch". So he actually has repos for three different versions of Debian stable branch enabled at the same time.

Yes, that update was a full upgrade to buster. Don't see any chance to revert that upgrade.

The stretch repos no longer exist since buster is now the new Debian release?

JayM wrote: Sun Jul 07, 2019 9:42 pm

dolphin_oracle wrote: Sun Jul 07, 2019 9:25 pm upgrade issues are why we use the distro name versions of the repo definitions.

Question: has MX done this all along, or did it ever just name the repos "Debian Stable"? Since we suddenly have two cases of lightdm/X11 issues after an update since Buster was released, I'm wondering if people who originally installed an older version of MX, like 17, still have repos named Debian Stable instead of Debian Stretch and that's what's causing the issues.

we we have deliberately used the distro codename all along. to be sure, I went back and checked mx 17 and 17.1 both had "stretch" rather than "stable".

to answer the other question, the stretch repos are still there, but they are no longer "stable" they are now "oldstable".

using the distro codename version of the debian repository definitions avoids these kinds of things.

Thanks dolphin_oracle! stretch no longer receives updates because it is oldstable?