Hi there,
I have created a kilosort batch connect and when I launch the app the dimension of the app goes beyond the browser window. I’m forced to zoom out to 50% to get the full-screen app, making it almost unreadable.
Does anyone have a solution for this problem?
here with 100% view:
here with 50% view:
PS: I can not scroll the screen.
Thank you.
Do you have an idea ? 
Well I see a couple issues. First is I don’t see any OS top panels to close/minimize/maximixe the window. I also don’t see desktop stuff like the start bar.
I would open xfce4-settings-editor in the ui and see what settings you can play around with. This will write an XML file that you can distribute with the app to use. I did this here with visit at OSC.
It could be enough to just provide the desktop background and panels and then you can resize the window.
There’s also xfce-settings-manager which may have other things to toggle.
I’m a bit confused. I have the same thing for Matlab, I thought it was what was expected with OpenOnDemand:
The window is small but full, and I’ve never had an xfce management interface. I only have the software windows and the “novnc” panel on the left.
Could you send me a screenshot of one of your interactive batch connect sessions (like Matlab) to see what the expected behavior is?
I pulled GitHub - OSC/bc_osc_matlab: Batch Connect - OSC Matlab into my sandbox and updated only form.yml submit.yml and template/script.sherb
and I get the same result as above, no desktop manager, only the Matlab screen.
Sure, here’s what my Matlab looks like. Note there’s an operating system dock panel at the top and that the Matlab window has a top panel for minimizing, maximizing and closing.
Maybe there’s something in the output.log that will tell us why you don’t have these.
Hoo 
it’s clearly not the same 
Here my output log :
I think xfsettingsd: No window manager registered on screen 0 could be the issue. I will do some search.
Setting VNC password...
Starting VNC server...
Desktop 'TurboVNC: cpu007.baobab:2 (alberta)' started on display cpu007.baobab:2
Log file is vnc.log
Successfully started VNC server on cpu007.baobab:5902...
Script starting...
Starting websocket server...
/home/users/a/alberta/ondemand/data/sys/dashboard/batch_connect/sys/ug_MatLab/output/700ae3b2-4774-4a4b-ae56-9f719c509749/script.sh: line 8: unsetenv: command not found
The system default contains no modules
(env var: LMOD_SYSTEM_DEFAULT_MODULES is empty)
No changes in loaded modules
xfwm4: Unknown option --daemon.
Type "xfwm4 --help" for usage.
[websockify]: pid: 357903 (proxying 22442 ==> localhost:5902)
[websockify]: log file: ./websockify.log
[websockify]: waiting ...
Currently Loaded Modules:
1) MATLAB/2022a
+ matlab -desktop
(xfsettingsd:357894): GLib-CRITICAL **: 17:10:36.238: g_str_has_prefix: assertion 'prefix != NULL' failed
(xfsettingsd:357894): GLib-GObject-CRITICAL **: 17:10:36.245: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed
(xfsettingsd:357894): GLib-GObject-CRITICAL **: 17:10:36.246: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed
(xfsettingsd:357894): GLib-GObject-CRITICAL **: 17:10:36.251: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed
MATLAB is selecting SOFTWARE OPENGL rendering.
[websockify]: started successfully (proxying 22442 ==> localhost:5902)
Scanning VNC log file for user authentications...
Generating connection YAML file...
xfsettingsd: No window manager registered on screen 0.
(xfsettingsd:357894): xfsettingsd-WARNING **: 17:10:41.354: Failed to get the _NET_NUMBER_OF_DESKTOPS property.
Setting VNC password...
Generating connection YAML file...
Opening log file: /home/users/a/alberta/java.log.30240
This actually may be the original error you want to look at. Instead of using the --daemon argument, you may be able to just background it with an &.
Weird,
The daemon option is in bc_osc_matlab/template/script.sh.erb at master · OSC/bc_osc_matlab · GitHub
MatLab/template/script.sh.erb: xfwm4 --compositor=off --daemon --sm-client-disable
I removed the --daemon option, now I have a black background:
But in the output.log I have not error anymore:
Setting VNC password...
Starting VNC server...
Desktop 'TurboVNC: cpu007.baobab:2 (alberta)' started on display cpu007.baobab:2
Log file is vnc.log
Successfully started VNC server on cpu007.baobab:5902...
Script starting...
Starting websocket server...
/home/users/a/alberta/ondemand/data/sys/dashboard/batch_connect/sys/ug_MatLab/output/d709f959-bedf-425d-a769-70f221c7ddcf/script.sh: line 8: unsetenv: command not found
The system default contains no modules
(env var: LMOD_SYSTEM_DEFAULT_MODULES is empty)
No changes in loaded modules
[websockify]: pid: 365050 (proxying 7681 ==> localhost:5902)
[websockify]: log file: ./websockify.log
[websockify]: waiting ...
Currently Loaded Modules:
1) MATLAB/2022a
+ matlab -desktop
(xfwm4:365041): GLib-CRITICAL **: 17:55:10.318: g_str_has_prefix: assertion 'prefix != NULL' failed
MATLAB is selecting SOFTWARE OPENGL rendering.
[websockify]: started successfully (proxying 7681 ==> localhost:5902)
Scanning VNC log file for user authentications...
Generating connection YAML file...
Opening log file: /home/users/a/alberta/java.log.37398
Setting VNC password...
Generating connection YAML file...
Setting VNC password...
Generating connection YAML file...
I am not sure but Window Manager (xfwm4) for xfce4 failing seems to be close to my issue. I am checking 
Ho I can’t trust my sight 
In fact, There is the the screen manager so I can extend the windows, Amen 
But I do not have the OS pannel :
I don’t follow this. It seems like you do have the start bar - I don’t know 100% what to call it - but it’s the panel with the Applications menu and where you have Matlab open as an application.
My bad, the screenshot is the shrinkage of yours 
to show what I’m missing ( the “OS panel”)
Here is my matlab session with the window manager (I can resize) but not the OS panel:
If I minimize the window, I can get it back. (complete black screen)
I see - that makes sense. Well you’re starting up xfwm4 but I wonder if you’re not backgrounding it. That is - i wonder if it’s blocking so that the other commands - like xfce4-panel (just pulled that from memory, could be a different command - aren’t being issued because xfwm4 is still running in the foreground.
@jeff.ohrstrom I found it !!
(
export SEND_256_COLORS_TO_REMOTE=1
export XDG_CONFIG_HOME="<%= session.staged_root.join("config") %>"
export XDG_DATA_HOME="<%= session.staged_root.join("share") %>"
export XDG_CACHE_HOME="$(mktemp -d)"
module restore
# set -x
echo toto1
#xfwm4 --replace --compositor=off&
xfwm4 --compositor=off --sm-client-disable&
echo toto2
xsetroot -solid "#D3D3D3"
xfsettingsd --sm-client-disable&
xfce4-panel --sm-client-disable
) &
I tested with echo toto to debug. As the “–daemon” option is not available (Don’t know why) I tried ‘&’ to background it as you said :
i wonder if it’s blocking so that the other commands
So I apply this logic for the following xfce4 command. It seems you only need to background xfsettingsd --sm-client-disable&, and look at my beautifull session:
I am not sure it’s fully working or it’s “best practice”, but the situation is much better.
Thank you very much for all your help !
PS: I think it would be a good idea to include a screenshot of what an interactive session should look like. Until today, I thought it was normal to have a non-resizable “post-it”.
That’s good news indeed!
They changed it at some point. It’s OS dependent at this point. Most of our compute nodes are still RHEL 7, you may have a higher version of XFCE.
You’re likely right. I find most of the stuff in this thread comes up a lot.
