Bug#895292: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

[Michael Biebl]

Am 10.04.2018 um 02:15 schrieb Vincent Lefevre:
> On 2018-04-09 20:41:55 +0200, Michael Biebl wrote:
>> Not reproducible with a default GNOME / systemd as init installation.
>>
>> Please investigate, if this issue is specific to sysvinit, xfce or some
>> other custom modification (like special kernel parameters)
> 
> I'd say that it is specific to sysvinit. I have two other machines
> with similar configuration but with systemd as the init system instead
> of sysvinit, and I haven't seen any such problem on them.
> 
> The only other major difference between my machines is that the one
> with sysvinit uses the nouveau driver instead of the nvidia one for
> the two other machines, but I doubt very much that this has an
> influence.

Do you use hidepid for /proc?


> Apr  9 15:33:25 ypig dbus-daemon[2930]: [system] Successfully activated 
> service 'org.freedesktop.ConsoleKit'

Please uninstall/purge consolekit. It's not only useless when logind is
used, but actively harmful:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#895292: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

[Michael Biebl]

Control: severity -1 normal
Control: tags -1 moreinfo unreproducible

Am 09.04.2018 um 16:22 schrieb Vincent Lefevre:
> Control: reassign -1 systemd 238-4
> Control: retitle -1 Restart, Suspend, Hibernate, Shut Down all greyed out in 
> lightdm
> 
> On 2018-04-09 15:10:47 +0200, Vincent Lefevre wrote:
>> After the upgrade to policykit-1 0.105-20, the Restart, Suspend,
>> Hibernate, Shut Down menu entries are all greyed out.
>>
>> Note: lightdm and lightdm-gtk-greeter have not changed.
> 
> This is actually an issue due to the upgrade of systemd from 237-4
> to 238-4, from a previous upgrade (I thought that 238-4 was OK, but
> I now remember that I didn't test after the previous upgrade due to
> a freeze of the X server in lightdm).

Not reproducible with a default GNOME / systemd as init installation.

Please investigate, if this issue is specific to sysvinit, xfce or some
other custom modification (like special kernel parameters)


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#894605: systemd: System fails to suspend.

[Michael Biebl]

Control: tags -1 + moreinfo

Am 02.04.2018 um 23:37 schrieb Michael Biebl:
> Am 02.04.2018 um 10:20 schrieb Hubert Golembiowski:
>> Package: systemd
>> Version: 238-3
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> Following issue observed:
>> - Select "Suspend" from UI or close laptop lid (closing lid is set to trigger
>> suspend)
>> - System doesn't suspend but instead:
>> - screen goes blank
>> - keyboard stops to take input
>> - pc is still running (fans, leds are on, etc.)
>> - The only way to get out if that state is hard reset
>> - This used to work without any problem, issue appeared 4-5 days ago
> 
> What happens if you run (as root)
> echo "mem" > /sys/power/state
> 
> Did you upgrade other packages the last couple of days, like say the
> kernel? Does the failure to suspend correlate with a certain package update?

Ping




signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#895239: [systemd] suspend works 1st time

[Michael Biebl]

Am 08.04.2018 um 19:56 schrieb Ted To:
> Package: systemd
> Version: 232-25+deb9u3
> Severity: important
> 
> --- Please enter the report below this line. ---
> 
> Suspend only works first time.  It worked fine on an ancient Acer Aspire
> One.  Now on an Acer S7 392, suspend works on its first try but
> afterwards fails.  Currently running the backports kernel but didn't
> work with stable either.

If you simply run (as root)
echo mem > /sys/power/state

can you suspend/resume multiple times?

If not, it's most likely a kernel problem and not a systemd problem.





signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

[Michael Biebl]

Am 05.04.2018 um 14:29 schrieb johnw:
> Hi Michael,
> 
> I found out, what cause the problem,
> I have this line in fstab
> "proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=2,gid=4   
> 0   0"
> 
> I changed it to
> "proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=2    0   0"
> (without gid=4), then the problem is gone.

https://github.com/systemd/systemd/issues/2941#issuecomment-213931080
might be relevant



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#894605: systemd: System fails to suspend.

[Michael Biebl]

Am 02.04.2018 um 10:20 schrieb Hubert Golembiowski:
> Package: systemd
> Version: 238-3
> Severity: normal
> 
> Dear Maintainer,
> 
> Following issue observed:
> - Select "Suspend" from UI or close laptop lid (closing lid is set to trigger
> suspend)
> - System doesn't suspend but instead:
> - screen goes blank
> - keyboard stops to take input
> - pc is still running (fans, leds are on, etc.)
> - The only way to get out if that state is hard reset
> - This used to work without any problem, issue appeared 4-5 days ago

What happens if you run (as root)
echo "mem" > /sys/power/state

Did you upgrade other packages the last couple of days, like say the
kernel? Does the failure to suspend correlate with a certain package update?
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#830230: systemd disable wake-on-lan

[Michael Biebl]

On Tue, 19 Jul 2016 17:39:40 +0200 Norbert Schulz
 wrote:
> 
> 
> Christian Hofstaedtler schrieb:
> > * Norbert Schulz  [160718 09:24]:
> >> Here are the required and some more information.
> > 
> > Thanks for following up on this. Unfortunately, I have no idea
> > either on what is happening here.
> > 
> Is there any possibility to get some output if I send a wake-on-lan packet 
> (with
> etherwake) to the ethernet card when the system is running?
> 

Is this still reproducible with an up-to-date stretch or sid system?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

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

[Michael Biebl]

On Wed, 17 Jan 2018 05:20:49 +0200 =?UTF-8?Q?Martin=2D=C3=89ric_Racine?=
<martin-eric.rac...@iki.fi> wrote:
> 2018-01-17 4:24 GMT+02:00 Michael Biebl <bi...@debian.org>:
> > 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:
> >> >>> 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. Maybe your issue is
> >> >>>> already fixed.
> >> >>>> If not, we'll have to involve upstream at some point by filing an
> >> >>>> upstream bug report. But let's first wait for your results with 236-1
> >> >>>
> >> >>> The issue is not fixed. Something fails at communicating with dbus,
> >> >>> and it messes up everything else.
> >> >>
> >> >> Just to be sure, have you rebooted your system after upgrading to 236-1?
> >> >
> >> > Yes I have, but this required issuing "exec reboot -f" to bypass init
> >> > entirely, otherwise it fails due to the lack of dbus connection.
> >>
> >> Sure, if PID 1 has crashed, it will freeze itself and no longer respond
> >> to any (D-Bus) requests.
> >>
> >> When exactly does systemd crash? Is it immediately during boot or after
> >> you've been using the system for a while?
> >> I assume it works at least for a while, otherwise no other services
> >> would be started and you would not be able to log in.
> >> When systemd crashes, you should get an entry in the kernel log (dmesg)
> >> respectively the journal.
> >>
> >> It would be great if you can follow the instructions at [1] to boot with
> >> debug logging enabled and then provide a journal log which shows such a
> >> crash.
> >>
> >
> > Any updates on this?
> 
> Not yet.  I just spent the last month or so giving interviews to the
> media.  Will get back to this ASAP.
> 

Ping

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 238-4 (source) into unstable

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 01 Apr 2018 13:02:57 +0200
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 238-4
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Changes:
 systemd (238-4) unstable; urgency=medium
 .
   [ Michael Biebl ]
   * udev/net-id: Fix check for address to keep interface names stable
   * debian/copyright: Move global wildcard section to the top
 .
   [ Martin Pitt ]
   * Fix daemon reload failures
 .
   [ Laurent Bigonville ]
   * Fix /sys/fs/cgroup mount when using SELinux.
 Since v236, all cgroups except /sys/fs/cgroup/systemd and
 /sys/fs/cgroup/unified are not mounted when SELinux is enabled (even in
 permissive mode). Disabling SELinux completely restores these cgroups.
 This patch fixes that issue by no longer making the assumption that those
 cgroups are mounted by initrd/dracut before systemd is started.
Checksums-Sha1:
 6358c18af5a705135ae2877bfcf37a6b7f09de66 4846 systemd_238-4.dsc
 2630234e544b0654f6304485c9941c4cf4bb2e26 139840 systemd_238-4.debian.tar.xz
 f6fee1a397fc488200ee342827d73fc98c88341f 9421 systemd_238-4_source.buildinfo
Checksums-Sha256:
 ce4d11ac2f1a1d4c0e06f031420bea2338eb39182a6cec78d90e53a6f599e792 4846 
systemd_238-4.dsc
 fd0353528020e4739b68fd7f68aca88df9fcd78cc78cd10e3d187b745a514846 139840 
systemd_238-4.debian.tar.xz
 954b1eb0652f833dbcd6957729a227ab814be57281f2df1438873bc0352b292e 9421 
systemd_238-4_source.buildinfo
Files:
 55f80c901de554d8b526b209a8053ada 4846 admin optional systemd_238-4.dsc
 94c745a6194a32b57233f9f72812197d 139840 admin optional 
systemd_238-4.debian.tar.xz
 3233bde4bf4c439e295cfcdc0e5b5d7c 9421 admin optional 
systemd_238-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlrAvdcACgkQauHfDWCP
ItxR9RAAlNVSgm7XOUQ/D0AioTXwMySu2FJr+x3hTUsU62VyWLpRDX7xGLFO7gfK
U/j3MBwkvZD0WjkFWh6u9gf/emeQIskQaocUhVNB59iMoymrxdmcud1QzLp4sP2r
wT3R7YPY3N+1Z1zvkgX5Bb9iHszzJAN9dCsVUWXNcYX9FCnILGMYjfRGKGOwsAIh
SjSkKUQHdJ4RJG9wrqL7fGyzWq/k1ZBagLbNuv+PDi/QmX+qTwc/R7/KuqdZsv6e
aZEWgGEzHNVvCb7l8xUAkhWGvJMW5aibsOMIVGORE+nXyQxTNvPB8Ms4m39drm44
4BLOYhWx84W13gPAfOyXtB9BYJouSxfYPXfqV+IyjnUapEHDIv8YLYmNr+FZoj9B
cM2CoqF/pZgUrpww+s3crhrWwLYRRf/wST6cS5Lsp2/gTuffXNV5EhbwmuCAre3F
RqLrjtn2TqCSTyShfaqcfb1FeMCphTcOcMJOkUkpAXsMhSXPyRtAjpMYmUSH942S
QyT7GZN+HJcLe30JWs7wCo4cox0/ZN/WUmtpDb5Y+uIKPn+EENeNhB0+CP5uZycv
EjYWKRLq9xLM1z77JcRXcWIeBRa+vB0YuvtQRhUlEIQncuLSw/qjPZU76TK1CkGY
mhnK99RB/XMeTPPBnzcSkBIm7GFPv6WgHXOXZ4jhBv3Jcs6uz5I=
=h/XJ
-END PGP SIGNATURE-


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#809069: logind sometimes blocks input to X after VT switch

[Michael Biebl]

Control: tags -1 + moreinfo

Am 09.03.2017 um 06:40 schrieb Michael Biebl:
> Hi Ben
> 
> On Sat, 26 Dec 2015 22:44:45 + Ben Hutchings <b...@decadent.org.uk>
> wrote:
>> Package: systemd
>> Version: 228-2
>> Severity: important
>>
>> After switching between a text console (VT 1) and X (VT 7) a few
>> times, I found that keyboard and mouse input no longer worked in X.
>> The system log showed this:
>>
>> [switching to VT 1]
>>
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) AIGLX: 
>> Suspending AIGLX clients for VT switch
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 226:0
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:69
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:64
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:66
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:72
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:65
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:68
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:71
>>
>> [switching to VT 7]
>>
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 226:0
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) AIGLX: 
>> Resuming AIGLX clients after VT switch
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) intel(0): 
>> switch to mode 1600x900@60.0 on LVDS1 using pipe 0, position (0, 0), 
>> rotation normal, reflection none
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:69
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:64
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:66
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: The XKEYBOARD 
>> keymap compiler (xkbcomp) reports:
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Meta_R added to symbol map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Meta_L added to symbol map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Key  added to map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: Errors from 
>> xkbcomp are not fatal to the X server
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:72
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: The XKEYBOARD 
>> keymap compiler (xkbcomp) reports:
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Meta_R added to symbol map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Meta_L added to symbol map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Key  added to map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: Errors from 
>> xkbcomp are not fatal to the X server
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:65
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (--) synaptics: 
>> SynPS/2 Synaptics TouchPad: touchpad found

Accepted systemd 232-25+deb9u3 (source) into proposed-updates->stable-new, proposed-updates

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Mar 2018 13:55:43 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-25+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 892794
Changes:
 systemd (232-25+deb9u3) stretch; urgency=medium
 .
   [ Cyril Brulebois ]
   * networkd-ndisc: Handle missing mtu gracefully.
 The previous upload made networkd respect the MTU field in IPv6 RA but
 unfortunately broke setups where there's no such field. (Closes: #892794)
Checksums-Sha1:
 e4226027323eca04a2e365a1b01c2334bdc67406 4797 systemd_232-25+deb9u3.dsc
 4bc17efc2f7190c93ef29ff691f409858a96a90c 208460 
systemd_232-25+deb9u3.debian.tar.xz
 09118a902f720e9e094e51cd23aa67ea32e63bc4 9789 
systemd_232-25+deb9u3_source.buildinfo
Checksums-Sha256:
 0e93ad29a9625e1ed964e949fc6deaa0a94c041a297311cd0c53ece9c00105f1 4797 
systemd_232-25+deb9u3.dsc
 534028b7bbe42ad1b02d2ca5a5ad5e9da4f5dcbf7cdd950cb31af57e6ff80809 208460 
systemd_232-25+deb9u3.debian.tar.xz
 b6f3ef51b3c946abe3b5865fbaa06638865a430868130de14652c6ee3706c4b6 9789 
systemd_232-25+deb9u3_source.buildinfo
Files:
 c772ab338389f4fafb0460f6ba606375 4797 admin optional systemd_232-25+deb9u3.dsc
 2b5ba81a6114e320df2746359b2c727c 208460 admin optional 
systemd_232-25+deb9u3.debian.tar.xz
 99c0c3a568abd0fcdcd1be1124f77dd1 9789 admin optional 
systemd_232-25+deb9u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlq5JwkACgkQauHfDWCP
ItxFUBAAmxduN7TZpFk1Bx9o14p9cattKbpfwp7HtPFFqKmwWQnsKK6HXHtte6FI
ZbNoF3r09rGkSLZPgjbdc+T+ld0+Wf7CfwaLDZfm+5Wjma7U/Mw99b6EeSmPmbjk
3vyG754FECIR85Ks+WDwNPHrK1liKgvt0Exql9uviDXbBYKlQ0akri1FUEEy5+ZP
/8evogkjO2VdKU2OG+Gx50KbRro6VnJkFXCdT0GIadPwyLxLuvnX46zTGJFgZerY
o8uaW44GbWaAllbVR6NyDWYUqq+oLiuwd2q53K+gESMwXGL41f91IQSzE0ped2wW
E0rBgTGWei73Gf81FD8a2Obe0/R9CF/g5ZwmTvT3kQ2w1i7TY+1ETEpS/E6pYvsx
wwNGuGU1UbY8nZIQUPAybP2nnvJuVREsNmNCS7hFM20Iq8mSSpk4tz/iBil788h6
oX5PpLrqs2ZZg/6nHSRDeo3tovB87HFo6L2TlNwtIGGtKK3p6ZTT2JFxcLcij9t/
mVwd5r3+XHq23vBflayf0MnG4kv4LD6gGcre8Cs+9HaUm1eFTE1G9s1wR0LWi1ge
x01CEWJtWVHcxGySgHkFw46EBpt6Y3NslwCb2NA/owXge2efNzaTVF6vsqaFbb8f
cEdcOyDV5gLnIv+nN9s9OMoWM/ouph1EMQV4TkgGnEVIZatFNCk=
=n6qy
-END PGP SIGNATURE-


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893574: closed by Simon McVittie <s...@debian.org> (Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if there is activity on a seat)

[Michael Biebl]

Control: reopen -1
Control: reassign -1 gnome-settings-daemon
Control: found -1 3.28.0-1

Am 27.03.2018 um 11:23 schrieb floris:
> Debian Bug Tracking System schreef op 2018-03-24 22:42:
>> This is an automatic notification regarding your Bug report
>> which was filed against the systemd package:
>>
>> #893574: gnome-shell: Suspend after 20 minutes even there is activity
>> on a seat
>>
>> It has been closed by Simon McVittie .
>>
>> Their explanation is attached below along with your original report.
>> If this explanation is unsatisfactory and you have not received a
>> better one in a separate message then please contact Simon McVittie
>>  by
>> replying to this email.
> 
> 
> Sorry, I cheered too early.
> 
> After some testing I think gsd-power from gnome-settings-daemon is
> monitoring the state of each seat, but fails to check if another one is
> still active
> (full log as attachment)
> 
> mrt 27 10:23:19 Jessica gsd-power[1568]: Starting power manager
> mrt 27 10:23:19 Jessica gsd-power[1568]: Registered client at path
> /org/gnome/SessionManager/Client17
> mrt 27 10:23:19 Jessica gsd-power[1568]: Adding suspend delay inhibitor
> 
> mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep callback 1200s
> <--- No user has a 20 minutes suspend setting in gnome-control-center
> power. Is this gdm3?

