Gnome desktop interactive

Greetings OnDemand community!

We are having trouble with the Gnome desktop on the interactive apps. We configured XFCE and that works fine, just the Gnome desktop is not working in our deployments.

We are using Open OnDemand version 4.0.6 and GNOME Shell 3.32.2, we are using slurm 24.11.0.

$ gnome-shell --version
GNOME Shell 3.32.2
$ srun --version
slurm 24.11.0

I copied the bc_desktop to my dev directory so I could add more verbosity to the gnome script. I added set -x to the top of the script hoping to capture more details about what is going on, have the output here:

---------------- SLURM prolog script on FSL dnode0002 ----------------
Wed Sep 10 12:44:57 CDT 2025
NodeList=dnode0002
NumNodes=1 NumCPUs=1 NumTasks=1
WorkDir=/nobackup2/testuser1/ondemand/sys/dashboard/batch_connect/dev/bc_desktop_2/output/62342f16-97f2-4485-8835-facd784893ec
--------------- End of output from prolog script ---------------
Setting VNC password...
Starting VNC server...
Killing Xvnc process ID 103315
Xvnc process ID 103315 already killed
Xvnc did not appear to shut down cleanly. Removing /tmp/.X11-unix/X2
Xvnc did not appear to shut down cleanly. Removing /tmp/.X2-lock
Killing Xvnc process ID 107607
Xvnc process ID 107607 already killed
Xvnc did not appear to shut down cleanly. Removing /tmp/.X11-unix/X4
Xvnc did not appear to shut down cleanly. Removing /tmp/.X4-lock

WARNING: dnode0002.example.com:1 is taken because of /tmp/.X1-lock
Remove this file if there is no X server dnode0002.example.com:1

Desktop 'TurboVNC: dnode0002.example.com:2 (testuser1)' started on display dnode0002.example.com:2

Log file is vnc.log
Successfully started VNC server on dnode0002.example.com:5902...
Script starting...
Starting websocket server...
[websockify]: pid: 114117 (proxying 30992 ==> localhost:5902)
[websockify]: log file: ./websockify.log
[websockify]: waiting ...
Running "module reset". Resetting modules to system default. The following $MODULEPATH directories have been removed: None
Launching desktop 'gnome'...
++ gconftool-2 --set -t boolean /apps/gnome-screensaver/idle_activation_enabled false
++ gconftool-2 --set -t boolean /apps/nautilus/preferences/always_use_browser true
[websockify]: started successfully (proxying 30992 ==> localhost:5902)
Scanning VNC log file for user authentications...
Generating connection YAML file...
++ mkdir -p /home/testuser1/.config/autostart
++ cat /etc/xdg/autostart/gdu-notification-daemon.desktop /dev/fd/63
+++ echo X-GNOME-Autostart-enabled=false
cat: /etc/xdg/autostart/gdu-notification-daemon.desktop: No such file or directory
++ [[ -f /home/testuser1/.config/monitors.xml ]]
+++ dbus-launch --sh-syntax
++ eval 'DBUS_SESSION_BUS_ADDRESS='\''unix:abstract=/tmp/dbus-llf2bfAyur,guid=ca7e98aba5918dca2545247068c1b91d'\'';' export 'DBUS_SESSION_BUS_ADDRESS;' 'DBUS_SESSION_BUS_PID=114167;' 'DBUS_SESSION_BUS_WINDOWID=2097153;'
+++ DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-llf2bfAyur,guid=ca7e98aba5918dca2545247068c1b91d
+++ export DBUS_SESSION_BUS_ADDRESS
+++ DBUS_SESSION_BUS_PID=114167
+++ DBUS_SESSION_BUS_WINDOWID=2097153
++ source /etc/os-release
+++ NAME='Rocky Linux'
+++ VERSION='8.10 (Green Obsidian)'
+++ ID=rocky
+++ ID_LIKE='rhel centos fedora'
+++ VERSION_ID=8.10
+++ PLATFORM_ID=platform:el8
+++ PRETTY_NAME='Rocky Linux 8.10 (Green Obsidian)'
+++ ANSI_COLOR='0;32'
+++ LOGO=fedora-logo-icon
+++ CPE_NAME=cpe:/o:rocky:rocky:8:GA
+++ HOME_URL=https://rockylinux.org/
+++ BUG_REPORT_URL=https://bugs.rockylinux.org/
+++ SUPPORT_END=2029-05-31
+++ ROCKY_SUPPORT_PRODUCT=Rocky-Linux-8
+++ ROCKY_SUPPORT_PRODUCT_VERSION=8.10
+++ REDHAT_SUPPORT_PRODUCT='Rocky Linux'
+++ REDHAT_SUPPORT_PRODUCT_VERSION=8.10
++ [[ rhel centos fedora =~ fedora ]]
++ [[ 8.10 < 8.0 ]]
++ wayland
++ export XDG_SESSION_TYPE=x11
++ XDG_SESSION_TYPE=x11
++ export GNOME_SHELL_SESSION_MODE=wayland
++ GNOME_SHELL_SESSION_MODE=wayland
++ export GNOME_SESSION_MODE=wayland
++ GNOME_SESSION_MODE=wayland
++ /etc/X11/xinit/Xsession gnome-session

