Processed: systemd-bootchart: debian/control refers to CC0 by URL

Processing control commands: > tag -1 + stretch buster Bug #882630 [systemd-bootchart] systemd-bootchart: debian/control refers to CC0 by URL Added tag(s) stretch and buster. > block -1 by 882628 Bug #882630 [systemd-bootchart] systemd-bootchart: debian/control refers to CC0 by URL 882630 was

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 wrote: > Fwiw, it's really mount or rather mount.nfs (from nfs-common) which > fails here: > > Nov 12 16:19:59 raspberrypi systemd-remount-fs[123]: /bin/mount for / >

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

Processing control commands: > reassign -1 nfs-common Bug #881834 [systemd] systemd: lib/systemd/systemd-remount-fs fails with /dev/nfs in fstab Bug reassigned from package 'systemd' to 'nfs-common'. No longer marked as found in versions systemd/232-25+deb9u1. Ignoring request to alter fixed

Processed: [bts-link] source package systemd

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] source package systemd

# # 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 #869995 (http://bugs.debian.org/869995) # Bug title: interface stuck in "configuring"

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

Processing control commands: > reassign -1 libmtp-runtime Bug #882494 [udev] systemd-udevd: failed to execute '/lib/udev/mtp-probe' Bug reassigned from package 'udev' to 'libmtp-runtime'. No longer marked as found in versions systemd/232-25+deb9u1. Ignoring request to alter fixed versions of bug

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#882494: systemd-udevd: failed to execute '/lib/udev/mtp-probe'

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 CET. -- nov 23 14:21:22 system systemd-udevd[280]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe

Bug#878965: systemd spam syslog with Detaching egress BPF program from cgroup failed: Invalid argument

Hello Another boot get this root@debian:/home/guy# journalctl -xb | grep BPF nov. 23 10:51:10 debian systemd[1]: Attaching egress BPF program to cgroup /sys/fs/cgroup/unified/system.slice/systemd-udevd.service failed: Invalid argument nov. 23 10:51:20 debian systemd[1]: Attaching egress BPF

Bug#878965: systemd spam syslog with Detaching egress BPF program from cgroup failed: Invalid argument

Hello Same problem here journalctl -xb -p err -- Logs begin at Thu 2017-11-23 08:13:01 CET, end at Thu 2017-11-23 09:21:44 CET. -- nov. 23 08:13:02 debian systemd[1]: Attaching egress BPF program to cgroup /sys/fs/cgroup/unified/system.slice/systemd-u nov. 23 08:13:04 debian kernel: ACPI

Bug#781151: boot often stalls with two "A start job is running" messages: binfmt and schroot sessions

Dear Michael, The machine on which I was seeing this bug recently died. In addition, the situation had improved and I can't remember whether I had seen the bug recently before the machine started to decay about six months ago. If I remember correctly, what did help quite a lot was to empty

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

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 option is followed by a number that should be skipped

Processed: bug 882245 is forwarded to https://github.com/systemd/systemd/issues/7413

Processing commands for cont...@bugs.debian.org: > forwarded 882245 https://github.com/systemd/systemd/issues/7413 Bug #882245 [systemd-sysv] systemd-sysv: shutdown does not parse correctly -t option Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/7413'. > thanks

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

I made a diff between systemd-sysv 215-17+deb8u5 (bug not present) and 215-17+deb8u7 (bug present), and there are 2 new patches (introduced in version 215-17+deb8u6) that may be related to this bug: * systemctl-fix-argument-handling-when-invoked-as-shutdown.patch *

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

Hi Michael, I can reproduce this bug on Strech as well (systemd-sysv 232-25+deb9u1). I think you should however also fix this bug on Jessie, because it is a recent regression (was not present on Jessie 8.6). Based on the package's recent changelog, it may be a regression of "systemctl: Fix

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

Package: systemd Version: 235-3 Severity: normal Dear Maintainer, I want to be able to configure if my laptop should suspend when closing the lid. Because I do not want to kill the X session for this, changing logind.conf and restarting logind is not an option. Therefore, I set

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#882245: systemd-sysv: shutdown does not parse correctly -t option

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 computer with: # shutdown -h -t 5 now * What was the outcome of this

Processed: [bts-link] source package systemd

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] source package systemd

# # 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 #879603 (http://bugs.debian.org/879603) # Bug title: systemd: network service enters

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

