If I've understood the issue correctly, the current "forwarded" tag on
this bug is wrong, in the sense that the fundamental underlying problem
is in sudo, and so any possible forwarding waiting for "upstream fix"
should point to a sudo bug.
AFAIK this problem with libpam-systemd is caused by the s
On 09.04.2012 22:07, Michael Biebl wrote:
Hello Michael,
After upgrading from 37-1.1, many commands fail with error codes 143 or
129 under sudo, including "sudo bash" or "sudo passwd root", meaning
that the problem cannot easily be rectified or circumvented if root
logins are disabled. Hence,
Am 10.04.2012 16:36, schrieb Alban Browaeys:
> Package: systemd
> Version: 44-1
> Followup-For: Bug #667470
>
> I found adding pam_loginuid.so fixes the problem in all cases,
> except obvously for already running user sessions.
> I have plain added it to common-session and
> common-session-noninte
On 2012-04-09 22:07 +0200, Michael Biebl wrote:
> This bug seems to happen only if if you use libpam-systemd.
Certainly, disabling libpam-systemd helped (thanks for the tip, BTW).
> The reason why I didn't encounter this myself is because I've added
> pam_loginuid.so to my login and gdm3* pam co
On Tue, 2012-04-10 at 16:36 +0200, Alban Browaeys wrote:
> Package: systemd
> Version: 44-1
> Followup-For: Bug #667470
>
> I found adding pam_loginuid.so fixes the problem in all cases,
> except obvously for already running user sessions.
> I have plain added it to common-session and
> common-ses
Package: systemd
Version: 44-1
Followup-For: Bug #667470
I found adding pam_loginuid.so fixes the problem in all cases,
except obvously for already running user sessions.
I have plain added it to common-session and
common-session-noninteractive.
Is there an issue with adding it to common-session ?
On Tue, 2012-04-10 at 12:42 +0100, Sam Morris wrote:
> I added pam_loginuid.so to common-session-noninteractive before
> pam_systemd.so and it appears to work around the bug.
Correction: adding pam_loginuid.so makes sudo work more often, but not
always. It still fails about 75% of the time (very r
On Mon, 2012-04-09 at 22:07 +0200, Michael Biebl wrote:
> On 04.04.2012 12:43, Sven Joachim wrote:
> > Package: systemd
> > Version: 44-1
> > Severity: grave
> >
> > After upgrading from 37-1.1, many commands fail with error codes 143 or
> > 129 under sudo, including "sudo bash" or "sudo passwd ro
On 04.04.2012 12:43, Sven Joachim wrote:
> Package: systemd
> Version: 44-1
> Severity: grave
>
> After upgrading from 37-1.1, many commands fail with error codes 143 or
> 129 under sudo, including "sudo bash" or "sudo passwd root", meaning
> that the problem cannot easily be rectified or circumve
I can reproduce the issue with exit code 143 on an
unstable/experimental system (x86-64 with custom kernels 3.3 and
3.4-rc1). Interestingly it seems that I was able to run
sudo echo Hello
successfully once, so it does not seem to happen everytime (but that
has really been the only time while test
reassign 667470 libpam-systemd
found 667470 44-1
forwarded 667470 https://bugs.freedesktop.org/show_bug.cgi?id=45670
thanks
On 04.04.2012 12:43, Sven Joachim wrote:
> After upgrading from 37-1.1, many commands fail with error codes 143 or
> 129 under sudo, including "sudo bash" or "sudo passwd ro
Hi,
I can reproduce this under wheezy when I install systemd from unstable.
-Timo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: systemd
Version: 44-1
Severity: grave
After upgrading from 37-1.1, many commands fail with error codes 143 or
129 under sudo, including "sudo bash" or "sudo passwd root", meaning
that the problem cannot easily be rectified or circumvented if root
logins are disabled. Hence, I'm filing th
13 matches
Mail list logo
