Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd

2017-03-06 Thread Andreas Bombe
For the record, my bug appears to have been reported before as #776863. I have generated a more complete backtrace from the same core: [New LWP 2615] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `ini

Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd

2017-03-06 Thread Andreas Bombe
It was pointed out to me that there should be core dumps and indeed there were from both instances of it happening to me. Here is one backtrace, the other looks identical: #0 0x7fc21779775b in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37 #1 0x7fc217bed4a8 in crash.lto_

Bug#856988: systemd: Timeout for sys-subsystem-net-devices-multi-user.device with missing /etc/machine-id

2017-03-06 Thread Felipe Sateler
Control: tags -1 moreinfo On Mon, Mar 6, 2017 at 7:14 PM, Ivan Baldo wrote: > Package: systemd > Version: 232-18 > Severity: normal > > Situation: PXE boot with RO NFS and using OverlayFS for RW /. Out of curiosity, why do you want read-write root? I figure you could just mount /var and /home as

Processed: Re: Bug#856988: systemd: Timeout for sys-subsystem-net-devices-multi-user.device with missing /etc/machine-id

2017-03-06 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #856988 [systemd] systemd: Timeout for sys-subsystem-net-devices-multi-user.device with missing /etc/machine-id Added tag(s) moreinfo. -- 856988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856988 Debian Bug Tracking System Contact ow...@

Bug#856988: systemd: Timeout for sys-subsystem-net-devices-multi-user.device with missing /etc/machine-id

2017-03-06 Thread Ivan Baldo
Package: systemd Version: 232-18 Severity: normal Situation: PXE boot with RO NFS and using OverlayFS for RW /. So, I rm'ed /etc/machine-id and /var/lib/dbus/machine-id, thinking that it would be generated at boot and they do, but sys-subsystem-net-devices-multi-user.device timeouts after 1m30s

Processed: [bts-link] source package systemd

2017-03-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.o

[bts-link] source package systemd

2017-03-06 Thread bts-link-upstream
# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #787028 (http://bugs.debian.org/787028) # Bug title: systemd-cryptsetup@.service fails

Bug#850855: [rtkit] rtkit daemon fails to start

2017-03-06 Thread Michael Biebl
Am 06.03.2017 um 14:03 schrieb Felipe Sateler: > If this only affects PrivateTmp when /var is a symlink, I agree it is > a corner case not worth spending much time on. My guess was that this > would be a bug in a more common part of the code, and that it may > affect other mount-related settings (R

Bug#850855: [rtkit] rtkit daemon fails to start

2017-03-06 Thread Felipe Sateler
On Sun, Mar 5, 2017 at 9:01 PM, Michael Biebl wrote: > On Fri, 20 Jan 2017 11:38:54 -0300 Felipe Sateler > wrote: >> Control: tags -1 - unreproducible moreinfo >> Control: reassign -1 systemd >> Control: affects -1 rtkit >> Control: retitle -1 Units with PrivateTmp fail when /var is a symlink >>

Processed: Re: please improve "unknown error -1" message

2017-03-06 Thread Debian Bug Tracking System
Processing control commands: > severity -1 wishlist Bug #856934 [systemd] please improve "unknown error -1" message Severity set to 'wishlist' from 'normal' -- 856934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#856934: please improve "unknown error -1" message

2017-03-06 Thread Michael Biebl
control: severity -1 wishlist On Mon, 6 Mar 2017 13:38:10 +0100 Harald Dunkel wrote: > Package: systemd > Version: 215-17+deb8u6 > > Sometimes systemctl fails with > > systemctl: Failed to get D-Bus connection: Unknown error -1 > > Since dbus is some IPC mechanism systemctl should provid

Bug#856924: systemd: on WorkingDirectory not existing, some weird log about CHROOT is generated

2017-03-06 Thread Felipe Sateler
On Mon, Mar 6, 2017 at 7:32 AM, Salvo Tomaselli wrote: > Package: systemd > Version: 232-19 > Severity: normal > > Dear Maintainer, > I have created a unit file like this > > [Unit] > Description=lala > > [Service] > WorkingDirectory=/does/not/exist > ExecStart=/bin/sh -c "echo ciao" > > [Install]

Bug#856934: please improve "unknown error -1" message

2017-03-06 Thread Harald Dunkel
Package: systemd Version: 215-17+deb8u6 Sometimes systemctl fails with systemctl: Failed to get D-Bus connection: Unknown error -1 Since dbus is some IPC mechanism systemctl should provide at least information about the peer it was trying to reach. Regards Harri __

Bug#856924: systemd: on WorkingDirectory not existing, some weird log about CHROOT is generated

2017-03-06 Thread Salvo Tomaselli
Package: systemd Version: 232-19 Severity: normal Dear Maintainer, I have created a unit file like this [Unit] Description=lala [Service] WorkingDirectory=/does/not/exist ExecStart=/bin/sh -c "echo ciao" [Install] WantedBy=multi-user.target And when I try to start it I obtain lala.service: Fai

Bug#856559: predictable interface name broken for virtio-ccw

2017-03-06 Thread Viktor Mihajlovski
On 05.03.2017 14:47, Martin Pitt wrote: > Control: notfound -1 233-1 > Control: tag -1 pending > > Viktor Mihajlovski [2017-03-02 13:52 +0100]: >> in Linux running as a KVM guest on a s390 system, virtio interfaces are >> named eth instead of enc as expected for ccw devices. > > The patch is fair