I tried the fix_db.pl script, there was no output. Here is the only
relevant difference:
--- debconf.old/config.datâ–¸-2019-03-10 18:43:37.265483165 +0100
+++ debconf/config.datâ–¸-2019-03-10 18:43:41.261085496 +0100
@@ -1151,7 +1151,7 @@
Name: libpam-modules/disable-screensaver
Template:
On Sat, Mar 09, 2019 at 08:25:50PM +0100, Michael Biebl wrote:
> [bringing Steve, our pam maintainer, into the loop]
> Hi Steve,
> the following looks like an issue in pam-auth-update and similar to
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923362
> Any idea what might be going wrong
Am 09.03.19 um 22:03 schrieb Julien Leproust:
> Indeed, it looks a lot like #923362, though I can't reproduce now by
> manually running dpkg-reconfigure libpam-runtime.
>
> Tell me if I can help debug this, I still have the full apt logs and
> etckeeper on two machines.
>
Sorry, can't really
Indeed, it looks a lot like #923362, though I can't reproduce now by
manually running dpkg-reconfigure libpam-runtime.
Tell me if I can help debug this, I still have the full apt logs and
etckeeper on two machines.
Anyway I learnt a lot about pam and systemd :-)
Best regards,
--
Julien
[bringing Steve, our pam maintainer, into the loop]
Hi Steve,
the following looks like an issue in pam-auth-update and similar to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923362
Any idea what might be going wrong there?
Am 09.03.19 um 19:55 schrieb Julien Leproust:
> Hi,
>
> Well
Am 09.03.19 um 20:17 schrieb Michael Biebl:
> Thanks for the follow-up information.
> That was really helpful.
>
> Am 09.03.19 um 19:55 schrieb Julien Leproust:
>> And then, pam_systemd.so was incorrectly removed? I'm sure you're going
>> to assume I disabled the second option, but I really doubt
Thanks for the follow-up information.
That was really helpful.
Am 09.03.19 um 19:55 schrieb Julien Leproust:
> And then, pam_systemd.so was incorrectly removed? I'm sure you're going
> to assume I disabled the second option, but I really doubt this.
I said, a manual modification is more likely
Hi,
Well we're in luck, I have etckeeper installed since 2012.
On both machines, I never edited /etc/pam.d/common-* manually.
* fc3256a - Sat, 9 Mar 2019 12:59:20 +0100 (7 hours ago) (HEAD -> master)
| daily autocommit - root
* efc0d23 - Thu, 7 Feb 2019 23:16:46 +0100 (4 weeks ago)
|
Am 09.03.19 um 15:00 schrieb Michael Biebl:
> Am 09.03.19 um 14:10 schrieb Julien Leproust:
>> Hi,
>>
>> I found the issue.
>>
>> When looking for /etc files not belonging to any package, I discovered
>> that /etc/pam.d/common-* files are managed by pam-auth-update.
>>
>> Most pam profiles were
Am 09.03.19 um 14:10 schrieb Julien Leproust:
> Hi,
>
> I found the issue.
>
> When looking for /etc files not belonging to any package, I discovered
> that /etc/pam.d/common-* files are managed by pam-auth-update.
>
> Most pam profiles were enabled, except "Register user sessions in the
>
Hi,
I found the issue.
When looking for /etc files not belonging to any package, I discovered
that /etc/pam.d/common-* files are managed by pam-auth-update.
Most pam profiles were enabled, except "Register user sessions in the
systemd control group hierarchy", and just enabling it fixed the
11 matches
Mail list logo
