Same problem affects me on Ubuntu 20.04 system. I have wifi adapter configured
as hotspot. The hotspot also seems to be working normally but the log files are
full of messages:
wpa_supplicant[1359]: wlp9s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Best regards,
Michael.
--
You received this bug
Hello, I am also affected by this bug - cannot login using any and all XDMCP
clients that I know of into my server running Ubuntu 14.04. I am reluctant to
switch to lightdm from gdm for a variety of reasons. I also would like to
understand how active this bug is. It seems to me that if it's a
Just to reproduce the problem you are welcome to get it from
my ftp server: ftp://mplotkin.com
(login as anonymous).
Sorry, it can be slow - I am using a very old computer for ftp...
You need to install all three (appropriate of course) packages
on the server and just nxclient on the client.
I'm sorry - I don't understand this at all: local gnome-session always
worked
all right without this fix in trusty-proposed, and the remote gnome-session
doesn't start at all with this fix in trusty-proposed but without other
changes
from ppa:rtandy/flashback repository. At least this was my
Did reasonably extensive testing last night of the proposed fix for
Trusty.
I believe that my results are very similar to Xavier: after I installed all
updates related to this bug from trusty-proposed repository (pre-released)
I couldn't start remote X2go session at all. In /var/log/messages I
Thank you Michael, very much, but in a sense my question was
whether there is (there would be) a way to have this option -
--disable-acceleration-check always (by default), so my users
wouldn't need to change their existing setups of many NX client
sessions that they already have.
Also NX has
Thank you Ryan for helping to resolve this problem. I've been waiting
anxiously for this problem being fixed because it's the main reason I
cannot start using 14.04 (and have to use 12.04) on a lot of systems.
I have a question - do you see any problems using original NX software
with this
Hello,
I'm sorry to bother, I know that practically the same question was asked
a few months ago by Nicholas DiPiazza, but it wasn't directly answered.
- Is there any time frame to fix this problem in the official
distribution of Trusty? Similarly to what was said previously - this
is the main