Processing commands for cont...@bugs.debian.org: > found #878811 235-3 Bug #878811 [systemd] dummy interface in bridge sticks in "configuring", leading to degraded system Marked as found in versions systemd/235-3. > thanks Stopping processing here. Please contact me if you need assistance. --

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

found #878811 235-3 thanks On Tue, Oct 17, 2017 at 07:36:43AM +0200, Marc Haber wrote: > I apologize, I filed this from a system with the fixed version > installed. Both 232 from stretch and 235 from sid (and 234 which was the > current version when the patch was developed) are affected, hence >

systemd 235-3 MIGRATED to testing

FYI: The status of the systemd source package in Debian's testing distribution has changed. Previous version: 235-2 Current version: 235-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive

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: (no subject)

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 standards. I have not changed any settings regarding

Bug#882067: marked as done (footnote for kernel-parameters.txt references a broken link)

Your message dated Sun, 19 Nov 2017 00:01:27 +0100 with message-id and subject line Re: Bug#882067: footnote for kernel-parameters.txt references a broken link has caused the Debian Bug report #882067, regarding footnote for kernel-parameters.txt

Bug#882067: footnote for kernel-parameters.txt references a broken link

Package: systemd Version: 232-25+deb9u1 In the manpage... man kernel-command-line A reference to the kernel-parameters.txt is a broken link. = For command line parameters understood by the kernel, please see

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

Processed: [bts-link] source package systemd

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] source package systemd

# # 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 #878965 (http://bugs.debian.org/878965) # Bug title: systemd spam syslog with

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. > > As said, the error comes from

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

Again, please always CC the bug report number on replies Am 15.11.2017 um 21:02 schrieb Duncan Hare: > Michael > > The mount is not in host:dir format because its kernal mount of the root > file system. > > The patch is correct, systemd process should ignore the /dev/nfs fstab > entry, and

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

Fwiw, it's really mount or rather mount.nfs (from nfs-common) which fails here: Nov 12 16:19:59 raspberrypi systemd-remount-fs[123]: /bin/mount for / exited with exit status 32. Nov 12 16:19:59 raspberrypi systemd-remount-fs[123]: mount.nfs: remote share not in 'host:dir' format

Processed: found 878965 in 235-3

Processing commands for cont...@bugs.debian.org: > found 878965 235-3 Bug #878965 {Done: Martin Pitt } [systemd] systemd spam syslog with Detaching egress BPF program from cgroup failed: Invalid argument Marked as found in versions systemd/235-3; no longer marked as fixed in

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

Processing control commands: > tags -1 + moreinfo Bug #881834 [systemd] systemd: lib/systemd/systemd-remount-fs fails with /dev/nfs in fstab Added tag(s) moreinfo. -- 881834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881834 Debian Bug Tracking System Contact ow...@bugs.debian.org with

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

Control: tags -1 + moreinfo Am 15.11.2017 um 18:12 schrieb Duncan Hare: > systemd " lib/systemd/systemd-remount-fs" fails with following fstab and > is processing fstab, and cannot process the fstab provided in the bug report. I'm having trouble parsing this sentence > The faulire resuts the

Bug#881823: systemd-networkd: Fails to start with 'Could not enumerate rules: Operation not supported'

Source: systemd Version: 235-3 Severity: normal Tags: upstream Hi! systemd-networkd fails to start on some machines with: Nov 15 15:13:37 pathfinder systemd[1]: Starting Network Service... Nov 15 15:13:37 pathfinder systemd-networkd[1799]: Could not enumerate rules: Operation not supported Nov

Bug#880026: marked as done (systemd: CVE-2017-15908)

Your message dated Wed, 15 Nov 2017 09:35:09 + with message-id and subject line Bug#880026: fixed in systemd 235-3 has caused the Debian Bug report #880026, regarding systemd: CVE-2017-15908 to be marked as done. This means that you claim that the problem

Bug#879191: marked as done (/usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d)

Your message dated Wed, 15 Nov 2017 09:35:09 + with message-id and subject line Bug#879191: fixed in systemd 235-3 has caused the Debian Bug report #879191, regarding /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d to be marked as

Bug#878182: marked as done (systemd: Should stop creating systemd-bus-proxy user)

