Am Mittwoch 04 Juli 2018 schrieb Nick Koretsky:
> On Wed, 4 Jul 2018 13:48:41 +0200
>
> Stefan Krusche <linux@...> wrote:
> > Alright, /var/cache/debconf/config.dat is from 2018-07-03 15:27:28,
> > probably when I manually reconfigured display-manager, and not from when
> > I did the upgrade on 2018-07-02 11:42:01. This is in it:
> >
> > $ grep -n -A1 -B1 -E "tdm|slim" config.dat
> > 756-Template: shared/default-x-display-manager
> > 757:Value: tdm-trinity
> > 758:Owners: slim, tdm-trinity
> > 759-Flags: seen
> > 760-Variables:
> > 761: choices = slim, tdm-trinity
> > 762-
> > --
> > What can you get out of this?
>
> Ok, this looks normal. At this point if you want to track down the bug, i
> suggest following:
>
> Force reinstall tdm-trinity (unless you clean apt-cache the package is
> in /var/cache/apt/archives, just dpkg -i the last version.
>
> If default dm stays tdm-trinity after that than i have absolutely no idea
> what happened. Maybe whatever program you used to update (apt? apt-get?
> aptitude? some gui?) calls dpkg in some weird way, but its hard to track
> this - downgrade to a previous version and upgrade again using different
> programs?
>
> If it changed to slim - Force reinstall slim.
>
> If default dm remained slim after that than this is a bug in tdm-trinity
> install scripts, create a bug report in trinity bugzilla.
>
> If it changed back to tdm-trinity than this is a bug in dpkg (probably
> devuan one, as i dont have this problem on stretch). Report this to devuan.

Alright, thanks. I'll keep on digging.
Stefan