Bug#922647: Info received (Bug#922647: systemd --user no longer running)

2019-03-10 Thread Julien Leproust
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:

Bug#922647: Info received (Bug#922647: systemd --user no longer running)

2019-03-09 Thread Steve Langasek
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

Bug#922647: Info received (Bug#922647: systemd --user no longer running)

2019-03-09 Thread Michael Biebl
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

Bug#922647: Info received (Bug#922647: systemd --user no longer running)

2019-03-09 Thread 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. Anyway I learnt a lot about pam and systemd :-) Best regards, -- Julien

Bug#922647: Info received (Bug#922647: systemd --user no longer running)

2019-03-09 Thread Michael Biebl
[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

Bug#922647: Info received (Bug#922647: systemd --user no longer running)

2019-03-09 Thread Michael Biebl
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

Bug#922647: Info received (Bug#922647: systemd --user no longer running)

2019-03-09 Thread 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 this. I said, a manual modification is more likely

Bug#922647: Info received (Bug#922647: systemd --user no longer running)

2019-03-09 Thread Julien Leproust
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) |

Bug#922647: Info received (Bug#922647: systemd --user no longer running)

2019-03-09 Thread Michael Biebl
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

Bug#922647: Info received (Bug#922647: systemd --user no longer running)

2019-03-09 Thread 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 enabled, except "Register user sessions in the >

Bug#922647: Info received (Bug#922647: systemd --user no longer running)

2019-03-09 Thread 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 systemd control group hierarchy", and just enabling it fixed the

Bug#922647: systemd --user no longer running

2019-03-06 Thread Julien Leproust
On 3/7/19 1:21 AM, Felipe Sateler wrot It is libpam-ck-connector I have no such package, neither installed nor available. -- Julien Leproust

Bug#922647: systemd --user no longer running

2019-03-06 Thread Felipe Sateler
On Wed, Mar 6, 2019, 21:19 Julien Leproust wrote: > On 3/7/19 1:14 AM, Felipe Sateler wrote: > > It seems yo still have pam ck connector installed. Can you confirm? > > I don't know, how do I check this? The only package I find referring > consolekit is lightdm, in its description. > It is

Bug#922647: systemd --user no longer running

2019-03-06 Thread Felipe Sateler
On Wed, Mar 6, 2019, 21:03 Julien Leproust wrote: > Yes, I do have dbus-user-session and dbus-x11 installed: > > $ apt-cache policy dbus-user-session dbus-x11 > dbus-user-session: >Installed: 1.12.12-1 >Candidate: 1.12.12-1 >Version table: > 1.13.8-1 1 >1

Bug#922647: systemd --user no longer running

2019-03-06 Thread Julien Leproust
Yes, I do have dbus-user-session and dbus-x11 installed: $ apt-cache policy dbus-user-session dbus-x11 dbus-user-session: Installed: 1.12.12-1 Candidate: 1.12.12-1 Version table: 1.13.8-1 1 1 http://ftp.fr.debian.org/debian experimental/main amd64 Packages *** 1.12.12-1

Bug#922647: systemd --user no longer running

2019-03-06 Thread Michael Biebl
To rule out the obvious, can you paste the output of apt-cache policy dbus-user-session dbus-x11 (you want dbus-user-session if you are using systemd --user) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc

Bug#922647: systemd --user no longer running

2019-03-06 Thread Felipe Sateler
On Wed, Mar 6, 2019 at 6:09 PM Julien Leproust wrote: > > Hi, > > I've been hit by seemingly the same bug on two of my machines. > > Since about mid-February, I noticed that my two Debian sid desktops no > longer produced any sound. On one of them, I use lightdm+mate, on the > other I use

Bug#922647: systemd --user no longer running

2019-03-06 Thread Julien Leproust
Hi, I've been hit by seemingly the same bug on two of my machines. Since about mid-February, I noticed that my two Debian sid desktops no longer produced any sound. On one of them, I use lightdm+mate, on the other I use lightdm+kodi. Both were updated roughly weekly, with only official sid

Bug#922647: systemd --user no longer running

2019-02-25 Thread Felipe Sateler
On Mon, Feb 25, 2019 at 3:12 PM Eduard Bloch wrote: > Control: reassign -1 systemd > > Hallo, > * Felipe Sateler [Thu, Feb 21 2019, 10:32:29AM]: > >On Wed, Feb 20, 2019 at 3:59 PM Eduard Bloch <[1]e...@gmx.de> wrote: > > Feb 08 20:38:51 zombie at-spi-bus-launcher[2625]: XIO: fatal IO >

Bug#922647: systemd --user no longer running

2019-02-25 Thread Eduard Bloch
Control: reassign -1 systemd Hallo, * Felipe Sateler [Thu, Feb 21 2019, 10:32:29AM]: >On Wed, Feb 20, 2019 at 3:59 PM Eduard Bloch <[1]e...@gmx.de> wrote: > Feb 08 20:38:51 zombie at-spi-bus-launcher[2625]: XIO:  fatal IO error > 11 (Resource temporarily unavailable) on X server

Bug#922647: systemd --user no longer running

2019-02-21 Thread Felipe Sateler
On Wed, Feb 20, 2019 at 3:59 PM Eduard Bloch wrote: > Hallo, > * Felipe Sateler [Wed, Feb 20 2019, 02:46:32PM]: > > > Yeah, so I tried also real username instead of "user" here, etc. > still > > getting "invalid argument" message. Which IMHO makes sense since, as > > said, the

Bug#922647: systemd --user no longer running

2019-02-20 Thread Eduard Bloch
Hallo, * Felipe Sateler [Wed, Feb 20 2019, 02:46:32PM]: > Yeah, so I tried also real username instead of "user" here, etc. still > getting "invalid argument" message. Which IMHO makes sense since, as > said, the systemd user instance was not started. > >Use journalctl --unit

Bug#922647: systemd --user no longer running

2019-02-20 Thread Felipe Sateler
On Wed, Feb 20, 2019, 14:25 Eduard Bloch Hallo, > * Felipe Sateler [Mon, Feb 18 2019, 06:34:37PM]: > >Control: tags -1 moreinfo > >On Mon, Feb 18, 2019 at 5:36 PM Eduard Bloch <[1]e...@gmx.de> wrote: > > > > Package: libpam-systemd > > Version: 240-5 > > Severity: normal >

Bug#922647: systemd --user no longer running

2019-02-20 Thread Eduard Bloch
Hallo, * Felipe Sateler [Mon, Feb 18 2019, 06:34:37PM]: >Control: tags -1 moreinfo >On Mon, Feb 18, 2019 at 5:36 PM Eduard Bloch <[1]e...@gmx.de> wrote: > > Package: libpam-systemd > Version: 240-5 > Severity: normal > > Hi, > > a few days ago some user services

Bug#922647: systemd --user no longer running

2019-02-18 Thread Felipe Sateler
Control: tags -1 moreinfo On Mon, Feb 18, 2019 at 5:36 PM Eduard Bloch wrote: > Package: libpam-systemd > Version: 240-5 > Severity: normal > > Hi, > > a few days ago some user services started failed - I mainly noticed that > pulseaudio was no longer available. > This looked very strange, and

Bug#922647: systemd --user no longer running

2019-02-18 Thread Eduard Bloch
Package: libpam-systemd Version: 240-5 Severity: normal Hi, a few days ago some user services started failed - I mainly noticed that pulseaudio was no longer available. This looked very strange, and while checking other systems, I saw that "systemd --user" is not launched, which would have