[Bug] - OpenSuse 15 Workspace not working on Rhel 9.3 based (Rocky) host

[verchalent]

Describe the bug Launching the OpenSuse 15 Desktop Workspace from the Kasm repo yields a black screen instead of the desktop.

To Reproduce Steps to reproduce the behavior:

1. Install Suse Workspace from Kasm registry
2. Launch Workspace

Expected behavior With all other desktop images tested (Fedora, Ubuntu, Kali, etc) the desktop is displayed/visible once the container launches.

Screenshots

Workspaces Version e.g Version 1.12

Workspaces Installation Method SingleServer CE

Client Browser (please complete the following information):

• OS: Fedora/Win11/MacOS
• Browser Firefox/Chrome
• Version latest

Workspace Server Information (please provide the output of the following commands):

• Uname -a Linux 5.14.0-362.24.1.el9_3.0.1.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 4 22:31:43 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
• cat /etc/os-release NAME="Rocky Linux" VERSION="9.3 (Blue Onyx)" ID="rocky" ID_LIKE="rhel centos fedora" VERSION_ID="9.3" PLATFORM_ID="platform:el9" PRETTY_NAME="Rocky Linux 9.3 (Blue Onyx)" ANSI_COLOR="0;32" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:rocky:rocky:9::baseos" HOME_URL="https://rockylinux.org/" BUG_REPORT_URL="https://bugs.rockylinux.org/" SUPPORT_END="2032-05-31" ROCKY_SUPPORT_PRODUCT="Rocky-Linux-9" ROCKY_SUPPORT_PRODUCT_VERSION="9.3" REDHAT_SUPPORT_PRODUCT="Rocky Linux" REDHAT_SUPPORT_PRODUCT_VERSION="9.3"
• sudo docker info Client: Docker Engine - Community Version: 26.1.1 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.14.0 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.27.0 Path: /usr/libexec/docker/cli-plugins/docker-compose scan: Docker Scan (Docker Inc.) Version: v0.23.0 Path: /usr/libexec/docker/cli-plugins/docker-scan
• sudo docker ps | grep kasm 6fb5fd02f6a3 kasmweb/opensuse-15-desktop:1.15.0 "/dockerstartup/kasm…" 6 minutes ago Up 6 minutes 1a48c4c6399d kasmweb/nginx:1.25.3 "/docker-entrypoint.…" 2 weeks ago Up 4 days 80/tcp, 0.0.0.0:443->443/tcp, ::: 443->443/tcp kasm_proxy 576ffcf20489 kasmweb/share:1.15.0 "/bin/sh -c '/usr/bi…" 2 weeks ago Up 4 days (healthy) 8182/tcp kasm_share ed7d988097d0 kasmweb/agent:1.15.0 "/bin/sh -c '/usr/bi…" 2 weeks ago Up 4 days (healthy) 4444/tcp 3ab01d9f1d63 kasmweb/manager:1.15.0 "/bin/sh -c '/usr/bi…" 2 weeks ago Up 4 days (healthy) 8181/tcp abf53901adf9 redis:5-alpine "docker-entrypoint.s…" 2 weeks ago Up 4 days 6379/tcp kasm_redis b4d88fc8aa8e kasmweb/api:1.15.0 "/bin/sh -c '/usr/bi…" 2 weeks ago Up 4 days (healthy) 8080/tcp kasm_api a07122a98078 kasmweb/kasm-guac:1.15.0 "/dockerentrypoint.sh" 2 weeks ago Up 4 days (healthy) kasm_guac 384d3084edde postgres:12-alpine "docker-entrypoint.s…" 2 weeks ago Up 4 days (healthy) 5432/tcp kasm_db

Additional context Add any other context about the problem here.

[thelamer]

The only thing I could get working in this scenario was to set this as the exec config for the workspace: ("Docker Exec Config (JSON)" under the workspace settings)

{
  "first_launch": {
    "user": "1000",
    "cmd": "bash -c '/usr/bin/desktop_ready && (dbus-launch xfdesktop &); (dbus-launch xfwm4 --replace &); (dbus-launch xfce4-panel &)'"
  }
}

Something about the RHEL 9 host does not pass around the dbus info properly so each individual component of what makes up XFCE needs to be launched with dbus-launch. This delays the init a bit but it does function normally after init.

[verchalent]

{ "first_launch": { "user": "1000", "cmd": "bash -c '/usr/bin/desktop_ready && (dbus-launch xfdesktop &); (dbus-launch xfwm4 --replace &); (dbus-launch xfce4-panel &)'" } }

Verified this works with my setup. Curious why Suse is the only impacted workspace though. No other XFCE based workspaces appear to be impacted.

[verchalent]

Verified this works with my setup. Curious why Suse is the only impacted workspace though. No other XFCE based workspaces appear to be impacted.

After some additional testing, it looks like the Alpine 3.19 and 3.18 images (did not tey 3.17) have a similar issue. They work on my Debian 12 based test host, but not on Rocky 9. So it's not totally unique to Suse.