Check with systemd-cgls or pstree, which process group 1568 belongs to.

> mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep warning
> callback 96 msec
> mrt 27 10:23:19 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
> mrt 27 10:23:19 Jessica gsd-power[1568]: System inhibitor fd is 13
> mrt 27 10:25:20 Jessica gsd-power[1568]: disabling server builtin
> screensaver: (xset s 0 0; xset s blank; xset s expose)
> mrt 27 10:28:28 Jessica gsd-power[1568]: Received screensaver
> ActiveChanged signal: 1 (old: 0)
> mrt 27 10:28:28 Jessica gsd-power[1568]: setting up blank callback for 15s
> mrt 27 10:28:28 Jessica gsd-power[1568]: setting up sleep callback 1200s
> mrt 27 10:28:28 Jessica gsd-power[1568]: setting up sleep warning
> callback 96 msec
> mrt 27 10:28:28 Jessica gsd-power[1568]: Doing a state transition: blank
> mrt 27 10:28:28 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
> mrt 27 10:28:29 Jessica gsd-power[1568]: idletime watch: blank (3)
> mrt 27 10:28:29 Jessica gsd-power[1568]: Not going to 'less idle' mode
> blank (current: blank)
> mrt 27 10:39:18 Jessica gsd-power[1568]: idletime watch: sleep-warning (5)
> mrt 27 10:39:19 Jessica gsd-power[1568]: Doing a state transition: normal
> mrt 27 10:39:19 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
> mrt 27 10:39:34 Jessica gsd-power[1568]: Doing a state transition: blank
> mrt 27 10:39:34 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
> mrt 27 10:43:18 Jessica gsd-power[1568]: idletime watch: sleep (4)
> 
> mrt 27 10:43:18 Jessica gsd-power[1568]: Doing a state transition: sleep
> <-- Is gsd-power responsible for the sleep mode or only the messenger?
> 
> mrt 27 10:43:19 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
> mrt 27 10:43:19 Jessica gsd-power[1568]: Removing suspend delay inhibitor
> mrt 27 10:43:29 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
> mrt 27 10:43:29 Jessica gsd-power[1568]: Adding suspend delay inhibitor
> mrt 27 10:43:29 Jessica gsd-power[1568]: Doing a state transition: normal
> mrt 27 10:43:29 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
> mrt 27 10:43:29 Jessica gsd-power[1568]: System inhibitor fd is 14
> mrt 27 10:43:29 Jessica gsd-power[1568]: idletime reset
> 
> I hope someone can point me in the right direction to find the source.

I'm going to reopen and reassign this to gnome-settings-daemon (which
provides gsd-power)


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

[Michael Biebl]

> Mar 12 08:43:37 kvm102 slim[703]: pam_unix(slim:session): session opened for 
> user kaka by (uid=0)
> Mar 12 08:43:37 kvm102 slim[703]: pam_systemd(slim:session): Failed to create 
> session: No such process

Is see that the autopkgtest for logind fails as well:

> autopkgtest [12:38:29]: test logind: [---
>  * try-restarting systemd-logind
>  * daemon is started
>  * loginctl succeeds
>  * XDG_SESSION_ID=
> FAIL: process is not in session cgroup
> /proc/self/cgroup:
> 10:cpuset:/
> 9:cpu,cpuacct:/
> 8:freezer:/
> 7:memory:/
> 6:net_cls,net_prio:/
> 5:devices:/
> 4:pids:/
> 3:perf_event:/
> 2:blkio:/
> 1:name=systemd:/
> 0::/
>SESSIONUID USER SEAT TTY 
> 
> 0 sessions listed.
> Failed to get session path: Caller does not belong to any known session
> autopkgtest [12:38:29]: test logind: ---]
> autopkgtest [12:38:29]: test logind:  - - - - - - - - - - results - - - - - - 
> - - - -
> logind   FAIL non-zero exit status 1
> autopkgtest [12:38:29]: test logind:  - - - - - - - - - - stderr - - - - - - 
> - - - -
> Failed to get session path: Caller does not belong to any known session


https://ci.debian.net/packages/s/systemd/unstable/amd64/
https://ci.debian.net/data/autopkgtest/unstable/amd64/s/systemd/64305/log.gz

Martin, do you have any idea?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#810247: RE: Bug#810247: Hyper-V network adapters are mapped to a different interface (ethN) on every boot

[Michael Biebl]

On Sat, 9 Jan 2016 17:20:26 + Fernando Soto
 wrote:
> Hi Martin,
> 
> Udevadm output is attached.
> 
> Thank you,
> Fernando
> 
> > -Original Message-
> > From: Martin Pitt [mailto:mp...@debian.org]
> > Sent: Saturday, January 09, 2016 10:45 AM
> > To: Fernando Soto; 810...@bugs.debian.org
> > Subject: Re: Bug#810247: Hyper-V network adapters are mapped to a different
> > interface (ethN) on every boot
> > 
> > Control: tag -1 moreinfo
> > 
> > Fernando Soto [2016-01-08 15:22 +]:
> > > The persistent-net udev rules are not created in virtual environments to 
> > > avoid
> > issues with cloning/migrating VMs.
> > 
> > This was true with the old persistent names in Jessie and before, but not 
> > true any
> > more with current testing and unstable versions. See
> > /usr/share/doc/udev/README.Debian.gz.
> > 
> > Maybe the current ifnames system cannot figure out an appropriate name for
> > Hyper-V interfaces? 


P:
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_0_16/net/eth0
E:
DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_0_16/net/eth0
E: ID_NET_DRIVER=hv_netvsc
E: ID_NET_NAME_MAC=enx00155d0ae2ad
E: ID_OUI_FROM_DATABASE=Microsoft Corporation
E: ID_PATH=acpi-VMBUS:01
E: ID_PATH_TAG=acpi-VMBUS_01
E: IFINDEX=2
E: INTERFACE=eth0
E: MATCHDEVID=0x0
E: MATCHIFTYPE=1
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth0
E: TAGS=:systemd:
E: USEC_INITIALIZED=39002

Looks like this is the case.
I notice that there is

Author: Hannes Reinecke 
Date:   Fri Nov 23 14:12:39 2012 +0100

udev: path_id - handle Hyper-V devices

Hyper-V has an abstract bus, which gets renumbered on guest
startup. So instead of the bus numbers we should be using
the device GUIDs, which can be retrieved from the 'device_id'
sysfs attribute.


That doesn't seem to handle network interfaces though.

That said, this doesn't look like a Debian specific problem. So it's
probably best if you raise this upstream at
https://github.com/systemd/systemd

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

[Michael Biebl]

Control: tags -1 + moreinfo
On Mon, 19 Mar 2018 09:46:04 -0600 Jeff Ketchum  wrote:
> Second issue, I have trouble getting my system to boot reliably after the
> changes.
> It is using systemd:amd64

Ok, so what exactly is the failure then? Please describe it in more
detail. Maybe also provide a complete, verbose boot log [1].


Regards,
Michael
https://freedesktop.org/wiki/Software/systemd/Debugging/
[1]
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#875557: Info received (Bug#875557: systemd: service mark as enabled but not in reality)

[Michael Biebl]

hm, the email address bounces here:

>
>The mail system
>
> : host mx.cblue.be[193.104.37.23] said: 550 Unrouteable
> address (in reply to RCPT TO command)
>
>
>
> Reporting-MTA: dns; dd17218.kasserver.com
> X-Postfix-Queue-ID: A90216801856
> X-Postfix-Sender: rfc822; bi...@debian.org
> Arrival-Date: Fri, 23 Mar 2018 17:12:34 +0100 (CET)
>
> Final-Recipient: rfc822; sth...@cblue.be
> Original-Recipient: rfc822;sth...@cblue.be
> Action: failed
> Status: 5.0.0
> Remote-MTA: dns; mx.cblue.be
> Diagnostic-Code: smtp; 550 Unrouteable address
>


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#875557: systemd: service mark as enabled but not in reality

[Michael Biebl]

Control: tags -1 + moreinfo

On Tue, 12 Sep 2017 10:08:49 +0200 Michael Biebl <bi...@debian.org> wrote:
> Am 12.09.2017 um 09:45 schrieb sthiry:
> > Package: systemd
> > Version: 232-25+deb9u1
> > Severity: normal
> > 
> > Hello,
> > 
> > I use multiple php-fpm process to run apache websites and I have to create 
> > one process by site, so I have a service file named php7-fpm@.service. It 
> > let me create service like this php7-fpm@mysite that 
> > I have to enable once it is created. So I notice that when I enable one 
> > service, the others are mark as enabled when I type "service php7-fpm* 
> > status", but they are not enabled. So you have to enable all
> > services.
> 
> Can you please include the full service file you are using and the
> output of the commands.

Would be great, if you can provide the requested information.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#803524: journalctl too slow

[Michael Biebl]

Control: tags -1 + moreinfo

On Sat, 31 Oct 2015 01:46:59 +0100 Christoph Egger
 wrote:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
> File: /bin/journalctl
> 
> Hi!
> 
> `journalctl -u nsd.service` just takes 10 minutes (!) cpu time to
> scrol to the newest entries. I'd call that too much for something
> that's supposed to replace a `grep nsd /var/log/syslog`

Is this still reproducible with a recent version of systemd?

Is this with persistent journal enabled? If so,
- how big is /var/log/journal?
- does journalctl --verify report any errors?
- is the problem reproducible after removing existing journal files?

Fwiw, if you are interested in the newest journal entries, journalctl
now provides a -r switch, ie. it shows the newest entries first.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

[Michael Biebl]

On Wed, 21 Mar 2018 16:16:40 +0800 johnw  wrote:
> After upgrade systemd to 238-3, I still have this problem :(
> Any one?
> Help, please.

Does it work if you switch to a different display manager, like say
lightdm (which IIRC is the preferred one of xfce). Might be a problem
specific to slim, since I don't see any such issues myself here (using
GNOME/gdm).

Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893866: stretch-pu: package systemd/232-25+deb9u3

[Michael Biebl]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi,

we already briefly discussed this via IRC on #debian-release.

The last stable upload of systemd introduced a rather nasty regression
in networkd, which broke IPv6 support for lots of users.

KiBi was so kind to dig out the relevant upstream commit which fixes
this and got confirmation from the bug reporter(s) that with this patch
applied, networkd behaves properly. I thus would like to get this
update into stable as quickly as possible.

Here's the changelog, debdiff is attached:

systemd (232-25+deb9u3) stretch; urgency=medium

  [ Cyril Brulebois ]
  * networkd-ndisc: Handle missing mtu gracefully.
The previous upload made networkd respect the MTU field in IPv6 RA but
unfortunately broke setups where there's no such field. (Closes: #892794)

 -- Michael Biebl <bi...@debian.org>  Fri, 23 Mar 2018 13:55:43 +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.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index e7b7ff1..1117655 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+systemd (232-25+deb9u3) stretch; urgency=medium
