Your message dated Thu, 16 Feb 2017 20:09:14 +0100
with message-id <[email protected]>
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 [email protected]
immediately.)
--
855272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855272
Debian Bug Tracking System
Contact [email protected] 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/[email protected].
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
SESSION UID USER SEAT TTY
297 1000 rrs
5 1000 rrs seat0 /dev/tty2
c1 127 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 libapparmor1 2.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 libidn11 1.33-1
ii libip4tc0 1.6.0+snapshot20161117-5
ii libkmod2 23-2
ii liblz4-1 0.0~r131-2
ii liblzma5 5.2.2-1.2
ii libmount1 2.29.1-1
ii libpam0g 1.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 dbus 1.10.14-1
ii libpam-systemd 232-17
Versions of packages systemd suggests:
ii policykit-1 0.105-17
ii systemd-container 232-17
ii systemd-ui 3-4
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.127
ii udev 232-17
-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandleLidSwitch=ignore
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 16.02.2017 um 19:41 schrieb Ritesh Raj Sarraf:
> But I'm again unhappy with this bug report. :-(
> I rebooted the machine, which may have happened after a week of uptime, and
> now I cannot reproduce the problem.
> I need to improve my bug filing skills.
>
> Do you see anything useful in this bug report? Otherwise, lets close this and
> sorry about the noise.
Not really, no.
I'm not able to reproduce the problem either, fwiw.
So yes, let's close it until we have a proper idea how to reproduce it.
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
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
