Your message dated Mon, 14 Dec 2020 21:32:44 +0100
with message-id <[email protected]>
and subject line Re: libpam0g: During configuration, "restart" kdm "starts" it!
has caused the Debian Bug report #443247,
regarding libpam0g: During configuration, "restart" kdm "starts" it!
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 [email protected]
immediately.)
--
443247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443247
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpam0g
Version: 0.99.7.1-4
Severity: normal
Hi,
During the installation (configuration) of this package, the user
is told:
The kdm, wdm, and xdm display managers require a restart for the
new version of libpam, but restarting these services would
terminate any X session. . . .
or something along the lines. Since I did "aptitude dist-upgrade"
when I was in the single-user mode (is it called the "recovery mode"
in Debian?), kdm wasn't started. So I thought, "it's OK because
there's nothing to restart" and mindlessly hit the return key.
But, the configuration process actually "started" kdm right there.
I lost the text terminal (console), I couldn't log in as a normal
user (because in the single-user mode, my normal-user account
doesn't quite work), root-user login isn't allowed, etc. Eventually
I managed to log in as a normal user in the "safe" mode. If I
recalled the key-combination to suspend/kill kdm, I may have been
able to get the console back.
Anyway, I think the right action would be to restart kdm only
when it's started.
Regards,
Ryo
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-2-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages libpam0g depends on:
ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy
ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries
ii libpam-runtime 0.99.7.1-4 Runtime support for the PAM librar
libpam0g recommends no packages.
-- debconf information:
* libpam0g/restart-services: samba kdm exim4 cupsys cron atd
libpam0g/restart-failed:
--- End Message ---
--- Begin Message ---
On Thu, 20 Dec 2018 02:14:59 +0100 Michael Biebl <[email protected]> wrote:
> The current documentation reads:
>
> invoke-rc.d itself only pays attention to the current runlevel;
> it will block any attempts to start a service in a runlevel in which the
> service is disabled. Other policies are implemented with the use of
> the policy-rc.d helper, and are only available if /usr/sbin/policy-rc.d
> is installed in the system.
>
> kdm is *not* disabled in runlevel 1.
> So I'd argue that the documentation is not incosistent with its behaviour.
>
> That said, it would probably a good idea if libpam0g drops that restart
> altogether (that functionality is of questionable value imho) or at
> least uses invoke-rc.d try-restart, to avoid unnecessarily starting
> services which haven't been running.
>
> If Steve is open to handle this in libpam0g, I'm going to reassign this
> back. Otherwise I'll close this bug report in a couple of weeks.
Since we didn't hear back from Steve, closing the bug report.
Regards,
Michael
signature.asc
Description: This is a digitally signed message part
--- End Message ---
