[Desktop-packages] [Bug 1901450] [NEW] XDMCP does not work on Raspi Groovy while it works fine on Groovy Ubuntu Mate AMD64

2020-10-25 Thread Ryutaroh Matsumoto
Public bug reported:

The following configuration enables XDMCP of LightDM in Ubuntu Mate Groovy.
But it fails on Groovy Raspberry Pi 64bit.

[LightDM]
start-default-seat=false
lock-memory=false
remote-sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions:/usr/share/wayland-sessions
[XDMCPServer]
enabled=true
#port=177
listen-address=127.0.0.1

journalctl -e shows the following:

Oct 26 07:56:41 raspi-groovy systemd[1]: Started Session 1 of user root.
Oct 26 07:57:10 raspi-groovy systemd[1]: 
/etc/systemd/system/Xtigervnc@.service:9: Special user nobody configured, this 
is not safe!
Oct 26 07:57:10 raspi-groovy systemd[1]: Created slice system-Xtigervnc.slice.
Oct 26 07:57:10 raspi-groovy systemd[1]: Starting XVNC Per-Connection Daemon 
(192.168.1.75:41812)...
Oct 26 07:57:10 raspi-groovy systemd[1]: Started XVNC Per-Connection Daemon 
(192.168.1.75:41812).
Oct 26 07:57:11 raspi-groovy lightdm[893]: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
Oct 26 07:57:11 raspi-groovy lightdm[893]: PAM adding faulty module: 
pam_kwallet.so
Oct 26 07:57:11 raspi-groovy lightdm[893]: PAM unable to 
dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared 
object file: No such file or directory
Oct 26 07:57:11 raspi-groovy lightdm[893]: PAM adding faulty module: 
pam_kwallet5.so
Oct 26 07:57:11 raspi-groovy lightdm[893]: pam_unix(lightdm-greeter:session): 
session opened for user lightdm by (uid=0)
Oct 26 07:57:11 raspi-groovy systemd[1]: Created slice User Slice of UID 108.
Oct 26 07:57:11 raspi-groovy systemd[1]: Starting User Runtime Directory 
/run/user/108...
Oct 26 07:57:11 raspi-groovy systemd-logind[530]: New session c1 of user 
lightdm.
Oct 26 07:57:11 raspi-groovy systemd[1]: Finished User Runtime Directory 
/run/user/108.
Oct 26 07:57:11 raspi-groovy systemd[1]: Starting User Manager for UID 108...
Oct 26 07:57:11 raspi-groovy systemd[897]: pam_unix(systemd-user:session): 
session opened for user lightdm by (uid=0)
Oct 26 07:57:12 raspi-groovy systemd[902]: gnome-systemd-autostart-condition 
not found: No such file or directory
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-org.gnome.SettingsDaemon.PrintNotifications-autostart.service, 
startup phases are not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-gnome\x2dinitial\x2dsetup\x2dcopy\x2dworker-autostart.service, 
startup phases are not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-org.gnome.SettingsDaemon.MediaKeys-autostart.service, startup 
phases are not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-org.gnome.SettingsDaemon.Smartcard-autostart.service, startup 
phases are not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-gnome\x2dkeyring\x2dsecrets-autostart.service, startup phases are 
not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-at\x2dspi\x2ddbus\x2dbus-autostart.service, startup phases are 
not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-org.gnome.SettingsDaemon.Housekeeping-autostart.service, startup 
phases are not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: gnome-systemd-autostart-condition 
not found: No such file or directory
Oct 26 07:57:12 raspi-groovy systemd[902]: gnome-systemd-autostart-condition 
not found: No such file or directory
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-gnome\x2dkeyring\x2dssh-autostart.service, startup phases are not 
supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-org.gnome.SettingsDaemon.Color-autostart.service, startup phases 
are not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-org.gnome.SettingsDaemon.Wwan-autostart.service, startup phases 
are not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-xdg\x2duser\x2ddirs-autostart.service, startup phases are not 
supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-pulseaudio-autostart.service, startup phases are not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-org.gnome.SettingsDaemon.Rfkill-autostart.service, startup phases 
are not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-gnome\x2dkeyring\x2dpkcs11-autostart.service, startup phases are 
not supported.
Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG 
autostart app-org.gnome.SettingsDaemon.A11ySettings-autostart.service, startup 
phases are 

[Desktop-packages] [Bug 1901376] [NEW] xdmcp stopped working with groovy gdm3

2020-10-24 Thread Ryutaroh Matsumoto
Public bug reported:

On Ubuntu Focal

[xdmcp]
Enable=tue
ShowLocalGreeter=false

in /etc/gdm3/custom.conf enabled XDMCP.
But the same config. has no effect in Groovy.

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: groovy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1901376

Title:
  xdmcp stopped working with groovy gdm3

Status in gdm3 package in Ubuntu:
  New

