| View previous topic :: View next topic |
| Author |
Message |
manu.rhel
n00b
Joined: 11 Apr 2014
Posts: 42
|
 Posted: Thu Sep 26, 2024 10:52 am Post subject: not able to start tigervnc |
 |
|
Hi Experts, I have recently installed TigerVNC server on a Gentoo machine -
| Quote: | USE="server" emerge --ask --update --newuse net-misc/tigervnc
|
Also I have installed xfce using below commands -
| Quote: | emerge --ask xfce-base/xfce4-meta xfce-extra/xfce4-notifyd
emerge --ask --deselect=y xfce-extra/xfce4-notifyd
emerge --ask x11-terms/xfce4-terminal
|
But when I am trying to bring up vncserver from one of the user accounts, I get the below message -
| Quote: | $ vncserver :11
~/.vnc is deprecated, please consult 'man vncsession' for paths to migrate to. at /usr/bin/vncserver line 43.
Using desktop session Xsession
xauth: (stdin):1: bad display name "XXXX:11" in "add" command
New 'XXXX:11 (xxxxvnc)' desktop is XXXX:11
Starting desktop session Xsession
Xvnc TigerVNC 1.14.0 - built Sep 26 2024 18:41:47
Copyright (C) 1999-2024 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12101013
Thu Sep 26 18:47:00 2024
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5911
vncext: created VNC server for screen 0
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Could not resolve keysym XF86CameraAccessEnable
> Warning: Could not resolve keysym XF86CameraAccessDisable
> Warning: Could not resolve keysym XF86CameraAccessToggle
> Warning: Could not resolve keysym XF86NextElement
> Warning: Could not resolve keysym XF86PreviousElement
> Warning: Could not resolve keysym XF86AutopilotEngageToggle
> Warning: Could not resolve keysym XF86MarkWaypoint
> Warning: Could not resolve keysym XF86Sos
> Warning: Could not resolve keysym XF86NavChart
> Warning: Could not resolve keysym XF86FishingChart
> Warning: Could not resolve keysym XF86SingleRangeRadar
> Warning: Could not resolve keysym XF86DualRangeRadar
> Warning: Could not resolve keysym XF86RadarOverlay
> Warning: Could not resolve keysym XF86TraditionalSonar
> Warning: Could not resolve keysym XF86ClearvuSonar
> Warning: Could not resolve keysym XF86SidevuSonar
> Warning: Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
[mi] mieq: warning: overriding existing handler (nil) with 0x5646746afb90 for event 2
[mi] mieq: warning: overriding existing handler (nil) with 0x5646746afb90 for event 3
xinit: XFree86_VT property unexpectedly has 0 items instead of 1
xinit: connection to X server lost
waiting for X server to shut down ComparingUpdateTracker: 0 pixels in / 0 pixels out
ComparingUpdateTracker: (1:-nan ratio) |
When I try to connect to this VNC Server from another machine, I get the below message on the Client machine -
| Quote: | # vncviewer 172.18.2.34:5911
TigerVNC Viewer v1.13.1
Built on: 2024-09-26 06:03
Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
Can't open display:
|
Please suggest how to get this fixed.
Thanks for all your help in advance |
|
| Back to top |
|
 |
sublogic
Apprentice
Joined: 21 Mar 2022
Posts: 269
Location: Pennsylvania, USA
|
| Posted: Thu Sep 26, 2024 9:40 pm Post subject: |
|
|
| I haven't tried to start a VNC server from a user account, but it works fine as a service. Edit /etc/tigervnc/vncserver.users to associate a userid to a VNC screen, then start the service; for example, with Openrc, rc-service tigervnc.1 start . Modify as needed if you use systemd. |
|
| Back to top |
|
|
Havin_it
Veteran
Joined: 17 Jul 2005
Posts: 1260
Location: Edinburgh, UK
|
| Posted: Thu Oct 17, 2024 5:05 pm Post subject: |
|
|
Hi manu.rhel,
First I'd better advise you that upstream TigerVNC have deprecated the vncserver script, and will only be supporting running the server via a service (a systemd service for that matter, but so far our Gentoo hero devs are working around that for us  ). Just to warn you, you may in future only be able to start it as a service; of course if you want to be able to start it as a user, you can simply use sudo to allow your user to start the service on-demand. (I won't bore you with the details now but just ask if you want them.)
That said, vncserver was still working last time I tried it. I'm not certain but the problem might be the lack of a config telling vncserver to start the XFCE session. For this you need a line like the following in ~/.vnc/config, or ~/.config/tigervnc/config if you want to get with the preferred current location:
Note: The value is a guess on my part, it should be named like whatever the XFCE session script is called in /usr/share/xsessions/ folder.
If you already have that, it's possible you need to add the following to /etc/tigervnc/vncserver.users (I think this is only needed for service use but I could be wrong)
After that you could check whether :1 works instead of :11 (if you still need the server to be on port 5911, I believe that's also doable). I did find it wouldn't let me use :0, which I'm sure they have their reasons for but is a bit dumb on a headless server  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
