Bug#852397: marked as done (lightdm does not display a greeter dialog when accessed via XDMCP from a cygwin XWin server)
Your message dated Mon, 20 Aug 2018 20:34:58 +0200
with message-id <f15964562b24849b8f0da8b940521ef78f31c760.camel@debian.org>
and subject line Re: Bug#852397: Problem resolved with latest Cygwin Xorg server
has caused the Debian Bug report #852397,
regarding lightdm does not display a greeter dialog when accessed via XDMCP from a cygwin XWin server
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 owner@bugs.debian.org
immediately.)
--
852397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852397
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: lightdm does not display a greeter dialog when accessed via XDMCP from a cygwin XWin server
- From: Paul Ausbeck <paula@soe.ucsc.edu>
- Date: Mon, 23 Jan 2017 23:41:36 -0800
- Message-id: <c20411b0-00b8-3ab2-788a-6e6769a21462@alumni.cse.ucsc.edu>
Package: lightdm
Version: 1.18.3-1
I attempt to connect via XDMCP to a machine running Debian Sid/Stretch
from a remote cygwin based Xserver. The remote session starts and
displays a black screen with nothing but a mouse cursor in the very
middle. The mouse cursor then jumps to the upper left corner of the
screen and nothing further happens. I am expecting to see the lightdm
greeter which never appears. I have several other machines running
Debian Jessie and Debian Wheezy and can connect to them with no
problems. I have two machines running Sid/Stretch and I can't connect to
either. The problem is specific to Sid/Stretch and I would classify it
as a regression.
I have included the lightdm greeter error log,
/var/log/lightdm/(null)-greeter.log, from the Sid/Stretch machine below.
The WARNING related to the upstart command and the WARNING related to
negative dimensions are present in the greeter log for the physical
monitor/keyboard so I guess that they are not related to the problem. I
would guess that the problem lies with the gdk_pixbuf calls.
I have also included the lightdm greeter log from a successful
connection to a Debian Jessie machine even further below. Note that the
name of the greeter log file is "x-192.168.1.50-0-greeter.log" for a
successful connection and "(null)-greeter.log" for an unsuccessful
connection. Perhaps the name difference is related to the problem.
I don't know enough about the various pieces of this puzzle so I don't
know if I should file this bug against Debian or cygwin. I'm thinking
somehow that I shouldn't have to make changes to my Xserver to connect
to a Sid/Stretch machine when I can connect just fine to Jessie and
Wheezy machines with the same Xserver.
The problem machines are running freshly updated/upgraded Debian
Sid/Stretch: /etc/debian_version 9.0
Unsuccessful greeter log from Debian Sid/Stretch machine:
root@dn2800mt2:/var/log/lightdm# cat \(null\)-greeter.log
** Message: Starting lightdm-gtk-greeter 2.0.2 (Nov 16 2016, 20:48:17)
** Message: [Configuration] Reading file:
/usr/share/lightdm/lightdm-gtk-greeter.conf.d/01_debian.conf
** Message: [Configuration] Reading file:
/etc/lightdm/lightdm-gtk-greeter.conf
Activating service name='org.a11y.atspi.Registry'
Successfully activated service 'org.a11y.atspi.Registry'
** (lightdm-gtk-greeter:1422): WARNING **: [PIDs] Failed to execute
command: upstart
(lightdm-gtk-greeter:1422): GdkPixbuf-CRITICAL **: gdk_pixbuf_new:
assertion 'width > 0' failed
(lightdm-gtk-greeter:1422): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite:
assertion 'GDK_IS_PIXBUF (dest)' failed
(lightdm-gtk-greeter:1422): GLib-GObject-CRITICAL **: g_object_ref:
assertion 'G_IS_OBJECT (object)' failed
** (lightdm-gtk-greeter:1422): WARNING **: [Background] Failed to read
wallpaper: /usr/share/images/desktop-base/login-background.svg
(lightdm-gtk-greeter:1422): GLib-GObject-CRITICAL **: g_object_unref:
assertion 'G_IS_OBJECT (object)' failed
(lightdm-gtk-greeter:1422): Gtk-WARNING **: Drawing a gadget with
negative dimensions. Did you forget to allocate a size? (node menubar
owner GreeterMenuBar)
Gdk-Message: lightdm-gtk-greeter: Fatal IO error 11 (Resource
temporarily unavailable) on X server 192.168.1.50:0.
Successful greeter log from Debian Jessie machine:
root@dn2800mt:/var/log/lightdm# cat x-192.168.1.50-0-greeter.log
(lightdm-gtk-greeter:1686): Gtk-CRITICAL **: gtk_container_foreach:
assertion 'GTK_IS_CONTAINER (container)' failed
(lightdm-gtk-greeter:1686): Gtk-CRITICAL **: gtk_container_foreach:
assertion 'GTK_IS_CONTAINER (container)' failed
(lightdm-gtk-greeter:1686): Gtk-CRITICAL **: gtk_container_foreach:
assertion 'GTK_IS_CONTAINER (container)' failed
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Fri, 2018-08-10 at 16:45 -0700, Paul Ausbeck wrote:
> I recently tested connecting to Debian Stretch from Debian Jessie via XDMCP
> and had no problems. That and the passage of time led me to look to see if a
> newer Xorg server was available from Cygwin and there was. I just downloaded
> the latest Cygwin Xorg server, version 1.20, and it connects to Debian
> Stretch via XDMCP just fine. Therefore, I consider the problem to now be
> resolved.
Thanks for the update, I'm closing the bug then.
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlt7CdIACgkQ3rYcyPpX
RFvr2wgA6tvQijeNgEN445yo4ATr21Y4GggnD6kpNpb1K2OTxG+TRT9tXjQBahpS
4z/LxV7vKCA6hGLyCb4PK9q3GsInKMXD7pS8qNFQYMUp8/boACI1aa/dPx79zbkW
a2H8dSrVPKD2vZSpTacyxAqChUH2AW8TgrMW7spmkqvKm6BWyT5ZF9W7KYWWHyyH
Tzn4I8sostDUAkx2Zo4skE1m2bA+/EensZHdtWHcJ3Xq/p8Oofeysaz7CZ3+XqAr
qNg6dcf3ifJtTSvU/W+3FQVVuE9xv+eUPp/W2F+7V80hADPsv/FGQSoynGobJU59
q73irBd6l6QvsqzW04Fn26PgJxn/mg==
=BBWo
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: