![]() ![]() The unit has successfully entered the 'dead' state.ĭez 14 20:03:24 myhost systemd-logind: Session 50 logged out. Subject: Unit UNIT has finished start-upĭez 14 20:03:23 myhost systemd: rvice: Succeeded.ĭez 14 20:03:24 myhost vncsession: pam_unix(tigervnc:session): session closed for user rootĭez 14 20:03:24 myhost systemd: Succeeded. Subject: Unit UNIT has finished shutting downĭez 14 20:03:23 myhost systemd: Started D-Bus User Message Bus. The unit UNIT has successfully entered the 'dead' state.ĭez 14 20:03:23 myhost systemd: Stopped D-Bus User Message Bus. Subject: Unit UNIT has begun shutting downĭez 14 20:03:23 myhost systemd: rvice: Succeeded. "systemctl status -l: Active: inactive (dead)"įrom the logfiles one can see that the session is immediately removed after being established, and this is reported as a success, just like there would something be configured to take care of stale sessions, and mistake the valid session with a stale session?ĭez 14 20:03:22 myhost at-spi-bus-launcher: dbus-daemon: Activating service name='' requested by ':1.0' (uid=0 pid=21640 comm="/usr/libexec/gnome-session-check-accelerated " label="unconfined_u:unconfined_r:unco>ĭez 14 20:03:22 myhost at-spi-bus-launcher: dbus-daemon: Successfully activated service ''ĭez 14 20:03:22 myhost at-spi-bus-launcher: SpiRegistry daemon is running with well-known name - ĭez 14 20:03:22 myhost gnome-session: gnome-session-check-accelerated: GL Helper exited with code 512ĭez 14 20:03:22 myhost gnome-session: gnome-session-check-accelerated: GLES Helper exited with code 512ĭez 14 20:03:22 myhost gnome-session: gnome-session-binary: WARNING: Unable to find required component ''ĭez 14 20:03:22 myhost gnome-session-binary: WARNING: Unable to find required component ''ĭez 14 20:03:22 myhost gnome-session-binary: WARNING: Unable to find required component ''ĭez 14 20:03:22 myhost gnome-session: gnome-session-binary: WARNING: Unable to find required component ''ĭez 14 20:03:22 myhost gnome-session-binary: Entering running stateĭez 14 20:03:22 myhost gnome-session: Unable to init server: Could not connect: Connection refusedĭez 14 20:03:22 myhost gnome-session-f: Cannot open display:ĭez 14 20:03:23 myhost at-spi2-registr: Failed to send session response The connection is closedĭez 14 20:03:23 myhost systemd: Stopping D-Bus User Message Bus. "systemctl status -l: Active: active (running)"īut this only lasts for a few seconds and then turns into: Start vnc server: "systemctl start behavior.Make sure "$HOME/.vnc/" has proper SE-label: "unconfined_u:object_r:xdm_home_t:s0" as generated by "vncpasswd".Leave "/etc/tigervnc/vncserver-config-mandatory" untouched. ![]()
0 Comments
Leave a Reply. |