Bug#792519: systemd-logind fails to start on system using LDAP

2015-07-15 Thread Michael Biebl
Am 15.07.2015 um 20:15 schrieb Felipe Sateler: > Jul 15 09:35:31 deb-dschepler dbus[836]: [system] Activating systemd > to hand-off: service name='org.freedesktop.login1' > unit='dbus-org.freedesktop.login1.service' > Jul 15 09:35:33 deb-dschepler dbus[836]: [system] Failed to activate > service 'o

Processing of systemd_222-2_amd64.changes

2015-07-15 Thread Debian FTP Masters
systemd_222-2_amd64.changes uploaded successfully to localhost along with the files: systemd_222-2.dsc systemd_222-2.debian.tar.xz libnss-myhostname_222-2_amd64.deb libnss-mymachines_222-2_amd64.deb libpam-systemd_222-2_amd64.deb libsystemd-daemon-dev_222-2_amd64.deb libsystemd-dev_22

Re: Fixing udev-udeb vs. net.ifnames for Stretch Alpha 1

2015-07-15 Thread Michael Biebl
Am 15.07.2015 um 19:08 schrieb Martin Pitt: > Cyril Brulebois [2015-07-15 18:03 +0200]: >> Bottom line(s): >> --- >> I'll be testing 221-1 to make sure I reproduce the issue with a full >> install, then 221-1 + two patches to make sure it goes away. If that >> works fine, it might be a

Bug#792519: systemd-logind fails to start on system using LDAP

2015-07-15 Thread Daniel Schepler
On Wed, Jul 15, 2015 at 11:48 AM, Felipe Sateler wrote: > Hmm. Could you please attach the upgrade logs since some time before > the problems occurred? Might network manager have been updated in the > meantime? > Attaching /var/log/dpkg.log. I think the first failed boot was 2015-07-08 or 2015

Bug#792519: systemd-logind fails to start on system using LDAP

2015-07-15 Thread Daniel Schepler
On Wed, Jul 15, 2015 at 11:15 AM, Felipe Sateler wrote: > On 15 July 2015 at 14:38, Daniel Schepler wrote: > > On Wed, Jul 15, 2015 at 10:18 AM, Felipe Sateler > > wrote: > >> > >> This contains a massive amount of: > >> > >> Jul 15 09:34:37 deb-dschepler nslcd[905]: nss_ldap: could not connect

Bug#792519: systemd-logind fails to start on system using LDAP

2015-07-15 Thread Felipe Sateler
On 15 July 2015 at 14:38, Daniel Schepler wrote: > On Wed, Jul 15, 2015 at 10:18 AM, Felipe Sateler > wrote: >> >> This contains a massive amount of: >> >> Jul 15 09:34:37 deb-dschepler nslcd[905]: nss_ldap: could not connect >> to any LDAP server as (null) - Can't contact LDAP server >> Jul 15 0

Bug#792519: systemd-logind fails to start on system using LDAP

2015-07-15 Thread Daniel Schepler
On Wed, Jul 15, 2015 at 10:18 AM, Felipe Sateler wrote: > This contains a massive amount of: > > Jul 15 09:34:37 deb-dschepler nslcd[905]: nss_ldap: could not connect > to any LDAP server as (null) - Can't contact LDAP server > Jul 15 09:34:37 deb-dschepler nslcd[905]: nss_ldap: failed to bind to

Bug#792519: systemd-logind fails to start on system using LDAP

2015-07-15 Thread Felipe Sateler
Control: tags -1 moreinfo Hi, On 15 July 2015 at 14:01, Daniel Schepler wrote: > Package: systemd > Version: 222-1 > Severity: important > > Since about a week ago, when systemd got upgraded to 221-1, the system almost > always does not boot properly. It gets to the kdm prompt, but then trying

Processed: Re: Bug#792519: systemd-logind fails to start on system using LDAP

2015-07-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #792519 [systemd] systemd-logind fails to start on system using LDAP Added tag(s) moreinfo. -- 792519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems _

Fixing udev-udeb vs. net.ifnames for Stretch Alpha 1

2015-07-15 Thread Cyril Brulebois
(tl;dr: See bottom.) Hi, So Michael just approached me regarding having this merged before Stretch Alpha 1: (A) | commit 7b5eb265bbb2b783cbf7563b57db2f5a9b5cc3cf | Author: Martin Pitt | Date: Sat Jul 11 11:56:42 2015 +0200 | | Fix udeb an initramfs for net.ifnames | | - debian/u

Bug#789439: similar case

2015-07-15 Thread Martin Pitt
Peter Eisentraut [2015-07-15 9:29 -0400]: > I also tried it a different way: I installed the jessie netinst "CD" > into a new virtualbox machine, upgraded it to sid, rebooted, but there > the network came up as eth0 again. This is doubly confusing. This is most probably because the new net.ifnam

Bug#789439: similar case

2015-07-15 Thread Peter Eisentraut
While looking into a similar case I found this bug report. I brought up the debian/jessie64 vagrant image and upgraded it to sid. The starting setup contains a /etc/network/interfaces file that refers to eth0: # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp pre-up sleep 2

Re: nbd-client and systemd

2015-07-15 Thread Ansgar Burchardt
On 07/15/2015 09:34 AM, Wouter Verhelst wrote: > However, recently I found out about the > systemd-no-service-for-init-rcS-script lintian error, which triggers for > nbd-client. I'm afraid that if I create such a unit generator, this > would still trigger. > > Is that correct? If so, is there anot

nbd-client and systemd

2015-07-15 Thread Wouter Verhelst
Hi folks, nbd-client ships with an init script that does two things: - If we're doing root-on-NBD, write the correct sysvinit sendsigs.omit.d file so that the nbd-client process serving the root filesystem doesn't get killed from under us at shutdown - Connect nbd devices based on configuratio