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

Bug#960026: marked as done ([release-notes] KDE is no longer supported as a Desktop Environment without systemd as init-system (PID 1))

Your message dated Sun, 29 Jan 2023 21:15:21 +0100
with message-id <f608cc71-3f8d-6368-1079-049420ab53d0@debian.org>
and subject line buster is EOL for a while; closing release-notes bugs
has caused the Debian Bug report #960026,
regarding [release-notes] KDE is no longer supported as a Desktop Environment without systemd as init-system (PID 1)
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

960026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960026
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Version: Buster
Severity: important

--- Please enter the report below this line. ---

As I tried to report in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935304#10 - but it
seems to have been overlooked in the wilder scheme of things. If one is
using something other than systemd as the init system under "Stretch"
and use KDE Plasma as your Desktop Environment then you will find the
latter gets removed during the upgrade as there is a dependency chain
that DEMANDS systemd-sysv which is, of course, not satisfiable without
systemd as PID 1.

This is because libpam-systemd has been revised in "Buster" to "require"
not only systemd but also systemd-sysv . I did experiment with building
a systemd set of packages where the "require" from `libpam-systemd` for
'systemd-sysv' was reduced to a "suggest" specifically BECAUSE I WAS NOT
INTENDING TO USE SYSTEMD AS MY INIT SYSTEM which was sufficient to get
most of the KDE Plasma Desktop working - although with the breakage in
the login system it wasn't possible to sleep/hibernate/shutdown from the
DE. However a either a recent change - or a failed attempt to switch to
elogind just as systemctl was updated {possibly
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959920 applies} has
broken my system and I cannot get several DEs to properly start up any more.

I am aware that Devuan has a replacement elogind / libpam-elongind which
does work to enable KDE to operate without libpam-systemd but this seems
to have been rejected for Debian.

As a consequence it looks like I will have to switch my main PC to
Devuan "Beowulf" if I want to keep using KDE.

Stephen Lyons

--- System information. ---
Kernel:       Linux 4.19.0-8-amd64

Debian Release: 10.3
  500 stable          security.debian.org
  500 stable          ftp.uk.debian.org
  500 stable          apt.spideroak.com

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

To mitigate against EFAIL attacks email messages will be handled only as
plain text, please do not send emails in an HTML form to this recipient!

Attachment: signature.asc
Description: OpenPGP digital signature

--- End Message ---
--- Begin Message ---
Dear bug submitter,

Thanks for taking the time to file bugs. However, the bug you reported was aimed at buster (or hasn't seen activity after the last queries). buster is EOL for a while now and we're preparing for the release of bookworm. Hence, I'm closing these bugs as no longer valid or actionable.


Attachment: OpenPGP_signature
Description: OpenPGP digital signature

--- End Message ---

Reply to: