We have discovered some issues with Xfce desktop on Rocky Linux 9 nodes. It seems to be pretty consistent on the nodes that run RL9, whereas our Rocky Linux 8 nodes work fine. Other apps, such as Jupyter, work fine on the RL9 nodes.
Our Xfce Desktop app is fairly vanilla - we have made modifications to the form and submit yaml files (mostly to accommodate slurm trackable resources scheduling) but no changes to the template.
I will follow this up with the output.log from a test job.
Here is the output.log from a test job on a RL9 node. The xfce4-panel-CRITICAL error seems like the most relevant error, but I don’t know how to troubleshoot that.
Setting VNC password…
Starting VNC server…
Desktop ‘TurboVNC: viz001:1 (jcreech)’ started on display viz001:1
Log file is vnc.log
Successfully started VNC server on viz001:5901…
Script starting…
Starting websocket server…
Running “module reset”. Resetting modules to system default. The following $MODULEPATH directories have been removed: None
[websockify]: pid: 316115 (proxying 14710 ==> localhost:5901)
[websockify]: log file: ./websockify.log
[websockify]: waiting …
Launching desktop ‘xfce’…
/usr/bin/iceauth: creating new authority file /run/user/546490/ICEauthority
(xfwm4:316163): xfwm4-WARNING **: 11:39:52.557: Unsupported GL renderer (llvmpipe (LLVM 16.0.6, 256 bits)).
vmware-user: could not open /proc/fs/vmblock/dev
double free or corruption (!prev)
(nm-applet:316277): libnotify-WARNING **: 11:39:53.042: Failed to connect to proxy
(nm-applet:316277): nm-applet-WARNING **: 11:39:53.043: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[websockify]: started successfully (proxying 14710 ==> localhost:5901)
Scanning VNC log file for user authentications…
Generating connection YAML file…
** (xfdesktop:316238): WARNING **: 11:39:53.220: Failed to register the newly set background with AccountsService ‘/usr/share/backgrounds/images/default.png’: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.DisplayManager.AccountsService”
(xfdesktop:316238): GVFS-RemoteVolumeMonitor-WARNING **: 11:39:59.944: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(tracker-miner-fs-3:316258): GVFS-RemoteVolumeMonitor-WARNING **: 11:39:59.944: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(xfdesktop:316238): GVFS-RemoteVolumeMonitor-WARNING **: 11:39:59.947: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(xfdesktop:316238): GVFS-RemoteVolumeMonitor-WARNING **: 11:39:59.947: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(tracker-miner-fs-3:316258): GVFS-RemoteVolumeMonitor-WARNING **: 11:39:59.947: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(xfdesktop:316238): GVFS-RemoteVolumeMonitor-WARNING **: 11:39:59.947: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(tracker-miner-fs-3:316258): GVFS-RemoteVolumeMonitor-WARNING **: 11:39:59.947: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(tracker-miner-fs-3:316258): GVFS-RemoteVolumeMonitor-WARNING **: 11:39:59.947: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
xfsettingsd: Another instance took over. Leaving…
(xfce4-panel:316229): xfce4-panel-CRITICAL **: 11:39:59.952: Name org.xfce.Panel lost on the message dbus, exiting.
** Message: 11:39:59.952: Got disconnected from the session message bus; retrying to reconnect every 10 seconds
(Thunar:316233): thunar-WARNING **: 11:39:59.952: Name ‘org.xfce.FileManager’ lost on the message dbus.
(Thunar:316233): thunar-WARNING **: 11:39:59.952: Name ‘org.freedesktop.FileManager1’ lost on the message dbus.
Terminated
Desktop ‘xfce’ ended with 143 status…
(xfce4-panel:316229): libxfce4ui-WARNING **: 11:39:59.957: ICE I/O Error
(xfdesktop:316238): libxfce4ui-WARNING **: 11:39:59.957: ICE I/O Error
Cleaning up…
(xfsettingsd:316226): libxfce4ui-WARNING **: 11:39:59.959: ICE I/O Error
OK
Killing Xvnc process ID 316092
It seems to be some issue with DBUS. I don’t know if I like those GVFS-RemoteVolumeMonitor-WARNING messages.
Many errors in the logs, but they don’t seem to indicate why they’re failing to use DBUS correctly.
I’d check other logs like journalctl or similar as to why DBUS is failing.
thanks. Maybe this is out of scope for OOD support. If I find something relevant in the logs, I’ll reply here
Yea it’s definitely a DBUS issue and maybe the way the scheduler (slurm?) interacts with systemd when the job starts.
It’s just tough for us because DBUS is a huge and complex system that honestly I’m not too familiar with.
Having said that - it could be this issue - we typically have to set XDG_RUNTIME_DIR somewhere else like $TMP. I just checked on our systems and it creates the ICEauthority file in this location.
Thank you, Jeff.
Joseph Glaser’s changes from this link ( [VNC Desktop / XFCE4] "Failed to connect to proxy" Issue - #19 by JPGlaser ) (from their final post there) worked for me. I guess it’s the same core issue. I also confirmed it did not break our Rocky 8 nodes (which would have been strange, but still good to confirm). Let me know if you think there is anything else to review. But I think we’re good to go now.
No if you’re good, I’m good!