I was able to start up x11vnc by disabling Wayland in the
/etc/gdm3/custom.conf file and rebooting as per this post:
https://askubuntu.com/questions/981313/x11vnc-on-ubuntu-17-10-not-
running-on-startup. I'm not sure what I lose by changing the DM, but for
now it seems to be OK.
--
You received t
Sorry, not understanding your "fix" here. I tried the change you note,
and restarted x11vnc (server) ... it's still not listening on the
defined ports.
Or is this not to fix x11vnc?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
UPDATE: I resolved my console only issue by changing
/etc/X11/Xwrapper.config from default
allowed_users = console
allowed_users = anybody
http://manpages.ubuntu.com/manpages/artful/man1/Xorg.wrap.1.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
disabled vino and installed x11vnc on artful, and can only login using
macos screen sharing app when i already have a xorg session active. if i
logout on the console, then can't start a remote session. pwd is set and
systemd service is running...
/usr/bin/x11vnc -auth guess -forever -loop -noxdama
It seems that Wayland is not supported by x11vnc（ which user libvncserver）
because Wayland doesn't have a screen capture api for x11vnc to use？
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711948
Ti
I have the same problem:
> x11vnc -usepw
...
03/09/2017 15:17:28 Default visual ID: 0x24
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 73 (X_GetImage)
Serial number of failed request: 41
Current serial number in output stream: 41
Yesterda
Hmmm ... you mean you logged in with that Window Manager? I can't even
connect to the machine any more - and checking it locally, the same
issue here ... it's not even listening on the port any more.
Thanks though!
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
What fixed the issue for me was reverting to "Ubuntu on Xorg".
The noob that I am can not explain why, but somehow this worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711948
Title:
x11vnc N
Arrgh ... OK, was having issues getting the new desktop working.
Uninstalled / reinstalled the display manager, moving it from lightdm to
gdm3 (the default, right?) => now VNC is broken on the second machine as
well ... :-(.
--
You received this bug notification because you are a member of Ubuntu
Hi,
Interestingly enough, I just upgraded a machine from 17.04 to 17.10 ->
VNC works fine. But the machine that was on the alpha / beta builds
still isn't working.
Hmmm ... is there a way to "clean reset" x11vnc on the machine that was
running older builds? Seems this should be able to work.
Tha
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: x11vnc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711948
Title:
x11
x11vnc not working under 17.10 artful
Ubuntu Artful Aardvark (development branch) (GNU/Linux 4.12.0-12-generic
x86_64)
$ x11vnc -display :0
03/09/2017 15:17:28 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 14552
03/09/2017 15:17:28 Using X display :0
03/09/2017 15:17:28 rootwin: 0x270 reswi
12 matches
Mail list logo
