Re: Bug#592549: gdm3 on {re,}start on kfreebsd displays only a black screen with an X cursor
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Petr Salinger wrote:
[snip]
> State of other display managers, mainly collected from BTS.
>
> * xdm: seems be fine
Also
* wdm: seems to be fine
> * gdm on initial start at bootup does not allow keyboard input (#586539)
> * kdm on initial start at bootup does not allow keyboard input (#586540)
>
> When the start of gdm/kdm is not during boot, it works fine,
> sort of race condition on boot between getty on vt2 and gdm/kdm on vt2.
>
> * slim just shows a black screen (#586593)
>
> Wrong usage of vfork, with fork() works (tested on non-bootup) fine.
I confirm that the vfork -> fork works. I've added this to the bug
report, along with the quilt patch and I've tagged the bug as having a
patch using control@b.d.o. Note that slim has a non-kfreebsd specific
bug of stop and restart not working.
Are there any other display managers apart these ones that we can test?
Mike.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBCAAGBQJMZEmoAAoJENdybD6q+OPv2TUQALYx5Y1qLrR3+Or3bmELhJvW
Yn54KYQFOK3vbVbJlMGIS3jW3QQsoCRQaK7J5mCwgAEiIL1AnYgd+o2NFSDTznrH
MDoDnEuH0vss7lBnRAIejsTKKFVUdkASv4/A506SkSMYMyJummqFIK3ZaGxUDbdy
aUlxFGjP8Ls7zS53ADjPfr5alhgCOnej74o2nwBOeyBKM98QNPbKgH+zbM9O5Gab
NeaKodEhau99EBRnF7LmqUKfW9k5F99atxGAvqlFLyZmCvOVR7MFvENFsPlKvtLd
SA8ngbNCMPWQqelK92rm/qCCDhlhnJWlHHNXIZ+fprVjne4WeAsDtqtHBKHH0IiI
P3dnraltRtV28LgMq7A8nH4ncntUZbF66HxUR9lxw3P9W1b3gilBlNjp7PsJ09DZ
RFN84YFIR7nDtXBGGr8tHZrpvRYcGbsO5ZRI1g6CkE1rhNKqD7hlabOBQxFvDu+d
nf/0Wda0wr0f06CEObuwNepIQdBwPrjRn4Pmc3SoqbOGo2rbmj/e190+iZu1YEcd
e4FFkiIxc4rN/Mnu2HJdn/81NFGE0qkQW0NJ+xtHGtSGgr4yx8d85y/o+FwfP7ei
GQ0TtKxgdfMGFKAgbKePzG3F35ZRHwjhZdUR7PUAltyNsRmvQJtky9dnVV4XzW0M
advLLsngWNIPXiB7z+Al
=PUKx
-----END PGP SIGNATURE-----
Reply to: