Hi, what a nice coincidence. Yesterday I noticed that some autoupgrade fully updated my TP. So I removed testing, run dist-upgrade to current stable. (TP completely freeze during the systemd upgrade) Then I rebooted and exactly the same problem. I finished the upgrade (due to previous crash) and again. But the same problem. So I had downgrade libappramor1 again to be able to boot. :( And I was just about to write you ...
Jozef with deb http://ftp2.de.debian.org/debian/ stable main non-free contrib in source list and after dist-upgrade On Fri, Sep 3, 2021 at 9:44 AM intrigeri <[email protected]> wrote: > Hi, > > Ďoďo (2021-04-11): > > Hi, yes, I do agree the problem is in libc dependencies. > > I'm glad we're on the same page here. > > > Yes, I am using testing and I just did allow the apt to upgrade all > > the recommended packages. > > […] > > Otherwise I do not understand your comment about "running testing on > > stretch system". > > I'm not convinced at all that you're using testing. > > The original bug report read: > > > Debian Release: 9.8 > > APT prefers oldstable-updates > > APT policy: (500, 'oldstable-updates'), (500, 'testing'), (500, > 'stable') > > Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU threads) > > That's the Buster kernel. > So to me it looks like you're using a mix of Buster and Bullseye. > > Please remove any APT source for anything older than Bullseye (which > is now stable), fully upgrade to Bullseye, and report back if you > can reproduce. > > Thanks in advance! >
