[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#895418: marked as done (systemd-shim: incompatibility with a new version of systemd)

Your message dated Sat, 01 Dec 2018 03:05:54 +0000
with message-id <[🔎] E1gSvbO-000HPq-8k@fasolo.debian.org>
and subject line Bug#915038: Removed package(s) from unstable
has caused the Debian Bug report #895292,
regarding systemd-shim: incompatibility with a new version of systemd
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
895292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895292
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: systemd-shim
Version: 10-3
Severity: important
Affects: gdm3

Hi,

I admit I didn't spend much time investigating this issue (I need a
working Sid box), but from past experience, I guess it comes from a new
systemd-shim incompatibility introduced by some change in systemd-logind
(or GDM, but IMHO it's less unlikely than systemd).

The symptoms are identical to #801749 (but since people there mention
journalctl, I guess they were not using SysV init, so it can't be a
duplicate of this bug): GDM doesn't start (the screen keeps displaying
the console, with the cursor blinking frenetically), and syslog shows
lots and lots of "gdm3: Child process XYZ was already dead." and "gdm3:
Unable to kill session worker process".

lightdm (under SysV init) does start normally.

Switching the init system to systemd gets rid of the problem, and allows
GDM to start normally (this is why I'm filing this report against
systemd-shim).

Please note that I didn't try to downgrade systemd or GDM to find the
exact culprit (or the version introducing the change), I made an
educated guess and switched the init system directly, which worked. I
have a lot of stuff to do on my Sid box ATM and I can't afford the time.
Please also note that I don't reboot this box very often, so the
incompatibility may have been introduced by a systemd update a long time
ago, not necessarily the latest one.

Regards,

-- 
Raphaël Halimi

--- End Message ---
--- Begin Message --- 
Version: 10-3+rm

Dear submitter,

as the package systemd-shim has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/915038

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
Reply to: