You are not logged in.
I have VNC to physical display enabled by loading libvnc.so which comes with tigervnc 1.4.3-4.
After upgrading xorg to the newest version from 1.17.1-5, it stopped working.
When I accss the 5900 port of the server, X crashes.
I cannot find the log, and I don't know what to do. Any help would be appreciated.
Here is my vnc part conf of the xorg.conf.
**************
Section "Module"
Load "vnc"
EndSection
Section "Screen"
Identifier "Screen0"
Option "SecurityTypes" "None"
EndSection
**************
Offline
Try. x0vncserver. See the wiki.
Offline
I can confirm the crash. It happens as soon as you move the mouse. If you're using startx the log will be in ~/.local/share/xorg, however it doesn't contain any info about the crash.
Found this bugreport for Fedora, it seems a simple recompile should fix it. I've opened a bug on the Arch bugtracker, requesting a rebuild: https://bugs.archlinux.org/task/45492
Offline
@Gusar
Thank you for providing the answer and links.
Unfortunately, installing the package built with PKGBUILD from https://bugs.archlinux.org/task/45492
did not fix the problem.
@graysky
Thank you for suggesting the workaround.
x0vncserver works fairly, but it does not meet my requirement by itself.
I need the service to start with X, and I don't know how to write a systemd service file
that starts x0vncserver with startx command.
Another issue is that keymapping gets messed up when I access from a machine with different keymap from the server's.
Offline
Crap. Now what? It worked on Fedora. Can you try tigervnc-git from AUR? Use AUR4, it has a more up-to-date version than the old AUR.
EDIT: Actually, even the AUR4 version builds tigervnc against xorg-server-1.17.1. Could be a good test though - try that, then build a new version but change _xorgver= at the top of the PKGBUILD to 1.17.2
Last edited by Gusar (2015-06-29 16:16:44)
Offline
I need the service to start with X, and I don't know how to write a systemd service file
that starts x0vncserver with startx command.
Ad the command to ~/.xinitrc ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
@Gusar
Tigervnc-git built with modified PKGBUILD did not work either.
No info in the xorg log which makes just too hard to fix the problem..
@Lone_Wolf
Oh, I totally forgot about xinitrc.
I'll do that until the bug gets fixed. Thank you!
EDIT; Adding x0vncserver to /etc/X11/xinit/xinitrc does not work..
Probably, I have to add it to ~/.xinitrc of every user?
Last edited by smekkleysa (2015-06-30 14:27:56)
Offline
The Fedora bug report has info on where the crash happens. But why did a recompile fix it on Fedora and not on Arch? Could be some patches Fedora applies to X.
One crazy idea - recompile xorg-server. If that doesn't work, file a bug report upstream at https://github.com/TigerVNC/tigervnc/issues and point to the Fedora bug.
Offline
The problem partially fixed!
I simply overwrote my libvnc.so with the libvnc.so from tigervnc-server-module-1.4.3-7.fc22.x86_64.rpm.
And the libvnc from the fedora package was specifically refering much older libraries (libjpeg,libgnutls,libnettle and libhogweed)
than arch's libvnc. So I downloaded the older libraries and placed under /usr/lib/.
Now I can access my physical display via VNC, but only with clients other than tigervnc...
Realvnc viewer and an android app called "Jump" are the among the successful clients.
Offline
You also may use x11vnc as another workaround.
Offline