Bug#855345: jessie-pu: package systemd/215-17+deb8u7

[Michael Biebl]

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

Hi,

I'd like to make a stable upload for systemd, fixing two bugs.

The changelog is

systemd (215-17+deb8u7) stable; urgency=medium

  * bus: Fix bus_print_property() to use "int" for booleans.
This fixes the problem that on big endian architectures, like mips or
powerpc, boolean properties that were retrieved via via sd-bus were always
set to 0 (no). (Closes: #774430)
  * systemctl: Add is-enabled support for SysV init scripts.
The update-rc.d utility does not provide is-enabled, so implement it
ourselves in systemctl using the same logic as systemd-sysv-install from
Stretch. (Closes: #809405)

 -- Michael Biebl   Fri, 17 Feb 2017 00:26:38 +0100

The complete debdiff is attached.

Regards,
Michael


-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (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 ffceb7d..3c17485 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+systemd (215-17+deb8u7) stable; urgency=medium
+
+  * bus: Fix bus_print_property() to use "int" for booleans.
+This fixes the problem that on big endian architectures, like mips or
+powerpc, boolean properties that were retrieved via via sd-bus were always
+set to 0 (no). (Closes: #774430)
+  * systemctl: Add is-enabled support for SysV init scripts.
+The update-rc.d utility does not provide is-enabled, so implement it
+ourselves in systemctl using the same logic as systemd-sysv-install from
+Stretch. (Closes: #809405)
+
+ -- Michael Biebl   Fri, 17 Feb 2017 00:26:38 +0100
+
 systemd (215-17+deb8u6) stable; urgency=medium
 
   [ Michael Biebl ]
diff --git 
a/debian/patches/bus-fix-bus_print_property-to-use-int-for-booleans.patch 
b/debian/patches/bus-fix-bus_print_property-to-use-int-for-booleans.patch
new file mode 100644
index 000..262252e
--- /dev/null
+++ b/debian/patches/bus-fix-bus_print_property-to-use-int-for-booleans.patch
@@ -0,0 +1,27 @@
+From: David Herrmann 
+Date: Thu, 18 Sep 2014 13:28:28 +0200
+Subject: bus: fix bus_print_property() to use "int" for booleans
+
+We always use "int" if we retrieve boolean values from sd-bus, as "bool"
+is only a single byte, but full int on va-args.
+
+Thanks to Werner Fink for the report!
+
+(cherry picked from commit c2fa048c4a70c8386c6d8fe939e5ea9edecf1e98)
+---
+ src/libsystemd/sd-bus/bus-util.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/libsystemd/sd-bus/bus-util.c 
b/src/libsystemd/sd-bus/bus-util.c
+index 6441c5b..d0b7c3d 100644
+--- a/src/libsystemd/sd-bus/bus-util.c
 b/src/libsystemd/sd-bus/bus-util.c
+@@ -631,7 +631,7 @@ int bus_print_property(const char *name, sd_bus_message 
*property, bool all) {
+ }
+ 
+ case SD_BUS_TYPE_BOOLEAN: {
+-bool b;
++int b;
+ 
+ r = sd_bus_message_read_basic(property, type, );
+ if (r < 0)
diff --git a/debian/patches/series b/debian/patches/series
index a883d86..3dc8933 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -170,6 +170,7 @@ polkit-don-t-start-polkit-agent-when-running-as-root.patch
 core-rework-logic-to-determine-when-we-decide-to-add-auto.patch
 systemctl-fix-argument-handling-when-invoked-as-shutdown.patch
 systemctl-when-reading-legacy-t-argument-for-shutdown-don.patch
+bus-fix-bus_print_property-to-use-int-for-booleans.patch
 
 ## Debian specific patches:
 Add-back-support-for-Debian-specific-config-files.patch
@@ -228,3 +229,4 @@ Skip-filesystem-check-if-already-done-by-the-initram.patch
 cryptsetup-Implement-offset-and-skip-options.patch
 Revert-core-one-step-back-again-for-nspawn-we-actual.patch
 udev-increase-udev-event-timeout-to-180s.patch
+systemctl-Add-is-enabled-support-for-SysV-init-scripts.patch
diff --git 
a/debian/patches/systemctl-Add-is-enabled-support-for-SysV-init-scripts.patch 
b/debian/patches/systemctl-Add-is-enabled-support-for-SysV-init-scripts.patch
new file mode 100644
index 000..7b73592
--- /dev/null
+++ 
b/debian/patches/systemctl-Add-is-enabled-support-for-SysV-init-scripts.patch
@@ -0,0 +1,84 @@
+From: Michael Biebl 
+Date: Wed, 15 Feb 2017 10:03:37 +0100
+Subject: systemctl: Add is-enabled support for SysV init scripts
+
+The update-rc.d utility does not provide is-enabled, so implement it
+ourselves in systemctl using the same logic as systemd-sysv-install from
+Stretch.
+See commit b5aa768d8108b294c1187a0728f5b13c033b3d47
+
+Closes: #809405
+---
+ src/systemctl/systemctl.c 

Re: unblock: systemd/231-18

[Michael Biebl]

Am 16.02.2017 um 22:12 schrieb Martin Pitt:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hello release team,
> 
> The current systemd in unstable (232-18) fixes an RC bug on architectures that
> don't support seccomp (https://bugs.debian.org/852811), some more seccomp bugs
> that also affect x86, and a couple of non-RC bugs; plus some autopkgtest
> improvements which increase coverage and tighten upstream CI. -18 has been in
> unstable for 3 days now without regression reports, built everywhere, and I am
> very confident that it doesn't break things compared to -15.

Afaics, Niels had already unblocked it.




-- 
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

unblock: systemd/231-18

[Martin Pitt]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Hello release team,

The current systemd in unstable (232-18) fixes an RC bug on architectures that
don't support seccomp (https://bugs.debian.org/852811), some more seccomp bugs
that also affect x86, and a couple of non-RC bugs; plus some autopkgtest
improvements which increase coverage and tighten upstream CI. -18 has been in
unstable for 3 days now without regression reports, built everywhere, and I am
very confident that it doesn't break things compared to -15.

debdiff between -15 (in testing) and current -18 attached. I also put the
changelog and some annotations to it below.

| systemd (232-18) unstable; urgency=medium
| 
|   * udev autopkgtest: Adjust to script-based test /sys creation.
| PR #5250 changes from the static sys.tar.xz to creating the test /sys
| directory with a script. Get along with both cases until 233 gets
| released and packaged.

Improved disto/upstream CI, no runtime effect.

|   * systemd-resolved.service.d/resolvconf.conf: Don't fail if resolvconf is
| not installed. ReadWritePaths= fails by default if the referenced
| directory does not exist. This happens if resolvconf is not installed, so
| use '-' to ignore the absence. (Closes: #854814)

Fallout from the change in -17. Now it's really a no-op in Debian (as the
stricter privilege restrictions of resolved are not yet, and will not be in
stretch).

|   * Fix two more seccomp issues.
|   * Permit seeing process list of units whose unit files are missing.
|   * Fix systemctl --user enable/disable without $XDG_RUNTIME_DIR being set.
| (Closes: #855050)

Non-RC bug fixes. The patches are relatively small and straightforward, and
people asked for them.
 
|  -- Martin Pitt   Mon, 13 Feb 2017 17:36:12 +0100
| 
| systemd (232-17) unstable; urgency=medium
| 
|   * Add libcap2-bin build dependency for tests. This will make
| test_exec_capabilityboundingset() actually run. (Closes: #854394)
|   * Add iproute2 build dependency for tests. This will make
| test_exec_privatenetwork() actually run; it skips if "ip" is not present.
| (Closes: #854396)
|   * autopkgtest: Run all upstream unit tests as root.
| Ship all upstream unit tests in libsystemd-dev, and run them all as root
| in autopkgtest. (Closes: #854392) This also fixes the FTBFS on non-seccomp
| architectures.

Improved disto/upstream CI, no runtime effect.

|   * systemd-resolved.service.d/resolvconf.conf: Allow writing to
| /run/resolvconf. Upstream PR #5283 will introduce permission restrictions
| for systemd-resolved.service, including the lockdown to writing
| /run/systemd/. This will then cause the resolvconf call in our drop-in to
| fail as that needs to write to /run/resolvconf/. Add this to
| ReadWritePaths=. (This is a no-op with the current unrestricted unit).

As said above, no-op in stretch (except that this first declaration had a bug,
fixed now).

|  -- Martin Pitt   Fri, 10 Feb 2017 11:52:46 +0100
| 
| systemd (232-16) unstable; urgency=medium
| 
|   [ Martin Pitt ]
|   * Add autopkgtest for test-seccomp

Improved disto/upstream CI, no runtime effect.

|   * udev: Fix by-id symlinks for devices whose IDs contain whitespace
| (Closes: #851164, LP: #1647485)

In terms of intrusiveness this is the change with the biggest regression
potential. However, it's rather academic to expect that something relies on the
broken symlinks. This change has been tested widely already though, as it
already landed in an Ubuntu stable update for all releases, and unbreaks stable
device symlinks for NVMe devices.

|   * Add lintian overrides for binary-or-shlib-defines-rpath on shipped test
| programs. This is apparently a new lintian warning on which uploads get
| rejected.  These are only test programs, not in $PATH, and they need to
| link against systemd's internal library.

No runtime effect, just lintian cleanup.

| 
|   [ Michael Biebl ]
|   * Fix seccomp filtering. (Closes: #852811)

That's the RC bug which really needs to go in.

|   * Do not crash on daemon-reexec when /run is full (Closes: #850074)

The patches are a bit large-ish, but this avoids completely ruining your
system when /run is out of space.

Please let me know if you have any question.

Thanks for considering!

Martin
diff --git a/debian/changelog b/debian/changelog
index a5acc0c..2e4d6da 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,57 @@
+systemd (232-18) unstable; urgency=medium
+
+  * udev autopkgtest: Adjust to script-based test /sys creation.
+PR #5250 changes from the static sys.tar.xz to creating the test /sys
+directory with a script. Get along with both cases until 233 gets
+released and packaged.
+  * systemd-resolved.service.d/resolvconf.conf: Don't fail if resolvconf is
+not installed. ReadWritePaths= fails by default if the referenced
+directory 

Bug#855272: marked as done (systemd: policykit does not show TUI for remote logins)

[Debian Bug Tracking System]

Your message dated Thu, 16 Feb 2017 20:09:14 +0100
with message-id <8b3c42d1-0853-ad26-65b8-4d52b3ceb...@debian.org>
and subject line Re: Bug#855272: systemd: policykit does not show TUI for 
remote logins
has caused the Debian Bug report #855272,
regarding systemd: policykit does not show TUI for remote logins
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
855272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 232-17
Severity: important

Hello,

***
rrs@chutzpah:~$ echo $DISPLAY
localhost:10.0
14:22 __   _
rrs@chutzpah:~$ export DISPLAY=""
14:22 __   _
rrs@chutzpah:~$ machinectl login debTemplate
  
Failed to get login PTY: Connection timed out
14:23 ___  => 1  
rrs@chutzpah:~$ sudo machinectl login debTemplate
[sudo] password for rrs:
Connected to machine debTemplate. Press ^] three times within 1s to exit
session.

Debian GNU/Linux 9 deb-template pts/0

deb-template login:

***

AND

***

rrs@chutzpah:~/foo$ systemctl enable systemd-nspawn@fitbit
Failed to enable unit: Connection timed out

rrs@chutzpah:~/foo$ sudo systemctl enable systemd-nspawn@fitbit
[sudo] password for rrs:
Created symlink
/etc/systemd/system/machines.target.wants/systemd-nspawn@fitbit.
service _ /etc/systemd/system/systemd-nspawn@fitbit.service.

rrs@chutzpah:~/foo$ echo $DISPLAY
localhost:10.0

***

This is a remote machine, to which I'm logged over ssh. The login run is
byobu. When I run machinectl, I do not receive a Terminal Interface
prompt. Instead, it shows a user prompt on the machine's gdm display,
which is very wrong because the displayed prompt is user interactable.

On the other hand, as you can see in the log above, over my ssh session,
it complains about timeout.

Shouldn't the tools be able to detect a local session vs a remote
session ?


***
loginctl output

   SESSIONUID USER SEAT TTY 
   297   1000 rrs   
 5   1000 rrs  seat0/dev/tty2   
c1127 Debian-gdm   seat0/dev/tty1   
   299   1000 rrs   
   298   1000 rrs   
 4   1000 rrs  seat0/dev/tty2   

6 sessions listed.

***

I think this is a bug because on my Jessie box running systemd from
backports, this issue is not seen. Ofcourse that box is headless and
does not have gdm installed


***
pi@pi:~$ systemctl daemon-reload 
 AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
Authentication is required to reload the systemd state.
Authenticating as: root
Password: 
 AUTHENTICATION COMPLETE ===
pi@pi:~$ 
***


-- Package-specific info:

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (990, 'testing'), (500, 'unstable-debug'), 
(500, 'testing-debug'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.10.0-rc8+ (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3
ii  libapparmor12.11.0-2
ii  libaudit1   1:2.6.7-1
ii  libblkid1   2.29.1-1
ii  libc6   2.24-9
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.3-3
ii  libgcrypt20 1.7.6-1
ii  libgpg-error0   1.26-2
ii  libidn111.33-1
ii  libip4tc0   1.6.0+snapshot20161117-5
ii  libkmod223-2
ii  liblz4-10.0~r131-2
ii  liblzma55.2.2-1.2
ii  libmount1   2.29.1-1
ii  libpam0g1.1.8-3.5
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.6-3
ii  libsystemd0 232-17
ii  mount   2.29.1-1
ii  util-linux  2.29.1-1

Versions of packages systemd recommends:
ii  dbus1.10.14-1
ii  libpam-systemd  232-17

Bug#855272: systemd: policykit does not show TUI for remote logins

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Thu, 2017-02-16 at 18:15 +0100, Michael Biebl wrote:
> > Still not getting the full picture here yet.
> 
> What if you simply run "pkexec /bin/true", what *exactly* happens

rrs@chutzpah:~$ pkexec /bin/true
 AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/bin/true' as the super user
Authenticating as: Ritesh Raj Sarraf,,, (rrs)
Password:
polkit-agent-helper-1: error response to PolicyKit daemon:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.
23:09 ♒♒♒☹  => 127  

- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAlil5DwACgkQpjpYo/Lh
dWlwahAAky8L0KGzgWF1gS71lFD10UQQMyX8g+45qI1bXrqVDjolbM48dz9fxCbJ
OX4NfI9ORHX/Y7TSuodQ8fmfjV6BRTPkEPZbGM5YEsMFpaIeQXzwoU0YJ1qrWX9U
ZY2U03/+WIdEkg8uttFSu1tgHYsnle7DGoSGMGexehJOb6/ZJxN0IG8q5N332egR
LM6bFPdB1U6aJWJ5hOJtY2j3VRvqKwmYK/HNuM0xWpOyCuc1JmEYQRgiqNpo0u7B
0uPFcnS0awXtNq++jOpFP5aEm3I6uBHaUfpAn625rZO2twEoFspR5gqTJvzNwDXu
CTaHuCY6rVK0IjtRc/6txzPd2/ThDuu5umZIULrpxOajji+79nFt7WkngTqn9E2R
LD4LlRDEX0ZAJc/+6dJX5cluZj91E6UY6hOgI5KqfAJ0DWbU22bKSgdzSEPDe2wL
VOHEaG1Z0uoZ5JJNtVskhr/QUUcbYW0VfzVNI2oaQlkGTRB1LPaSk4sbNIDY5fHg
eRgXD5oIq0RjYYQ2TfUnzwrFqRusmfBhNT8NgHb5y9LXxVUa4rSvfesppBWBtDBF
V3WywD5h+oBh2KCa6eYiyq1U8dMwl6x1LyTEaOewD3YAmcvmt7p/r5+47o7lpNdb
rhhTiR9bNUNYfyTXgKw+xdgwhWOQgZrgW5ZLTsXKiQTWLCzRZhw=
=M386
-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#855272: systemd: policykit does not show TUI for remote logins

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Thu, 2017-02-16 at 18:14 +0100, Michael Biebl wrote:
> So, you have hostA and hostB, both run an X server.
> 
> You login from hostA to hostB via SSH as userC (and X-forwarding enabled).
> If you run an action which triggers a polkit prompt where exactly?
> On hostA, hostB?

The action (machinectl) is run on hostB over SSH.

> Does userC have a running X session on hostB besides the SSH session?
> 

Yes. hostB also runs Debian Unstable + Xorg + GNOME.

> Still not getting the full picture here yet.

- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAlil45gACgkQpjpYo/Lh
dWkaZg/8DgU9tDw9cuJy30DQjQ1CTzOT5rKlU+Wz2OjyotBLk4A5AkVPAxPOPwPw
cmAsjQplci4L8z5i7SUzWOq85ThRdv0/6RSX/nVsk8IMU7w9XrE1leaJ+O+HnTbb
Fed6Kg2InkLTMpEYbjGSAXzGCb0y0jd+RLDo/+t+LYgrpuQOU+q+FckdfyRXg4YV
szMUBgq6EUczEe7dH6cys7RoaKnSg0Go/l2wSkvmPY+eb00c6JtAMP+JVZpgudYm
xIsVCT0ANHbCD39pA1fRJkHR21TCE2z2uzcJd9OsNIJJUF2Y3O3bwwq5yBjhdi4E
oXS9oWGWYmOg/AqyIFQV+YKSdytLVo4o1O1TkdIIHabV7q67uGzSxN+wk2NWhtyd
DYAF8HHB/4G4p0fKl/7jibQMKkgM4lLMtYIhKMIU2whbXJTaLvRg7MGDAbe04CnN
vczW6rFVdUq9wBJLtXHtOFmaLIwK1ovS+oe6MmDgxof/JQHhAyqSIk3nBYbtZQwZ
u3SzdN4VjcMrx0IXl+fjZCbrCDZgdgzaPpxonjDLSK+dX3+ndoUlsamSy+74hNzP
YD2evFvEsqJ/6aFygzGjBFXxy24DDvMMLAILZ4x/4yI7JQXgcDYve+7/IO0Q3e7p
tTtbBx72kFA0qXVS8KIoPH2B4mksPojsDE84QlqJRYoThthDli8=
=SHKK
-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

[bts-link] source package systemd

[bts-link-upstream]

#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #848044 (http://bugs.debian.org/848044)
# Bug title: systemd: Stretch+Luks system encryption + LVM = delayed shutdown - 
A stop job is waiting for..
#  * https://github.com/systemd/systemd/issues/1620
#  * remote status changed: (?) -> open
usertags 848044 + status-open

thanks

___
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#855272: systemd: policykit does not show TUI for remote logins

[Michael Biebl]

Am 16.02.2017 um 18:14 schrieb Michael Biebl:
> Am 16.02.2017 um 18:05 schrieb Ritesh Raj Sarraf:
>> 1. When X11 forwarding is enabled, it shows the policykit prompt on gdm 
>> display
>> server. And even with the gdm screen locked, one can still feed in the 
>> password
>> there.
> 
> 
> So, you have hostA and hostB, both run an X server.
> 
> You login from hostA to hostB via SSH as userC (and X-forwarding enabled).
> If you run an action which triggers a polkit prompt where exactly?
> On hostA, hostB?
> Does userC have a running X session on hostB besides the SSH session?
> 
> Still not getting the full picture here yet.

What if you simply run "pkexec /bin/true", what *exactly* happens


-- 
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#855272: systemd: policykit does not show TUI for remote logins

[Michael Biebl]

Am 16.02.2017 um 10:42 schrieb Ritesh Raj Sarraf:
> Package: systemd
> Version: 232-17
> Severity: important
> 
> Hello,
> 
> ***
> rrs@chutzpah:~$ echo $DISPLAY
> localhost:10.0
> 14:22 __   _


If that is set, do you have X forwarding enabled over ssh?

What does systemctl (--user) show-environment show?

-- 
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#854041: getting past this issue

[Daniel Pocock]

On 16/02/17 12:42, Felipe Sateler wrote:
> On Thu, Feb 16, 2017 at 8:42 AM, Daniel Pocock  wrote:
>> I tried:
>>
>>   dpkg -i --force-breaks /var/cache/apt/archives/systemd_232-15_amd64.deb
> What breaks did dpkg tell you it had to ignore?
>
>


ifupdown

___
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#854041: getting past this issue

[Felipe Sateler]

On Thu, Feb 16, 2017 at 8:42 AM, Daniel Pocock  wrote:
>
> I tried:
>
>   dpkg -i --force-breaks /var/cache/apt/archives/systemd_232-15_amd64.deb

What breaks did dpkg tell you it had to ignore?


-- 

Saludos,
Felipe Sateler

___
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#854041: getting past this issue

[Daniel Pocock]

I tried:

  dpkg -i --force-breaks /var/cache/apt/archives/systemd_232-15_amd64.deb


and then got the upgrade proceeded successfully with:

  apt-get -f install
  apt-get dist-upgrade

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

Processed: Re: Bug#854697: nbd-client: error in nbd@.service systemd unit file

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 systemd
Bug #854697 [nbd-client] nbd-client: error in nbd@.service systemd unit file
Bug reassigned from package 'nbd-client' to 'systemd'.
No longer marked as found in versions nbd/1:3.15.1-2.
Ignoring request to alter fixed versions of bug #854697 to the same values 
previously set
> retitle -1 systemd-analyze incorrectly claims that Before= on devices has no 
> effect
Bug #854697 [systemd] nbd-client: error in nbd@.service systemd unit file
Changed Bug title to 'systemd-analyze incorrectly claims that Before= on 
devices has no effect' from 'nbd-client: error in nbd@.service systemd unit 
file'.

-- 
854697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
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#855272: systemd: policykit does not show TUI for remote logins

[Ritesh Raj Sarraf]

Package: systemd
Version: 232-17
Severity: important

Hello,

***
rrs@chutzpah:~$ echo $DISPLAY
localhost:10.0
14:22 __   _
rrs@chutzpah:~$ export DISPLAY=""
14:22 __   _
rrs@chutzpah:~$ machinectl login debTemplate
  
Failed to get login PTY: Connection timed out
14:23 ___  => 1  
rrs@chutzpah:~$ sudo machinectl login debTemplate
[sudo] password for rrs:
Connected to machine debTemplate. Press ^] three times within 1s to exit
session.

Debian GNU/Linux 9 deb-template pts/0

deb-template login:

***

AND

***

rrs@chutzpah:~/foo$ systemctl enable systemd-nspawn@fitbit
Failed to enable unit: Connection timed out

rrs@chutzpah:~/foo$ sudo systemctl enable systemd-nspawn@fitbit
[sudo] password for rrs:
Created symlink
/etc/systemd/system/machines.target.wants/systemd-nspawn@fitbit.
service _ /etc/systemd/system/systemd-nspawn@fitbit.service.

rrs@chutzpah:~/foo$ echo $DISPLAY
localhost:10.0

***

This is a remote machine, to which I'm logged over ssh. The login run is
byobu. When I run machinectl, I do not receive a Terminal Interface
prompt. Instead, it shows a user prompt on the machine's gdm display,
which is very wrong because the displayed prompt is user interactable.

On the other hand, as you can see in the log above, over my ssh session,
it complains about timeout.

Shouldn't the tools be able to detect a local session vs a remote
session ?


***
loginctl output

   SESSIONUID USER SEAT TTY 
   297   1000 rrs   
 5   1000 rrs  seat0/dev/tty2   
c1127 Debian-gdm   seat0/dev/tty1   
   299   1000 rrs   
   298   1000 rrs   
 4   1000 rrs  seat0/dev/tty2   

6 sessions listed.

***

I think this is a bug because on my Jessie box running systemd from
backports, this issue is not seen. Ofcourse that box is headless and
does not have gdm installed


***
pi@pi:~$ systemctl daemon-reload 
 AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
Authentication is required to reload the systemd state.
Authenticating as: root
Password: 
 AUTHENTICATION COMPLETE ===
pi@pi:~$ 
***


-- Package-specific info:

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (990, 'testing'), (500, 'unstable-debug'), 
(500, 'testing-debug'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.10.0-rc8+ (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3
ii  libapparmor12.11.0-2
ii  libaudit1   1:2.6.7-1
ii  libblkid1   2.29.1-1
ii  libc6   2.24-9
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.3-3
ii  libgcrypt20 1.7.6-1
ii  libgpg-error0   1.26-2
ii  libidn111.33-1
ii  libip4tc0   1.6.0+snapshot20161117-5
ii  libkmod223-2
ii  liblz4-10.0~r131-2
ii  liblzma55.2.2-1.2
ii  libmount1   2.29.1-1
ii  libpam0g1.1.8-3.5
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.6-3
ii  libsystemd0 232-17
ii  mount   2.29.1-1
ii  util-linux  2.29.1-1

Versions of packages systemd recommends:
ii  dbus1.10.14-1
ii  libpam-systemd  232-17

Versions of packages systemd suggests:
ii  policykit-10.105-17
ii  systemd-container  232-17
ii  systemd-ui 3-4

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.127
ii  udev 232-17

-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandleLidSwitch=ignore


-- no debconf information

___
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#854041: me too, but not getting past "apt-get -f install"

[Daniel Pocock]

I've tried upgrading two systems from jessie to stretch

The first one didn't experience this issue, the second one did.  Both
systems had been upgraded through several versions of Debian over many
years, they had not been clean installs of jessie.

I've tried

   dpkg --purge sysvinit
   apt-get -f install

and so far "apt-get -f install" isn't getting past the issue, it fails
with the same error so the system is now in limbo.

Any suggestions what should be attempted next?

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