Your message dated Wed, 15 Nov 2017 09:35:09 + with message-id and subject line Bug#878182: fixed in systemd 235-3 has caused the Debian Bug report #878182, regarding systemd: Should stop creating systemd-bus-proxy user to be marked as done. This means

Bug#878965: marked as done (systemd spam syslog with Detaching egress BPF program from cgroup failed: Invalid argument)

Your message dated Wed, 15 Nov 2017 09:35:09 + with message-id and subject line Bug#878965: fixed in systemd 235-3 has caused the Debian Bug report #878965, regarding systemd spam syslog with Detaching egress BPF program from cgroup failed: Invalid

Bug#878183: marked as done (systemd-journal-remote: Should stop creating systemd-journal-gateway user)

Your message dated Wed, 15 Nov 2017 09:35:09 + with message-id and subject line Bug#878183: fixed in systemd 235-3 has caused the Debian Bug report #878183, regarding systemd-journal-remote: Should stop creating systemd-journal-gateway user to be marked

systemd_235-3_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 15 Nov 2017 09:34:00 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

Processing of systemd_235-3_amd64.changes

systemd_235-3_amd64.changes uploaded successfully to localhost along with the files: systemd_235-3.dsc systemd_235-3.debian.tar.xz libnss-myhostname-dbgsym_235-3_amd64.deb libnss-myhostname_235-3_amd64.deb libnss-mymachines-dbgsym_235-3_amd64.deb libnss-mymachines_235-3_amd64.deb

Bug#881769: udev: Docs on upgrading to predictable network interface names don't work

On Wed, 15 Nov 2017 01:08:06 +0100 Michael Biebl wrote: > Am 14.11.2017 um 23:46 schrieb Karl O. Pinc: > > The stretch README.Debian.gz for udev omits mention that > > update-initramfs -u must be run after changing configuration files > > when converting to the new

Bug#881769: udev: Docs on upgrading to predictable network interface names don't work

Am 14.11.2017 um 23:46 schrieb Karl O. Pinc: > Package: udev > Version: 232-25+deb9u1 > Severity: normal > Tags: patch > > Hi, > > The stretch README.Debian.gz for udev omits mention that > update-initramfs -u must be run after changing configuration files > when converting to the new

Bug#881769: udev: Docs on upgrading to predictable network interface names don't work

Package: udev Version: 232-25+deb9u1 Severity: normal Tags: patch Hi, The stretch README.Debian.gz for udev omits mention that update-initramfs -u must be run after changing configuration files when converting to the new "predictable network interface names". Attached is a patch which clarifies

Processed: pending

Processing commands for cont...@bugs.debian.org: > tag 878965 pending Bug #878965 [systemd] systemd spam syslog with Detaching egress BPF program from cgroup failed: Invalid argument Added tag(s) pending. > tag 880026 pending Bug #880026 [src:systemd] systemd: CVE-2017-15908 Added tag(s)

Bug#878183: systemd-journal-remote: Should stop creating systemd-journal-gateway user

Control: tag -1 pending Martin Pitt [2017-10-11 22:37 +0200]: > if there's any doubt in whether it's safe to remove, I think it's okay to not > bother -- after all, a DynamicUser= unit will still use the existing system > user if it exists, so there isn't that much gain in cleaning it up. Done

Processed: Re: Bug#878183: systemd-journal-remote: Should stop creating systemd-journal-gateway user

Processing control commands: > tag -1 pending Bug #878183 [systemd-journal-remote] systemd-journal-remote: Should stop creating systemd-journal-gateway user Added tag(s) pending. -- 878183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878183 Debian Bug Tracking System Contact

Bug#878182: systemd: Should stop creating systemd-bus-proxy user

Control: tag -1 pending Michael Biebl [2017-10-11 18:41 +0200]: > This one seems safe. v232 from stretch no longer ships the > systemd-bus-proxyd service, so we can safely drop the useradd call and > remove the obsolete system user account. Agreed. Done in git. Martin

Processed: Re: Bug#878182: systemd: Should stop creating systemd-bus-proxy user

Processing control commands: > tag -1 pending Bug #878182 [systemd] systemd: Should stop creating systemd-bus-proxy user Added tag(s) pending. -- 878182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

PLEASE REPLY QUICK FOR DETAILS

Good day my good friend, Let me start by introducing myself. I am James Musa, an accounts officer with Bank of Africa here in Burkina Faso West Africa. I am writing you this letter based on the latest development at my bank whichI will like to bring to your personal edification. ($9million)