+
+  [ Cyril Brulebois ]
+  * networkd-ndisc: Handle missing mtu gracefully.
+The previous upload made networkd respect the MTU field in IPv6 RA but
+unfortunately broke setups where there's no such field. (Closes: #892794)
+
+ -- Michael Biebl <bi...@debian.org>  Fri, 23 Mar 2018 13:55:43 +0100
+
 systemd (232-25+deb9u2) stretch; urgency=medium
 
   * networkd: Handle MTU field in IPv6 RA (Closes: #878162)
diff --git 
a/debian/patches/networkd-ndisc-handle-missing-mtu-gracefully-4913.patch 
b/debian/patches/networkd-ndisc-handle-missing-mtu-gracefully-4913.patch
new file mode 100644
index 000..59d6808
--- /dev/null
+++ b/debian/patches/networkd-ndisc-handle-missing-mtu-gracefully-4913.patch
@@ -0,0 +1,28 @@
+From: =?utf-8?q?J=C3=B6rg_Thalheim?= <jo...@higgsboson.tk>
+Date: Mon, 19 Dec 2016 15:34:07 +0100
+Subject: networkd-ndisc: handle missing mtu gracefully (#4913)
+
+At least bird's implementation of router advertisement does not
+set MTU option by default (instead it supplies an option to the user).
+In this case just leave MTU as it is.
+
+(cherry picked from commit 29b5ad083a6925efec8e188013d1298742e0baaa)
+---
+ src/network/networkd-ndisc.c | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/src/network/networkd-ndisc.c b/src/network/networkd-ndisc.c
+index 9cfdf01..d3fa56b 100644
+--- a/src/network/networkd-ndisc.c
 b/src/network/networkd-ndisc.c
+@@ -117,7 +117,9 @@ static void ndisc_router_process_default(Link *link, 
sd_ndisc_router *rt) {
+ }
+ 
+ r = sd_ndisc_router_get_mtu(rt, );
+-if (r < 0) {
++if (r == -ENODATA)
++mtu = 0;
++else if (r < 0) {
+ log_link_warning_errno(link, r, "Failed to get default router 
MTU from RA: %m");
+ return;
+ }
diff --git a/debian/patches/series b/debian/patches/series
index 3f93454..2866963 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -78,6 +78,7 @@ networkd-handle-MTU-field-in-IPv6-RA-4719.patch
 shared-Add-a-linker-script-so-that-all-functions-are-tagg.patch
 resolved-fix-loop-on-packets-with-pseudo-dns-types.patch
 machinectl-don-t-output-No-machines.-with-no-legend-optio.patch
+networkd-ndisc-handle-missing-mtu-gracefully-4913.patch
 debian/Use-Debian-specific-config-files.patch
 debian/don-t-try-to-start-autovt-units-when-not-running-wit.patch
 debian/Make-logind-hostnamed-localed-timedated-D-Bus-activa.patch
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893605: warning: #warning "Consider adding the right mmap() syscall definitions here!" [-Wcpp]

[Michael Biebl]

Am 22.03.2018 um 12:31 schrieb James Cowgill:
> I sent a patch upstream (see above).

Thanks!

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 22.03.2018 um 10:24 schrieb LEDUQUE Mickaël:
> Ah yes.
> I'm not sure you'll get much more from my system and logs now, can I
> install systemd:amd64 back now ?

Please go ahead and install systemd:amd64 again.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 19.03.2018 um 16:36 schrieb LEDUQUE Mickaël:
> Start-Date: 2018-03-15  09:28:21
> Commandline: apt dist-upgrade

[..]

> Remove: bundler:amd64 (1.15.1-1), systemd:amd64 (237-4),
> ruby-bundler:amd64 (1.15.1-1)
> End-Date: 2018-03-15  09:28:29
> 
> Also it seems at some point I had systemd:amd64 237-4 and many other
> packages as 238-2.
> Strangely I find no mention of removing system:amd64 even though

See above: Remove: ...  systemd:amd64 (237-4)

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893369: 893369

[Michael Biebl]

Am 21.03.2018 um 14:47 schrieb Michael Biebl:
> Am 21.03.2018 um 13:18 schrieb Felix Defrance:
> 
>> Start-Date: 2018-03-20  14:02:40
>> Commandline: apt full-upgrade
>> Requested-By: fdef (1000)
>> Install: libpam0g:i386 (1.1.8-3.7, automatic), libdevmapper1.02.1:i386
>> (2:1.02.145-4.1, automatic), libseccomp2:i386 (2.3.1-2.1, automatic),
>> gir1.2-mutter-2:amd64 (3.28.0-1, automatic), libargon2-0:i386
>> (0~20161029-1.1, automatic), libacl1:i386 (2.2.52-3+b1, automatic),
>> libkmod2:i386 (25-1, automatic), libmutter-2-0:amd64 (3.28.0-1,
>> automatic), libapparmor1:i386 (2.12-3, automatic), libattr1:i386
>> (1:2.4.47-2+b2, automatic), libpam-systemd:i386 (238-2, automatic),
>> systemd:i386 (238-2, automatic), libcap-ng0:i386 (0.7.7-3.1+b1,
> 
> [..]
> 
>> Remove: systemd:amd64 (237-4)

Felix, are you using sid or buster


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893369: 893369

[Michael Biebl]

Am 21.03.2018 um 13:18 schrieb Felix Defrance:

> Start-Date: 2018-03-20  14:02:40
> Commandline: apt full-upgrade
> Requested-By: fdef (1000)
> Install: libpam0g:i386 (1.1.8-3.7, automatic), libdevmapper1.02.1:i386
> (2:1.02.145-4.1, automatic), libseccomp2:i386 (2.3.1-2.1, automatic),
> gir1.2-mutter-2:amd64 (3.28.0-1, automatic), libargon2-0:i386
> (0~20161029-1.1, automatic), libacl1:i386 (2.2.52-3+b1, automatic),
> libkmod2:i386 (25-1, automatic), libmutter-2-0:amd64 (3.28.0-1,
> automatic), libapparmor1:i386 (2.12-3, automatic), libattr1:i386
> (1:2.4.47-2+b2, automatic), libpam-systemd:i386 (238-2, automatic),
> systemd:i386 (238-2, automatic), libcap-ng0:i386 (0.7.7-3.1+b1,

[..]

> Remove: systemd:amd64 (237-4)

Be careful with full-upgrade, it does potentially bad things like in
this case replacing systemd:amd64 with systemd:i386 and always
double-check what it is going to do. For normal operation, apt upgrade
is safer, especially for sid, where packages can be temporarily not
installable. Still curious, why apt decided to do that in this case.

To fix your breakage, please switch systemd back to your native
architectue by running

apt install systemd:amd64


Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 238-3 (source) into unstable

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Mar 2018 23:22:57 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 238-3
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 881769 888126 893282 893426
Changes:
 systemd (238-3) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * Enable systemd-sysusers unit and provide correct Debian static u/gids.
 Add a helper script debian/extra/make-sysusers-basic which generates a
 sysusers.d(5) file from Debian's static master passwd/group files.
 systemd 238 now supports  specifying different uid and gid and a
 non-default login shell, so this is possible now. (Closes: #888126)
   * udev README.Debian: Include initrd rebuild and some clarifications in
 migration.
 While initrd update is already being mentioned in the introductory
 section, it is easy to miss when going through the migration steps, so
 explicitly mention it again. Also add a warning about keeping a fallback
 on misconfigurations, and the possibility to migrate one interface at a
 time.
 Thanks to Karl O. Pinc for the suggestions! (Closes: #881769)
 .
   [ Michael Biebl ]
   * basic/macros: Rename noreturn into _noreturn_.
 "noreturn" is reserved and can be used in other header files we include.
 (Closes: #893426)
   * units: Fix SuccessAction that belongs to [Unit] section not [Service]
 section (Closes: #893282)
Checksums-Sha1:
 8899f8ea14335bf5444e4fe7021157a25e9cc097 4846 systemd_238-3.dsc
 e865b02eb54e2166d2fcd3533f5ea71d55a260f2 137192 systemd_238-3.debian.tar.xz
 7d41d9b479880eeab846186cc093e2947e222d1c 9386 systemd_238-3_source.buildinfo
Checksums-Sha256:
 bce6925b0f8e34625df4fc295bb851e6f8fe7d31da4fd598640efe69a9d93066 4846 
systemd_238-3.dsc
 1512abbb4b9b72a90a609bbc8535694d84e1b4e575e5609b6a39edf4e9eb2252 137192 
systemd_238-3.debian.tar.xz
 19fe0be4f73ebaa30f3d00da07b599be410fcda79047b80621e7e21307933e82 9386 
systemd_238-3_source.buildinfo
Files:
 cd368aab72d22495aed38b1e9e40a98d 4846 admin optional systemd_238-3.dsc
 6343673a01667f6601c46635eadafc7b 137192 admin optional 
systemd_238-3.debian.tar.xz
 6394742c97ac03cedaceb6520baac486 9386 admin optional 
systemd_238-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlqxjjcACgkQauHfDWCP
Itw4hg//RQZMGPHtG1y1LyyQQr1JY1OdDYtZF8m4e7WqUyH/Hoj3C4qUBYlz9Osw
GgUQ5l+ggWtQiZi3ALIbBBIzuM+HQHpUMzFOgVm6LCxwBJUosCakK6BuXsF8Gx8A
4MbxORg105Gmt2QWYXm0/8bXHDVruGBbEsRXSrs/InEB/M3Y18575BbPaHEZ4jXO
tS+d6osjLElQNAF/6G90mAwdNlVEoG74N6THnrllYOjT/BJHDa4x51frO0oja4qx
VRYt5II6bjLCRlPTDvC7huwGsce3wuP64hO6+QGXuh197dONCcFRPyxXy8SBs+0W
aEDUbMuBhpwFtAbAvBxiArF7HSpjtFtSIwCgh+eEOqnJjr1b5ifP2ypSDhCCXqOh
9LIIG9XNPXkmd5Zp3rbYRlbZqTYFZvXpv7iox+Tw8iCCPH85IH+r8iVjY6B7Chyi
LhKna5puIrUUm8sgs3yW+V+Qtj2NnP2MpspDMI/3Evgz5cxJqfcA12s7Q2XT2wET
Pg0otCe8AvYLRfWG0vpKyL6MJWZO26Ov71x0JASaGsFTZkoYXkwZZ/8nxAiRvFCZ
NjTjiSSgdm6txIRp/lXWISKqfewIKDXOzF3+JlWa/Ys/h41KeYchTqfIEWJ/R2/G
7kT1Q/4eKFKPBCIKKIdMSUaJzpOb7XiJ0vcY21XTuunGl30w5dc=
=u70W
-END PGP SIGNATURE-


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893602: macro.h:423:18: error: expected ')' before '__attribute__'

[Michael Biebl]

Control: forcemerge 893426 -1

On Tue, 20 Mar 2018 11:32:52 +0100 Mathieu Malaterre 
wrote:

> ../src/basic/macro.h:423:18: error: expected ')' before '__attribute__'
>  #define noreturn __attribute__((noreturn))
   ^

Duplicate of #893426

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#883690: Buck-passing

[Michael Biebl]

Control: tags -1 moreinfo

On Wed, 20 Dec 2017 11:10:18 +0100 (CET) Jan Fuchs  wrote:
> Hello Michael,
> 
> After recompile systemd with patch in attachement then every boot is success

I've forwarded this issue upstream,
see https://github.com/systemd/systemd/issues/8483

It was closed though. Quoting from
https://github.com/systemd/systemd/issues/8483#issuecomment-374271819

"I don't think the code should be changed at least until the original
bug reporter clarifies why /proc/self was semi-functional."

Can you clarify why your /proc/self is semi-functional?

The issue itself is not reproducible on a regular Debian installation.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 19.03.2018 um 09:51 schrieb LEDUQUE Mickaël:
> You're right, but honestly, I have no idea how this happened :
> 
> $ dpkg -l systemd
> Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
> |
> État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
> |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
> ||/ Nom  
> Version  
> Architecture  Description
> +++-=-=-=-===
> ii  systemd:i386 
> 238-2
> i386  system and service manager

I have no idea how this happened either and why apt decided to replace
systemd:amd64 with systemd:i386 on an amd64 system.
But apparently you are not the only one,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893054 sounds like the
user ran into a similar problem.

Do you still have the apt logs (check /var/log/apt) which show the
installation of systemd:i386 and removal of systemd:amd64?

Julian, do you have an idea why something like this can happen?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#883569: libpam-systemd: Prefer systemd-sysv over systemd-shim

[Michael Biebl]

On Thu, 8 Mar 2018 12:47:22 +0100 Martin Pitt <mp...@debian.org> wrote:
> Hello Michael,
> 
> Michael Biebl [2018-03-08 12:16 +0100]:
> > Am 08.03.2018 um 09:22 schrieb Martin Pitt:
> > There is one case: someone installs a minimal system without
> > libpam-systemd, then switches to sysvinit-core, then installs a desktop
> > environment which pulls libpam-systemd (via polkit in most cases). In
> > that specific scenario, apt will uninstall sysvinit-core and install
> > systemd-sysv again.
> 
> Good point. The same in the other direction (install minimal system, then a
> desktop which pulls in libpam-systemd) ought to be satisfied with the already
> installed systemd-sysv, so that should work (modulo apt getting confused).
> 
> > Is this something the TC has considered and is ok with?
> 
> I don't think they considered this at all. They simply said that there is no
> longer an ordering requirement from their side, and it's back to us
> maintainer's consideration.

So, what are we going to do now then?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

[Michael Biebl]

Am 15.03.2018 um 23:31 schrieb Jeff Ketchum:
> I upgraded systemd, and after a failure to boot, realized it was on
> systemd:i386.
> I went into a recovery environment and removed systemd:i386 and
> installed systemd.
> After that It failed to boot at a different location.
> I was able to get it to boot by removing the kernel parameter
> for the nouveau driver to use the binary firmware.

Just to be clear: What is this bug report about?
About the first issue, where systemd:i386 was installed on a amd64
system (and you probably ran into #869719)
or the second issue? The log you posted, is that with systemd:amd64 or
systemd:i386?
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893426: Processed: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Michael Biebl]

Control: tags -1 fixed-upstream patch
Control: forwarded -1 https://github.com/systemd/systemd/pull/8456

Fixed upstream by
https://github.com/systemd/systemd/commit/848e863acc51ecfb0f3955c498874588201d9130



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 18.03.2018 um 22:41 schrieb LEDUQUE Mickaël:
> No I don't think I have one
> dpkg -l udev only shows udev and64

what about systemd? i386 or amd64


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël:
> Looks like commenting out
> 
> SystemCallArchitectures=native
> 
> fixes  the issue.

Does that mean you have a udev:i386 installed on a amd64 system?



If so, that would basically be a duplicate of #869719


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Michael Biebl]

Control: reassign -1 libgpg-error-dev
Control: found -1 1.28-1
Control: affects -1 + systemd

Am 18.03.2018 um 19:54 schrieb Helmut Grohne:
> Package: systemd
> Version: 238-2
> Severity: serious
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> systemd fails to build from source on amd64. Here is a tail of the build
> log.
> 
> | FAILED: journal-core@sta/src_journal_journald-context.c.o 
> | cc  -Ijournal-core@sta -I. -I.. -I../ -Isrc/libsystemd-network 
> -I../src/libsystemd-network -I../src/libsystemd/sd-network 
> -I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-id128 
> -I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-device 
> -I../src/libsystemd/sd-bus -Isrc/core -I../src/core -Isrc/libudev 
> -I../src/libudev -Isrc/udev -I../src/udev -Isrc/login -I../src/login 
> -Isrc/timesync -I../src/timesync -Isrc/resolve -I../src/resolve -Isrc/journal 
> -I../src/journal -Isrc/systemd -I../src/systemd -Isrc/shared -I../src/shared 
> -Isrc/basic -I../src/basic -flto -fdiagnostics-color=always -pipe 
> -D_FILE_OFFSET_BITS=64 -std=gnu99 -Wextra -Werror=undef -Wlogical-op 
> -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self 
> -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn 
> -Werror=missing-prototypes -Werror=implicit-function-declaration 
> -Werror=missing-declarations -Werror=return-type 
> -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes 
> -Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow 
> -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow 
> -Wdate-time -Wnested-externs -ffast-math -fno-common 
> -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden 
> -fstack-protector -fstack-protector-strong --param=ssp-buffer-size=4 -fPIE 
> -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result 
> -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -ffunction-sections 
> -fdata-sections -include config.h -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
> 'journal-core@sta/src_journal_journald-context.c.o' -MF 
> 'journal-core@sta/src_journal_journald-context.c.o.d' -o 
> 'journal-core@sta/src_journal_journald-context.c.o' -c 
> ../src/journal/journald-context.c
> | In file included from ../src/basic/alloc-util.h:28:0,
> |  from ../src/journal/journald-context.c:25:
> | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
> |  #define noreturn __attribute__((noreturn))
> |   ^
> | In file included from /usr/include/gcrypt.h:30:0,
> |  from ../src/journal/journal-file.h:26,
> |  from ../src/journal/journald-server.h:31,
> |  from ../src/journal/journald-context.h:30,
> |  from ../src/journal/journald-context.c:33:
> | /usr/include/x86_64-linux-gnu/gpg-error.h:1545:46: error: expected ‘,’ or 
> ‘;’ before ‘)’ token
> |  void gpgrt_log_bug (const char *fmt, ...)GPGRT_ATTR_NR_PRINTF(1,2);
> |   ^
> | In file included from ../src/basic/alloc-util.h:28:0,
> |  from ../src/journal/journald-context.c:25:
> | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
> |  #define noreturn __attribute__((noreturn))
> |   ^
> | In file included from /usr/include/gcrypt.h:30:0,
> |  from ../src/journal/journal-file.h:26,
> |  from ../src/journal/journald-server.h:31,
> |  from ../src/journal/journald-context.h:30,
> |  from ../src/journal/journald-context.c:33:
> | /usr/include/x86_64-linux-gnu/gpg-error.h:1546:46: error: expected ‘,’ or 
> ‘;’ before ‘)’ token
> |  void gpgrt_log_fatal (const char *fmt, ...)  GPGRT_ATTR_NR_PRINTF(1,2);
> |   ^
> | In file included from ../src/basic/alloc-util.h:28:0,
> |  from ../src/journal/journald-context.c:25:
> | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
> |  #define noreturn __attribute__((noreturn))
> |   ^
> | In file included from /usr/include/gcrypt.h:30:0,
> |  from ../src/journal/journal-file.h:26,
> |  from ../src/journal/journald-server.h:31,
> |  from ../src/journal/journald-context.h:30,
> |  from ../src/journal/journald-context.c:33:
> | /usr/include/x86_64-linux-gnu/gpg-error.h:1558:43: error: expected ‘,’ or 
> ‘;’ before ‘)’ token
> |  const char *func) GPGRT_ATTR_NORETURN;
> |^
> | [231/1523] /usr/bin/python3 /usr/bin/meson --internal exe 
> /<>/build-deb/meson-private/meson_exe_awk_ec289b1578d245bbf1d8589a5ea437fc6525ccd3.dat
> | ninja: build stopped: subcommand failed.
> | dh_auto_build: cd build-deb && LC_ALL=C.UTF-8 ninja 

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 18.03.2018 um 20:38 schrieb Mickaël Leduque:
> Package: systemd
> Version: 238-2
> Followup-For: Bug #893369
> 
> It didn't work so I just added the options in /etc/default/grub.
> Here are the journal and the systemctl list-jobs output (which is just "no 
> jobs").
> 

Ok, thanks.
Once you are dropped into the rescue shell, can you try running
systemd-udevd manually, via
/lib/systemd/systemd-udevd

If that works, you can try disabling the security features in
/lib/systemd/system/systemd-udevd.service
by commenting out the lines

MemoryDenyWriteExecute=yes
RestrictRealtime=yes
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
SystemCallArchitectures=native
LockPersonality=yes

one by one and test if that makes a difference.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 18.03.2018 um 18:50 schrieb LEDUQUE Mickaël:
> I'll do all that, thanks. Do you know how I can set a correct keymap in
> the grub "e" text editor ?

I don't. But this is literally the first google hit regarding that question
https://askubuntu.com/questions/751259/how-to-change-grub-command-line-grub-shell-keyboard-layout


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

On Sun, 18 Mar 2018 12:14:41 +0100 =?utf-8?q?Micka=C3=ABl_Leduque?=
 wrote:
> Package: systemd
> Version: 238-2
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> After an update and a restart of the system, boot fails. It enters a loop, 
> where (apparently) systemd-udevd fails to start and is retries for a certain 
> time.
> After thaat, I am dropped into recovery mode (or failsafe, I don't remember 
> the word).
> I tried investigating the logs, but I couldn't go very far, I just saw 
> something that may (or may nt) be related, seccomp logs about systemd-udevd 
> using a syscall
> but that's an "audit" log so I'm not sure it does anyhting at all.

See https://freedesktop.org/wiki/Software/systemd/Debugging/
"If You Can Get a Shell", and attach the journalctl output of such a boot.
Since this affects udev, please also consider adding
udev.log_priority=debug to the kernel command line (see man
kernel-command-line)

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893282: systemd: SuccessAction=reboot in wrong stanza in /lib/systemd/system/system-update-cleanup.service

[Michael Biebl]

Am 17.03.2018 um 18:37 schrieb Michael Grant:
> Package: systemd
> Version: 238-2
> Severity: normal
> 
> I noticed the following in the log file:
> Mar 17 07:12:41 example systemd[1]: 
> /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue
> 'SuccessAction' in section 'Service'
> Mar 17 07:12:42 example systemd[1]: 
> /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue
> 'SuccessAction' in section 'Service'
> Mar 17 07:12:43 example systemd[1]: 
> /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue
> 'SuccessAction' in section 'Service'
> Mar 17 07:12:44 example systemd[1]: 
> /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue
> 'SuccessAction' in section 'Service'
> Mar 17 07:12:44 example systemd[1]: 
> /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue
> 'SuccessAction' in section 'Service'
> 
> This line 'SuccessAction=reboot' is in the [Services] stanza.  It
> appears form the systemd.unit man page that this belongs in the [Unit]
> stanza.

From which version did you upgrade?

SuccessAction= should be supported since v236, so my only guess why you
see this issue is, that v235 or earlier was running on your system, then
v238 was unpacked, something triggered a "systemctl daemon-reload" which
causes this warning message as the unpacked .service files now use
SuccessAction but v235 was still running. We do reexec systemd in
postinst, so this issue is temporary.

Not sure we can really do something about it and it's harmless anyway.

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#886914: systemd: Kernel Panic on systemctl daemon-relaod, unit enable/disable when libvirt vms are running

[Michael Biebl]

On Thu, 11 Jan 2018 11:01:03 +0200 "Plamen K. Kosseff"
 wrote:
> Package: systemd
> Version: 236-2
> Severity: normal
> 
> Dear Maintainer,
> 
> 
> This is new debian buster install on HP z600 workstation (for hardware spec 
> see below).
> The issue has manifested first during normal "apt-get upgrade" over ssh the 
> system would free during processing systemd triggers.
> Upon local investigation there was Kernel panic - not synching: Attempted to 
> kill init exitcode=0x9. I'll try to attach picture of the full panic message.
> 
> After some more investigation it looks like the probelm is reproducible only 
> when there are libvirt VMs running.
> If I stop the VMs before systemctl daemon-reload, enable disable it works as 
> expected

Is this problem still reproducible?
Might this actually be a kernel/kvm bug triggered by the reload of libvirt?

CCing Guido, maybe he has an idea.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#870301: systemd: Touchpad fix Dell Inspiron Mini 1012

[Michael Biebl]

On Tue, 30 Jan 2018 04:30:58 -0500 (EST) bw  wrote:

> I'll go back and read your earlier posts, and see what I need to do.  I 
> guess you are recommending that I upgrade systemd and use upstream bug 
> reporting instead of debian bugtracker?

Yes, please upgrade to v238, try to reproduce your (libinput) problem,
if it still exists, file a bug report upstream at
https://github.com/systemd/systemd/issues
and report back with the bug number.
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#884784: systemd-network segfaults

[Michael Biebl]

On Tue, 19 Dec 2017 19:50:49 +0200 =?utf-8?q?R=C3=A9mi_Denis-Courmont?=
 wrote:
> Package: systemd
> Version: 235-3
> Severity: critical
> Justification: breaks unrelated software
> 
> Dear Maintainer,
> 
> systemd-networkd from version 236-1 systematically segfaults at start-up.

Could you test with v238 please and report back with your results.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892321: attempts to suspend failing after crash

[Michael Biebl]

On Thu, 8 Mar 2018 10:02:32 + Daniel Pocock  wrote:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: important
> 
> 
> Laptop was connected to a Thunderbolt dock, lid closed, using desktop
> monitor and keyboard, everything connected through the dock.  It is a
> laptop with encrypted LVM and swap on LVM.
> 
> Laptop's thunderbolt cable was bumped very slightly without coming out
> completely and then pushed back in.  As the lid was down, it appears the
> laptop tried to suspend
> 
> It didn't really suspend though, it became frozen with a blank screen.
> 
> After a hard reboot, every subsequent attempt to close the lid or undock
> also failed, the screen would go blank and it wouldn't come back.
> 
> journalctl and /var/log/messages provided no clues.
> 
> Guessing it was a problem with the swap partition, tried the following:
> 
>  swapoff /dev/mapper/vg00--vg-swap_1
>  mkswap /dev/mapper/vg00--vg-swap_1
> mkswap: /dev/mapper/vg00--vg-swap_1: warning: wiping old swap signature.
> Setting up swapspace version 1, size = 23.8 GiB (25513947136 bytes)
> no label, UUID=
> swapon /dev/mapper/vg00--vg-swap_1
> 
> In this case, the swap partition is named in /etc/fstab, not the UUID. 
> For somebody with the UUID in fstab it would be necessary to update
> there too and also run update-initramfs
> 
> This is not hard for an experienced user to resolve but very annoying as
> you only discover you have a problem after the second attempt to sleep.
> 
> Can systemd or whatever else is involved in the suspend/sleep mechanism
> be improved to detect problems like this, give some kind of error to the
> user and maybe even help them automatically correct it?

It's unclear to me what exactly your specific problem is/how and how
systemd should detect that.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892989: weird chars found in dpkg output

[Michael Biebl]

Am 16.03.2018 um 08:45 schrieb Harald Dunkel:
> On 03/15/18 18:46, Michael Biebl wrote:
>>
>> With a UTF-8 locale (which you really should enable), systemctl will use
>> '→', for a non-UTF8 locale, systemctl will fall back to '->'
>>
>>
> 
> Sorry to say, but thats ridiculous. Shouldn't it work no matter
> what? Ain't that "if locale == xxx" just asking for troubles?

No, I don't think it's ridiculous at all to use Unicode in 2018. The
ASCII fallback is only to be super-nice to people still refusing to use
a UTF-8 locale.

https://github.com/systemd/systemd/blob/master/src/basic/locale-util.c#L370
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

[Michael Biebl]

Am 15.03.2018 um 23:31 schrieb Jeff Ketchum:
> Package: systemd
> Version: 238-2
> Severity: normal
> 
> 
> 
> -- Package-specific info:
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.15.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
> LANGUAGE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages systemd depends on:
> ii  adduser  3.117
> ii  libacl1  2.2.52-3+b1
> ii  libapparmor1 2.12-3
> ii  libaudit11:2.8.2-1
> ii  libblkid12.31.1-0.5
> ii  libc62.27-2
> ii  libcap2  1:2.25-1.2
> ii  libcryptsetup12  2:2.0.1-1
> ii  libgcrypt20  1.8.1-4
> ii  libgpg-error01.27-6
> ii  libidn11 1.33-2.1
> ii  libip4tc01.6.2-1
> ii  libkmod2 25-1
> ii  liblz4-1 0.0~r131-2+b1
> ii  liblzma5 5.2.2-1.3
> ii  libmount12.31.1-0.5
> ii  libpam0g 1.1.8-3.7
> ii  libseccomp2  2.3.1-2.1
> ii  libselinux1  2.7-2+b1
> ii  libsystemd0  238-2
> ii  mount2.31.1-0.5
> ii  procps   2:3.3.12-4
> ii  util-linux   2.31.1-0.5
> 
> Versions of packages systemd recommends:
> ii  dbus1.12.6-2
> ii  libpam-systemd  238-2
> 
> Versions of packages systemd suggests:
> ii  policykit-10.105-18
> pn  systemd-container  
> 
> Versions of packages systemd is related to:
> pn  dracut   
> ii  initramfs-tools  0.130
> ii  udev 238-2
> 
> -- Configuration Files:
> /etc/systemd/journald.conf changed:
> [Journal]
> Storage=auto
> 
> 
> -- no debconf information
> 
> I upgraded systemd, and after a failure to boot, realized it was on
> systemd:i386.
> I went into a recovery environment and removed systemd:i386 and
> installed systemd.
> After that It failed to boot at a different location.
> I was able to get it to boot by removing the kernel parameter
> for the nouveau driver to use the binary firmware.
> 
> nouveau.config=NvGrUseFw=1

Where exactly is the problem that is caused by systemd?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892989: weird chars found in dpkg output

[Michael Biebl]

Am 15.03.2018 um 18:11 schrieb Michael Biebl:
> Am 15.03.2018 um 14:38 schrieb Guillem Jover:
> 
>> AFAIR, this is coming from systemd, and the character should be an
>> arrow (→), but I assume there's some kind of locale/encoding problem
>> somewhere. Perhaps even a misconfiguration in your system, but I'll
>> leave that up to the systemd maintainers.
> 
> Harald, what is your locale?
> What do you get if you run systemctl enable/disable directly?

Oh, and which version of systemd is this?

Btw, I can't really reproduce your problem:
With a UTF-8 locale (which you really should enable), systemctl will use
'→', for a non-UTF8 locale, systemctl will fall back to '->'


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892989: weird chars found in dpkg output

[Michael Biebl]

Am 15.03.2018 um 14:38 schrieb Guillem Jover:

> AFAIR, this is coming from systemd, and the character should be an
> arrow (→), but I assume there's some kind of locale/encoding problem
> somewhere. Perhaps even a misconfiguration in your system, but I'll
> leave that up to the systemd maintainers.

Harald, what is your locale?
What do you get if you run systemctl enable/disable directly?




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Re: Bug#767016: fixed in cron 3.0pl1-129

[Michael Biebl]

[systemd maintainer speaking here]

Hi Javier


On Sun, 11 Mar 2018 23:04:21 +
=?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?=  wrote:
>* debian/cron.init, debian/cron.service: Make sure cron is started last and
>  stopped first, with patch provided by Harald Dunke
>  (Closes: #767016, #801384, #783665) (LP: #1593317)

(mis)using Type=idle for this is not a proper fix.
See the relevant documentation in man systemd.service:

>Behavior of idle is very similar to simple; however, actual 
> execution of the service program is delayed until all active jobs are
>dispatched. This may be used to avoid interleaving of output of 
> shell services with the status output on the console. Note that this
>type is useful only to improve console output, it is not useful as 
> a general unit ordering tool, and the effect of this service type
>is subject to a 5s time-out, after which the service program is 
> invoked anyway.

The documentation is pretty clear, that Type=idle should *not* be used
for ordering purposes. It is not a proper fix.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767016#37
for a better alternative of actually specifying what cron needs.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Re: Bug#892730: nslcd: Please add systemd .service file

[Michael Biebl]

Am 12.03.2018 um 11:26 schrieb Laurent Bigonville:
> Package: nslcd
> Version: 0.9.9-1
> Severity: normal
> User: pkg-systemd-maintainers@lists.alioth.debian.org
> Usertags: systemd-units
> 
> Hi,
> 
> nslcd currently doesn't provides a systemd .service file.
> 
> This is a problem as nslcd should order itself with the
> nss-lookup.target and/or nss-user-lookup.target (see systemd.special(7)
> manpage).

Well, the SysV init has

# Should-Start:  $named

So the generated .service file should already have an
After=nss-lookup.target ordering. Are you saying this is incorrect?
If so, is the SysV init script incorrect as well?

> Quickly looking at the initscript, it starts two daemon at once.
> Spliting that in two .service file would be a good idea.
> 
> If it's not possible, adding a .service file doing
> ExecStart/ExecStop=/etc/init.d/nslcd start/stop would be a good
> workaround

Fwiw, I wouldn't call that a good workaround. A workaround maybe, but
not a good one and we should not recommend doing that.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

[Michael Biebl]

Control: tags -1 moreinfo

Am 11.03.2018 um 03:34 schrieb johnw:
> Package: systemd
> Version: 238-2
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>   I noticed, my system(xfce4, slim) can not create user.slice /
>   user session,
> 
>   and start-pulseaudio-x11 can not start
>   (start-pulseaudio-x11 error message:
>Connection failure: Connection refused
>pa_context_connect() failed: Connection refuse)
>   and the system become no sound
> 
>   systemctl --user status
>   Failed to read server status: Process org.freedesktop.systemd1 exited 
> with status 1
> 
>   All work well before systemd =< 237-4
> 
>   Please help, thanks.
> 

Please provide the output of
systemctl status
journalctl -alb (as root)

Have you rebooted after the upgrade?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Re: Starting powertop --auto-tune from systemd

[Michael Biebl]

Am 10.03.2018 um 18:55 schrieb Rainer Dorsch:
> [Please follow-up to debian-user]
> 
> Hello,
> 
> I run
> 
> /usr/bin/powertop --auto-tune
> 
> to optimize the power consumption of my system. Running it manually works 
> nicely. When I try to run from systemd, I see no effect :-/
> 
> I followed
> 
> https://wiki.archlinux.org/index.php/Powertop#Apply_settings
> 
> added
> 
> root@master:~# cat /etc/systemd/system/powertop.service 
> [Unit]
> Description=Powertop tunings
> 
> [Service]
> ExecStart=/usr/bin/powertop --auto-tune
> RemainAfterExit=true
> 
> [Install]
> WantedBy=multi-user.target
> root@master:~# 
> 
> enabled it for systemd and got
> 
> root@master:~# systemctl status powertop.service 
> ● powertop.service - Powertop tunings
>Loaded: loaded (/etc/systemd/system/powertop.service; enabled; vendor 
> preset: enabled)
>Active: active (exited) (Result: exit-code) since Sat 2018-03-10 18:29:53 
> CET; 22min ago
>   Process: 642 ExecStart=/usr/bin/powertop --auto-tune (code=exited, 
> status=203/EXEC)
>  Main PID: 642 (code=exited, status=203/EXEC)

systemct tells you there was a problem trying to execute the binary.
Possibly because it's the wrong path?
$ whereis powertop
powertop: /usr/sbin/powertop /usr/share/man/man8/powertop.8.gz

(note bin vs sbin)
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

[Michael Biebl]

Am 11.03.2018 um 19:12 schrieb Francesco Poli:

> My ~/.bash_logout is attached, but it's nothing special: it should be
> identical to the one provided by the bash package in /etc/skel/

Can you comment out / remove the following three lines:

if [ "$SHLVL" = 1 ]; then
[ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q
fi

and then test again, if you still encounter the problem.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#888955: open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc

[Michael Biebl]

Am 10.03.2018 um 01:39 schrieb Bernd Zeimetz:
> Hi,
> 
> because it needs to run before cloud-init. 

Why does it need to run before cloud-init i.e. why does cloud-init need
open-vm-tools?
Feel free to point me to the relevant parts of the bug report which
explain that.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 238-2 (source) into unstable

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 10 Mar 2018 01:12:47 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 238-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 892360
Changes:
 systemd (238-2) unstable; urgency=medium
 .
   [ Alf Gaida ]
   * core: do not free stack-allocated strings.
 Fixes a crash in systemd when the cpuacct cgroup controller is not
 available. (Closes: #892360)
Checksums-Sha1:
 13f610948ee713472dd83acbef3f7b96c310ddc2 4846 systemd_238-2.dsc
 1ed921c885503fa885969f6711dd09740e749a8a 134552 systemd_238-2.debian.tar.xz
 d078c42a65fa1a012706d54a803513b1b095847e 9424 systemd_238-2_source.buildinfo
Checksums-Sha256:
 b747bb1cdd47b658666bbb2f4e1a2d52eda4ec37c9318894ba191a6a40222bfb 4846 
systemd_238-2.dsc
 532e24c141acffd18ff1671799b8c8919f438c3b4f80c01e6032c813fffcd0fc 134552 
systemd_238-2.debian.tar.xz
 fae85e71d8f11563cf97173567592b00ce3f4313b4a2c89628cea14f25e12295 9424 
systemd_238-2_source.buildinfo
Files:
 16a433884e5092f4c8943d00a232c672 4846 admin optional systemd_238-2.dsc
 d4220542c1e2e76bfaac152a432f3d40 134552 admin optional 
systemd_238-2.debian.tar.xz
 83a80b518ed44bab9bd778ea9b0fcc6f 9424 admin optional 
systemd_238-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlqjI0sACgkQauHfDWCP
ItwHdg/+Lq6AHlVMDkuCMZ0puY7YYUrFcldMpxgj/4k0TjgSwQI1X/8Y7xmoNaT1
iFCkIdkbAJ/Y+QEsFNUjWU7gdCTJEx+5DJbhZJBkDK1lxyMhYtEYXZkbOmx3VN7Y
4aiL5N/C6rSTRKTe222WC/AhfxBbyDURWkXPA8TLabp9LPw1OqVSw0r+LoMoJJTb
ohBRfUxo/EM2kpgO8LQR0ZAvUzxFwbG7MfuQTAARpj1mqRjAzqmg70vXmLKyTruY
L5oBM+GolggyMjKd1+Zvfy4m46UBqGeyk0p1Rh4ECnIrq4b9S0tEJm/0vH3qeysU
8Argr09QlTO14vzI4gDt5GZxtZNu6d/JgOmktyfeeHMqj6hktgaL0ZInUE8374uX
3NlnGmi0zA9X8pkPke2kJtN+RwIALZHRjIT2eBJtS8heVWdesANz+hdKJu/kriUQ
rgzjFkN4US88/sIQQjg2e9973ivZdIsiRvC5CXREKQsliHWt0rkmp3yswgtdXEz/
153aMmoGu7Phv//t+A/i7rFkreNG3SGcca+2mhnZHuqP67VWrhiu7ET55RKDqf/R
6uNUVJjdi5iz0lWZ5YrbI7VpcwdpTBpJA5cboWcVrjeFHi+BZxYowC0/jAV5jO3+
CTE0ugtQTiV84fe0n728V6h4SCD+/XDyidFGiK1l8QjQPzLHDUE=
=PnW5
-END PGP SIGNATURE-


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#888955: open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc

[Michael Biebl]

On Fri, 2 Feb 2018 09:31:28 +0100 =?UTF-8?Q?Patrick_Matth=c3=a4i?= > for
the public:
> systemd does not start open-vm-tools at all in this scenario. If you
> configure open-vm-tools.service to use DefaultDependencies=yes instead
> of =no, it works as a workaround.

Why does open-vm-tools.service need DefaultDependencies=no? Those should
only be used by very few selected early boot services.

vmtoolsd doesn't ship a man page, but from a quick internet search, this
tool does not seem to fall into this category.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#888955: open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc

[Michael Biebl]

On Wed, 31 Jan 2018 16:06:16 +0100 =?UTF-8?Q?Patrick_Matth=c3=a4i?=
 wrote:
> Package: open-vm-tools
> Version: 2:10.2.0-2
> Severity: important
> 
> Dear Maintainer,
> 
> here all systems on vSphere 6.0/6.5 fail to start open-vm-tools.service
> on boot.
> The only thing I see is:
> 
> # systemctl status open-vm-tools.service
> ● open-vm-tools.service - Service for virtual machines hosted on VMware
>    Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled)
>    Active: failed (Result: resources)
>  Docs: http://open-vm-tools.sourceforge.net/about.php
> 
> This happens on jessie and stretch:
> 
> Stretch:
> Works: 2:10.1.5-5055683-4+deb9u1
> Fails: 2:10.2.0-2~bpo9+1

Please attach the output of /etc/fstab, systemctl show
open-vm-tools.service, systemctl cat open-vm-tools.service and
journalctl -alb from a boot where the service failed.

Is this happening reproducibly?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892360: systemd: Breaks also all my tested amd64 machines

[Michael Biebl]

Am 08.03.2018 um 18:31 schrieb Elimar Riesebieter:
> * Michael Biebl <bi...@debian.org> [2018-03-08 17:09 +0100]:
> 
>> Am 08.03.2018 um 17:05 schrieb Michael Biebl:
>>> Control: tags -1 moreinfo
>>>
>>> Am 08.03.2018 um 16:23 schrieb valette:
>>>
> [...]
> 
>> Could you check if
>> https://github.com/systemd/systemd/issues/8387
>> looks related
>>
>> I.e. if booting with systemd.unified_cgroup_hierarchy avoids the problem.
> 
> Booting with ystemd.unified_cgroup_hierarchy avoids the problem. But
> FMPOV this is only a workaround. Maybe
> https://github.com/systemd/systemd/pull/8391 should be merged
> upstream?

So, I got confirmation from Eric, that booting with a Debian kernel,
i.e. linux-image-4.14.0-3-amd64 avoids the problem, so does booting with
systemd.unified_cgroup_hierarchy according to Elimar.

Can you check your custom kernel config, specifically if
CONFIG_CGROUP_CPUACCT=y

Probably easiest if you just use grep
grep CGROUP /boot/config-$(uname -r)

Thanks,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892360: systemd pid 1 freezes at startup on x86 systems

[Michael Biebl]

Am 08.03.2018 um 18:27 schrieb Elimar Riesebieter:
> * Michael Biebl <em...@michaelbiebl.de> [2018-03-08 17:05 +0100]:
> 
>> Control: tags -1 moreinfo
>>
>> Am 08.03.2018 um 16:23 schrieb valette:
>>
>>> Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT)
>>
>> Is this also happening with a Debian provided kernel?
>> I see both you and Elimar use a custom one.
> 
> Didn't test it.

Please do

Please also try to gather the other data I asked for in my other replies


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892360: systemd: Breaks also all my tested amd64 machines

[Michael Biebl]

Am 08.03.2018 um 17:09 schrieb Michael Biebl:

> Could you check if
> https://github.com/systemd/systemd/issues/8387
> looks related
> 
> I.e. if booting with systemd.unified_cgroup_hierarchy avoids the problem.

If not, follow the instructions at
https://freedesktop.org/wiki/Software/systemd/Debugging/ to get a more
verbose boot log by using systemd.log_level=debug

and capture the error messages
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892360: systemd: Breaks also all my tested amd64 machines

[Michael Biebl]

Am 08.03.2018 um 17:05 schrieb Michael Biebl:
> Control: tags -1 moreinfo
> 
> Am 08.03.2018 um 16:23 schrieb valette:
> 
>> Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT)
> 
> Is this also happening with a Debian provided kernel?
> I see both you and Elimar use a custom one.
> 
> Is this a virtualized environment or read hardware?
> Do you get a coredump? If so, please attach to this bug report.
> 
> 
> 

Could you check if
https://github.com/systemd/systemd/issues/8387
looks related

I.e. if booting with systemd.unified_cgroup_hierarchy avoids the problem.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892360: systemd: Breaks also all my tested amd64 machines

[Michael Biebl]

Control: tags -1 moreinfo

Am 08.03.2018 um 16:23 schrieb valette:

> Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT)

Is this also happening with a Debian provided kernel?
I see both you and Elimar use a custom one.

Is this a virtualized environment or read hardware?
Do you get a coredump? If so, please attach to this bug report.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#883569: libpam-systemd: Prefer systemd-sysv over systemd-shim

[Michael Biebl]

Am 08.03.2018 um 09:22 schrieb Martin Pitt:
> Hello,
> 
> Julian Andres Klode [2017-12-05 11:43 +0100]:
>> libpam-systemd depending on systemd-shim first causes severe trouble with
>> resolving dependencies, as APT picks systemd-shim but then later sees a
>> package which needs systemd-sysv and fails.
>>
>> I understand the order was necessary for preventing upgrades to stretch
>> from migrating to systemd, but with the packages now widely installed,
>> this should not be a problem anymore, as the dependencies are satisfied
>> already, so APT won't switch them.
> 
> With the recent TC decision [1] I think we should actually be good now to flip
> this around in unstable/testing. Michael, do you have any reservation there?

There is one case: someone installs a minimal system without
libpam-systemd, then switches to sysvinit-core, then installs a desktop
environment which pulls libpam-systemd (via polkit in most cases). In
that specific scenario, apt will uninstall sysvinit-core and install
systemd-sysv again.
Is this something the TC has considered and is ok with?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#846377: discovered likely cause of this issue

[Michael Biebl]

Thanks Trent for further investigating this.

Dirk, can you confirm that adding pam_keyinit.so to
/etc/pam.d/systemd-user solves the problem for you as well?

Am 08.03.2018 um 09:47 schrieb Trent Lloyd:
> I believe I know the cause for this issue.  I ran into the same issue
> when trying to use fscrypt to setup ext4 encryption for /home on Ubuntu
> Bionic
> 
> /etc/pam.d/systemd-user does not currently call pam_keyinit.so. This
> means that the keyring does not link to the user keyring as it should,
> and will cause issues with programs needing a key from the keyring.
> 
> Something non-obvious about this, is that many desktop session processes
> are started under 'systemd-user' instead of the 'session' - this
> includes gnome-terminal-server which means any gnome-terminal shell runs
> under this context. If you start xterm instead of gnome-terminal, you
> get a different keyring and this can cause confusion when debugging the
> issue as some processes are in one state and the others are in another
> including your primary debug tool gnome-terminal. You can verify this by
> running 'systemctl status $(pidof gnome-terminal)' and 'systemctl status
> $(pidof xterm)' and note the different hierachy.
> 
> The change to add pam_keyinit.so was made upstream in December 2016:
> https://github.com/systemd/systemd/commit/ab79099d1684457d040ee7c28b2012e8c1ea9a4f
> 
> 
> In my test I add the usual pam_keyinit.so line after "pam_limits.so" and
> before "common-session-noninteractive". I am not sure if this is the
> most ideal location (but it appears to work).
> 
> You can test the behavior by running "keyctl show @s" in both contexts
> 
> Working contexts:
> - xterm
> - SSH login
> 
> Broken contexts:
> - gnome-terminal
> - systemd-run --user keyctl show @s (then check output with journalctl
> --user --follow)
> 
> When the configuration is broken you will see this output:
> lathiat@ubuntu:~/src/systemd$ keyctl show @s
> Keyring
>   59654779 --alswrv 1000 1000 keyring: _ses
>    6806191 s-rv 0 0 \_ user: invocation_id
> 
> When the configuration is working, you will see a link to the user
> session instead:
> lathiat@ubuntu:~/src/systemd$ keyctl show @s
> Keyring
>   59654779 --alswrv 1000 1000 keyring: _ses
>    6806191 s-rv 0 0 \_ keyring: _uid.1000
> 
> As background, what is broken on my test setup with libpam-fscrypt?
> gnome-terminal for example is unable to write any file in my encrypted
> /home which means that it cannot save preferences, so if you go into
> preferences and try to tick a checkbox it will immediately revert and an
> error is logged to the journal. You can use the guide at
> https://github.com/google/fscrypt to setup such a system if you wish to
> fully test my case. But you can simply verify the behavior as above.
> 
> This sounds very similar to the behavior described by the AFS users.   A
> quick google suggests as I would expect that AFS is in fact using the
> kernel keyring.
> 
> I detailed most of this same info in my bug for Ubuntu here, including
> for reference:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754270
> 
> Regards,
> Trent
> 
> ___
> Pkg-systemd-maintainers mailing list
> Pkg-systemd-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892302: libpam-systemd: Does not recgonize serial consoles as part of a seat

[Michael Biebl]

On Wed, 07 Mar 2018 19:05:13 -0500 Matthew Gabeler-Lee
 wrote:
> Package: libpam-systemd
> Version: 232-25+deb9u1
> Severity: normal
> 
> Various policykit actions that flag as for "active" or even "inactive", but
> not "any", do not work from serial console sessions.  After much pain, I'm
> fairly sure I've traced this down to libpam-systemd not marking serial
> logins as part of a seat.  This causes policykit to decide that the session
> is not local, and thus its activity state is irrelevant for the
> allow_inactive / allow_active policykit grants.

Are you logging in via serial console as unprivileged user?

> This seems to boil down, finally, to the get_seat_from_display function in
> pam_systemd.c.
> 
> Granted, serial console sessions are not _always_ local, given that I guess
> modems still technically exist and you might have dialup sessions, but this
> basically means that policykit is half-broken on headless systems, and that
> breaks significant bits of systemd, such as systemd-inhibit, which is where
> I began this adventure.
> 
> For headless systems, being able to identify serial consoles that _are_
> local and thus should have a "seat" would be helpful.  The contents of
> /etc/securetty seem like they would be a useful starting place here.

/etc/securetty (pam_securetty) is not really a good idea.


That all said, you should really take this up with upstream at
https://github.com/systemd/systemd/issues
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 238-1 (source) into unstable

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Mar 2018 23:21:53 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 238-1
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 890779
Changes:
 systemd (238-1) unstable; urgency=medium
 .
   [ Michael Biebl ]
   * New upstream version 238
 - Fixes systemd-tmpfiles to correctly handle symlinks present in
   non-terminal path components. (CVE-2018-6954, Closes: #890779)
   * Rebase patches
   * Use compat symlinks as provided by upstream.
 As the upstream build system now creates those symlinks for us, we no
 longer have to create them manually.
   * Update symbols file for libsystemd0
   * test-cgroup-util: bail out when running under a buildd environment
 .
   [ Dimitri John Ledkov ]
   * systemd-sysv-install: Fix name initialisation.
 Only initialise NAME after --root optional argument has been parsed,
 otherwise NAME is initialized to e.g. `enable`, instead of to the
 `unit-name`, resulting in failures. (LP: #1752882)
Checksums-Sha1:
 938cd28b6144bc79482c3df2888f73d6556cf973 4846 systemd_238-1.dsc
 8179cc62c7f0cb1b61b7fa21e843197229535fe6 6954022 systemd_238.orig.tar.gz
 f3f1ef8967fa797a2dacf01f1801aca5f62863cc 134088 systemd_238-1.debian.tar.xz
 3a103b057d9c763d1cde648a5478fd6bc23eb709 9424 systemd_238-1_source.buildinfo
Checksums-Sha256:
 e818654e5437ee08e68992cdea464b01085b5e6de1a786dd4e78e2ecaf4c3580 4846 
systemd_238-1.dsc
 bbc8599bab2e3c4273886dfab12464e488ecdaf20b8284949e50f8858de3e022 6954022 
systemd_238.orig.tar.gz
 8204804653fecdadc824e4cb0cd341a703ed846a87eec11050f67b19df4b149f 134088 
systemd_238-1.debian.tar.xz
 e3e688bfce4a9e9e8913ed8004ea3f5a7aed841893fb3e141c0ff1254b77 9424 
systemd_238-1_source.buildinfo
Files:
 e224e439374370d9ed2b8a24fc816e6b 4846 admin optional systemd_238-1.dsc
 76db8004647283b779234364cd637d3c 6954022 admin optional systemd_238.orig.tar.gz
 69d5b6c7e8038db0544c1617a9a5554d 134088 admin optional 
systemd_238-1.debian.tar.xz
 b9f14e1390fc5c37c29b8f475a64856a 9424 admin optional 
systemd_238-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlqganAACgkQauHfDWCP
ItwUuQ/+M1RnZgLgRdf4oi4Rnc+oRSTTl3Wx3PAIQICwBlswjjdQGd39Fk75akMd
7Edbr/yjGP6VwMK31JisguJJAngHKYRfeEtiQFV0M4I/D97lfSw+tO/H/edYEGT6
hRmyd4dVjkulchajeYYSK89DBwvAT3UZF5Z01q42lNi50zFPMSVo6YocxO+6vcEM
LdbhUV6fBLd44SPYM36vdwXDfESrnAV+mmNPMFAhsFMm7JOWxTgGmWpPq4gmjuD9
NWjBpXfwFKHZxtxCjVjbUzbD0rbrReYamBzAmtktA3i2CwoP1vBJVvJc3WH9ydRY
tFq0l6qFkPTvvtOizdFU0w0qbOwBv0hnqckFuAc657uOfQ/sOUXKB08hhoz3Dg3W
pgk3yrDMnso8Avdt0tWNv8ZpuTM8DCU2Y8z8A3hgtRgoYHrxBfxzvKNG2+ZML456
jDO9BvTL/MBcOncukxQE145Mg6hQ19hkiu38+neRVgxVNawRNOm4ABDIQvDBflJB
6SMsfd3VOZsERChV2MaKBKufn/ooVjt6F249onN6gxdIwM3lqafdidvWLoh+6o6C
yGsxQXXDc1Fe/RpkPyO/iH4oTTJLTsfKexssiy9Z3RH6rmnzDrVFkU+sbmbC0YB8
1wkZkxm8ouzzLX5X8Lg71aXqbcQOUfi5f6I7qmuwMTokVNdF30A=
=anbu
-END PGP SIGNATURE-


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

[Michael Biebl]

Am 25.11.2015 um 22:20 schrieb Francesco Poli (wintermute):
> Package: libpam-systemd
> Version: 228-2
> Severity: normal
> 
> Hello,
> I noticed a weird bug that is possibly caused by libpam-systemd.
> 
> Steps to reproduce (on a box with systemd as PID 1 process):
> 
>   0) login on TTY1 (virtual terminal 1) as a regular user
> 
>   1) start an X session with
> 
>  $ startx
> 
>   2) press [Ctrl+Alt+F2], in order to switch to TTY2
> 
>   3) login on TTY2 as the same user
> 
>   4) logout by pressing [Ctrl+D] on the empty command prompt
> 
>   5) awkwardly the screen goes automatically back to the X session
>  (rather than showing a fresh new TTY2 login prompt)
> 
>   6) even more awkwardly, any keyboard and mouse input is ignored
>  except for [Ctrl+Alt+F1], which however causes the screen to
>  go blank and immediately enter sleep mode
> 
>   7) the only way out seems to be a poweroff command, issued by
>  pressing the power button (which is handled by acpid)
> 
> I didn't try to SSH into the box and take a look at the system...
> 
> 
> I suspect that this bug is caused by libpam-systemd, since starting
> an X session on a box with systemd as PID 1 process, but without
> libpam-systemd installed, causes the same inability to use X input
> devices.
> 
> I noticed this bug some days ago with libpam-systemd/227-2: I waited
> for version 228-2 to migrate to testing, before reporting the bug.
> After reproducing the same exact misbehavior with libpam-systemd/228-2,
> I decided that it is time to report it.
> 
> Could you please investigate this bug and fix it and/or forward it
> upstream, as appropriate?