After hitting the “Launch Desktop” button, I got a VNC window in the browser that had a dialog window that let me select my language and a few other questions but when I got to the end of the setup it closed and I don’t see the gnome desktop. I believe this means that VNC is setup and was working at one point but something is not getting kicked off correctly. Now when I select the gnome desktop I only get a new browser window but a blank screen.

I have done some research on the forums and found the following articles:

I didn’t see anything in these issues that was relevant to our situation but I might have missed it. Please let me know if you need different logs or have questions. Any help on what logs to look at or what else I can do to close in on the problem would be much appreciated.

Thank you for your time,

Matt Bruzek

Can you provide a screenshot of the blank screen?

Also if you’re editing the script you can add --debug to the gnome-session command.

Lastly, there may be some information in journalctl about what gnome is trying to do/failing to do.

Also hi and welcome (I know we met in the office hours this week)!

Thank you Jeff. It was great to meet you on the community call.

The blank screen is in this image. I get the vnc menu on the left side. I did not get the language selection screen this time.

I added the –debug option and uploaded the journalctl -xe output and I do see some errors in the journal that I will start looking into.

journalctl_output.txt (37.8 KB)

Does this message means anything to you?

Sep 10 14:30:39 dnode0002.example.com gnome-shell[125706]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
Sep 10 14:30:39 dnode0002.example.com gnome-shell[125706]: JS ERROR: TypeError: this._userProxy.Display is null
                                                                     getCurrentSessionProxy@resource:///org/gnome/shell/misc/loginManager.js:90:17
                                                                     ScreenShield<@resource:///org/gnome/shell/ui/screenShield.js:534:9
                                                                     _initializeUI@resource:///org/gnome/shell/ui/main.js:175:24
                                                                     start@resource:///org/gnome/shell/ui/main.js:128:5
                                                                     @<main>:1:31

Is JS from OOD or is this JS in the gnome-shell?

That error is from gnome-shell. I wonder if you can try to set GNOME_SHELL_SESSION_MODE=classic if that could help. If not, try setting GNOME_SESSION_MODE=classic as well.

JS ERROR: TypeError: this._userProxy.Display is null has some hits on google, but it’s not clear what the resolution is.

I also wonder if an update to gnome and it’s accompanying libraries could help resolve the issue.

One last thing I see on these forums is using dbus-launch. So instead of just

/etc/X11/xinit/Xsession gnome-session

You can try

dbus-launch /etc/X11/xinit/Xsession gnome-session

And see if that’s any better.

I tried the dbus-launch and it didn’t seem like that worked any different, new browser tab, VNC connection and black screen.

I will look at setting those environment variables separately and report back.

I configured gnome.sh to classic and forgot to take out the dbus-launch. Here is the output:

++ export GNOME_SHELL_SESSION_MODE=classic
++ GNOME_SHELL_SESSION_MODE=classic
++ export GNOME_SESSION_MODE=classic
++ GNOME_SESSION_MODE=classic
++ dbus-launch /etc/X11/xinit/Xsession gnome-session --debug

No change, still blank VNC window. Looks like more of the same error in journalctl

JS ERROR: TypeError: this._userProxy.Display is null

1,000 apologies for completley dropping this.

I think at this point, the most I can do is google JS ERROR: TypeError: this._userProxy.Display is null and see what others have found and so on. My guess is an update through yum/dnf/apt is required, but I’m not 100% sure on that.

I’ll continue to google around and see if there are any forums that may have some indication of a solution.