Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

2015-06-16 Thread eric2.valette
On 06/16/2015 01:30 PM, Michael Biebl wrote: Am 16.06.2015 um 13:18 schrieb eric2.vale...@orange.com: On 06/16/2015 11:58 AM, Michael Biebl wrote: My suggestion would be, to fix your setup to either use an initramfs like initramfs-tools or dracut, which mounts your /usr partition, or use no

Bug#761951: marked as done (systemd: networking service not started due to dependency cycle)

2015-06-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jun 2015 15:11:29 +0200 with message-id 20150616131128.ga32...@piware.de and subject line Re: Bug#761951: systemd: Did not start network in default has caused the Debian Bug report #761951, regarding systemd: networking service not started due to dependency cycle to be

Processed: Re: Bug#761951: systemd: Did not start network in default

2015-06-16 Thread Debian Bug Tracking System
Processing control commands: reopen -1 Bug #761951 {Done: Martin Pitt mp...@debian.org} [systemd] systemd: networking service not started due to dependency cycle Bug reopened Ignoring request to alter fixed versions of bug #761951 to the same values previously set -- 761951:

Bug#761951: systemd: Did not start network in default

2015-06-16 Thread Martin Pitt
Control: reopen -1 Bah, pilot error, sorry. I initially thought that setserial was already fixed in sid, but it isn't. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital

Re: Proposal: enable stateless persistant network interface names

2015-06-16 Thread Thorsten Glaser
Martin Pitt mpitt@... writes: - [mac] For many many years our we have installed an udev rule /lib/udev/rules.d/75-persistent-net-generator.rules which on first boot creates a MAC address → current name mapping and writes /etc/udev/rules.d/70-persistent-net.rules. Hm, that usually

Processed (with 1 errors): forcibly merging 786976 761951

2015-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: forcemerge 786976 761951 Bug #786976 [setserial] setserial: Please add systemd unit for rcS init.d script Unable to merge bugs because: package of #761951 is 'systemd' not 'setserial' Failed to forcibly merge 786976: Did not alter merged bugs.

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

2015-06-16 Thread Michael Biebl
Am 16.06.2015 um 13:18 schrieb eric2.vale...@orange.com: On 06/16/2015 11:58 AM, Michael Biebl wrote: My suggestion would be, to fix your setup to either use an initramfs like initramfs-tools or dracut, which mounts your /usr partition, or use no separate /usr partition at all. There is just

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

2015-06-16 Thread Martin Pitt
eric2.vale...@orange.com [2015-06-16 13:18 +0200]: This has been fixed for apparmor, why not for seccomp? I filed a bug about it and pinged the maintainer; I don't see a reason why it shouldn't get fixed. Can't you add a test at build time that checks that systemd does not depend on /usr/lib

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

2015-06-16 Thread eric2.valette
On 06/16/2015 11:58 AM, Michael Biebl wrote: My suggestion would be, to fix your setup to either use an initramfs like initramfs-tools or dracut, which mounts your /usr partition, or use no separate /usr partition at all. There is just to much stuff that is (silently) broken by this. I just

Re: Bug#788923: libseccomp2: please move to /lib, so that systemd can use it

2015-06-16 Thread Michael Biebl
Am 16.06.2015 um 19:35 schrieb Kees Cook: On Tue, Jun 16, 2015 at 11:55:30AM +0200, Martin Pitt wrote: Would you mind moving this into /lib? Sure, that would be fine by me. I don't see a common way to handle this, though. Each package I've looked at does it differently. Can you send a patch

Bug#788904: systemd fails to activate vg on crypt device after upgrade to 215-17+deb8u1

2015-06-16 Thread David Mohr
close 788904 thanks On 2015-06-16 00:19, Michael Biebl wrote: Am 16.06.2015 um 08:12 schrieb Michael Biebl: Am 16.06.2015 um 06:35 schrieb David Mohr: I have a crypto device which I use as a physical volume for LVM. After upgrading to systemd 215-17+deb8u1 my system fails to boot, because

Processed: Re: Bug#788904: systemd fails to activate vg on crypt device after upgrade to 215-17+deb8u1

2015-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: close 788904 Bug #788904 [systemd] systemd fails to activate vg on crypt device after upgrade to 215-17+deb8u1 Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 788904:

Bug#788904: systemd fails to activate vg on crypt device after upgrade to 215-17+deb8u1