Processed: [bts-link] source package systemd

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] source package systemd

# # 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 #878965 (http://bugs.debian.org/878965) # Bug title: systemd spam syslog with

☢some interesting facts

Hey, I've found that interesting article with a lot of surprising reality, simply take a look http://www.moussamara.net/logical.php?UE9zeXN0ZW1kQHBhY2thZ2VzLmRlYmlhbi5vcmc- Andreas Henriksson ___ Pkg-systemd-maintainers mailing list

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Control: tags -1 = patch Am 12.11.2017 um 00:33 schrieb Alex King: > So it seems like this will be a problem for stretch systems with > usrmerge enabled, and are not using systemd-resolved Indeed, these are the conditions under which you can trigger this issue. Looking through the git history,

Processed: Re: Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Processing control commands: > tags -1 = patch Bug #881310 [systemd-container] systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf Added tag(s) patch; removed tag(s) upstream and moreinfo. -- 881310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881310 Debian

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

On 12/11/17 00:53, Michael Biebl wrote: Hi Alex Am 11.11.2017 um 00:33 schrieb Alex King: looks like everything that should be in /lib/systemd and /usr/lib/systemd is duplicated in both places?!  I guess that is most likely a sysadmin typo, although the system was reloaded relatively

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Hi Alex Am 11.11.2017 um 00:33 schrieb Alex King: > looks like everything that should be in /lib/systemd and > /usr/lib/systemd is duplicated in both places?!  I guess that is most > likely a sysadmin typo, although the system was reloaded relatively > recently and I have no idea how this could

