You are not logged in.
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
Last edited by MpRethRu (2020-09-24 13:35:22)
Offline
It looks like in the update, /etc/pam.d/tigervnc was modified, to remove the pam_selinux.so lines
Edit: Nevermind, I must be tired, didn't look
Last edited by pintert3 (2020-09-28 16:14:37)
Things are never what they seem...
Offline