As the original bug reporter, can you still reproduce the issue, and if
so, could you share your ~/.bash_logout file.

Thanks,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

[Michael Biebl]

Control: reassign -1 postgresql

Am 03.03.2018 um 11:16 schrieb Christoph Berg:
> Re: To Michael Biebl 2018-03-03 <20180303085701.ga9...@msg.df7cb.de>
>> In that case the error is in a config file, and marking the service as
>> faulty makes sense. In the unit@instancetypo case, there's nothing
>> wrong with the system.
> 
> Fwiw, it looks like AssertPathExists=/etc/postgresql/%I/postgresql.conf
> would do what I'm looking for. I'll play with that a bit and report
> back.

Reassigning this to postgresql. Suppressing the error message is
apparently a deliberate choice made by the package maintainer.

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

[Michael Biebl]

Am 02.03.2018 um 20:48 schrieb Christoph Berg:

> "systemctl start foo.service" throws an error, but does not mark
> foo.service as failed.
> 
> If "systemctl start postgresql@foo.service" would not have
> ConditionFileExists, it would permanently be marked as failed (until
> "systemctl reset-failed").
> 
> Both should behave the same in the sense that typoing the service name
> on start shouldn't leave the system in a degraded state. (It would be
> nice if "systemctl start postgresql@foo.service" would throw a
> one-time error, but it doesn't look like that could be achieved.)