Bug description:
  On Ubuntu Focal

  [xdmcp]
  Enable=tue
  ShowLocalGreeter=false

  in /etc/gdm3/custom.conf enabled XDMCP.
  But the same config. has no effect in Groovy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901376/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1895420] [NEW] gdm3 with xdmcp does not show login box to a remote X server

2020-09-12 Thread Ryutaroh Matsumoto
Public bug reported:

With a fresh installation of Ubuntu 20.04.1,
adding the following to /etc/gdm/custom.conf

[xdmcp]
Enable=tue
ShowLocalGreeter=false

works fine. But with ShowLocalGreeter=true,
gdm3 does not show a login box to a remote X server.
journalctl -u gdm shows "GdmDisplay: Session never registered, failling"

If the combination of Enable=true and ShowLocalGreeter=true is unsupported,
Enable=true should also mean ShowLocalGreeter=false.

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: gdm3 (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: focal

** Bug watch added: Debian Bug tracker #970212
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970212

** Also affects: gdm3 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970212
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1895420

Title:
  gdm3 with xdmcp does not show login box to a remote X server

Status in gdm3 package in Ubuntu:
  New
Status in gdm3 package in Debian:
  Unknown

Bug description:
  With a fresh installation of Ubuntu 20.04.1,
  adding the following to /etc/gdm/custom.conf

  [xdmcp]
  Enable=tue
  ShowLocalGreeter=false

  works fine. But with ShowLocalGreeter=true,
  gdm3 does not show a login box to a remote X server.
  journalctl -u gdm shows "GdmDisplay: Session never registered, failling"

  If the combination of Enable=true and ShowLocalGreeter=true is unsupported,
  Enable=true should also mean ShowLocalGreeter=false.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1895420/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1894356] Re: could not acquire name on session bus by simultaneous login by XDMCP and keyboard

2020-09-04 Thread Ryutaroh Matsumoto
** Bug watch added: Debian Bug tracker #969564
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969564

** Also affects: lightdm (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969564
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1894356

Title:
  could not acquire name on session bus by simultaneous login by XDMCP
  and keyboard

Status in Light Display Manager:
  New
Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  New
Status in lightdm package in Debian:
  Unknown

Bug description:
  This symptom is observed with Ubuntu Mate 20.04.

  1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as

  [XDMCPServer]
  enabled=true

  and restart lightdm.

  2. Login as a normal user from keyboard.

  3. Login as the same user as 2 from XDMCP gives
  "Could not acquire name on session bus"
  and I cannot login from XDMCP.
  Without Step 2, XDMCP login succeeds.

  The same symptom is reported at
  https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001
  which recommends removal of "dbus-user-session" Ubuntu package.

  I worked around the above issue by putting
  "unset DBUS_SESSION_BUS_ADDRESS"
  in /etc/X11/Xsession.d/

  The same issue is also reported at
  https://bugs.launchpad.net/ubuntu-mate/+bug/1769353

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1894356/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1894356] [NEW] could not acquire name on session bus by simultaneous login by XDMCP and keyboard

2020-09-04 Thread Ryutaroh Matsumoto
Public bug reported:

This symptom is observed with Ubuntu Mate 20.04.

1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as

[XDMCPServer]
enabled=true

and restart lightdm.

2. Login as a normal user from keyboard.

3. Login as the same user as 2 from XDMCP gives
"Could not acquire name on session bus"
and I cannot login from XDMCP.
Without Step 2, XDMCP login succeeds.

The same symptom is reported at
https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001
which recommends removal of "dbus-user-session" Ubuntu package.

I worked around the above issue by putting
"unset DBUS_SESSION_BUS_ADDRESS"
in /etc/X11/Xsession.d/

The same issue is also reported at
https://bugs.launchpad.net/ubuntu-mate/+bug/1769353

** Affects: lightdm
 Importance: Undecided
 Status: New

** Affects: ubuntu-mate
 Importance: Undecided
 Status: New

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: ubuntu

** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-mate
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1894356

Title:
  could not acquire name on session bus by simultaneous login by XDMCP
  and keyboard

Status in Light Display Manager:
  New
Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  This symptom is observed with Ubuntu Mate 20.04.

  1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as

  [XDMCPServer]
  enabled=true

  and restart lightdm.

  2. Login as a normal user from keyboard.

  3. Login as the same user as 2 from XDMCP gives
  "Could not acquire name on session bus"
  and I cannot login from XDMCP.
  Without Step 2, XDMCP login succeeds.

  The same symptom is reported at
  https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001
  which recommends removal of "dbus-user-session" Ubuntu package.

  I worked around the above issue by putting
  "unset DBUS_SESSION_BUS_ADDRESS"
  in /etc/X11/Xsession.d/

  The same issue is also reported at
  https://bugs.launchpad.net/ubuntu-mate/+bug/1769353

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1894356/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp