Edit: Nevermind, I must be tired, didn't look
]]>MpRethRu wrote:I'm dissapointed with how they did a break change with half-assed alternative, and just shrug with it.
I've tried following all suggestions here and still keep having problem with it, with the nearest I could to is just returning error code 0 SUCCESS on systemd start.
I don't know what caused the problem with it even with strace and we just gave up with this. I've already request a proposal to switch to X11vnc to HR because of this.You've provided no info for someone to help you. I updated the wiki distilling out what I thought were key points to get this working. Post what you did and what isn't working.
Here's some logs and configs if you need it.
cat ~/.vnc/config
session=xfce
geometry=800x600
localhost
alwaysshared
cat /etc/pam.d/tigervnc
#%PAM-1.0
# pam_selinux.so close should be the first session rule
#-session required pam_selinux.so close
session required pam_loginuid.so
#-session required pam_selinux.so open
session required pam_namespace.so
session optional pam_keyinit.so force revoke
session required pam_limits.so
-session optional pam_systemd.so
session required pam_unix.so
-session optional pam_reauthorize.so prepare
sudo systemctl --full edit vncserver@:1
[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target[Service]
Type=forking
ExecStart=/usr/bin/vncsession-start %i
PIDFile=/run/vncsession-%i.pid[Install]
WantedBy=multi-user.target
cat /etc/tigervnc/vncserver.users
# TigerVNC User assignment
#
# This file assigns users to specific VNC display numbers.
# The syntax is <display>=<username>. E.g.:
#
# :2=andrew
# :3=lisa:1=server
systemctl status vncserver@:1
vncserver@:1.service - Remote desktop service (VNC)
Loaded: loaded (/etc/systemd/system/vncserver@:1.service; disabled; vendor preset: disabled)
Active: inactive (dead)Sep 24 20:17:40 nexx-server systemd[1]: Starting Remote desktop service (VNC)...
Sep 24 20:17:40 nexx-server systemd[1]: Started Remote desktop service (VNC).
Sep 24 20:17:40 nexx-server systemd[1]: vncserver@:1.service: Succeeded.
sudo strace -ff /usr/bin/vncsession server :1 &> trace.log
journalctl -f &> journal.log ( executing systemctl start vncserver@:1 )
let me know if you can trace the problem
]]>I'm dissapointed with how they did a break change with half-assed alternative, and just shrug with it.
I've tried following all suggestions here and still keep having problem with it, with the nearest I could to is just returning error code 0 SUCCESS on systemd start.
I don't know what caused the problem with it even with strace and we just gave up with this. I've already request a proposal to switch to X11vnc to HR because of this.
You've provided no info for someone to help you. I updated the wiki distilling out what I thought were key points to get this working. Post what you did and what isn't working.
]]>karabaja4 wrote:I'm still having issues with this I'm using Openbox and no systemd (busybox).
Seems it was fixed with 1.11.0-5 (I suspect my previous attempts failed because I didn't set Xsession as executable), Xsession now works normally just by starting "/usr/bin/vncserver :1". Thank you Arch devs.
The recommended method is using the systemd service, see the wiki.
]]>I'm still having issues with this I'm using Openbox and no systemd (busybox).
Seems it was fixed with 1.11.0-5 (I suspect my previous attempts failed because I didn't set Xsession as executable), Xsession now works normally just by starting "/usr/bin/vncserver :1". Thank you Arch devs.
]]>I still noticed a problem, the session starts fine, but when I try to start LXTerminal it now puts me in "/" (root dir) instead of $HOME. LXTerminal shortcut that starts it has a preference "working dir" but even if I set it to "/home/<user>" bash still ends up in "/" when it starts which is weird. Env vars seem correct, user id, $HOME, etc.
Does anything else need to happen in the systemd unit or elsewhere to change the working dir to the user's $HOME before the session starts?
Sirarch, did you find a solution to this? I was hit with the same phenomena. I'm on Plasma using Konsole. I have set /usr/bin/fish as the default shell in Konsole ages ago. The solution now was to reset the default shell setting in Konsole, restart it, and set fish back as the default shell. This has misteriously solved the problem of setting my working dir to /. Hopefully this will work for you as well.
]]>@karabaja4 - Did you read the response from the tigervnc developer in the issue I linked?
I did.
There must have been some misunderstanding, at least partially. TigerVNC does not require Xorg as it ships its own replacement in the form of Xvnc. It does however require large parts of Xorg's infrastructure as it tries to start a similar session. It also requires systemd as sessions must be run as services.
I have no idea what the environment on Android looks like so I'm afraid I don't know if it has what's required. Our target is standard Linux distributions and I'm afraid we don't have the resources to deal with exotic stuff.
Please see the tigervnc-users mailing list for more help on the new model. There are already some tips there from people.
It doesn't explain why systemd is required though, except that "it must be run as systemd service". As I understand it, systemd service is nothing but a wrapper around a binary or script (in this case, vncsession) which makes it run as a daemon under a specific user. What makes it run in a systemd service that wouldn't make it run as a manual command?
]]>It also requires systemd as sessions must be run as services.
Why is this exactly?
]]>I'm still having issues with this I'm using Openbox and no systemd (busybox).
See: https://github.com/TigerVNC/tigervnc/issues/1094
It also requires systemd as sessions must be run as services.
I have done the following:
1. Added following to $HOME/.vnc/config:
session=openbox
2. Added user maping to /etc/tigervnc/vncserver.users
:1=igor
3. Added /etc/X11/Xsession file with the following content:
exec openbox-session
4. The following file exists /usr/share/xsessions/openbox.desktop
5. The following commands do nothing:
~ >> vncserver :1
vncserver: Couldn't find suitable Xsession.
~ >> sudo /usr/bin/vncsession igor :1
# just exits, does nothing, same error as above in $HOME/.vnc/*.log
Here is the output of
sudo strace -ff /usr/bin/vncsession igor :1
$ ll /usr/share/xsessions/
total 28
drwxr-xr-x 2 root root 4096 Jul 11 13:06 ./
drwxr-xr-x 131 root root 12288 Aug 28 06:38 ../
-rw-r--r-- 1 root root 1507 Jul 7 08:31 LXDE.desktop
-rw-r--r-- 1 root root 198 May 23 19:55 openbox.desktop
-rw-r--r-- 1 root root 205 May 23 19:55 openbox-kde.desktop
I set session=LXDE in ~/.vnc/config
Also make sure you don't have a ~/.vnc/xstartup or similar file, though not sure that file is used anymore.
]]>