Well, I don't think those two cases are the same and as such should be
treated equally by systemd.
I see typoing the template name more like adding a typo to
ExecStart=/sbin/foobard /etc/typo_in_file_name
In this case foobard would most likely fail to start and systemd would
mark the service as failed. This is more comparable to your case,
because the template name is passed as a config option to the service


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

[Michael Biebl]

Am 02.03.2018 um 17:23 schrieb Christoph Berg:
> Re: Michael Biebl 2018-03-02 <4c3431e8-36e3-d86b-4bb8-1f99eaa38...@debian.org>
>> Am 02.03.2018 um 13:45 schrieb Christoph Berg:
>>
>>> I agree that it is not helpful that it doesn't raise an error here,
>>> but I think it is working as intended by systemd. Or should we rather
>>> be using AssertFileExists here? But starting the non-existing "foo"
>>> service doesn't put "foo" into a permanent error state either.
>>
>> Why not just drop the Condition altogether?
>> This way you'd get a proper error message from posgresql, and it would
>> be easier to diagnose what's going wrong?
> 
> For the same reason that "systemctl start nonexisting.service" doesn't
> permanently leave nonexisting.service in a error state that is visible
> e.g. via "systemctl". I'd think that would be worse.

Not sure what you mean by that. Can you elaborate?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

