Bug#667814: sudo: Fails to start process with signal 143

2012-06-03 Thread Joachim Breitner 
Hi,

I did not see a “confirmed” tag on the bug report, so I’m not sure if
you are still looking for more reports that this is systemd related: I
just restarted into systemd and sudo fails to start with return value
143 as well.

Greetings,
Joachim

-- 
Joachim nomeata Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata


signature.asc
Description: This is a digitally signed message part

Bug#667814: sudo: Fails to start process with signal 143

2012-04-09 Thread Julien Cristau 
On Fri, Apr  6, 2012 at 20:42:13 +0200, Achim Schaefer wrote:

 Package: sudo
 Version: 1.8.3p2-1
 Severity: grave
 Justification: renders package unusable
 
 Dear Maintainer,
 
 since some days, I can not tell exactly when, sudo fails with error status:

Are you using systemd?

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#667814: sudo: Fails to start process with signal 143

2012-04-09 Thread Achim Schaefer 


On 04/09/2012 03:45 PM, Julien Cristau wrote:

On Fri, Apr  6, 2012 at 20:42:13 +0200, Achim Schaefer wrote:


Package: sudo
Version: 1.8.3p2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

since some days, I can not tell exactly when, sudo fails with error status:

Are you using systemd?

Cheers,
Julien

yes indeed.

I saw in another mail, some people have similar issues with su as well, 
I don't .


Achim



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#667814: sudo: Fails to start process with signal 143

2012-04-06 Thread Achim Schaefer 
Package: sudo
Version: 1.8.3p2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

since some days, I can not tell exactly when, sudo fails with error status:
sudo -D 9 /bin/bash ; echo $?
sudo: settings: debug_level=9
sudo: settings: progname=sudo
sudo: settings: network_addrs=192.168.178.2/255.255.255.0 
192.168.100.1/255.255.255.0 192.168.10.1/255.255.255.0 
:::::/::::: 
:::::/:::::
sudo: sudo_mode 1
sudo: policy plugin returns 1
sudo: command info: umask=022
sudo: command info: command=/bin/bash
sudo: command info: runas_uid=0
sudo: command info: runas_gid=0
sudo: command info: runas_groups=0
sudo: command info: closefrom=3
sudo: command info: set_utmp=true
sudo: received signal 17
sudo: calling policy close with wait status
143

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.3.0-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sudo depends on:
ii  libc6   2.13-27
ii  libpam-modules  1.1.3-7
ii  libpam0g1.1.3-7
ii  libselinux1 2.1.9-4

sudo recommends no packages.

sudo suggests no packages.

-- Configuration Files:
/etc/sudoers [Errno 13] Permission denied: u'/etc/sudoers'
/etc/sudoers.d/README [Errno 13] Permission denied: u'/etc/sudoers.d/README'

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org