BigCheeZ
BigCheeZ
PostsComments
CCoder.com
Created by Spiked_Grape on 11/4/2024 in #help
Kasm template / module
I updated the host machine to Ubuntu 24.04. When I do this, kasmVNC works as expected without the security_opts option.
30 replies
CCoder.com
Created by Spiked_Grape on 11/4/2024 in #help
Kasm template / module
I've got it working now. I think the issue is that the host system I am using is still on Ubuntu 20.04 and there may be a kernel mismatch. As a temporary workaround, I added security_opts = [ "seccomp:unconfined" ] to my docker_container resource in TF and now it works. It seems I need to look into upgrading the base OS soon.
30 replies
CCoder.com
Created by Spiked_Grape on 11/4/2024 in #help
Kasm template / module
The server I am running this on does not have a GPU. I wonder if this is causing the issue.
30 replies
CCoder.com
Created by Spiked_Grape on 11/4/2024 in #help
Kasm template / module
(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.969: Unable to launch "xfdesktop": Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.970: Unable to launch "sh -c "systemctl --user start xfce4-notifyd.service 2>/dev/null || exec /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd"" (specified by autostart/xfce4-notifyd.desktop): Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.971: Unable to launch "xfsettingsd" (specified by autostart/xfsettingsd.desktop): Failed to close file descriptor for child process (Operation not permitted)
(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.969: Unable to launch "xfdesktop": Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.970: Unable to launch "sh -c "systemctl --user start xfce4-notifyd.service 2>/dev/null || exec /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd"" (specified by autostart/xfce4-notifyd.desktop): Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.971: Unable to launch "xfsettingsd" (specified by autostart/xfsettingsd.desktop): Failed to close file descriptor for child process (Operation not permitted)
30 replies
CCoder.com
Created by Spiked_Grape on 11/4/2024 in #help
Kasm template / module
Running /home/coder/.vnc/xstartup
+ exec xfce4-session
 2024-11-19 14:24:40,901 [DEBUG] Selection: Selection owner change for _DBUS_SESSION_BUS_SELECTION_coder_dae41af03ba14667a7c6dc4999b94cb0
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
glx: failed to create drisw screen

(xfce4-session:729): dbind-WARNING **: 14:24:40.942: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
_IceTransmkdir: ERROR: euid != 0,directory /tmp/.ICE-unix will not be created.

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.960: No GPG agent found

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.962: Failed to spawn ssh-agent: Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.963: failed to call dbus-update-activation-environment. Output was (null), error was Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.965: Unable to launch "xfwm4": Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.966: Unable to launch "xfsettingsd": Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.967: Unable to launch "xfce4-panel": Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.968: Unable to launch "Thunar": Failed to close file descriptor for child process (Operation not permitted)
Running /home/coder/.vnc/xstartup
+ exec xfce4-session
 2024-11-19 14:24:40,901 [DEBUG] Selection: Selection owner change for _DBUS_SESSION_BUS_SELECTION_coder_dae41af03ba14667a7c6dc4999b94cb0
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
glx: failed to create drisw screen

(xfce4-session:729): dbind-WARNING **: 14:24:40.942: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
_IceTransmkdir: ERROR: euid != 0,directory /tmp/.ICE-unix will not be created.

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.960: No GPG agent found

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.962: Failed to spawn ssh-agent: Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.963: failed to call dbus-update-activation-environment. Output was (null), error was Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.965: Unable to launch "xfwm4": Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.966: Unable to launch "xfsettingsd": Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.967: Unable to launch "xfce4-panel": Failed to close file descriptor for child process (Operation not permitted)

(xfce4-session:729): xfce4-session-WARNING **: 14:24:40.968: Unable to launch "Thunar": Failed to close file descriptor for child process (Operation not permitted)
30 replies
CCoder.com
Created by Spiked_Grape on 11/4/2024 in #help
Kasm template / module
HI @Atif , thanks for the reply. I started off with the 'base' and 'desktop' images from here: https://github.com/coder/images/tree/main/images. I did modify the base image by removing the docker packages. I then use the desktop image as the base for my team's development image. This image's dockerfile installs tools needed by the team. This image has been used previously with xfce and noVNC based on a deprecated image from the repo above. That image has been working fine, but I wanted to test out moving to kasmVNC for moving forward. In the VNC log file I can see these warnings/messages when the vncserver is started.
30 replies
CCoder.com
Created by Spiked_Grape on 11/4/2024 in #help
Kasm template / module
Just an FYI, I was having the same issue where everytime I loaded the kasmVNC window, it would show the "Cound not connect to server" error. I had also modififed subdomain to be "false". I do have the option of enabling subdomains, so I did so. kasmVNC now can connect to the VNC server it seems, but the window is entirely black. The only thing I can see is the kasmVNC controls on the left. I'm guessing this is an issue with xfce4, but I'm not sure what.
30 replies