[Michael Biebl]

Am 02.03.2018 um 13:45 schrieb Christoph Berg:

> I agree that it is not helpful that it doesn't raise an error here,
> but I think it is working as intended by systemd. Or should we rather
> be using AssertFileExists here? But starting the non-existing "foo"
> service doesn't put "foo" into a permanent error state either.

Why not just drop the Condition altogether?
This way you'd get a proper error message from posgresql, and it would
be easier to diagnose what's going wrong?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

[Michael Biebl]

Am 01.03.2018 um 20:35 schrieb Felipe Sateler:
> On Thu, Mar 1, 2018 at 2:46 PM, Michael Biebl <bi...@debian.org> wrote:
>> Control: tags -1 moreinfo unreproducible
>>
>> Am 01.03.2018 um 16:00 schrieb Martin von Wittich:
>>> Hi Michael,
>>>
>>> On Thu, 1 Mar 2018 15:10:26 +0100 Michael Biebl <bi...@debian.org> wrote:
>>>> I can't reproduce this, neither on v237 nor on v232:
>>>>
>>>> # systemctl stop postgresql@does-not-exist
>>>> Failed to stop postgresql@does-not-exist.service: Unit
>>>> postgresql@does-not-exist.service not loaded.
>>>>
>>>> # systemctl start postgresql@does-not-exist
>>>> Failed to start postgresql@does-not-exist.service: Unit
>>>> postgresql@does-not-exist.service not found.
>>>>
>>>> # systemctl restart postgresql@does-not-exist
>>>> Failed to restart postgresql@does-not-exist.service: Unit
>>>> postgresql@does-not-exist.service not found.
>>>
>>> Do you have a postgresql template installed (should be the case when you
>>> have a postgresql-9.{4,6} (jessie/stretch) server package installed)? If
>>> not, try another template, maybe getty (I hope that's available on every
>>> system, would make reproducing this a lot easier):
>>
>> Hm, right. I completely missed the part about "valid-template", and no,
>> I didn't have postgresql@.service.
>>
>> But I'm not sure if what you are seeing is actually a bug. A templated
>> service does not necessarily need a representation on disk. It is very
>> much possible, that you simply want to pass a command flag to a daemon
>> for example.
>>
>> So systemd will happily start/stop/restart such a noop in your case. The
>> only case where it fails is, on a reload, because there wasn't actually
>> a process running which could be reloaded.
>>
>> Sounds a bit strange but is imho consistent.
>>
> 
> I think the problem is postgres has:
> 
> # -: ignore startup failure (recovery might take arbitrarily long)
> # the actual pg_ctl timeout is configured in pg_ctl.conf
> ExecStart=-/usr/bin/pg_ctlcluster --skip-systemctl-redirect %i start
> 
> If postgres would report the error back to systemd, it would at least
> tell you that.
> 
> getty@.service suffers from the same issue. Other units do not:
> 

You are spot on, Felipe. Afaics, systemd works as designed.
Question is, whether this bug report should be assigned to postgresql to
not use '-'.

CCing Christoph for his input.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

[Michael Biebl]

Control: tags -1 moreinfo unreproducible

Am 01.03.2018 um 16:00 schrieb Martin von Wittich:
> Hi Michael,
> 
> On Thu, 1 Mar 2018 15:10:26 +0100 Michael Biebl <bi...@debian.org> wrote:
>> I can't reproduce this, neither on v237 nor on v232:
>>
>> # systemctl stop postgresql@does-not-exist
>> Failed to stop postgresql@does-not-exist.service: Unit
>> postgresql@does-not-exist.service not loaded.
>>
>> # systemctl start postgresql@does-not-exist
>> Failed to start postgresql@does-not-exist.service: Unit
>> postgresql@does-not-exist.service not found.
>>
>> # systemctl restart postgresql@does-not-exist
>> Failed to restart postgresql@does-not-exist.service: Unit
>> postgresql@does-not-exist.service not found.
> 
> Do you have a postgresql template installed (should be the case when you
> have a postgresql-9.{4,6} (jessie/stretch) server package installed)? If
> not, try another template, maybe getty (I hope that's available on every
> system, would make reproducing this a lot easier):

Hm, right. I completely missed the part about "valid-template", and no,
I didn't have postgresql@.service.

But I'm not sure if what you are seeing is actually a bug. A templated
service does not necessarily need a representation on disk. It is very
much possible, that you simply want to pass a command flag to a daemon
for example.

So systemd will happily start/stop/restart such a noop in your case. The
only case where it fails is, on a reload, because there wasn't actually
a process running which could be reloaded.

Sounds a bit strange but is imho consistent.






-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

[Michael Biebl]

Control: tags -1 + moreinfo unreproducible

Am 01.03.2018 um 13:24 schrieb Martin von Wittich:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: normal
> Tags: upstream
> 
> Dear Maintainer,
> 
> the following commands unexpectedly do not print any error messages or
> return non-zero exit codes:
> 
> martin.mein-iserv.de ~ # systemctl stop postgresql@does-not-exist
> martin.mein-iserv.de ~ # systemctl start postgresql@does-not-exist
> martin.mein-iserv.de ~ # systemctl restart postgresql@does-not-exist
> 

I can't reproduce this, neither on v237 nor on v232:

# systemctl stop postgresql@does-not-exist
Failed to stop postgresql@does-not-exist.service: Unit
postgresql@does-not-exist.service not loaded.

# systemctl start postgresql@does-not-exist
Failed to start postgresql@does-not-exist.service: Unit
postgresql@does-not-exist.service not found.

# systemctl restart postgresql@does-not-exist
Failed to restart postgresql@does-not-exist.service: Unit
postgresql@does-not-exist.service not found.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 237-4 (source) into unstable

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 28 Feb 2018 19:18:34 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 237-4
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Changes:
 systemd (237-4) unstable; urgency=medium
 .
   [ Gunnar Hjalmarsson ]
   * Fix PO template creation.
 Cherry-pick upstream patches to build a correct systemd.pot including
 the polkit policy files even without policykit-1 being installed.
 (LP: #1707898)
 .
   [ Michael Biebl ]
   * Drop mask for fuse SysV init script.
 The fuse package has removed its SysV init script a long time ago, so
 the mask is no longer needed.
   * Replace two Debian specific patches which cherry-picks from upstream
 master
Checksums-Sha1:
 503d35a0689b7486e7c826a703f47c8abbca9105 4846 systemd_237-4.dsc
 07c0ffa468d44870f73d90839d04d4126ef47150 143108 systemd_237-4.debian.tar.xz
 60ff9a19e4c9f1f772fef4636e9fde7dfeb5413c 9442 systemd_237-4_source.buildinfo
Checksums-Sha256:
 2cb4f4b0b7810ed99b20cf3083592e6e4b21af07d095ab2c41ccf645751f2dd2 4846 
systemd_237-4.dsc
 5f234b1f960a0aa4767a20edbef805c04b9bb3f5003f4fb396db3cb7393781ef 143108 
systemd_237-4.debian.tar.xz
 3afc3d8c054ed757f38710fa8704dbba425c0534ac0d381f1a9ae2ed3c9a5f12 9442 
systemd_237-4_source.buildinfo
Files:
 8f02a3f8ed974980d9b823f992064dd2 4846 admin optional systemd_237-4.dsc
 5009987d16774b41c77bf3f9bb695f24 143108 admin optional 
systemd_237-4.debian.tar.xz
 fc9c8473b555f92ed966adaad1f5ab36 9442 admin optional 
systemd_237-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlqW8tsACgkQauHfDWCP
ItwmXw/9EqB4QvmzOlNCk3PdTF5WtyEEVva+O1F62S0U5L3H5JyQbIqQhT+IjMF0
W7CQV9o2kz4/LEd1seiSkXPvLwplrDGKV/sp+7+C9Dzdb3WbGqt7Ixq38pkrhIVX
YlGjA7Ndr++NJqKlLp8b0KR60YsCZ3IdHoV4v8SS4eYjhJy+b9smPaQqxBnrSRXZ
ZAeDzN/AdalStCfZMIbzKD4KE5mWRda7gbkIWPPLZGY3nYm3QHJt7UmSmXvMaqva
GvxYy1z9uZLsg2FWbzAXIfQ8ERKN7Hanjiu8l33rWka7IeGXiuPYW9WU0rfb1aZ9
fXEno1j9J5igqSgnEG5EUaFLCDcDm2bmXmvdrWQzvrdLQ7AGb1hPfphD1/pl/U+Q
qj2iAEHtPK8mSbdQjIC01tQRfae0Tb8q2RBo0/hccNybR/d3I4+1HSK/AZBX5jju
1RTsqjagG8yIBNFwxvihVn6vv6RJaswhPftpaWpq74chIBmx+PjDqBiVaHgRELKn
gv3bdLRfkKohvJASSd+ewEl/bel9c53QYmI17kT3KtcIYtMRPO9/1dnqloPvznUu
PQf59paAyotmae41mq4VUk4IRl/D5BC8NEmj1+adPHOPV5ezcRNuvthFF/8dL3by
wnyXwhfYDjFBDQqNGxIOET+5FQ1RSIOTYh14Y1ooVbeWJQhhnkE=
=0kKd
-END PGP SIGNATURE-


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

[Michael Biebl]

Control: reassign -1 gzip
Control: forcemerge 890279 -1

Am 25.02.2018 um 23:22 schrieb Pascal Hambourg:
> Error message:
> 
> error while loading shared libraries: cannot restore segment prot after
> reloc: Operation not permitted

..

> Actually I am not sure whether this bug should be filed against udev or
> gzip. There might be other affected programs still unnoticed in Debian.

Fwiw: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890279

Let's reassign this to gzip then.

I'd still prefer though, if console-setup wouldn't run complex shell
scripts, which spawn arbitrary binaries. directly from the udev rules
file and used a dedicated service for that instead.
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

[Michael Biebl]

Am 25.02.2018 um 23:22 schrieb Pascal Hambourg:
> Package: udev
> Version: 232-25+deb9u1
> 
> This a follow-up to bug #855798 "udev: MemoryDenyWriteExecute=yes should
> not be applied to udev plugins" which was closed because the affected
> program was not part of Debian. Now it seems that gzip is also affected
> by MemoryDenyWriteExecute=yes when run by udev on i386.
> 
> Context:
> VT console events trigger a rule in
> /lib/udev/rules.d/90-console-setup.rules which runs
> /etc/console-setup/cached_setup_font.sh. This script runs setfont to set
> the configured console font. setfont calls gzip to uncompress the
> .psf.gz (cached_Lat15-Fixed16.psf.gz in my case) font file but gzip
> fails. So the console font is not set at boot time.
> 
> The following command triggers the error on i386:
> 
> systemd-run -t -p MemoryDenyWriteExecute=yes gzip -h
> 
> Error message:
> 
> error while loading shared libraries: cannot restore segment prot after
> reloc: Operation not permitted
> 
> strace:
> ==
> execve("/bin/gzip", ["gzip", "-h"], [/* 4 vars */]) = 0
> brk(NULL)   = 0x9ac000
> access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or
> directory)
> mmap2(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0xb7703000
> access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or
> directory)
> open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
> fstat64(3, {st_mode=S_IFREG|0644, st_size=14043, ...}) = 0
> mmap2(NULL, 14043, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb76ff000
> close(3)    = 0
> access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or
> directory)
> open("/lib/i386-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
> read(3,
> "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\360\203\1\0004\0\0\0\334L\33\0\0\0\0\0004\0
> \0\n\0(\0E\0D\0\6\0\0\0004\0\0\0004\0\0\0004\0\0\0@\1\0\0@\1\0\0\5\0\0\0"...,
> 512) = 512
> fstat64(3, {st_mode=S_IFREG|0755, st_size=1791908, ...}) = 0
> mmap2(NULL, 1800732, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
> 0) = 0xb7547000
> mprotect(0xb76f8000, 4096, PROT_NONE)   = 0
> mmap2(0xb76f9000, 12288, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1b1000) = 0xb76f9000
> mmap2(0xb76fc000, 10780, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb76fc000
> close(3)    = 0
> set_thread_area({entry_number:-1, base_addr:0xb7705840, limit:1048575,
> seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
> seg_not_present:0, useable:1}) = 0 (entry_number:6)
> mprotect(0xb76f9000, 8192, PROT_READ)   = 0
> mprotect(0x405000, 98304, PROT_READ|PROT_WRITE) = 0
> mprotect(0x405000, 98304, PROT_READ|PROT_EXEC) = -1 EPERM (Operation not
> permitted)
> writev(2, [{iov_base="gzip", iov_len=4}, {iov_base=": ", iov_len=2},
> {iov_base="error while loading shared libraries", iov_len=36},
> {iov_base=": ", iov_len=2}, {iov_base="", iov_len=0}, {iov_base="",
> iov_len=0}, {iov_base="cannot restore segment prot after reloc",
> iov_len=39}, {iov_base=": ", iov_len=2}, {iov_base="Operation not
> permitted", iov_len=23}, {iov_base="\n", iov_len=1}], 10) = 109
> exit_group(127) = ?
> +++ exited with 127 +++
> ==
> 
> One can see that mprotect is called with PROT_EXEC, which is prohibited
> by MemoryDenyWriteExecute and returns an error. The error message text
> is from /lib/ld-linux.so.2.
> 
> setfont/gzip works on i386 when run outside udev or when run from udev
> without MemoryDenyWriteExecute=yes in
> /lib/systemd/system/systemd-udevd.service.
> It works on amd64 in any case.
> 
> Actually I am not sure whether this bug should be filed against udev or
> gzip. There might be other affected programs still unnoticed in Debian.

I think this should be filed against console-setup. It really should use
a dedicated service to run its setup routine and not directly call
complex shell scripts directly from udev via
RUN+="/etc/console-setup/cached_setup_font.sh"

See SYSTEMD_WANTS (man systemd.device).


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 237-3~bpo9+1 (source) into stretch-backports

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Feb 2018 18:22:14 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 237-3~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Changes:
 systemd (237-3~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports
   * Rebase patches
   * Revert "Add Build-Depends on python3-evdev "
 This package is not availabe in stretch or stretch-backports.
   * Revert "Drop debian/extra/rules/70-debian-uaccess.rules"
 There is no libu2f-udev package in stretch or stretch-backports shipping
 the udev rules for U2F devices.
Checksums-Sha1:
 7c056518409bff38ce8c3d907a1373ad141f6355 4850 systemd_237-3~bpo9+1.dsc
 eab6cd40cfe5ae31edeeff944e09d927aadcac1f 144008 
systemd_237-3~bpo9+1.debian.tar.xz
 1fa37cc9ca9b04501259d75422d529f715762c60 9438 
systemd_237-3~bpo9+1_source.buildinfo
Checksums-Sha256:
 c1d01f5bfb614be3895cb2850af2760184a680ce751dccafc6f042b065baedb2 4850 
systemd_237-3~bpo9+1.dsc
 5ea65e531246db024cf17308f12cd3b18c581e786100c2d2ef1e2d77aa159ba7 144008 
systemd_237-3~bpo9+1.debian.tar.xz
 354c6c756843433e05267d92b1aba2298284c2d79e4fd61f48a64529830bd98c 9438 
systemd_237-3~bpo9+1_source.buildinfo
Files:
 8a800edd24cde160bf8f2598a2f335ec 4850 admin optional systemd_237-3~bpo9+1.dsc
 671f2378d2164d4a43b99735b5e1c844 144008 admin optional 
systemd_237-3~bpo9+1.debian.tar.xz
 71c6589f16d4cf02224f4efa9221cb44 9438 admin optional 
systemd_237-3~bpo9+1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlqS9PMACgkQauHfDWCP
ItxlZw/+PZy+Y3lFKAHwecYrQxnB0sgvjCvVnlIk0DyH9g+cwO6boofGFTsNkUhG
xLy5OBBtmu8dHyVPNN6mtaqZIJFdWAexQTJ9zKKRUfrFNUET3dH1g9FZyS5oVBvS
//GrpHMVExBXBm8D+tRQqQrvB/DRHLzQYYTy/j9YrNgpyQqDjkQbReJ73OxqaxQz
5xRdWssWg7ea/Ax6hQ9uUpBewBV4xFGg2wvYJNnmqADOKYkg18VDa5AuOy93aOF0
m3nv3WfJjdHiXhdjI93BIslztHWZl/ms2D25cBcuC4VHyXnrLP2x7HH5Klf24z85
GJ9gzOHvdj7ACZWNBIzMMKaiTgdh9Dck5MHjq6US6GydAE3qLXrrDFkmvHJFJtVP
KHP9HKGia4ElOZMPWIL6tj817X8ITGG5DHLxxItDDgzP6+APC+WEqxCAhgOBW8Al
LdTp6CuJxvR90hbFD3ydKcNdcKU4QTW+6lzssXfbzUYWSROnjMOYqesDndSEobF9
/VxLgVJJ2xARX5OmFSKdabZ51r7iwCO79R+NKTGUaEKvBpaOJIpvyTF3OVdmrsnM
rKi5L0Lzi+82lIR0iWJM+ExzMuY3ZHPPlNvfHVmSuIDtfAUWCbH/X4UuGiD/Hdow
koFpC0hATquJixcR0lSZub0KVdeUQf7v4j4CfX2oZR5GZgIK5u8=
=6O3K
-END PGP SIGNATURE-


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

[Michael Biebl]

On Tue, 20 Feb 2018 19:38:08 +0100 Gert Wollny <gw.foss...@gmail.com> wrote:
> Am Dienstag, den 20.02.2018, 15:31 +0100 schrieb Michael Biebl:
> > 
> > > Kernel: Linux 4.15.1-cm-fx6-my (SMP w/4 CPU cores; PREEMPT)
> > 
> > 
> > Does this also happen with a Debian provided kernel? If so, which
> > kernel version is that? 
> I haven't tried this so far, for that reason I was initially also a bit
> reluctant to report the bug here and I didn't report anything against
> the kernel package. There is another problem: reproducing the bug is
> not straightforward: in theory I should be able to trigger it by
> setting the clock to a time past the year 2038, but hwclock doesn't let
> me, and unplugging the device also doesn't switchset the RTC to a bogus
> value right away.

I was under the impression, that this issue was fixed in the kernel. So,
are you still running into this with your self-compiled 4.15.1-cm-fx6-my?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

[Michael Biebl]

Am 20.02.2018 um 12:40 schrieb Gert Wollny:
> on an 32 bit arm system when the RTC is set to a wrong time booting the 
> system might 
> fail because systemd gets stuck in a loop printing "systemd[1]: Time has been 
> changed". 
> 
> The problem is known upstream and claimed to be a problem of the kernel: 
>   https://github.com/systemd/systemd/issues/1143
> 
> However, while upstream is certainly correct that a kernel bug is the trigger 
> of 
> the lockup, 


...

> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: armhf (armv7l)
> 
> Kernel: Linux 4.15.1-cm-fx6-my (SMP w/4 CPU cores; PREEMPT)


Does this also happen with a Debian provided kernel? If so, which kernel
version is that? Which hardware?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

[Michael Biebl]

Am 20.02.2018 um 13:57 schrieb Gert Wollny:
> Am Dienstag, den 20.02.2018, 13:33 +0100 schrieb Michael Biebl:
>> Am
>>
>>> make it lock up in this loop, but if someone can spoof this kind of
>>> message and the system locks up because of this, wouldn't this be a
>>> typical DoS attack?
>>
>> How could an unprivileged user spoof such messages?
> 
> I am by no means a security expert, but doesn't the story usually go:
> someone finds a bug that allows an escalation of rights that allows
> them to do certain things, in the extreme case they can open a root
> shell, in another case they may be able to set the RTC to a bogus value
> that triggers the kernel to flood timerfd with messages that lock up
> the system. Of course that is not a very likely scenario, but to me it
> seems possible.

If an attacker can get a root shell, you have lost anyway.
As for the other cases, those are all hypothetical at this point, right?




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

[Michael Biebl]

Am 20.02.2018 um 13:19 schrieb Gert Wollny:
> Am Dienstag, den 20.02.2018, 12:56 +0100 schrieb Michael Biebl:
>> Am 20.02.2018 um 12:40 schrieb Gert Wollny:
>>> However, while upstream is certainly correct that a kernel bug is
>>> the trigger of  the lockup, systemd should not hang on this,
>>> because if sending messages to systemd can lock up the system then
>>> this is actually an attack vector for a DoS attack. 
>>
>> How is this an attack vector for a DoS attack? Please elaborate
>>
> I don't really know by which channel systemd gets these messages that

timerfd

> make it lock up in this loop, but if someone can spoof this kind of
> message and the system locks up because of this, wouldn't this be a
> typical DoS attack?

How could an unprivileged user spoof such messages?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

[Michael Biebl]

Am 20.02.2018 um 12:40 schrieb Gert Wollny:
> However, while upstream is certainly correct that a kernel bug is the trigger 
> of 
> the lockup, systemd should not hang on this, because if sending messages to 
> systemd 
> can lock up the system then this is actually an attack vector for a DoS 
> attack. 

How is this an attack vector for a DoS attack? Please elaborate


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890824: Container: unsets cgroup memory limit on user login

[Michael Biebl]

Am 19.02.2018 um 13:09 schrieb Maximilian Philipps:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: important
> 
> Hi
> 
> I have an issue with Systemd unsetting the memory limit for my container,
> whereupon programs like free and htop report having access to 8 exabyte
> of memory.
> 
> The setup is the following:
> 
> Host:
> Release: Debian jessie
> Kernel: 4.9.65-3+deb9u2~bpo8+1 (jessie backports)
> Container provider: libvirt 3.0.0-4~bpo8+1 (jessie backports)
> Systemd: 215-17+deb8u7 (jessie)
> cgroup hierarchy: legacy
> 
> Guest:
> Release: Debian stretch
> Systemd: 232-25+deb9u1 (stretch)
> 
> There are several containers running on the host, but this problem only
> occurs with all the Debian stretch containers. Containers running Debian
> jessie or older Ubuntu 12.04 aren't affected.
> Each container is configured to cgroup enforced memory limit in it's
> libvirt domain file.
> Example:
> 4194304
> 2097152
> 
> Steps to reproduce + observations:
> 1) start a container with virsh -c lxc:// container.example.com
> 2) virsh -c lxc:// memtune container.example.com
>    reports a hard_limit of 2097152
> 3) cat
> "/sys/fs/cgroup/memory/machine.slice/machine-.scope/memory.limit_in_bytes"
> 
> outputs 2147483648
> 4) nsenter -t  -m -u -i -n -p free  reports 2097152 kB
> 5) ssh container.example.com free  reports 9007199254740991 kB
> 3) cat
> "/sys/fs/cgroup/memory/machine.slice/machine-.scope/memory.limit_in_bytes"
> 
> outputs 9223372036854771712
> 6) nsenter -t  -m -u -i -n -p free  reports 9007199254740991 kB
> 7) virsh -c lxc:// memtune container.example.com
>    reports a hard_limit of unlimited
> 
> As far as I can tell it seems to be that systemd unsets the cgroup memory
> limit when creating the user session. However why it gets set to
> 9223372036854771712 instead of the 255G of the host I don't know.