Processed: Re: Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Processing control commands: > fixed -1 234-1 Bug #881310 [systemd-container] systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf Marked as fixed in versions systemd/234-1. -- 881310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881310 Debian Bug Tracking

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Control: fixed -1 234-1 Am 11.11.2017 um 00:33 schrieb Alex King: > Looking at the code ("src/nspawn/nspawn.c" in v232), it appears that the > existence of /usr/lib/systemd/resolv.conf, which exists on the > problematic system, is triggering the problem. Ok, I had another look. In v232, the

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Am 11.11.2017 um 00:58 schrieb Michael Biebl: > As for your question, how this file got there: Did you install systemd > from source in the past? What does dpkg -S /usr/lib/systemd/resolv.conf say? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Am 11.11.2017 um 00:33 schrieb Alex King: > Looking at the code ("src/nspawn/nspawn.c" in v232), it appears that the > existence of /usr/lib/systemd/resolv.conf, which exists on the > problematic system, is triggering the problem. Actually, that points at another problem: With split-usr (as

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Looking at the code ("src/nspawn/nspawn.c" in v232), it appears that the existence of /usr/lib/systemd/resolv.conf, which exists on the problematic system, is triggering the problem. Not sure how that resolv.conf file got there. $ ls /usr/lib/systemd/ boot 

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Am 10.11.2017 um 23:05 schrieb Alex King: > $ sudo systemctl status systemd-resolved.service > ● systemd-resolved.service - Network Name Resolution >    Loaded: loaded (/lib/systemd/system/systemd-resolved.service; > disabled; vendo >   Drop-In: /usr/lib/systemd/system/systemd-resolved.service.d >

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Interesting. I tried to reproduce this myself on another machine and could not.  It may be peculiar to this machine which is a VPS in xen. Neither host nor guest is running resolved: $ sudo systemctl status systemd-resolved.service ● systemd-resolved.service - Network Name Resolution   

Processed: Re: Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Processing control commands: > tags -1 + moreinfo Bug #881310 [systemd-container] systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf Added tag(s) moreinfo. -- 881310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881310 Debian Bug Tracking System Contact

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Control: tags -1 + moreinfo Am 10.11.2017 um 01:10 schrieb Alex King: > After installing the package to get systemd-nspawnd, I created an etch > image with: > > # cd /var/lib/machines > # debootstrap --variant=minbase --no-check-gpg --arch=i386 etch etchruby \ > http://archive.debian.org/debian/

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

Package: systemd-container Version: 232-25+deb9u1 Severity: normal Tags: upstream Dear Maintainer, After installing the package to get systemd-nspawnd, I created an etch image with: # cd /var/lib/machines # debootstrap --variant=minbase --no-check-gpg --arch=i386 etch etchruby \

Processed: closing 728290

Processing commands for cont...@bugs.debian.org: > close 728290 Bug #728290 [udev] No link in /dev/input/by-id without the -ifXX- stuff Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 728290:

[bts-link] source package systemd

# # 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 #802211 (http://bugs.debian.org/802211) # Bug title: systemd: rescue.service fails if

Bug#758808: Warnning Needs Extension!!

Your E-mail Needs Extension!! 95% Space USED 5 % Space FREE Due to low E-mail Account quota, further incoming emails with high massage size above 10kb might be discarded until your email quota has been extended. You have used 95% MB of 5G of your email account quota. We

Bug#811473: systemd: timer with WakeSystem=yes doesn't always start the service it's supposed to trigger

Am 19.01.2016 um 10:36 schrieb Christian Pernegger: > Package: systemd > Version: 215-17+deb8u2 > Severity: normal > > > Hello, > > I'm trying to do the following: > 1) wake up the system every night at 3 am (using a timer unit with > WakeSystem=yes) > 2) pull in backups (using a service

Bug#811473: systemd: timer with WakeSystem=yes doesn't always start the service it's supposed to trigger

Am 19.01.2016 um 10:36 schrieb Christian Pernegger: > Package: systemd > Version: 215-17+deb8u2 > Severity: normal > > > Hello, > > I'm trying to do the following: > 1) wake up the system every night at 3 am (using a timer unit with > WakeSystem=yes) > 2) pull in backups (using a service

Bug#811473: systemd: timer with WakeSystem=yes doesn't always start the service it's supposed to trigger

Am 08.11.2017 um 20:21 schrieb Alberto Manzaneque García: > I have the same problem too on version 234. > Do you know if there is a systemd (not debian) bug open? > > On Sat, 25 Feb 2017 16:35:20 +0200 (EET) Madis Janson > wrote: >> >> I have exactly the

Bug#811473: systemd: timer with WakeSystem=yes doesn't always start the service it's supposed to trigger

I have the same problem too on version 234. Do you know if there is a systemd (not debian) bug open? On Sat, 25 Feb 2017 16:35:20 +0200 (EET) Madis Janson wrote: > > I have exactly the same problem with Debian Stretch (testing) on amd64. > Package version is 232-15. > > $

Processed: Re: Bug#880982: ifup does not trigger scripts any more after booting

Processing control commands: > reassign -1 ifupdown Bug #880982 [udev] ifup does not trigger scripts any more after booting Bug reassigned from package 'udev' to 'ifupdown'. No longer marked as found in versions systemd/232-25+deb9u1. Ignoring request to alter fixed versions of bug #880982 to the

Bug#880982: ifup does not trigger scripts any more after booting

Control: reassign -1 ifupdown Am 06.11.2017 um 17:53 schrieb Narcis Garcia: > Package: udev > Version: 232-25+deb9u1 > Severity: serious > > Tested with updated Debian 9 (amd64): > > Interface is declared at /etc/network/interfaces : > auto enp2s0 > allow-hotplug enp2s0 > iface enp2s0 inet dhcp

Bug#880982: ifup does not trigger scripts any more after booting

Package: udev Version: 232-25+deb9u1 Severity: serious Tested with updated Debian 9 (amd64): Interface is declared at /etc/network/interfaces : auto enp2s0 allow-hotplug enp2s0 iface enp2s0 inet dhcp An executable script: /etc/network/if-up.d/test1 only runs on boot (per each NIC). If network

Bug#867368: systemd-udevd: delays boot for 2+ minutes when LVM PV is inside a LV

I'm experiencing the same behavior with a lvm pv on top of a md mirror: Nov 2 22:03:13 zero systemd-udevd[515]: seq 4167 '/devices/virtual/block/md4' is taking a long time pvscan PV /dev/sda VG BACKUP0 lvm2 [9.10 TiB / 98.00 GiB free] PV /dev/md4 VG MAIN0 lvm2 [9.10

Bug#758808: Network Update

Please be advised that we will be performing a scheduled email maintenance within the next 24hrs, during this maintenance you will be require to update your email account via link http://ow.ly/Sq6F30gkrWH --- This email has been checked for viruses by Avast antivirus software.

Processed: [bts-link] source package src:systemd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src: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] source package src:systemd

# # bts-link upstream status pull for source package src: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 #880026 (http://bugs.debian.org/880026) # Bug title: systemd: CVE-2017-15908 # *

Bug#880158: systemd-container: machinectl incorrectly reports "No machines." when using --no-legend

Control: fixed -1 235-2 Hello David Preece, Thanks for your bug report. On Mon, Oct 30, 2017 at 04:19:23AM +, David Preece wrote: > Package: systemd-container > Version: 232-25+deb9u1 > Severity: important (What motivates this severity? I'd say minor is more suitable.) [...] > Running

Processed: Re: systemd-container: machinectl incorrectly reports "No machines." when using --no-legend

Processing control commands: > fixed -1 235-2 Bug #880158 [systemd-container] systemd-container: machinectl incorrectly reports "No machines." when using --no-legend Marked as fixed in versions systemd/235-2. -- 880158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880158 Debian Bug

Processed: found in stretch

Processing commands for cont...@bugs.debian.org: > package libpam-systemd Limiting to bugs with field 'package' containing at least one of 'libpam-systemd' Limit currently set to 'package':'libpam-systemd' > tags 732209 stretch Bug #732209 [libpam-systemd] unable to create file

[bts-link] source package systemd

# # 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 #879603 (http://bugs.debian.org/879603) # Bug title: systemd: network service enters

Processed: Metadata for #848327: RFS: libu2f-host/1.1.4-1 [RC]

Processing commands for cont...@bugs.debian.org: > unarchive 824532 Bug #824532 {Done: Michael Biebl } [udev] udev: Include udev rules for more U2F devices Bug #862067 {Done: Michael Biebl } [udev] udev: U2F support. Outdated uaccess udev rules. Unarchived

Processed: severity of 880158 is minor

Processing commands for cont...@bugs.debian.org: > severity 880158 minor Bug #880158 [systemd-container] systemd-container: machinectl incorrectly reports "No machines." when using --no-legend Severity set to 'minor' from 'important' > thanks Stopping processing here. Please contact me if you

Bug#879191: /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d

On Oct 20, Michael Biebl wrote: > That path is read by kmod. Given that kmod supports > /usr/lib/modules-load.d and /lib/modules-load.d/ it would imho make > sense if it also supported /usr/lib/modprobe.d besides /lib/modprobe.d I would rather have this patch be submitted

Bug#880026: systemd: CVE-2017-15908

Hi Michael, On Sat, Oct 28, 2017 at 08:16:46PM +0200, Michael Biebl wrote: > Hi Salvatore! > > Am 28.10.2017 um 17:38 schrieb Salvatore Bonaccorso: > > > Since systemd-resolved is not enabled by default I think an update via > > an upcoming stretch point release would be enough. Please let us

init-system-helpers 1.51 MIGRATED to testing

FYI: The status of the init-system-helpers source package in Debian's testing distribution has changed. Previous version: 1.50 Current version: 1.51 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

Bug#880026: systemd: CVE-2017-15908

Source: systemd Version: 232-1 Severity: important Tags: patch security upstream Forwarded: https://github.com/systemd/systemd/pull/7184 Hi, the following vulnerability was published for systemd. CVE-2017-15908[0]: | In systemd 223 through 235, a remote DNS server can respond with a | custom

Bug#877985: user@1000.service: Start operation timed out. Terminating.

Michael Biebl (bi...@debian.org) wrote: > The output of > systemctl --user status > busctl --user > systemctl --user list-unit-files > systemctl --user show-environment > > might be helpful as well. Sure: vk@sherri ~ % systemctl --user status

Bug#877985: user@1000.service: Start operation timed out. Terminating.

Michael Biebl (bi...@debian.org) wrote: > Could you disable the user services you use one by one and test if that > makes a service. > I would probably start by disabling the syncthing.service user service. You need to help me out on that one I guess: vk@sherri ~ % systemctl --user disable

Bug#877985: user@1000.service: Start operation timed out. Terminating.

Michael Biebl (bi...@debian.org) wrote: > Am 08.10.2017 um 11:59 schrieb Karl Voit: > > Oct 08 10:10:16 sherri syncthing[1594]: [GDIGF] INFO: Established secure > > connection to [...] > > Oct 08 10:10:16 sherri syncthing[1594]: [GDIGF] INFO: Device [...] client > > is "syncthing v0.14.38"

Processed: [bts-link] source package systemd

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

<    4   5   6   7   8   9   10   11   12   13   >