[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 #879191 (http://bugs.debian.org/879191) # Bug title: /usr/lib/modprobe.d/systemd.conf

Bug#879603: systemd: network service enters failed state when client goes away too fast

On 10/26/2017 06:10 PM, Michael Biebl wrote: > Control: tags -1 moreinfo > > upstream requested this information at > https://github.com/systemd/systemd/issues/7172#issuecomment-339601311: > > "any chance you can run strace -p1 -s 500 before this, then trigger > this, so that we can see where

Bug#879603: systemd: network service enters failed state when client goes away too fast

Control: tags -1 moreinfo upstream requested this information at https://github.com/systemd/systemd/issues/7172#issuecomment-339601311: "any chance you can run strace -p1 -s 500 before this, then trigger this, so that we can see where precisely the ENOTCONN is generated" -- Why is it that

Processed: Re: Bug#879603: systemd: network service enters failed state when client goes away too fast

Processing control commands: > tags -1 moreinfo Bug #879603 [systemd] systemd: network service enters failed state when client goes away too fast Added tag(s) moreinfo. -- 879603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879603 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#879771: marked as done (init-system-helpers: update-rc.d falsly creates K-symlinks on installation which breaks switching init systems later)

Your message dated Wed, 25 Oct 2017 17:35:38 + with message-id and subject line Bug#879771: fixed in init-system-helpers 1.51 has caused the Debian Bug report #879771, regarding init-system-helpers: update-rc.d falsly creates K-symlinks on installation

init-system-helpers_1.51_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 25 Oct 2017 12:38:42 -0300 Source: init-system-helpers Binary: init-system-helpers init Architecture: source Version: 1.51 Distribution: unstable Urgency: high Maintainer: Debian systemd Maintainers

Processing of init-system-helpers_1.51_source.changes

init-system-helpers_1.51_source.changes uploaded successfully to localhost along with the files: init-system-helpers_1.51.dsc init-system-helpers_1.51.tar.xz init-system-helpers_1.51_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed: Re: Bug#879771: init-system-helpers: update-rc.d falsly creates K-symlinks on installation which breaks switching init systems later

Processing control commands: > tags -1 pending Bug #879771 [init-system-helpers] init-system-helpers: update-rc.d falsly creates K-symlinks on installation which breaks switching init systems later Added tag(s) pending. -- 879771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879771 Debian

Bug#879771: init-system-helpers: update-rc.d falsly creates K-symlinks on installation which breaks switching init systems later

Control: tags -1 pending Hi Daniel, On Wed, Oct 25, 2017 at 1:13 PM, Daniel Reichelt wrote: > Package: init-system-helpers > Version: 1.50 > Severity: important > Tags: patch > > Hi, > > Assume this environment: > > - debootstrap sid > - chroot apt-get install

Bug#879771: init-system-helpers: update-rc.d falsly creates K-symlinks on installation which breaks switching init systems later

Package: init-system-helpers Version: 1.50 Severity: important Tags: patch Hi, Assume this environment: - debootstrap sid - chroot apt-get install openssh-server With init-system-helpers <1.50 you would now find S-symlinks in etc/rc?.d. However with init-system-helpers 1.50, you'll see

Bug#879727: debhelper: dh_systemd_start script fails to start new units when an existing unit is updated (LP#1707880)

Package: debhelper Version: 10.10.3 Severity: important Quote from [LP#1707880]: """ Upon upgrading apt from a version that only ships apt-daily.timer to the one that ships apt-daily.timer and apt-daily-upgrade.timer, the latter is not started on zesty and later. I believe this may be a bug

Processed: bug 879603 is forwarded to https://github.com/systemd/systemd/issues/7172

Processing commands for cont...@bugs.debian.org: > forwarded 879603 https://github.com/systemd/systemd/issues/7172 Bug #879603 [systemd] systemd: network service enters failed state when client goes away too fast Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/7172'.

Processed: tagging 806852

Processing commands for cont...@bugs.debian.org: > tags 806852 - fixed-upstream Bug #806852 [systemd] systemd: rescue.service fails if root password is not set, needs sulogin --force Bug #802211 [systemd] systemd: rescue.service fails if root password is not set, needs sulogin --force Removed

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

Bug#879603: systemd: network service enters failed state when client goes away too fast

On 10/23/2017 01:31 PM, Michael Biebl wrote: > Am 23.10.2017 um 12:21 schrieb Julien Cristau: >> Package: systemd >> Version: 232-25+deb9u1 >> User: debian-ad...@lists.debian.org >> Usertag: needed-by-DSA-Team >> >> It looks like systemd has a race condition where instead of giving up >>

Bug#879603: systemd: network service enters failed state when client goes away too fast

Am 23.10.2017 um 12:21 schrieb Julien Cristau: > Package: systemd > Version: 232-25+deb9u1 > User: debian-ad...@lists.debian.org > Usertag: needed-by-DSA-Team > > It looks like systemd has a race condition where instead of giving up > gracefully when a client goes away, it enters a bogus failure

Bug#879603: systemd: network service enters failed state when client goes away too fast

Package: systemd Version: 232-25+deb9u1 User: debian-ad...@lists.debian.org Usertag: needed-by-DSA-Team It looks like systemd has a race condition where instead of giving up gracefully when a client goes away, it enters a bogus failure mode. ●

Processed: tagging 879191

Processing commands for cont...@bugs.debian.org: > tags 879191 + pending Bug #879191 [systemd] /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 879191:

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

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" named "Blackbox" > Oct 08 10:10:45 sherri systemd[1]:

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

The output of systemctl --user status busctl --user systemctl --user list-unit-files systemctl --user show-environment might be helpful as well. Since you mentioned that it worked in the past, can you investigate if you installed any new packages/upgrades or changed your configuration since the

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

Am 08.10.2017 um 11:59 schrieb Karl Voit: > [boot process] > [things seem to be normal, even syncthing is starting up and then] > 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 [...]

Bug#879277: systemd: After resume from suspend to ram system immediiately hibernates

Hello, On 22 October 2017 at 14:14, Michael Biebl wrote: > Am 22.10.2017 um 13:43 schrieb Michal Suchanek: > Please try downgrading the kernel to the previous version and report back. Downgrading the kernel is not really an option. It was broken so I did not keep a backup and

Bug#879277: systemd: After resume from suspend to ram system immediiately hibernates

Am 22.10.2017 um 13:43 schrieb Michal Suchanek: > On 21 October 2017 at 17:13, Michael Biebl wrote: >> Control: severity -1 normal >> Control: tags -1 moreinfo >> >> Am 21.10.2017 um 14:29 schrieb Michal Suchanek: >>> Package: systemd >>> Version: 232-25+deb9u1 >>> Severity:

Bug#879277: systemd: After resume from suspend to ram system immediiately hibernates

On 21 October 2017 at 17:13, Michael Biebl wrote: > Control: severity -1 normal > Control: tags -1 moreinfo > > Am 21.10.2017 um 14:29 schrieb Michal Suchanek: >> Package: systemd >> Version: 232-25+deb9u1 >> Severity: important >> >> Hello, >> >> after recent upgrade I was

Bug#879277: systemd: After resume from suspend to ram system immediiately hibernates

Control: severity -1 normal Control: tags -1 moreinfo Am 21.10.2017 um 14:29 schrieb Michal Suchanek: > Package: systemd > Version: 232-25+deb9u1 > Severity: important > > Hello, > > after recent upgrade I was unable to wake up from suspend. Which packages were updated? systemd in stable was

Processed: Re: Bug#879277: systemd: After resume from suspend to ram system immediiately hibernates

Processing control commands: > severity -1 normal Bug #879277 [systemd] systemd: After resume from suspend to ram system immediiately hibernates Severity set to 'normal' from 'important' > tags -1 moreinfo Bug #879277 [systemd] systemd: After resume from suspend to ram system immediiately

Toronto PO# 8730 + 8731

Hi, Please find attached Toronto PO# 8730 + 8731. Kindly forward the Proforma�s for confirmation. Please Click to Download We need these dispatched in the last week of This Month. Thanks, Bruce Bradley Download PO# 8730 + 8731.PDF 186K

GREAT NEWS!!! – LOGO DESIGN PROFESSIONAL IS HERE FOR YOU (IN)

Hello there, It is with great pleasure to announce to you that your worries on getting the perfect logo for your businesses or websites are no more. Yes! And I am very sure you won’t want to miss out this great opportunity. With our years of experience in this field, we have been able to

Processed: Re: Bug#878625: systemd: NIS users login takes longtime.

Processing control commands: > reassign -1 nis Bug #878625 [systemd] systemd: NIS users login takes longtime. Bug reassigned from package 'systemd' to 'nis'. No longer marked as found in versions systemd/235-2. Ignoring request to alter fixed versions of bug #878625 to the same values previously

Bug#878625: systemd: NIS users login takes longtime.

Control: reassign -1 nis Control: retitle -1 "nscd should be a Depends" * Michael Biebl [2017-10-16 11:27 +0200]: > Control: forwarded -1 https://github.com/systemd/systemd/issues/7074 > > Am 15.10.2017 um 10:55 schrieb Elimar Riesebieter: > > Package: systemd > > Version:

Bug#879216: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved

Package: systemd Version: 235-2 Severity: normal Something about the service configuration for systemd-resolved doesn't match what the service manager expects. What does it mean to start an executable path with "!!" ? 0 dkg@alice:~$ systemctl status systemd-resolved ● systemd-resolved.service

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

Processing control commands: > forwarded -1 https://github.com/systemd/systemd/pull/7149 Bug #879191 [systemd] /usr/lib/modprobe.d/systemd.conf ignored, should be in /lib/modprobe.d Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/7149'. -- 879191:

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

Control: forwarded -1 https://github.com/systemd/systemd/pull/7149 Am 20.10.2017 um 10:38 schrieb Marc Haber: > /usr/lib/modprobe.d/systemd.conf gets ignored, at least on non-usrmerged > systems. The file should be in /lib/modprobe.d, where already other > files are placed. Moving the file gets

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

Am 20.10.2017 um 13:00 schrieb Marc Haber: > On Fri, Oct 20, 2017 at 12:54:38PM +0200, 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

Bug#791944: /etc/init.d/sendsigs kills systemd-udevd upon shutdown, causing dmsetup to hang

On Monday 12 June 2017 13:37:13 Pali Rohár wrote: > On Saturday 10 June 2017 22:44:31 Michael Biebl wrote: > > Hi > > > > Am 10.06.2017 um 21:14 schrieb Pali Rohár: > > > > > PING. Do you need to test something more? Or is that patch enough? > > > > The patch seems to contain some left-over

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

Am 20.10.2017 um 10:38 schrieb Marc Haber: > Package: systemd > Version: 235-2 > Severity: normal > > > Hi, > > /usr/lib/modprobe.d/systemd.conf gets ignored, at least on non-usrmerged > systems. The file should be in /lib/modprobe.d, where already other > files are placed. Moving the file gets

Bug#878625: systemd: NIS users login takes longtime.

* Elimar Riesebieter [2017-10-17 18:24 +0200]: > * Michael Biebl [2017-10-17 16:38 +0200]: > > > Am 15.10.2017 um 11:15 schrieb Elimar Riesebieter: > > > * Elimar Riesebieter [2017-10-15 10:55 +0200]: > > > > > >> Package: systemd > >

Bug#877672: [systemd] System Stalled at Pam-nologon

Control: severity -1 normal Due to lack of feedback I'm downgrading the severity to normal and will close the bug report in two weeks if no further information is provided. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Processed: Re: [systemd] System Stalled at Pam-nologon

Processing control commands: > severity -1 normal Bug #877672 [systemd] [systemd] System Stalled at Pam-nologon Severity set to 'normal' from 'critical' -- 877672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tagging 878768, notfound 878768 in 232-25+deb9u1, closing 878768

Processing commands for cont...@bugs.debian.org: > tags 878768 - moreinfo unreproducible Bug #878768 [systemd] systemd: *.dpkg-remove.service entries in systemctl Removed tag(s) unreproducible and moreinfo. > notfound 878768 232-25+deb9u1 Bug #878768 [systemd] systemd: *.dpkg-remove.service

Bug#878625: systemd: NIS users login takes longtime.

Am 15.10.2017 um 11:15 schrieb Elimar Riesebieter: > * Elimar Riesebieter [2017-10-15 10:55 +0200]: > >> Package: systemd >> Version: 235-2 >> Severity: normal >> >> Login as a NIS user journalctl tells: >> >> systemd-logind[666]: do_ypcall: clnt_call: RPC: Unable to send;

Bug#878768: systemd: *.dpkg-remove.service entries in systemctl

Control: found -1 215-17+deb8u7 Control: fixed -1 219-1 Am 17.10.2017 um 16:16 schrieb Martin von Wittich: > Am 16.10.2017 um 17:52 schrieb Michael Biebl: >> systemd should already ignore files ending in dpkg-remove, see >> https://github.com/systemd/systemd/blob/master/src/basic/path-util.c#L808

Processed: notfound 878811 in 235-2.0~zgSID+1

Processing commands for cont...@bugs.debian.org: > notfound 878811 235-2.0~zgSID+1 Bug #878811 [systemd] dummy interface in bridge sticks in "configuring", leading to degraded system There is no source info for the package 'systemd' at version '235-2.0~zgSID+1' with architecture '' Unable to

Processed: found 878811 in 232-19

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

Processed: found 878811 in 232-25

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

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

On Tue, Oct 17, 2017 at 12:11:07AM +0200, Michael Biebl wrote: > Control: > Am 16.10.2017 um 21:57 schrieb Marc Haber: > > Package: systemd > > Version: 235-2.0~zgSID+1 > > Seems the bts is not happy with that version. > For proper version tracking, which version is affected by this? > Is this a

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

Control: Am 16.10.2017 um 21:57 schrieb Marc Haber: > Package: systemd > Version: 235-2.0~zgSID+1 Seems the bts is not happy with that version. For proper version tracking, which version is affected by this? Is this a regression in v235 or (given your comment) is not a regression and happens with

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

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, where a dummy interface configured into a bridge gets stuck in "configuring" state, with the usual consequences of the network

Processed: Re: Bug#869995: fixed in systemd 235-1

Processing control commands: > tags -1 - fixed-upstream Bug #869995 [systemd] interface stuck in "configuring" if SLAAC prefix announced with preferred lifetime zero Removed tag(s) fixed-upstream. -- 869995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869995 Debian Bug Tracking System

Bug#831414: systemd: learns IPv6 prefix from its own RAs and configures IP address on wrong interface

Version: 234-1 Am 16.10.2017 um 18:52 schrieb Marc Haber: > Hi, > > stumbling upon this again. The system behaves now, so the issue as at > least fixed in systemd 234. Ah, perfect. Thanks for reporting back. Closing the bug report for that version then. Michael -- Why is it that all of the

Processed: Re: Bug#869995: fixed in systemd 235-1

Processing commands for cont...@bugs.debian.org: > found #869995 235-1 Bug #869995 {Done: Michael Biebl } [systemd] interface stuck in "configuring" if SLAAC prefix announced with preferred lifetime zero There is no source info for the package 'systemd' at version '235-1' with

Bug#831414: systemd: learns IPv6 prefix from its own RAs and configures IP address on wrong interface

Hi, stumbling upon this again. The system behaves now, so the issue as at least fixed in systemd 234. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany

Processed: Re: Bug#878768: systemd: *.dpkg-remove.service entries in systemctl

Processing control commands: > tags -1 moreinfo unreproducible Bug #878768 [systemd] systemd: *.dpkg-remove.service entries in systemctl Added tag(s) moreinfo and unreproducible. -- 878768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878768 Debian Bug Tracking System Contact

Bug#878768: systemd: *.dpkg-remove.service entries in systemctl

Control: tags -1 moreinfo unreproducible Am 16.10.2017 um 17:03 schrieb Martin von Wittich: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > Dear Maintainer, > > one of our servers has several "*.dpkg-remove.service" entries in its > systemctl output: > > asterisk.iserv.eu ~

amazing weekend

Dear! We've spent an extremely wonderful weekend in a very nice place, please have a look at that http://www.gymn32.ru/considerably.php?UE91ZGV2QHBhY2thZ2VzLmRlYmlhbi5vcmc- Pardon my monkey thumbs, Samuel Thibault - In no event will we be liable for any loss or damage including without

Processed: Re: Bug#878625: systemd: NIS users login takes longtime.

Processing control commands: > forwarded -1 https://github.com/systemd/systemd/issues/7074 Bug #878625 [systemd] systemd: NIS users login takes longtime. Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/7074'. -- 878625:

Bug#878625: systemd: NIS users login takes longtime.

Control: forwarded -1 https://github.com/systemd/systemd/issues/7074 Am 15.10.2017 um 10:55 schrieb Elimar Riesebieter: > Package: systemd > Version: 235-2 > Severity: normal > > Login as a NIS user journalctl tells: > > systemd-logind[666]: do_ypcall: clnt_call: RPC: Unable to send; errno = >

systemd 235-2 MIGRATED to testing

FYI: The status of the systemd source package in Debian's testing distribution has changed. Previous version: 234-3 Current version: 235-2 -- 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#802211: RFC: wip patch to force sulogin on locked root accounts

On Thu, Oct 12, 2017 at 7:07 PM, Stijn van Drongelen wrote: > Hi, > >> TL;DR... > > Yes, I knew about that risk. But shorter messages have failed to draw > attention to a supposedly "important" bug. > > I expected that the original patch was good to go, but I somehow forgot >

Processed: Re: Problem persists

Processing commands for cont...@bugs.debian.org: > reopen 764557 Bug #764557 {Done: Michael Biebl } [systemd] "Persistent journal gets corrupted" Bug reopened Ignoring request to alter fixed versions of bug #764557 to the same values previously set > thanks Stopping processing

Bug#878625: systemd: NIS users login takes longtime.

* Elimar Riesebieter [2017-10-15 10:55 +0200]: > Package: systemd > Version: 235-2 > Severity: normal > > Login as a NIS user journalctl tells: > > systemd-logind[666]: do_ypcall: clnt_call: RPC: Unable to send; errno = > Operation not permitted >

Bug#878590: systemd: jessie to stretch upgrade resulted in eth0 being given a new style predictable name (enp1s9)

Package: systemd Version: 232-25+deb9u1 Severity: important Hi, After upgrading to Stretch, the system came up with its NIC named as enp1s9, and thus had no working network (since eth0 was configured in /etc/network/interfaces), requiring me to get console access to fix things. I suspect that

Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

Control: reassign -1 alsa-utils The same changes should also be applied to /lib/systemd/system/alsa-restore.service /etc/init.d/alsa-utils ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

Processed: Re: Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

Processing control commands: > reassign -1 alsa-utils Bug #878401 [systemd] [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount) Bug reassigned from package 'systemd' to 'alsa-utils'. No longer marked as found in versions

Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

On 10/13/17 09:27, Felipe Sateler wrote: > On Fri, Oct 13, 2017 at 9:58 AM, Antonio Russo > wrote: >> On 10/13/17 07:30, Michael Biebl wrote: >>> >>> That seems like the wrong approach. sound.target does not have any >>> dependencies on /tmp. >>> If anything, it's

Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

On Fri, Oct 13, 2017 at 9:58 AM, Antonio Russo wrote: > On 10/13/17 07:30, Michael Biebl wrote: >> >> That seems like the wrong approach. sound.target does not have any >> dependencies on /tmp. >> If anything, it's pulseaudio which should ensure that /tmp is mounted. >

Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

On 10/13/17 07:30, Michael Biebl wrote: > > That seems like the wrong approach. sound.target does not have any > dependencies on /tmp. > If anything, it's pulseaudio which should ensure that /tmp is mounted. I agree, wholeheartedly. But getting this directory out of /tmp has been a bug for 7

Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

On Fri, Oct 13, 2017 at 8:30 AM, Michael Biebl wrote: > Control: tags -1 moreinfo > > On Fri, 13 Oct 2017 07:21:18 -0400 Antonio Russo > wrote: >> Package: systemd >> Version: 234-3 >> Severity: normal >> >> --- Please enter the report below this

Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

Control: tags -1 moreinfo On Fri, 13 Oct 2017 07:21:18 -0400 Antonio Russo wrote: > Package: systemd > Version: 234-3 > Severity: normal > > --- Please enter the report below this line. --- > I mount a filesystem over /tmp in /etc/fstab, but if I take a peek

Processed: Re: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

Processing control commands: > tags -1 moreinfo Bug #878401 [systemd] [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount) Added tag(s) moreinfo. -- 878401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878401 Debian

Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)

Package: systemd Version: 234-3 Severity: normal --- Please enter the report below this line. --- I mount a filesystem over /tmp in /etc/fstab, but if I take a peek underneath, > # mount --bind / /mnt > # cd /mnt > # ls -la > total 16 > drwxrwxrwt 4 root root 4096 Oct 13 01:46 ./ > drwxr-xr-x

Bug#856415: marked as done (-n (dry-run) seems to be broken completely)

Your message dated Fri, 13 Oct 2017 00:04:02 + with message-id and subject line Bug#856415: fixed in init-system-helpers 1.50 has caused the Debian Bug report #856415, regarding -n (dry-run) seems to be broken completely to be marked as done. This means

Bug#873789: marked as done (init-system-helpers: autopkgtests broken in 1.49)

Your message dated Fri, 13 Oct 2017 00:04:02 + with message-id and subject line Bug#873789: fixed in init-system-helpers 1.50 has caused the Debian Bug report #873789, regarding init-system-helpers: autopkgtests broken in 1.49 to be marked as done. This

Bug#857452: marked as done (update-rc.d: please provide a defaults-disabled option)

Your message dated Fri, 13 Oct 2017 00:04:02 + with message-id and subject line Bug#857452: fixed in init-system-helpers 1.50 has caused the Debian Bug report #857452, regarding update-rc.d: please provide a defaults-disabled option to be marked as done.

init-system-helpers_1.50_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 12 Oct 2017 20:16:13 -0300 Source: init-system-helpers Binary: init-system-helpers init Architecture: source Version: 1.50 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers

Processing of init-system-helpers_1.50_source.changes

init-system-helpers_1.50_source.changes uploaded successfully to localhost along with the files: init-system-helpers_1.50.dsc init-system-helpers_1.50.tar.xz init-system-helpers_1.50_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#802211: RFC: wip patch to force sulogin on locked root accounts

Hi, > TL;DR... Yes, I knew about that risk. But shorter messages have failed to draw attention to a supposedly "important" bug. I expected that the original patch was good to go, but I somehow forgot that a 720+ day old patch is subject to bitrot. Please correct me if I'm wrong, but wouldn't we

Bug#802211: RFC: wip patch to force sulogin on locked root accounts

Hi all, On Thu, Oct 12, 2017 at 9:21 AM, Andreas Henriksson wrote: > Hello, > > I'm attaching a completely untested patch against systemd packaging git. > > @Stijn van Drongelen : > Maybe you can offer to test it (and maybe even finish it up)? > > (Please note how I

Bug#802211: RFC: wip patch to force sulogin on locked root accounts

Hello, I'm attaching a completely untested patch against systemd packaging git. @Stijn van Drongelen : Maybe you can offer to test it (and maybe even finish it up)? (Please note how I *intentionally* isn't setting a patch tag since the patch is both untested and *unfinished*. This is mostly a

Processed: Re: Please, just patch rescue.service and emergency.service

Processing control commands: > tags -1 - patch Bug #802211 [systemd] systemd: rescue.service fails if root password is not set, needs sulogin --force Bug #806852 [systemd] systemd: rescue.service fails if root password is not set, needs sulogin --force Removed tag(s) patch. Removed tag(s)

Bug#802211: Please, just patch rescue.service and emergency.service

Control: tags -1 - patch Hello, The patch supplied with the initial bug report is definitely flawed, no matter how you view this. I'm thus removing the patch tag. On Wed, Oct 11, 2017 at 04:22:51PM +, Stijn van Drongelen wrote: TL;DR If you want to see this fixed, please focus on

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

Michael Biebl [2017-10-11 18:47 +0200]: > I don't systemd-journal-gateway creates any systemd-journal-gateway > owned files. That said, if we want to remove the system user account, we > probably need to add a systemctl try-restart > systemd-journal-gatewayd.service before the deluser call so we

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

Am 10.10.2017 um 22:03 schrieb Felipe Sateler: > Package: systemd-journal-remote > Version: 235-1 > Severity: normal > > Since systemd 235, systemd-journal-gateway has DynamicUsers=yes. This > means there is no longer need to allocate a static UID for it. > I have not checked if it is safe to

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

Am 10.10.2017 um 21:59 schrieb Felipe Sateler: > Package: systemd > Version: 234-3 > Severity: normal > > Systemd is still creating in postinst the systemd-bus-proxy user. That > user is no longer used upstream as all kdbus code was removed. > > The user should no longer be created. It appears

Bug#802211: Please, just patch rescue.service and emergency.service

Hi everyone, I obviously posted my ranty +1 to the wrong bugreport (#806852) and didn't read this one thoroughly enough. My apologies for the noise. In short: Marga Manterola is completely right about Michael Biebl's example being convoluted. I might be wrong here, but I get the impression that

Bug#763601: systemd: booting is extremely slow depending on order of "console" arguments to kernel

Hello, I have the same problem on my jessie machine. The only difference is, that in contrast to Sven, I get the serial getty after booting was finished, but no status lines on the serial console during the boot process, after changing GRUB_CMDLINE_LINUX="console=tty0

Processed: closing 770135

Processing commands for cont...@bugs.debian.org: > close 770135 Bug #770135 [systemd] systemd: ssh logins considerably delayed (until PAM timeout) when systemd is upgraded but the system not rebooted Bug #793814 [systemd] systemd-logind: Logins via ssh and su are delayed by 25 seconds Bug

Bug#770135: systemd: ssh logins considerably delayed (until PAM timeout) since 215-6

Am 11.10.2017 um 14:19 schrieb Christoph Anton Mitterer: > Hey Michael. > > > On Tue, 2017-10-10 at 18:49 +0200, Michael Biebl wrote: >> Is this issue still reproducible with a recent version from stretch >> or >> buster? I failed to reproduce it myself with a stretch VM. > > At least I haven't

Bug#770135: systemd: ssh logins considerably delayed (until PAM timeout) since 215-6

Hey Michael. On Tue, 2017-10-10 at 18:49 +0200, Michael Biebl wrote: > Is this issue still reproducible with a recent version from stretch > or > buster? I failed to reproduce it myself with a stretch VM. At least I haven't encountered it anymore since ages. I did once or twice (even with the

Bug#794744: systemd-logind: Lid closed event does not suspend

Michael Biebl writes: > Is this problem still reproducible with a recent version of systemd? Sorry, I can't even remember making this report now. Stretch seems fine. Please close it. -- Brian May ___

Bug#747629: Problem still exists in systemd 234-3

Hi. I just encountered this bug. I'm using systemd 234-3 on a fresh install. The advice here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747629#15 worked for me. Cheers, --Dave ___ Pkg-systemd-maintainers mailing list

systemd_235-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 11 Oct 2017 00:46:07 +0200 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

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

Package: systemd Version: 234-3 Severity: normal Systemd is still creating in postinst the systemd-bus-proxy user. That user is no longer used upstream as all kdbus code was removed. The user should no longer be created. It appears (but I haven't checked) that it is safe to remove the user on

Processed: closing 778378

Processing commands for cont...@bugs.debian.org: > close 778378 Bug #778378 [systemd] systemd: Mounts inconsistent rootfs read-write Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 778378:

Bug#764557: marked as done ("Persistent journal gets corrupted")

Your message dated Tue, 10 Oct 2017 18:51:33 +0200 with message-id and subject line Re: Problem persists has caused the Debian Bug report #764557, regarding "Persistent journal gets corrupted" to be marked as done. This means that you claim that

Bug#870638: marked as done (systemd: /var/log/btmp has inconsistent permissions)

Your message dated Tue, 10 Oct 2017 16:48:47 + with message-id and subject line Bug#870638: fixed in systemd 235-1 has caused the Debian Bug report #870638, regarding systemd: /var/log/btmp has inconsistent permissions to be marked as done. This means

Bug#867902: marked as done (systemd: don't try to execute non-executables under /lib/systemd/system-sleep/)

Your message dated Tue, 10 Oct 2017 16:48:47 + with message-id and subject line Bug#867902: fixed in systemd 235-1 has caused the Debian Bug report #867902, regarding systemd: don't try to execute non-executables under /lib/systemd/system-sleep/ to be

Bug#865450: marked as done (systemd: tmpfs size mount option ignored when expressed in %)

Your message dated Tue, 10 Oct 2017 16:48:47 + with message-id and subject line Bug#865450: fixed in systemd 235-1 has caused the Debian Bug report #865450, regarding systemd: tmpfs size mount option ignored when expressed in % to be marked as done. This

Bug#852534: marked as done (systemd: cryptsetup-generator does not support LUKS on network devices)

Your message dated Tue, 10 Oct 2017 16:48:46 + with message-id and subject line Bug#852534: fixed in systemd 235-1 has caused the Debian Bug report #852534, regarding systemd: cryptsetup-generator does not support LUKS on network devices to be marked as

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