I'm confused: Are you saying that systemd inside the guest (i.e. running
systemd v232) resets the memory limits on the host (running v215)?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890095: systemd: Failed to start network time synchronization

[Michael Biebl]

Control: tags -1 + moreinfo

On Sun, 11 Feb 2018 03:38:51 -0200 Carlos Donizete Froes
 wrote:
> Package: systemd
> Version: 236-3
> Severity: normal
> 
> Dear Maintainer,
> 
> At startup, the following failures appear:
> 
> [FAILED] Failed to start network time synchronization.
> See 'systemctl status systemd-timesyncd.service' for details.
> 
> After bootup, the command 'timedatectl' produces:
> 
> -
> coringao@debian:~$ timedatectl
>   Local time: dom 2018-02-11 03:03:45 -02
>   Universal time: dom 2018-02-11 05:03:45 UTC
> RTC time: dom 2018-02-11 05:03:46
>Time zone: America/Sao_Paulo (-02, -0200)
>System clock synchronized: yes
> systemd-timesyncd.service active: no
>  RTC in local TZ: no
> -
> 
> So I checked the statuses:
> 
> -
> coringao@debian:~$ systemctl status systemd-timesyncd
> ● systemd-timesyncd.service - Network Time Synchronization
>Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
> vendor preset: enabled)
>Active: failed (Result: exit-code) since Sun 2018-02-11 02:15:58 -02; 
> 49min ago
>  Docs: man:systemd-timesyncd.service(8)
>   Process: 280 ExecStart=/lib/systemd/systemd-timesyncd (code=exited, 
> status=1/FAILURE)
>  Main PID: 280 (code=exited, status=1/FAILURE)
>Status: "Shutting down..."
> -
> 
> Can anyone explain what the problem is? 

For that we would need a more complete log. You can get that via journalctl.

That said, have you installed and enabled libnss-systemd? If not, please
do so, reboot and report back if systemd-timesyncd still fails.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890265: systemd: journalctl compiled without pattern matching support

[Michael Biebl]

Am 12.02.2018 um 18:02 schrieb Calum Mackay:
> Package: systemd
> Version: 237-2
> Severity: normal
> 
> Dear Maintainer,
> 
> The -g/--grep option was recently added to the man page, but:
> 
>   $ journalctl --grep=blah
>   Compiled without pattern matching support
> 
> this could be a man page bug, of course, although it's a useful feature.

As the message says, systemd has been compiled without pattern matching
support. This is deliberate, as this would required linking against
pcre2, which would basically make this library mandatory on every
system. That's why I hesitated to enable that feature.





-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890659: systemd segfault in libsystemd-shared-232.so

[Michael Biebl]

See #890470

