On Mon, Aug 9, 2021 at 4:33 AM Olaf Meeuwissen <paddy-hack@???>
wrote:

> HI,
>
> o1bigtenor via Dng writes:
>
> > ---------- Forwarded message ---------
> > From: o1bigtenor <o1bigtenor@???>
> > Date: Sun, Aug 8, 2021 at 9:23 PM
> > Subject: Re: [DNG] display manager problems
> > To: Olaf Meeuwissen <paddy-hack@???>
> >
> > On Sun, Aug 8, 2021 at 8:24 PM Olaf Meeuwissen <
> paddy-hack@???>
> > wrote:
> >
> >> Hi,
> >>
> >> o1bigtenor writes:
> >>
> >> > On Sat, Aug 7, 2021 at 9:27 PM Olaf Meeuwissen <
> >> paddy-hack@???>
> >> > wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> o1bigtenor via Dng writes:
> >> >>
> >> >> > Greetings
> >> >> >
> >> >> > I've been using lxdm for my display manager.
> >> >> > Yesterday evening after returning to my machine after supper the
> display
> >> >> > wouldn't move out of sleep mode and I found this (see next) in
> >> >> > /var/log/lightdm/
> >> >> >
> >> >> > [+101478.18s] DEBUG: Got signal 15 from process 1
> >> >> > [...snip...]
> >> >> >
> >> >> > (Any idea what process 1 might be or how I can find out?)
> >> >>
> >> >> Your init. Assuming you're using Devuan, that could come from any
> ofdpkg -S /sbin/init
> >> >
> >> > Thanks Mr Olaf
> >> >
> >> > Alas - - - this machine is not yet on Devuan.
> >> >
> >> > So on Debian testing that init would be systemd - - - yes ?
> >>
> >> If your running a recent Debian version then yes, but why don't you
> >> check for yourself using the command-lines I added to my previous mail?
> >> That works a lot better then asking me to look into my crystal ball ;-)
> >>
> >> Hmmmmmm - - - - that's very interesting - - -
> >
> > # cat /proc/1/cmdline | tr '\0' ' '
> > /sbin/init root@debianbase:~#
>
> That's confirming that your PID 1 is indeed /sbin/init.
>
> > yet there is systemd all over most everything else.
> >
> > Not sure what the above means nor signifies.
>
> Next, `dpkg -S /sbin/init` will tell you which package provides it.
> And given your other information, I expect that to be systemd.
>
> # dpkg -S /sbin/init
systemd-sysv: /sbin/init

was the result.

What I'm having a hard time wrapping my head around is the fact
that systemd somehow shut down or better couldn't bring lightdm
back up after a system 'suspend'. I'm smelling a very stinky rat!!!

Thanks for the assistance.

Regards