2015-06-16 Thread Michael Biebl
Am 16.06.2015 um 08:12 schrieb Michael Biebl: Am 16.06.2015 um 06:35 schrieb David Mohr: I have a crypto device which I use as a physical volume for LVM. After upgrading to systemd 215-17+deb8u1 my system fails to boot, because `vgchange -ay` is not run after the crypto device is set up (which

Bug#788904: systemd fails to activate vg on crypt device after upgrade to 215-17+deb8u1

2015-06-16 Thread Michael Biebl
Am 16.06.2015 um 06:35 schrieb David Mohr: I have a crypto device which I use as a physical volume for LVM. After upgrading to systemd 215-17+deb8u1 my system fails to boot, because `vgchange -ay` is not run after the crypto device is set up (which [..] Please let me know if I can help to

Bug#788910: Systemd logics corrupted on USB UUID mount

2015-06-16 Thread Thomas Korimort
Package: systemd Severity: critical I am using Debian 8.0 Jessie on my RaspBerrry Pi 2. I do regular firmware updates with the script of Hexxeh (rpi-update). Yesterday my RaspBerry Pi 2 worked nicely. However, today i could not log in via SSH in our WLAN which happens sometimes. Thats why i

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

2015-06-16 Thread Eric Valette
Package: systemd Version: 220-6 Severity: critical Justification: breaks the whole system After yesterday upgrade to systemd 220.6, my system no longer boot. It reports a kernel panic witha attempting to kill init. I guess a kind of fault occurs in the daemon but I cannot easilly find traces.

Bug#788662: Logged-in user no longer granted permission to removable disks

2015-06-16 Thread intrigeri
Hi, Josh Triplett wrote (15 Jun 2015 15:56:33 GMT) : [...] I do think this functionality from wheezy should be restored. I'm aware this is not a poll, so just for the record: Tails Installer will soon be uploaded to Debian, and then to jessie-backports; it uses udisks whenever possible, but

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

2015-06-16 Thread Michael Biebl
Separate /usr and no initramfs to mount it? Am 16. Juni 2015 10:06:07 MESZ, schrieb Eric Valette eric2.vale...@orange.com: Package: systemd Version: 220-6 Severity: critical Justification: breaks the whole system After yesterday upgrade to systemd 220.6, my system no longer boot. It reports a

Bug#788910: Systemd logics corrupted on USB UUID mount

2015-06-16 Thread Michael Biebl
Please attach your /etc/fstab. Was the USB drive attached when you booted your system? Am 16. Juni 2015 09:22:16 MESZ, schrieb Thomas Korimort tomk...@gmx.net: Package: systemd Severity: critical I am using Debian 8.0 Jessie on my RaspBerrry Pi 2. I do regular firmware updates with the script

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

2015-06-16 Thread Michael Biebl
Am 16.06.2015 um 10:42 schrieb eric2.vale...@orange.com: On 06/16/2015 10:17 AM, Michael Biebl wrote: Separate /usr and no initramfs to mount it? yes but 220-5 was working. I rather suspect the /tmp change as I do have this line in my /etc/fstab Nope, it's more likely this: * Enable

Bug#788910: Systemd logics corrupted on USB UUID mount

2015-06-16 Thread Michael Biebl
Control: forcemerge 785525 -1 [please always CC the bug report] Am 16.06.2015 um 11:16 schrieb Thomas Korimort: Dear Michael, my fstab is short and consists of just 3 lines. The first two mount the 2 partitions of the SD card, first partition as /boot/firmware with FAT file system and

Processed: Re: Bug#788910: Systemd logics corrupted on USB UUID mount

2015-06-16 Thread Debian Bug Tracking System
Processing control commands: forcemerge 785525 -1 Bug #785525 [systemd] systemd fails to boot if non-essential block device is missing Bug #788910 [systemd] Systemd logics corrupted on USB UUID mount Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/91'. Marked as found

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

2015-06-16 Thread Michael Biebl
[please don't use HTML only mails, or better no HTML at all] Am 16.06.2015 um 11:46 schrieb eric2.vale...@orange.com: On 06/16/2015 11:40 AM, Michael Biebl wrote: Am 16.06.2015 um 10:42 schrieberic2.vale...@orange.com: On 06/16/2015 10:17 AM, Michael Biebl wrote: Separate /usr and no

Bug#788910: Systemd logics corrupted on USB UUID mount

2015-06-16 Thread Michael Biebl
[again, please always CC the bug report] Am 16.06.2015 um 12:38 schrieb Thomas Korimort: Thanks. My intention with the USB drive was to keep all the frequently changing and voluminous things there. /var is still on the SD card, but i decided to not put such essential thing on an unreliable USB

Processed: retitle 788913 to boot failure with separate /usr and no initramfs due to libseccomp being in /usr ...

2015-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: retitle 788913 boot failure with separate /usr and no initramfs due to libseccomp being in /usr Bug #788913 [systemd] systemd prevents to boot with a kernel panic. Boot in systemv mode is ok Changed Bug title to 'boot failure with separate /usr

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

2015-06-16 Thread eric2.valette
On 06/16/2015 10:17 AM, Michael Biebl wrote: Separate /usr and no initramfs to mount it? yes but 220-5 was working. I rather suspect the /tmp change as I do have this line in my /etc/fstab LABEL=TMP /tmp ext2defaults0 2 -- eric

Bug#788913: Fwd: Re: Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

2015-06-16 Thread eric2.valette
On 06/16/2015 10:20 AM, VALETTE Eric OLNC/OLPS wrote: On 06/16/2015 10:17 AM, Michael Biebl wrote: Separate /usr and no initramfs to mount it? yes but 220-5 was working. I rather suspect the /tmp change as I do have this line in my /etc/fstab LABEL=TMP /tmp ext2defaults

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

2015-06-16 Thread eric2.valette
On 06/16/2015 11:40 AM, Michael Biebl wrote: Am 16.06.2015 um 10:42 schrieb eric2.vale...@orange.com: On 06/16/2015 10:17 AM, Michael Biebl wrote: Separate /usr and no initramfs to mount it? yes but 220-5 was

libseccomp2: please move to /lib, so that systemd can use it

2015-06-16 Thread Martin Pitt
Package: libseccomp2 Version: 2.2.1-1 Hello, We would like to use systemd's seccomp support. In fact we recently enabled it already in 220-6 (https://tracker.debian.org/news/689328), but this caused boot failure with separate /usr and no initramfs (https://bugs.debian.org/788913_ as libseccomp2