> Am 16.02.2018 um 20:09 schrieb Lukas Hejtmanek :
> 
> Package: systemd
> Version: 232-25+deb9u1
> Severity: important
> Tags: patch
> 
> 
> 
> -- Package-specific info:
> 
> -- System Information:
> Debian Release: 9.3
>  APT prefers stable-updates
>  APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.9.0-5-amd64 (SMP w/144 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages systemd depends on:
> ii  adduser 3.115
> ii  libacl1 2.2.52-3+b1
> ii  libapparmor12.11.0-3
> ii  libaudit1   1:2.6.7-2
> ii  libblkid1   2.29.2-1
> ii  libc6   2.24-11+deb9u1
> ii  libcap2 1:2.25-1
> ii  libcryptsetup4  2:1.7.3-4
> ii  libgcrypt20 1.7.6-2+deb9u2
> ii  libgpg-error0   1.26-2
> ii  libidn111.33-1
> ii  libip4tc0   1.6.0+snapshot20161117-6
> ii  libkmod223-2
> ii  liblz4-10.0~r131-2+b1
> ii  liblzma55.2.2-1.2+b1
> ii  libmount1   2.29.2-1
> ii  libpam0g1.1.8-3.6
> ii  libseccomp2 2.3.1-2.1
> ii  libselinux1 2.6-3+b3
> ii  libsystemd0 232-25+deb9u1
> ii  mount   2.29.2-1
> ii  procps  2:3.3.12-3
> ii  util-linux  2.29.2-1
> 
> Versions of packages systemd recommends:
> ii  dbus1.10.24-0+deb9u1
> ii  libpam-systemd  232-25+deb9u1
> 
> Versions of packages systemd suggests:
> pn  policykit-1
> pn  systemd-container  
> pn  systemd-ui 
> 
> Versions of packages systemd is related to:
> pn  dracut   
> ii  initramfs-tools  0.130
> ii  udev 232-25+deb9u1
> 
> -- Configuration Files:
> /etc/systemd/journald.conf changed:
> [Journal]
> RuntimeMaxUse=30M
> 
> /etc/systemd/logind.conf changed:
> [Login]
> RemoveIPC=no
> 
> 
> -- no debconf information
> 
> 
> I believe, this issue is resolved here:
> https://github.com/systemd/systemd/issues/6624
> 
> it is not included in debian systemd package though.
> 
> ___
> Pkg-systemd-maintainers mailing list
> Pkg-systemd-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890470: stretch-pu: package systemd/232-25+deb9u1

[Michael Biebl]

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 systemd fixing a couple of issues.

An annotated changelog follows.
Full debdiff is attached.

systemd (232-25+deb9u2) stretch; urgency=medium

  * networkd: Handle MTU field in IPv6 RA (Closes: #878162)

https://salsa.debian.org/systemd-team/systemd/commit/9f134218fa5ed60a4d7b0a2282d86ab56f52a3e9
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878162

It's a cherry-pick of an upstream commit which is already in
unstable/testing.
This change was requested by Julien Cristau who already confirmed that it
fixes the issue for stretch.

  * shared: Add a linker script so that all functions are tagged @SD_SHARED
instead of @Base.
This helps prevent symbol collisions with other programs and libraries.
In particular, because PAM modules are loaded into the process that is
creating the session, and systemd creates PAM sessions, the potential
for collisions is high. (Closes: #873708)

https://salsa.debian.org/systemd-team/systemd/commit/bd33312f7fcf660f568bf2bac288b5ceec6981ab
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873708

It's a backport of an upstream commit which is already in
unstable/testing.

I'd consider this the most important fix, as we have seen segfaults in
systemd when e.g. libpam-heimdal was used.

  * resolved: Fix loop on packets with pseudo dns types.
CVE-2017-15908 (Closes: #880026)

https://salsa.debian.org/systemd-team/systemd/commit/5a469751160af8334ca4748ee00ee9b7e1a3efe3
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880026

It's a cherry-pick of an upstream commit which is already in
unstable/testing.
The security team suggested to fix this via a stable upload, as the
issue was not considered severe enough for a security upload (resolved
is not enabled by default in Debian)

  * machinectl: Don't output "No machines." with --no-legend option
(Closes: #880158)

https://salsa.debian.org/systemd-team/systemd/commit/9c22320c9d012bb515fb91752795fa4a6649dc5f
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880158

It's a cherry-pick of an upstream commit which is already in
unstable/testing.

The fix is trivial and has very low regression potential, so I decided
to include this patch as well. I'm fine with dropping it though, if you
have concerns.


The changes don't affect the installer. That said I've CCed debian-boot
for their ack.

Please let me know if I can proceed with the upload.

Regards,
Michael

-- 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.15.0-rc8-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 237-3 (source) into unstable

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Feb 2018 23:07:17 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 237-3
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 890423 890436
Changes:
 systemd (237-3) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * debian/tests/boot-smoke: More robust journal checking.
 Also fail the test if calling journalctl fails, and avoid calling it
 twice. See https://github.com/systemd/systemd/pull/8032
   * Simplify PO template creation.
 Use the existing upstream build system instead of a manual call to
 `intltool-update` and `xgettext` to build systemd.pot. Remove the now
 obsolete intltool build dependency, but still explicitly keep gettext.
 (LP: #1707898)
   * Make systemd-sysv-install robust against existing $ROOT.
 Always initialize `$ROOT`, to avoid the script getting confused by an
 existing outside env variable. Also fix the `--root` option to actually
 work, the previous approach was conceptually broken due to how shell
 quoting works. Make the work with `set -u`. (Closes: #890436)
 .
   [ Felipe Sateler ]
   * Backport upstream patch fixing a wrong assert() call (Closes: #890423)
Checksums-Sha1:
 dbc1a05bd9a86990b5447659e85202eb1d3a5e82 4846 systemd_237-3.dsc
 4bc806ab01199a9b8f765d62c2dd521b347d0475 134712 systemd_237-3.debian.tar.xz
 4a19e2b7ede89f19a2ff10fcb5cf0780947924b4 9141 systemd_237-3_source.buildinfo
Checksums-Sha256:
 f5c745d185aba0f1af3a65186d75eafd0f8bead91af3056ed4ecf95a37a0ef4f 4846 
systemd_237-3.dsc
 b509fd6228ef8864653db573ccbe0094ea99e4a07295bbdf7c5fc8b505ba38c3 134712 
systemd_237-3.debian.tar.xz
 e77afbebb865df35f398857798deb19ab4059888a9c1147ae197e82a75b8bc25 9141 
systemd_237-3_source.buildinfo
Files:
 673d247a9b41c02f92b4113d7fab8dd7 4846 admin optional systemd_237-3.dsc
 3fd7a7251dfea1668c86f510d70b671d 134712 admin optional 
systemd_237-3.debian.tar.xz
 d0a12a8238d7ab9142a460eb36a941f1 9141 admin optional 
systemd_237-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlqEs04ACgkQauHfDWCP
ItwVHxAAnNMxDuo/A5tAm3Uam/I0TuhhhmsCZAAj88dcbhnrzovYBryemwc6NAac
Vh7CqLv/0ziLe8nc5i+0U4QWoKuegiNQPdS9DeJoYlWtcTkqUAsyhm5j0oqjIfoa
6erk6RyIQNIj+Gv7hQ2jOEmc7iLhkLDJAhjBmyyjeKYx5r/vw+zi6noiyUI4mUsk
IBI/Q8ejYZSdagb1fRsO4F7URoN4QabqWfJruJR61VLWAVEQh99eRPjRl0+nntkz
vUvqSd37boKQ7Nz0NMWKEe5daKt42oKSY10zGmiQyQzFYENzsWtEPKAbcQANywCh
EpZuYo/SYsjRAeYALVI4eRZUM7cY77I6l7LpkytTg/4UWbaD8ljHrj+s0vRtri4l
jGQmPojC8Am7eQd6ElzseBvrWFHEqy6xwgztBGBwdZIhJc49FwgoMvbUWkKd5VKp
IXm/xr3MXzgoEg9Eh84kEWYTZr2X+BjDYXpV63zKLB1XFo/1atDNY34SQMGYXrEh
8EZm2PeYnpDrc1E5xiccQ9HYVdIF6+xjy+uhpiYlM/GlYjecrHXqTsi4C9zgIbLZ
pfSmFPH2vBijP0Bc5K4JVF/gbrtuQZbHKM4mCi4oyTFnWILsBQAMifgNu2BRVD8h
kuaj7ftwc/bP6eVBZEt/Be4JKrHveYc8zmKDpbFguSGeO+QwiUw=
=Fj87
-END PGP SIGNATURE-


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#873613: systemd gets confused at shutdown time

[Michael Biebl]

On Fri, 1 Dec 2017 10:39:33 +0100 Harald Dunkel
 wrote:
> Hi Felipe,
> 
> sorry for the delay.
> 
> On 9/5/17 10:09 PM, Felipe Sateler wrote:
> > 
> > 
> > On Mon, Sep 4, 2017 at 3:26 AM, Harald Dunkel  > > wrote:
> > 
> > If there is already a patch 6588, then would you mind to include
> > it for Stretch?
> > 
> > 
> > Before this is considered, we need confirmation it fixes the issue. Could 
> > you try that patch?
> > 
> 
> I applied 9cbc4547702aac28466c497f720038b9e2dc510c to 232-25+deb9u1:
> No luck. It still gets stuck at shutdown time for about 3 minutes.
> 
> Attached you can find 2 screenshots I managed to take. The list-open.service
> was in place. Please note the "nfs-data not responding" due to the lost
> network connection. "nfs-data" is a CNAME for the NFServer for both
> /home and /data.
> 
> Maybe its an option to not shutdown the network at all?

That's up to the network config system.

NetworkManager e.g. does not shut down ethernet connections when being
stoppend.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890436: systemd-sysv-install uses ROOT variable from environment for chrooting

[Michael Biebl]

Am 14.02.2018 um 18:32 schrieb Lars Michelsen:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: normal
> 
> systemd-sysv-install uses `ROOT` variable from environment when not set
> via `-r` and tries to execute update-rc.d chrooted to the content of
> this variable.

Both CHROOT and ROOT are set conditionally, but CHROOT is used
uncoditionally later on.

We should unset both CHROOT and ROOT at the beginning of the script (or
set it to an empty string).

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 237-2 (source) into unstable

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 09 Feb 2018 23:35:31 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 237-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 889144 889665
Changes:
 systemd (237-2) unstable; urgency=medium
 .
   * Drop debian/extra/rules/70-debian-uaccess.rules.
 Up-to-date udev rules for U2F devices are shipped in libu2f-udev nowadays.
 (Closes: #889665)
   * service: relax PID file symlink chain checks a bit.
 Let's read the PID file after all if there's a potentially unsafe symlink
 chain in place. But if we do, then refuse taking the PID if its outside of
 the cgroup. (Closes: #889144)
Checksums-Sha1:
 42a25a70aca4c68f37a91964699b0c359d51374f 4847 systemd_237-2.dsc
 02bb23e925619c53888b9f8cc3ecc13156188218 134104 systemd_237-2.debian.tar.xz
 38d09fcd0a0d9a3f7098b7e65fe90b31601574ab 9973 systemd_237-2_source.buildinfo
Checksums-Sha256:
 ac589748103ad5e704cde8d6b69ce9a4b45370418b1486b4137c8bd20f1c0a13 4847 
systemd_237-2.dsc
 ed743c30614252caafb5572582858aab7014a2452429448c06543ea6b1431441 134104 
systemd_237-2.debian.tar.xz
 1668fc3b33b4f235a71b2c4eed6e1b0786dba006e6f6e6b24644c0ca2455152a 9973 
systemd_237-2_source.buildinfo
Files:
 dfeb1cdc2dd35abd871663227329c798 4847 admin optional systemd_237-2.dsc
 90279fd7bb8d221a61071c04956ecc51 134104 admin optional 
systemd_237-2.debian.tar.xz
 309c7ebe56c26d0cd6632b6a0fdd1c93 9973 admin optional 
systemd_237-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlp+ImwACgkQauHfDWCP
Itz+OQ/9EgLy2/GsNV61+4CebTHkoyDVldQfJ3L2ziA58GqVmZfFJWIutnzjDlyv
9KIXl9VF+qe852nEosjtwRoEyjXA4QKP5IJmG5y5yepwX74Qx9vHLAkk/kfKWo4e
65Dkx50MF4IgTL+T32UsAbNicojmPGjMSiDK4Sc5u73i3TMbXFJNcJ/bM/UeSERi
oUhvKPlpxN9LZVySYqpHvb2X2ukeb+HTRf48BBUsgGASKNyLNYEu917OHsDY6YB4
vGNZ3geel+kWL3H38Fsxklq/KjrlvAL02Sh2VY0UahrJFAHrbKedthOmqn2kLUdo
EOV2iOQGk+q28iFprFCK3jtbaR3vWtq0Bd3D8aWSq3vavP8Ok2gWyMVNjb4A58xv
+dZSbyn/iEU4pXu6HyaWoEIfbys9/cv9/RFdV8DHyHwUfPlO7vg9QBPyuNJWrzm7
htwkWtbqCpioSz/qncq3iyjl4qQ5iZ3k27tJ9w53JVM9NscrIBHceq2zrsrk/HBY
CjDmKpc2h4T6ttgS5AjgDE91rS02sLEQTU6dVQ0p48CrSvdR0FV39ISGfGEIkVB1
o8gr+FHruPdnzXJP7jRTOrQs7ez6F13S0gimfY5PUzMdN7uqrW25oeWOlro8bQdu
AS9+LAF8GUZWiKEhiwCbgQ+7TeMdfpOvZmtvZIXKzxzntoriWKs=
=Wf4M
-END PGP SIGNATURE-


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#889144: systemd 237-1: problem starting dnsmasq

[Michael Biebl]

Am 07.02.2018 um 22:12 schrieb Jonathan de Boyne Pollard:
> Michael Biebl:
> 
>> If other services depend on dnsmasq, please keep
>> https://www.lucas-nussbaum.net/blog/?p=877 in mind
>>
> Please do not.  It is an erroneous conclusion based upon a faulty
> analysis that conflates the readiness protocols
> <http://jdebp.eu./FGA/unix-daemon-readiness-protocol-problems.html> with
> the non-daemon nature of the way that things are run by the |service|
> command

[..]

So how exactly does dnsmasq signal readiness if it's run in foreground?
It does neither implement sd_notify nor use D-Bus activation.
So there is no way for systemd to know when it's ready to accept
connections. As a result, daemon, which depend on dnsmasq would be
started immediately once the dnsmasq binary has been spawned.





-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Re: Openvswitch must started before networking servise

[Michael Biebl]

On Mon, 16 Oct 2017 20:28:26 +0700 Fedor Goncharov  wrote:
> Package: openvswitch-switch
> Version: 2.6.2~pre+git20161223-3
> Priority: critical
> 
> The Openvswitch daemon must be started before the network.service. 
> Because when the initiation of the network started interfaces from the 
> options should exist, or if you try to configure openvswitch in 
> /etc/network/interfaces, then the ovs daemon must be running to execute 
> commands.
> Please create a systemd configuration with the option "Before: 
> networking.service" for a stable version of debian.

That seems like the wrong thing to do.
networking.service is specific to ifupdown (auto). We do have several
other network configuration systems. I hope this was not actually
applied as a fix? The changelog is unfortunately unclear in that regard:

  * Added 2 debian/*.service files (Closes: #878757, #771507).

Thomas, can you please post the complete change that was actually applied.


Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#889110: udev: extremely high cpu usage (overheats notebook after a minute of use)

[Michael Biebl]

Am 02.02.2018 um 04:50 schrieb Alex Henry:
> Here's the "bluez" issue report
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889111
> 
> Hopefully the maintainers for both packages can communicate to identify
> responsibilities and solve the issue. Thank you!

Looks like neither a udev nor bluez issue but a kernel/driver bug to me.
Might also be faulty hardware.
systemd-udevd is simply reacting to the uevents that are generated by
the kernel here. And since apparently you are flooded with those
bind/unbind events, systemd-udevd keeps your CPU busy.

You might try rolling back to an older kernel and see if that fixes the
problem.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

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

[Michael Biebl]

Am 30.01.2018 um 15:15 schrieb Ritesh Raj Sarraf:
> Hello Michael,
> 
> On Tue, 2018-01-30 at 15:07 +0100, Michael Biebl wrote:
>> Am 30.01.2018 um 15:01 schrieb Ritesh Raj Sarraf:
>>
>>> /etc/systemd/network/tap.netdev:5: Unknown section 'Tap'. Ignoring.
>>
>> Please always share your full config files you use.
>>
> Here's my config.

Thanks. Seems I can't reproduce the issue using v237 here.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#888892: No permission on U2F security key

[Michael Biebl]

Am 30.01.2018 um 23:47 schrieb Kurt Roeckx:

> There is no such package, but I do have u2f-host instaled, and so
> libu2f-host0 and libhidapi-hidraw0. I also have libykpers-1-1
> installed that ships /lib/udev/rules.d/69-yubikey.rules

Seems the package was named libu2f-udev, not libu2f-common.
You want /lib/udev/rules.d/70-u2f.rules most likely.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#888850: systemd-timesyncd fails to start

[Michael Biebl]

Control: forcemerge 887343 -1

Am 30.01.2018 um 17:12 schrieb John Williams:
> Package: systemd
> Version: 236-6

There is no such version in the archive?
Please consider using reportbug next time, which will include correct
version information and lots of diagnostic info which helps to triage bugs.

> 
> After a recent installation of buster (aarch64), systemd-timesyncd fails to 
> start 
> 
> systemctl status systemd-timesyncd says:
>   systemd-timesyncd.service: Start request repeated too quickly
>   systemd-timesyncd.service: Failed with result 'exit-code'
> 
> I notice that /lib/systemd/system/systemd-timesyncd.service contains both the 
> lines:
>   DynamicUser=yes
> and
>   User=systemd-timesync
> but there is no such user as 'systemd-timesync' in /etc/passwd; if I add such 
> a user, the service starts up correctly, running as that user.

I would recommend installing libnss-systemd.
That said, since 236-4, systemd-timesync will cope if no
systemd-timesync user exists.

Closing as duplicate of 887343


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

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

[Michael Biebl]

Am 30.01.2018 um 15:01 schrieb Ritesh Raj Sarraf:

> /etc/systemd/network/tap.netdev:5: Unknown section 'Tap'. Ignoring.

Please always share your full config files you use.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#870301: systemd: Touchpad fix Dell Inspiron Mini 1012

[Michael Biebl]

On Tue, 10 Oct 2017 16:04:46 +0200 Michael Biebl <bi...@debian.org> wrote:
> On Mon, 31 Jul 2017 20:44:17 -0400 (EDT) bw <bwtn...@yahoo.com> wrote:
> > On Tue, 1 Aug 2017, Michael Biebl wrote:
> > > It would be great if you can file this issue upstream at
> > > https://github.com/systemd/systemd/issues
> > >
> > > Such a change really belongs into upstream and should not be added as a
> > > downstream patch.
> > >
> > > Regards,
> > > Michael
> > >
> > 
> > I know but they don't want it, I put info in the attachment.
> 
> Well, if the issue is still valid with v234 or v235, upstream is happy
> to review a patch.
> 
> You can either test on a sid/buster system or use the v234 stretch backport.
> 


Ping? Are you still interested in getting this upstream?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 237-1 (source) into unstable

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 30 Jan 2018 01:55:24 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 237-1
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Changes:
 systemd (237-1) unstable; urgency=medium
 .
   * New upstream version 237
   * Rebase patches
   * Update symbols file for libsystemd0
   * Update Vcs-* to point to https://salsa.debian.org
   * Bump Standards-Version to 4.1.3
   * Set Rules-Requires-Root to no
Checksums-Sha1:
 20dd274577e8561b5f34c90191f4cb8280711d08 4847 systemd_237-1.dsc
 95ad75df18e7f1c7083cd88ce7b167613e403d21 6871350 systemd_237.orig.tar.gz
 22b7e5c1c7f423731db13a5a87e727f7828e1cd8 133560 systemd_237-1.debian.tar.xz
 188b4b833dbf0c66e5a2dff39947660c33828369 9976 systemd_237-1_source.buildinfo
Checksums-Sha256:
 4c1bec5a1d47e1d3f73c3320e5954a684e057602aded2b99425423288a139d8d 4847 
systemd_237-1.dsc
 c83dabbe1c9de6b9db1dafdb7e04140c7d0535705c68842f6c0768653ba4913c 6871350 
systemd_237.orig.tar.gz
 be9d605bb47ae8a88b4a401cde1453d3afc20ffc10bf4ec4336a1ddeb2784350 133560 
systemd_237-1.debian.tar.xz
 d6ffed74c1023aa9367d4ceeac1a08f5e24c29a5ec7689f493c12c4c10e6a16e 9976 
systemd_237-1_source.buildinfo
Files:
 6af5ddba11fa2e2574d23362dd45696a 4847 admin optional systemd_237-1.dsc
 5a835ddc2a2ae9ef523a5a11674a6713 6871350 admin optional systemd_237.orig.tar.gz
 827ad9aaa7a70b40f8c8831fa8d595ae 133560 admin optional 
systemd_237-1.debian.tar.xz
 6bfece5f9cc97eb2225076cf0710d514 9976 admin optional 
systemd_237-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlpvxcwACgkQauHfDWCP
ItyWuRAAix2oB584iRDKPrLUkfjkn5ulCYqago1OOjzGKNUI3mSiY5VIG0U5LWux
WUT2zKOhQcMYSBPllmfZrvyK7asK1EdRFh2VRsoqyum1gBYWVfDMa2Cz5BmPSYmb
n8TQjGZihuOs80KVXhU2AAx335zQpgw3kq4vIqdGdcleB6nYkvwiw+f3N064RJ/q
lmN6Vmth3hV9ZPhm+bl5Sdyf4pSbzTaTcMETJ16sA6kgEfMCD5AB+lEqv5l8jEt1
P2kPK1Qj1SncxSq8/8TNOBm3zLiQAkd53fI9n5TMt8ifhZ7nTRqY/Rf+B33ycUGO
mFLi7mv8xBWAHPlAkZyB8zoRwDtutSLFxvwS6YlVhRbHCBbTNmNV06bnjZRkd2dT
hFlctKYGviuX/+c78k4HQArD/9Re7QMwf7nWpKdWGNdJln4hgSt7YrcvCYG4ULb0
zDnqC6hr8KMCRep4SaM3d4yRKyW4QKQOdgZ8XMh0C5HOdv/hwuv8lJery628Dczo
+pgiO90K2/pU8KrxHp1yFLjPgJyzbj0hAEo8r4a/5THbI212st/Vu6c9+f0ZirmI
rFCpf9meY/QG4JzQF4T8Vh35jjGXuuTL1iy+iY4aoI1bUE0XbcJOHC4jkxJzHgRS
CeOLg4xjevYM7R2Kgw0JFkP5e3hg22rjfuaWNOJRamis6wkzsQ4=
=3Y0r
-END PGP SIGNATURE-


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers