Re: Action requested: migration of alioth list pkg-systemd-maintainers

Hi, since the systemd team in Debian doesn't have any alternative mailing list atm and we use it as Maintainer in a couple of important packages, we would appreciated if you could migrate pkg-systemd-maintainers. Thanks a lot. Michael Am 28.01.2018 um 19:26 schrieb alioth lists migration team:

Bug#887716: not necessarily not running

On Fri, 19 Jan 2018 18:46:22 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson wrote: > Package: nftables > Version: 0.8.1-1 > Severity: minor > > Setting up nftables (0.8.1-1) ... > nftables.service is a disabled or a static unit not running, not starting it. > > Not completely

Bug#887716: [pkg-netfilter-team] Bug#887716: not necessarily not running

After reading your initial bug report again, it seems you have started nftables not using the nftables.service i.e. nftables.service is indeed not running. I thus think the message from deb-systemd-invoke is correct. The only bit that could be maybe be tweaked is: > } elsif

Bug#887716: [pkg-netfilter-team] Bug#887716: not necessarily not running

Am 24.01.2018 um 02:50 schrieb Michael Biebl: > Control: reassign -1 init-system-helpers > Control: tags -1 - moreinfo unreproducible > > > Am 23.01.2018 um 23:57 schrieb Michael Biebl: >> Control: tags -1 + moreinfo unreproducible >> >> [please always CC the

Bug#887716: [pkg-netfilter-team] Bug#887716: not necessarily not running

Control: tags -1 + moreinfo unreproducible [please always CC the maintainer if you reassign a bug report] On Mon, 22 Jan 2018 13:31:06 +0100 Arturo Borrero Gonzalez wrote: > On Fri, 19 Jan 2018 21:58:11 +0800 =?utf-8?B?56mN5Li55bC8?= Dan > Jacobson

Bug#822635: udev rules for USB device access effective at boot, but not on hotplug

Hi Josh! On Wed, 21 Dec 2016 20:15:12 +0100 Michael Biebl <bi...@debian.org> wrote: > On Fri, 6 May 2016 18:12:27 -0500 Martin Pitt <mp...@debian.org> wrote: > > Control: tag -1 moreinfo > > > > Hello Josh, > > > > Josh Triplett [2016-04-25 13:48 -0

Bug#887250: systemd should depend on e2fsprogs explicitly

On Wed, 17 Jan 2018 20:21:50 +0100 Helmut Grohne wrote: > I think it warrants a "Suggests" at most. A Suggests won't help anyway. I see that mkfs.ext* is used in systemd-makefs. This is a swecial feature though imho doesn't warrant a hard dependency though. After all, we

Bug#887852: /dev/kvm is no longer accessible to local users

On Sat, 20 Jan 2018 18:21:33 +0100 Alexander Kurtz wrote: > Package: systemd > Version: 236-3 > > Hi! > > Until recently, /dev/kvm was made accessible to local users by this > line in /lib/udev/rules.d/70-uaccess.rules: > > # KVM > SUBSYSTEM=="misc",

Re: Bug#887904: dh_installsystemd will unmask services *after* an attempt to start them

Am 21.01.2018 um 16:28 schrieb Michael Biebl: > Package: debhelper > Version: 11.1.3 > Severity: important > > dh_installsystemd masks services on "remove". The background here is, that > SysV init scripts are conffiles which are only removed on "purge"

Bug#887904: dh_installsystemd will unmask services *after* an attempt to start them

Package: debhelper Version: 11.1.3 Severity: important dh_installsystemd masks services on "remove". The background here is, that SysV init scripts are conffiles which are only removed on "purge". Upon re-installation, this mask is removed again. With dh_systemd_enable, this was done before

Bug#887900: dh_installsystemd does not properly handle aliased services

Package: debhelper Version: 11.1.3 Severity: normal I use the following in network-manager: override_dh_systemd_start: dh_link -pnetwork-manager \ lib/systemd/system/NetworkManager.service \ lib/systemd/system/network-manager.service dh_systemd_start

Bug#887899: overrides for dh_systemd_enable|start are silently ignored in compat 11

Package: debhelper Version: 11.1.3 Severity: normal I use the following in network-manager: override_dh_systemd_start: dh_link -pnetwork-manager \ lib/systemd/system/NetworkManager.service \ lib/systemd/system/network-manager.service dh_systemd_start

Re: problems with pkg systemd

Am 18.01.2018 um 15:59 schrieb Matthieu Castay: > Hi > > I installed a new debian buster and  the systemd-timesync did not start. > I had to create user & group manualy to make systemd-timesync able to start > > user : > systemd-timesync:x:121:126:systemd Time >

Bug#887396: systemd-timesyncd.service: Start request repeated too quickly.

Am 18.01.2018 um 05:26 schrieb Andre Verwijs: > additional information: > >   > > /etc/passwd should have this line by default : > > systemd-timesync:x:100:102:NTP Time sync:/sbin/nologin > >   > > to set user/group and to start systemd-timesyncd.service at boot. Adding this user statically

Bug#887456: init-system-helpers: deb-systemd-helper does not honor the same package-relevant unit paths as systemd

Am 17.01.2018 um 11:35 schrieb Guillem Jover: > --- a/script/deb-systemd-helper > +++ b/script/deb-systemd-helper > @@ -122,6 +122,8 @@ sub find_unit { > $service_path = "/etc/systemd/system/$scriptname"; > } elsif (-f "/lib/systemd/system/$scriptname") { > $service_path =

Bug#887556: non deterministic behavior of network-online.target

Am 17.01.2018 um 22:11 schrieb Michael Biebl: > It's not systemd that pulls in network-online.target. You should contact > the ifupdown maintainers why apparently network-online.target does not > work for you. btw, in your syslog.fail, it seems like network-online.target is not start

Bug#887556: non deterministic behavior of network-online.target

Am 17.01.2018 um 21:39 schrieb Vladislav Kurz: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > Hello, > > This is a followup to archived bug #870361 > > I have been installing new servers with similar setup as last time, and > ran into the same problem. I think I have

Bug#887250: systemd should depend on e2fsprogs explicitly

Am 14.01.2018 um 20:11 schrieb Helmut Grohne: > * Add e2fsprogs to Depends. > * Add e2fsprogs to Recommends. A recommends will probably not work for systemd to ensure that e2fsprogs is by default installed alongside systemd. It's the same problem as discussed in #887343 where Recommends are not

Bug#887501: systemctl status should not use --pager

Hi Guido, for all my replies, keep in mind, that I don't have any idea what serverspec is or does... Am 17.01.2018 um 15:25 schrieb Guido Günther: > On Wed, Jan 17, 2018 at 02:59:07PM +0100, Michael Biebl wrote: >> Am 17.01.2018 um 14:15 schrieb Guido Günther: >> Hm, I'm not qui

Bug#887501: systemctl status should not use --pager

Am 17.01.2018 um 14:15 schrieb Guido Günther: > Package: init-system-helpers > Version: 1.51 > Severity: normal > Tags: patch > > Hi, > systemctl status should be invoked with --no-pager, otherwise it might > hang on non-interactive command. This was observed running serverspec's > >describe

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

On Tue, 19 Dec 2017 06:55:34 +0100 Michael Biebl <bi...@debian.org> wrote: > Am 19.12.2017 um 02:18 schrieb Martin-Éric Racine: > > 2017-12-19 2:02 GMT+02:00 Michael Biebl <bi...@debian.org>: > >> Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: > >>> 2

Bug#886908: systemd enabled services unable to access shares

Am 11.01.2018 um 07:54 schrieb Hannu Laitinen: > Package: systemd > Version: 236-2 Can you please upgrade to 236-3, reboot and then test again and report back with your findings. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Bug#887456: init-system-helpers: deb-systemd-helper does not honor the same package-relevant unit paths as systemd

Hi Guillem Am 16.01.2018 um 20:02 schrieb Guillem Jover: > Source: init-system-helpers > Source-Version: 1.51 > Severity: normal > Tags: patch > > Hi! > > The current list of paths honored by deb-systemd-helper does not match > the one in systemd [L]. That's fine for several of them because

Bug#887396: systemd-timesyncd.service: Start request repeated too quickly.

Am 16.01.2018 um 10:55 schrieb André Verwijs: > > libnss-systemd  installed. > > "getent passwd systemd-timesync" says: > > systemd-timesync:*:62583:62583:Dynamic User:/:/sbin/nologin Does this problem persist after a reboot? What is the output of systemctl status systemd-timesyncd.service

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Am 15.01.2018 um 23:58 schrieb Felipe Sateler: > Control: tags -1 patch fixed-upstream > > On Mon, Jan 15, 2018 at 10:42 AM, Felipe Sateler wrote: >> It appears timesyncd wants to do this to support being run as root and then >> dropping privileges. However, this will fail

Bug#887396: systemd-timesyncd.service: Start request repeated too quickly.

Am 15.01.2018 um 21:57 schrieb Andre Verwijs: > Package: systemd > Version: 236-2 > Severity: important > Tags: upstream > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Am 15.01.2018 um 12:57 schrieb Martin Pitt: > If timesyncd in particular somehow wants to resolve the systemd-timesyncd > system user in its own code, then that either should be fixed, or systemd > needs > to raise libnss-systemd to a Depends: for that particular bug/reason. grepping through the

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Am 15.01.2018 um 12:57 schrieb Martin Pitt: > Note that *in general*, DynamicUser=yes does not *require* libnss-systemd. > Services start without it, the only effect is that showing the process with > tools like "ps" will not be able to resolve a dynamic user ID to a name - it > will just be shown

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes (requires libnss-systemd)

Am 15.01.2018 um 12:55 schrieb Guido Günther: > Turning it into a dependency would probably be best. It might be > sufficient to have it as a dependency of systemd-sysv, not systemd > itself. Yes, the Recommends: libnss-systemd in systemd-sysv would be bumped to Depends: libnss-systemd. While

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes (requires libnss-systemd)

Hi Guido Am 15.01.2018 um 12:14 schrieb Guido Günther: > Hi, > On Mon, Jan 15, 2018 at 11:24:33AM +0100, Michael Biebl wrote: >> Am 15.01.2018 um 10:18 schrieb Guido Günther: >> It requires libnss-systemd, yes. Do you not have it installed? >> It's a recommends, so should

Bug#887250: systemd should depend on e2fsprogs explicitly

Hi Helmut Am 14.01.2018 um 20:11 schrieb Helmut Grohne: > Package: systemd > Version: 236-3 > User: helm...@debian.org > Usertags: nonessentiale2fsprogs > > Dear maintainer, > > We want to make removing e2fsprogs from installations possible. For standard > installations this is not useful, but

Bug#887250: systemd should depend on e2fsprogs explicitly

Am 14.01.2018 um 21:07 schrieb Michael Biebl: > Hi Helmut > > Am 14.01.2018 um 20:11 schrieb Helmut Grohne: >> /bin/journalctl contains chattr. According to file it is a ELF 64-bit LSB >> shared object, x86-64, version 1 (SYSV) >> /bin/systemd-tmpfiles contain

Bug#886908: systemd enabled services unable to access shares

[please always CC the bug report] Am 11.01.2018 um 14:15 schrieb Hannu Laitinen: > Hello > > It doesn't matter if I use server with keyboard/monitor (which I mainly > use) or SSH both have same issue. When you mean keyboard/monitor, I assume you meant that you login locally on a tty? > A

Bug#886908: systemd enabled services unable to access shares

Am 11.01.2018 um 07:54 schrieb Hannu Laitinen: > Package: systemd > Version: 236-2 > Severity: important > > - My system starts with openvpn, plexmediaserver etc. After the system has > booted up I mount smb shares from vpn tunnel and files are accessable via > normal commandline and can

Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

Control: tags -1 + moreinfo On Wed, 10 Jan 2018 18:12:46 + Ben Hutchings wrote: > Control: reassign -1 systemd > > On Tue, 2018-01-09 at 11:50 +0100, Marc-Robin Wendt wrote: > > Package: src:linux > > Version: 4.9.65-3+deb9u1 > > Severity: normal > > > > Dear

Bug#886812: service: start/stop tries to use invalid systemd units when using socket templates

Am 10.01.2018 um 09:57 schrieb Cyrill Troxler: > Package: init-system-helpers > Version: 1.48 > > I stumbled upon a issue with the start/stop triggers when using systemd > socket templates on Debian stretch. I started getting unrelated error > messages when entering `service some_service start`

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

Am 08.01.2018 um 13:20 schrieb Christoph Pleger: > Hello, > >> >> This functionality has been reworked completely based on systemd-logind. >> >> Can you please test with a more recent version, like 232 from stable. > > at least, the problem does not occur in this form on a stretch machine, >

Bug#886342: systemd-networkd: Unknown section 'Tap'. Ignoring.

Am 04.01.2018 um 19:30 schrieb Wolfgang Walter: > Package: systemd > Version: 236-2 > > Problem: since upgrading to 236-1 I get the following error: > > systemd-networkd:[810]: /etc/systemd/network/tunnel.netdev: :5: Unknown > section 'Tap'. Ignoring. > Please share the complete file. Have

Bug#886131: cryptsetup freezes shutdown procedure

On Tue, 02 Jan 2018 16:27:18 +0100 Raphael wrote: > Package: cryptsetup > Version: 2:1.7.5-1 > Severity: normal > > Hi, > > Like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792552 , my > shutdown process never ends due to 'stopping remaining crypto disks'. > Though,

Bug#886156: systemd: crashes the system on reloading

Control: reassign -1 linux-image-4.14.0-2-amd6 Am 02.01.2018 um 19:09 schrieb Kjö Hansi Glaz: > Package: systemd > Version: 236-2 > Severity: normal > > Dear Maintainer, > > When I upgrade the system with apt, the system often becomes > unresponsive after reloading systemd. Please find below

Bug#878811: dummy interface in bridge sticks in "configuring", leading to degraded system

Control: tags -1 + moreinfo On Mon, 16 Oct 2017 21:57:15 +0200 Marc Haber wrote: > Package: systemd > Version: 235-2.0~zgSID+1 > Severity: normal > Tags: upstream patch > Forwarded: https://github.com/systemd/systemd/issues/6961 > > This is upstream issue 6961,

Bug#807041: 807041

On Sun, 13 Dec 2015 15:48:20 + "George B." wrote: > tags 807041 - moreinfo This was closed upstream as being fixed. Can you please retry if you still run into this issue with a recent version of systemd. Thanks, Michael -- Why is it that all of the instruments seeking

Bug#886053: override: libudev1:libs/optional

Package: ftp.debian.org Severity: normal With the recent changes in debian policy, libudev1 is now flagged as https://lintian.debian.org/tags/excessive-priority-for-library-package.html Please downgrade libudev1 to optional. I'll make the corresponding change in debian/control in the next

Bug#884788: systemd-ask-password echos password as stars (*) while decrypting LUKS partition

Am 20.12.2017 um 10:41 schrieb root kea: > On Wed, Dec 20, 2017 at 4:46 AM, Michael Biebl <bi...@debian.org> wrote: > >> I think this is intentional behaviour, so you'll easily spot that your >> input system works > > The current implementation is that the pass

Bug#885325: Similar issue: Mount points not found by apache2 and another services

Am 29.12.2017 um 13:03 schrieb Sumit Madan: > I'll try that tomorrow evening and inform you; I'm not at home > currently. But what I can tell is that the behavior over SSH has been > changed. In the past I often created mounts over SSH. My guess is that this is related to this upstream change

Bug#885325: Similar issue: Mount points not found by apache2 and another services

Am 29.12.2017 um 01:28 schrieb Sumit Madan: > Do you have an idea how to propagate the mount points created in an ssh > session to other namespaces? Just to clarify: This issue only happens if you login via SSH? If you login locally, e.g. on tty1, the manually mounted mount points are visible

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Control: reassign -1 xserver-xorg-core Control: forcemerge 810660 -1 Am 29.12.2017 um 09:30 schrieb Awtul: > Changingif [ "$SHLVL" = 1 ] in .bash_logout to if [ "$SHLVL" = 2 ] > > solves my problem; now X doesn't crash and I can switch between my openbox > session (on tty1) > and other

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Am 29.12.2017 um 08:55 schrieb Michael Biebl: > Which shell do you use as user shell. If it is bash, how does > ~/.bash_logout look like? > > Is the problem gone if you edit ~/.bash_logout as suggested in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858073#10 Fwiw, my

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Am 29.12.2017 um 08:43 schrieb Awtul: > Package: systemd > Followup-For: Bug #885318 > > Hi, > > I may have reported this bug against the wrong package (systemd); I apologize > if that is the case (?). > I wonder if this bug should be merged with #858073 & #791342. > I tried to reproduce with

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

control: tags -1 + unreproducible Am 28.12.2017 um 21:35 schrieb Michael Biebl: >> Please, let me know if you need more info/details. > > Why do you suspect it is systemd which kills your X session? > Can you provide logs or error messages which would confirm such a guess? I tri

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

Control: tags -1 + moreinfo Am 26.12.2017 um 07:56 schrieb Nekki Nekki: > Package: systemd > Version: 236-1 > Severity: critical > > Dear maintainers, > > When using startx (no DM enabled) I suspect that systemd logs me out > from my X session > if it doesn't freezes it. I try to explain: I

Bug#885325: systemd: Daemon start with systemctl start daemon can not find mount point not mounted by boot

Control: tags -1 + moreinfo Am 26.12.2017 um 09:30 schrieb John Wong: > Package: systemd > Version: 236-1 > Severity: important > > Dear Maintainer, > > After upgrade systemd* to 236-1, I noticed nfsd/smbd can not share some > mount point, > which is not mounted on boot (eg: luks

Bug#885201: systemd-cryptsetup-generator: incorrectly reports “Out of memory”

Control: forwarded -1 https://github.com/systemd/systemd/pull/7688 Would be great if you can try the upstream patch and verify that it fixes the issue. Am 26.12.2017 um 00:04 schrieb Ben Finney: > There is a patch suggested for the bug in SystemD Please write "systemd" in the future:

Bug#885061: systemd-timesyncd.service fails to start if static user is removed, but group is retained

Am 23.12.2017 um 09:26 schrieb Martin Dickopp: > Package: systemd > Version: 236-1 > Severity: normal > > Hi, > > Following the instructions in /usr/share/doc/systemd/NEWS.Debian.gz > > DynamicUser=yes has been enabled for systemd-journal-upload.service, > systemd-journal-gatewayd.service

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

Control: tags -1 moreinfo Control: severity -1 normal Am 22.12.2017 um 17:00 schrieb Christoph Pleger: > Package: systemd > Version: 215-17+deb8u7 > Severity: important > > Dear maintainers, > > The command 'shutdown -h +$time" does not send its repeated warning > messages to logged in users

Bug#884784: systemd-network segfaults

Am 20.12.2017 um 17:35 schrieb Rémi Denis-Courmont: > Le keskiviikkona 20. joulukuuta 2017, 0.05.02 EET Michael Biebl a écrit : >> Please try to provide a backtrace of the crash. > > eth0: Gained IPv6LL > > Program received signal SIGSEGV, Segmentation fault. ... >>

Bug#884258: machinectl shell should use bash as a default

On Wed, 13 Dec 2017 01:26:00 +0100 Michael Biebl <bi...@debian.org> wrote: > Am 13.12.2017 um 00:30 schrieb Marco d'Itri: > > Package: systemd-container > > Version: 235-3 > > Severity: normal > > > > Until https://github.com/systemd/systemd/issues/139

Bug#884788: systemd-ask-password echos password as stars (*) while decrypting LUKS partition

Am 19.12.2017 um 19:33 schrieb Avinash Sonawane: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > Dear Maintainer, > > I have encrypted swap and /home. When the system starts it asks password to > decrypt swap. The password doesn't get echoed at all. Totally expected >

Bug#884784: systemd-network segfaults

Control: severity -1 important Control: tags -1 moreinfo Control: found -1 236-1 Control: notfound -1 235-3 Am 19.12.2017 um 18:50 schrieb Rémi Denis-Courmont: > Package: systemd > Version: 235-3 > Severity: critical > Justification: breaks unrelated software > > Dear Maintainer, > >

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

Am 19.12.2017 um 02:18 schrieb Martin-Éric Racine: > 2017-12-19 2:02 GMT+02:00 Michael Biebl <bi...@debian.org>: >> Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: >>> 2017-12-18 2:08 GMT+02:00 Michael Biebl <bi...@debian.org>: >>>> Hi, >>&

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: > 2017-12-18 2:08 GMT+02:00 Michael Biebl <bi...@debian.org>: >> Hi, >> >> I just uploaded v236 today. Before we try to debug this further, it >> would be great if you can give this version a try. May

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: > 2017-12-18 2:08 GMT+02:00 Michael Biebl <bi...@debian.org>: >> Hi, >> >> I just uploaded v236 today. Before we try to debug this further, it >> would be great if you can give this version a try. May

Bug#884258: machinectl shell should use bash as a default

On Wed, 13 Dec 2017 01:26:00 +0100 Michael Biebl <bi...@debian.org> wrote: > Am 13.12.2017 um 00:30 schrieb Marco d'Itri: > > Package: systemd-container > > Version: 235-3 > > Severity: normal > > > > Until https://github.com/systemd/systemd/issues/139

Bug#862992: systemd: avoid attempt to re-create /etc/mtab by systemd-tmpfiles-setup.service

Control: clone -1 -2 Control: reassign -2 finish-install 2.90 Control: retitle -2 Stop using/creating /etc/mtab Control: block -1 by -2 On Mon, 29 May 2017 21:23:28 +0200 Cyril Brulebois <k...@debian.org> wrote: > Michael Biebl <bi...@debian.org> (2017-05-29): > > I th

Bug#884595: powermanga: Controls didn't work

Control: tags -1 + moreinfo On Sun, 17 Dec 2017 22:24:15 +0100 Markus Koschany wrote: > Control: reassign -1 udev > Control: retitle -1 udev creates a fake joystick device for MS mouse > Control: found -1 175-7.2 > Control: found -1 235-3 > > Am 17.12.2017 um 22:05 schrieb

Bug#869354: systemd: Overwrites local config without warning

On Sat, 22 Jul 2017 16:39:26 +0100 Nick wrote: > The upgrade today appears to have overwritten the target of the symlink > /etc/systemd/system/getty.target.wants/getty@tty1.service > from my local target under /etc (which does autologin) > to the package-provided file

Bug#787473: systemd: Segfault while adding a new job

Control: tags -1 + moreinfo Hi Tino, I'm looking through old bug reports. A lot has changed since v215, so it would be great if you can test this with v232 from current stable or event better v235 from testing and report back, if the issue is still reproducible. Regards, Michael -- Why is it

Bug#884506: systemd: "systemd-analyze plot" fails for root

Control: forwarded -1 https://github.com/systemd/systemd/issues/7667 Am 15.12.2017 um 23:24 schrieb Rainer Kupke: > Package: systemd > Version: 235-3 > Severity: normal > > Dear Maintainer, > > A long time ago I set up a cronjob to mail the output of "systemd-analyze > plot" > (as root) after

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

Am 15.12.2017 um 20:26 schrieb Peter 'p2' De Schrijver: > On 2017-12-15 20:23:11 (+0100), Michael Biebl <bi...@debian.org> wrote: >> Could it be a problem that >> >> [ OK ] Stopped LSB: Open vSwitch switch. >> >> is stopped before the NFS mou

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

Am 15.12.2017 um 20:19 schrieb Peter 'p2' De Schrijver: > On 2017-12-14 00:58:33 (+0100), Michael Biebl <bi...@debian.org> wrote: >> Am 14.12.2017 um 00:09 schrieb Michael Biebl: >>> Am 13.12.2017 um 22:04 schrieb Peter 'p2' De Schrijver: >>>> On 2017-12-13

Bug#884374: systemd: dpkg fails for systemd package when upgrading from jessie to stretch

Am 14.12.2017 um 18:51 schrieb zythox: > hi, got this : > > dpkg: systemd : problème de dépendance, mais suppression comme demandé : >  systemd-sysv dépend de systemd. >  libpam-systemd:amd64 dépend de systemd (= 215-17+deb8u7). > > (Lecture de la base de données... 65% > (Lecture de la base de

Bug#884374: systemd: dpkg fails for systemd package when upgrading from jessie to stretch

Am 14.12.2017 um 17:13 schrieb phil: > Package: systemd > Version: 232-25+deb9u1 > Severity: important > > Dear Maintainer, > > > I've just done an upgrade from jessie to strech and i'm stuck with the same pb > that is mentionned in this bug (https://bugs.debian.org/cgi- >

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

Am 14.12.2017 um 00:09 schrieb Michael Biebl: > Am 13.12.2017 um 22:04 schrieb Peter 'p2' De Schrijver: >> On 2017-12-13 21:53:10 (+0100), Michael Biebl <bi...@debian.org> wrote: >>> Control: tags -1 + moreinfo >> NFS mount is just done manually: >> >>

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

Am 13.12.2017 um 22:04 schrieb Peter 'p2' De Schrijver: > On 2017-12-13 21:53:10 (+0100), Michael Biebl <bi...@debian.org> wrote: >> Control: tags -1 + moreinfo >> >> >> Am 13.12.2017 um 21:32 schrieb Peter De Schrijver: >>> Package: systemd >>&g

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

Control: found 883877 235-3 Am 08.12.2017 um 21:47 schrieb Martin-Éric Racine: > http://q-funk.iki.fi/core.systemd.2857 > Not really a backtrace, but a core file, but ok. Looks like this is i386, so the backtrace should look like the attached .txt file. Would be great if you can file this

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

Control: tags -1 + moreinfo Am 13.12.2017 um 21:32 schrieb Peter De Schrijver: > Package: systemd > Version: 235-2 > Severity: important Please include more information about your network setup. What tools do you use (NM, ifupdown, networkd), what configuration (ethernet, wifi, dhcp, static),

Bug#878965: Detaching egress BPF program from cgroup failed: Invalid argument

Am 13.12.2017 um 12:01 schrieb Christian Göttsche: > I am also still getting these error messages on my machines. > > Any further information needed? No -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc

Bug#884258: machinectl shell should use bash as a default

Am 13.12.2017 um 00:30 schrieb Marco d'Itri: > Package: systemd-container > Version: 235-3 > Severity: normal > > Until https://github.com/systemd/systemd/issues/1395 will be fixed, > machinectl should be patched to use /bin/bash as the default shell > instead of /bin/sh. > While some people

Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

Am 08.12.2017 um 01:44 schrieb Duncan Hare: > Michael > > Full DNS is provided by an MS Windows server 2012R2. > > Because it is net boot, the network in enabled before the kernel is > loaded by u-boot, > and the kernel starts and mounts the file system over NFS. > > Networking parameters,

Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

Control: tags -1 moreinfo Control: severity -1 normal Am 08.12.2017 um 00:06 schrieb Duncan Hare: > browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw > 0 0 > tmpfs/tmptmpfs >

Bug#883738: systemd: RO Linux, systemd's link fail, links should not be created cross directory tree, use full paths

Control: tags -1 + moreinfo Am 07.12.2017 um 01:41 schrieb Duncan Hare: > Package: systemd > Version: 232-25+deb9u1 > Severity: important > > > This bug report is empty (again). Please describe your issues in much more detail. Otherwise I'll close this bug report (again) -- Why is it that

Bug#883690: systemd Caught , "Freezing execution", __libc_fatal("*** %n in writable segment detected ***\n") after execute asprintf(, "U\002%c%s%n"... in src/core/manager.c:2404

Hi Jan Am 06.12.2017 um 15:42 schrieb Jan Fuchs: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > systemd[1]: Caught , dumped core as pid 786. > systemd[1]: Freezing execution. Are you able to reproduce the issue and can you describe the circumstances that are needed to

Bug#883692: systemd: pam_systemd(su:session): Failed to create session

Control: forcemerge 883347 -1 Am 06.12.2017 um 16:37 schrieb Francesco Potortì: > After an upgrade two days ago, I get errors in system logs shortly after > midnight. I was not able to understand what program exactly has > problems, so I am not able to repsoduce this from the command line.

Re: stretch-pu: package systemd/232-25+deb9u2

On Sun, 03 Dec 2017 15:17:53 +0100 Michael Biebl <bi...@debian.org> wrote: > Package: release.debian.org > Severity: normal > Tags: stretch > User: release.debian@packages.debian.org > Usertags: pu > > Hi, > > I'd like to make a stable upload for syst

Bug#883395: stretch-pu: package systemd/232-25+deb9u2

s, Michael -- Michael Biebl <bi...@debian.org> Sun, 03 Dec 2017 15:03:50 +0100 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (S

Bug#876103: systemd-nspawn: --read-only is broken

Am 18.09.2017 um 15:43 schrieb Lauri Tirkkonen: > Package: systemd-container > Version: 232-25+deb9u1 > Severity: normal > > Dear Maintainer, > > on stretch, 'systemd-nspawn --read-only' fails to start the container > entirely. Trivial test case: > > # machinectl pull-tar >

Bug#883347: systemd fails to load pam_unix.so when spawning user.service

Am 02.12.2017 um 22:39 schrieb Michael Biebl: > Hi Russ! > > Am 02.12.2017 um 19:41 schrieb Russ Allbery: >> Package: systemd >> Version: 235-3 >> Severity: normal >> >> Since upgrading a system to 235-3, all ssh connections are producing the >> f

Bug#883202: systemd: only sets baud rate for first console= kernel parameter

Am 30.11.2017 um 17:23 schrieb Joshua Marshall: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > Dear Maintainer, > > root@debian:/home/testing# uname -a > > Linux debian 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28)

Bug#883185: systemd-networkd: physical port in bridge stuck in "configuring", failing systemd-networkd-wait-online.service

Am 30.11.2017 um 13:11 schrieb Bernhard Schmidt: > Package: systemd > Version: 235-3 > Severity: normal > > Hi, > > after upgrading from Stretch to Buster the physical interface in my bridge > is stuck in "configuring", causing systemd-networkd-wait-online to stall > and eventually timeout. > >

Bug#883089: udev: on alpha architecture, /dev/disk/by-XXX nodes not created

Am 29.11.2017 um 15:56 schrieb Bob Tracy: > Package: udev > Version: 235-3 > Severity: important > > Dear Maintainer, > > With kernel version 4.13, udev worked correctly at least two releases ago. > The > current release (and maybe the prior one) fails to detect/enumerate SCSI disk >

Bug#883026: systemd-fsck invalid parameters fo f2fs file system

Control: reassign -1 f2fs-tools Control: retitle -1 fsck.f2fs should support -y On Tue, 28 Nov 2017 22:23:18 + Piotr P. wrote: > Package: systemd > Version: 232-25+deb9u1 > > I found with debsums invalid packages(not systemd) so I created file > /forcefsck to

Bug#882270: systemd-logind crashes when closing lid after "systemctl mask sleep.target"

Control: forwarded -1 https://github.com/systemd/systemd/issues/7466 On Mon, 20 Nov 2017 22:05:49 +0100 Lars Stoltenow wrote: > disable suspend using "systemctl mask sleep.target suspend.target". ... > Nov 20 21:39:26 litterbox systemd-logind[10892]: Assertion

Bug#881834: systemd: lib/systemd/systemd-remount-fs fails with /dev/nfs in fstab

Control: reassign -1 nfs-common Control: tags -1 + patch On Wed, 15 Nov 2017 20:30:27 +0100 Michael Biebl <bi...@debian.org> wrote: > Fwiw, it's really mount or rather mount.nfs (from nfs-common) which > fails here: > > Nov 12 16:19:59 raspberrypi systemd-remount-f

Bug#882494: systemd-udevd: failed to execute '/lib/udev/mtp-probe'

Control: reassign -1 libmtp-runtime Am 23.11.2017 um 14:56 schrieb Narcis Garcia: > Package: udev > Version: 232-25+deb9u1 > Severity: minor > > This bug can be related to #693763 > > $ sudo journalctl -b -p err > -- Logs begin at Tue 2017-11-21 22:12:42 CET, end at Thu 2017-11-23 > 14:22:56

Bug#882245: systemd-sysv: shutdown does not parse correctly -t option

Am 22.11.2017 um 09:09 schrieb Thomas L: > Thank you for your answer. > >> I don't see a -t parameter there. It looks like -t is a legacy command >> line option which systemctl parses but ignores: > > Ok. However: > * systemctl does not correctly parse (and ignore) the -t option, because this >

Bug#882245: systemd-sysv: shutdown does not parse correctly -t option

Am 20.11.2017 um 18:07 schrieb Thomas L: > Try to reboot the computer with: > # shutdown -h -t 5 now Looking at shutdown --help (v232), I get > # shutdown --help > shutdown [OPTIONS...] [TIME] [WALL...] > > Shut down the system. > > --help Show this help > -H --halt

Bug#882245: systemd-sysv: shutdown does not parse correctly -t option

Hello Thomas Am 20.11.2017 um 18:07 schrieb Thomas L: > Package: systemd-sysv > Version: 215-17+deb8u7 > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > Try to reboot the

Bug#882027: (no subject)

Am 19.11.2017 um 16:11 schrieb Torsten Boese: > Hi Michael, > > thanks for the quick response. My goal is not to use a specific daemon, my > goal is to have a working suspend mode - if it's pam or systemd or whatever > is not important for me. But in my opinion it's useful to use the system >

Bug#882027: systemd: black screen after waking up from suspend to RAM

Am 17.11.2017 um 19:24 schrieb Torsten Boese: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > Dear Maintainer, > > after freshly installing debian stretch i ahd the following issue after > resume from suspend to RAM: > > The screen is just black but the PC is reachable via

Bug#881834: systemd: lib/systemd/systemd-remount-fs fails with /dev/nfs in fstab

Am 16.11.2017 um 00:32 schrieb Michael Biebl: > > Am 15.11.2017 um 21:02 schrieb Duncan Hare: >> The patch is correct, systemd process should ignore the /dev/nfs fstab >> entry, and report the dependency of remounting the file system correctly >> completed. > >

<    1   2   3   4   5   6   7   8   9   10   >