Ok, thanks a lot for prioritizing this! Please let me know as soon as I can try again. In the meantime, I ordered an Iris Board as a backup solution but I hope I won’t need it.
Best regards,
Andreas
Hi @amueller,
The team seems to have found a configuration that works. So to fully disable the parallel RGB interface try this overlay:
// disable parallel RGB display
/dts-v1/;
/plugin/;
/ {
compatible = "toradex,colibri-imx7d-emmc","toradex,apalis_imx6q", "toradex,colibri_imx6dl";
fragment@0 {
target-path = "/panel-dpi";
__overlay__ {
status = "disabled";
};
};
fragment@1 {
target-path = "/disp0";
__overlay__ {
status = "disabled";
};
};
};
After applying that there’s also a slightly modified docker-compose.yml file. This is the modified file for the Grafana example:
# this override brings up Grafana on a local display
version: "2.4"
services:
weston:
command: --developer weston-launch --tty=/dev/tty7 --user=torizon
environment:
- ACCEPT_FSL_EULA=1
container_name: weston
# For armhf (i.MX 6- and i.MX 7-based modules) use this image:
image: torizon/arm32v7-debian-weston:latest
# For i.MX 8-based modules use this image:
#image: torizon/arm64v8-debian-weston-vivante:latest
# Required to get udev events from host udevd via netlink
network_mode: host
volumes:
- type: bind
source: /tmp
target: /tmp
- type: bind
source: /dev
target: /dev
- type: bind
source: /run/udev
target: /run/udev
cap_add:
- CAP_SYS_TTY_CONFIG
# Add device access rights through cgroup...
device_cgroup_rules:
# ... for tty0
- 'c 4:0 rmw'
# ... for tty7
- 'c 4:7 rmw'
# ... for /dev/input devices
- 'c 13:* rmw'
- 'c 199:* rmw'
# ... for /dev/dri devices
- 'c 226:* rmw'
kiosk:
container_name: kiosk
# For armhf (i.MX 6- and i.MX 7-based modules) use this image:
image: torizon/arm32v7-debian-kiosk-mode-browser:latest
# For i.MX 8-based modules use this image:
#image: torizon/arm64v8-debian-kiosk-mode-browser:latest
command: --window-mode http://grafana:3000
security_opt:
- seccomp:unconfined
networks:
- frontend
volumes:
- type: bind
source: /tmp
target: /tmp
- type: bind
source: /var/run/dbus
target: /var/run/dbus
- type: bind
source: /dev/dri
target: /dev/dri
depends_on:
- weston
- grafana
- influxdb
shm_size: '256mb'
device_cgroup_rules:
# ... for /dev/dri devices
- 'c 226:* rmw'
Really the only significant modification is adding --developer weston-launch --tty=/dev/tty7 --user=torizon after the weston command. You can try the same modification with portainer as well. Make sure you use the default containers and not the custom ones I had you try, it seems there’s no correlation between the DISPLAY variable and the physical display anyways. As a final note the team noticed in testing that if you try to run these examples at full HD quality/resolution you may run into out of memory errors.
Best Regards,
Jeremias
This works, thanks a lot!
Glad it worked for you.
Solution does not work for TorizonCore 5.0
I am trying to port the solution to TorizonCore 5.0 and torizoncore-builder, but I cannot get it working.
Here is the tcbuild.yaml
# >> NOTES:
# >> Lines containing ">>" are simply comments explaining the properties that
# >> follow; if you don't like these comments run:
# >> $ grep -v '>>' tcbuild.yaml > tcbuild-clean.yaml
# >> A line not containing ">>" can be uncommented (by removing the hash mark
# >> plus a space from its beginning); also set the corresponding property to
# >> appropriate values.
# >> When uncommenting a line having a property, remember to uncomment all its
# >> parent properties as well; for example: if you uncomment the
# >> 'splash-screen' property, also uncomment its parent property called
# >> 'customization'.
# >> The input section specifies the image to be taken as the base for the
# >> customization.
input:
easy-installer:
# >> Choose one of the options (REQUIRED):
# >> (1) Image as local folder or tarball.
local: images/torizon-core-docker-colibri-imx6-Tezi_5.3.0+build.7.tar
# >> (2) Remote file (optionally with a filename and or a sha256 checksum):
# remote: "https://artifacts.toradex.com/.../torizon-core-docker-apalis-imx8-Tezi_5.1.0%2Bbuild.1.tar"
# remote: "https://artifacts.toradex.com/.../torizon-core-docker-colibri-imx6-Tezi_5.0.0-devel-202009%2Bbuild.2.tar;filename=torizon-core-docker-colibri-imx6-Tezi_5.0.0-devel-202009+build.2.tar;sha256sum=368595fa3fb00af9604e70311de3b04df6b30b280deec2f8918c46f479026ddb"
# >> (3) Image specification (URL will be generated by the tool)
# toradex-feed:
# version: "5.1.0"
# release: quarterly
# machine: colibri-imx6-emmc
# distro: torizon-upstream
# variant: torizon-core-docker
# build-number: "1"
# build-date: "20210408"
# >> The customization section defines the modifications to be applied to get
# >> the desired output image.
customization:
# >> Splash screen:
# splash-screen: ressources/logo.png
# >> Directories overlayed to the base OSTree
# filesystem:
# - fs_volumes
# - fs_changes
device-tree:
# >> Directories where to look for include files.
# include-dirs:
# - device-trees/include/
# >> Custom device tree source:
# custom: device-trees/dts-arm32/imx6ull-colibri-eval-v3.dts
# >> Device-tree overlays configuration:
overlays:
# >> Whether to ignore all overlays from the base image (or ostree
# >> archive in the future).
# clear: false
# >> Specific overlays not to use from base image (useful only when
# >> clear is false and not DT has been selected).
# remove:
# - apalis-imx8_hdmi_overlay.dtbo
# >> Overlays to add to output image.
add:
- device-trees/overlays/disable-vga.dts
# kernel:
# >> Custom kernel arguments.
# arguments:
# - key1=val1
# - key2=val2
# >> Modules to build and possibly load automatically.
# modules:
# - source-dir: virtual_touchscreen/
# autoload: no
# >> The output section defines properties of the output image.
output:
# >> OSTree deployment configuration (relevant also for Easy Installer output).
# ostree:
# branch: my-dev-branch
# commit-subject: "OSTree commit subject"
# commit-body: "OSTree commit body"
# >> Parameters for deploying to an Easy Installer image.
easy-installer:
# >> Output directory of the customized image (REQUIRED):
local: images/built
# >> Information shown by Toradex Easy Installer:
name: "My Test Build"
description: "Build Number: 7"
# licence: files/custom-licence.html
# release-notes: files/custom-release-notes.html
bundle:
# >> Choose one of the options:
# >> (1) Specify a docker-compose file whose referenced images will be downloaded.f
# >> Properties platform, username, password and registry are optional.
compose-file: docker/docker-compose.yml
platform: linux/arm/v7
# username: "${USERNAME}"
# password: "${PASSWORD}"
# registry: hub.docker.com
# >> (2) Specify a local directory containing the bundled images (previously
# >> obtained by 'torizoncore-builder bundle' command).
# dir: bundle/
the disable-vga.dts as provided:
// disable parallel RGB display
/dts-v1/;
/plugin/;
/ {
compatible = "toradex,colibri-imx7d-emmc","toradex,apalis_imx6q", "toradex,colibri_imx6dl";
fragment@0 {
target-path = "/panel-dpi";
__overlay__ {
status = "disabled";
};
};
fragment@1 {
target-path = "/disp0";
__overlay__ {
status = "disabled";
};
};
};
and the docker-compose.yml
version: "2.4"
services:
mosquitto:
image: eclipse-mosquitto
restart: always
mem_limit: 25m
mem_reservation: 5m
volumes:
- /volumes/mosquitto/config:/mosquitto/config
- /volumes/mosquitto/data:/mosquitto/data
- /volumes/mosquitto/log:/mosquitto/log
ports:
- "1883:1883"
- "9001:9001"
networks:
- localnet
weston:
command: --developer weston-launch --tty=/dev/tty7 --user=torizon
restart: always
mem_limit: 75m
mem_reservation: 50m
environment:
- ACCEPT_FSL_EULA=1
container_name: weston
image: torizon/arm32v7-debian-weston:latest
# Required to get udev events from host udevd via netlink
network_mode: host
volumes:
- type: bind
source: /tmp
target: /tmp
- type: bind
source: /dev
target: /dev
- type: bind
source: /run/udev
target: /run/udev
cap_add:
- CAP_SYS_TTY_CONFIG
# Add device access rights through cgroup...
device_cgroup_rules:
# ... for tty0
- 'c 4:0 rmw'
# ... for tty7
- 'c 4:7 rmw'
# ... for /dev/input devices
- 'c 13:* rmw'
- 'c 199:* rmw'
# ... for /dev/dri devices
- 'c 226:* rmw'
kiosk:
image: torizon/arm32v7-debian-kiosk-mode-browser:latest
restart: always
mem_limit: 200m
mem_reservation: 100m
security_opt:
- seccomp:unconfined
command: --window-mode http://webserver:8000/dashboard
volumes:
- type: bind
source: /tmp
target: /tmp
- type: bind
source: /var/run/dbus
target: /var/run/dbus
- type: bind
source: /dev/dri
target: /dev/dri
depends_on:
- weston
shm_size: '256mb'
device_cgroup_rules:
# ... for /dev/dri devices
- 'c 226:* rmw'
networks:
- localnet
networks:
localnet:
I can build the image with torizoncore-builder build and install it with easyinstaller via a local webserver.
After bootup, weston and kisok are stuck in a restart loop. Here ist the output from weston:
colibri-imx6-10778387:~$ docker logs e928525972d6
Switching to VT 7
Date: 2021-08-03 UTC
[11:34:36.319] weston 5.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: unknown (not built from git or tarball)
[11:34:36.319] Command line: /usr/bin/weston
[11:34:36.319] OS: Linux, 5.4.77-5.3.0+git.a2e5dc80229e, #1-TorizonCore SMP Mon Jun 21 11:19:26 UTC 2021, armv7l
[11:34:36.322] Using config file '/etc/xdg/weston-dev//weston.ini'
[11:34:36.327] Output repaint window is 7 ms maximum.
[11:34:36.329] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-5/drm-backend.so'
[11:34:36.369] initializing drm backend
[11:34:36.379] logind: not running in a systemd session
[11:34:36.380] logind: cannot setup systemd-logind helper (-61), using legacy fallback
[11:34:36.398] no drm device found
[11:34:36.398] fatal: failed to create compositor backend
failed to restore keyboard mode: No such file or directory
failed to set KD_TEXT mode on tty: Operation not supported
Switching to VT 7
Date: 2021-08-03 UTC
[11:34:39.177] weston 5.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: unknown (not built from git or tarball)
[11:34:39.177] Command line: /usr/bin/weston
[11:34:39.177] OS: Linux, 5.4.77-5.3.0+git.a2e5dc80229e, #1-TorizonCore SMP Mon Jun 21 11:19:26 UTC 2021, armv7l
[11:34:39.178] Using config file '/etc/xdg/weston-dev//weston.ini'
[11:34:39.186] Output repaint window is 7 ms maximum.
[11:34:39.187] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-5/drm-backend.so'
[11:34:39.213] initializing drm backend
[11:34:39.214] logind: not running in a systemd session
[11:34:39.215] logind: cannot setup systemd-logind helper (-61), using legacy fallback
[11:34:39.243] no drm device found
[11:34:39.243] fatal: failed to create compositor backend
failed to restore keyboard mode: No such file or directory
failed to set KD_TEXT mode on tty: Operation not supported
Switching to VT 7
Date: 2021-08-03 UTC
[11:34:43.034] weston 5.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: unknown (not built from git or tarball)
[11:34:43.036] Command line: /usr/bin/weston
[11:34:43.037] OS: Linux, 5.4.77-5.3.0+git.a2e5dc80229e, #1-TorizonCore SMP Mon Jun 21 11:19:26 UTC 2021, armv7l
[11:34:43.037] Using config file '/etc/xdg/weston-dev//weston.ini'
[11:34:43.038] Output repaint window is 7 ms maximum.
[11:34:43.038] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-5/drm-backend.so'
[11:34:43.061] initializing drm backend
[11:34:43.063] logind: not running in a systemd session
[11:34:43.063] logind: cannot setup systemd-logind helper (-61), using legacy fallback
[11:34:43.086] no drm device found
[11:34:43.087] fatal: failed to create compositor backend
failed to restore keyboard mode: No such file or directory
failed to set KD_TEXT mode on tty: Operation not supported
Switching to VT 7
Date: 2021-08-03 UTC
[11:34:46.053] weston 5.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: unknown (not built from git or tarball)
[11:34:46.053] Command line: /usr/bin/weston
[11:34:46.054] OS: Linux, 5.4.77-5.3.0+git.a2e5dc80229e, #1-TorizonCore SMP Mon Jun 21 11:19:26 UTC 2021, armv7l
[11:34:46.055] Using config file '/etc/xdg/weston-dev//weston.ini'
[11:34:46.057] Output repaint window is 7 ms maximum.
[11:34:46.057] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-5/drm-backend.so'
[11:34:46.077] initializing drm backend
[11:34:46.079] logind: not running in a systemd session
[11:34:46.079] logind: cannot setup systemd-logind helper (-61), using legacy fallback
[11:34:46.101] no drm device found
[11:34:46.102] fatal: failed to create compositor backend
failed to restore keyboard mode: No such file or directory
failed to set KD_TEXT mode on tty: Operation not supported
Switching to VT 7
Date: 2021-08-03 UTC
[11:34:50.029] weston 5.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: unknown (not built from git or tarball)
[11:34:50.030] Command line: /usr/bin/weston
[11:34:50.030] OS: Linux, 5.4.77-5.3.0+git.a2e5dc80229e, #1-TorizonCore SMP Mon Jun 21 11:19:26 UTC 2021, armv7l
[11:34:50.032] Using config file '/etc/xdg/weston-dev//weston.ini'
[11:34:50.033] Output repaint window is 7 ms maximum.
[11:34:50.037] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-5/drm-backend.so'
[11:34:50.118] initializing drm backend
[11:34:50.131] logind: not running in a systemd session
[11:34:50.131] logind: cannot setup systemd-logind helper (-61), using legacy fallback
[11:34:50.167] no drm device found
[11:34:50.167] fatal: failed to create compositor backend
failed to restore keyboard mode: No such file or directory
failed to set KD_TEXT mode on tty: Operation not supported
Switching to VT 7
Date: 2021-08-03 UTC
[11:34:56.081] weston 5.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: unknown (not built from git or tarball)
[11:34:56.082] Command line: /usr/bin/weston
[11:34:56.082] OS: Linux, 5.4.77-5.3.0+git.a2e5dc80229e, #1-TorizonCore SMP Mon Jun 21 11:19:26 UTC 2021, armv7l
[11:34:56.092] Using config file '/etc/xdg/weston-dev//weston.ini'
[11:34:56.093] Output repaint window is 7 ms maximum.
[11:34:56.098] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-5/drm-backend.so'
[11:34:56.164] initializing drm backend
[11:34:56.167] logind: not running in a systemd session
[11:34:56.168] logind: cannot setup systemd-logind helper (-61), using legacy fallback
[11:34:56.205] no drm device found
[11:34:56.205] fatal: failed to create compositor backend
failed to restore keyboard mode: No such file or directory
failed to set KD_TEXT mode on tty: Operation not supported
Switching to VT 7
Date: 2021-08-03 UTC
[11:35:02.911] weston 5.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: unknown (not built from git or tarball)
[11:35:02.911] Command line: /usr/bin/weston
[11:35:02.911] OS: Linux, 5.4.77-5.3.0+git.a2e5dc80229e, #1-TorizonCore SMP Mon Jun 21 11:19:26 UTC 2021, armv7l
[11:35:02.913] Using config file '/etc/xdg/weston-dev//weston.ini'
[11:35:02.913] Output repaint window is 7 ms maximum.
[11:35:02.918] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-5/drm-backend.so'
[11:35:02.956] initializing drm backend
[11:35:02.964] logind: not running in a systemd session
[11:35:02.964] logind: cannot setup systemd-logind helper (-61), using legacy fallback
[11:35:02.991] no drm device found
[11:35:02.992] fatal: failed to create compositor backend
failed to restore keyboard mode: No such file or directory
failed to set KD_TEXT mode on tty: Operation not supported
Switching to VT 7
Date: 2021-08-03 UTC
[11:35:14.360] weston 5.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: unknown (not built from git or tarball)
[11:35:14.360] Command line: /usr/bin/weston
[11:35:14.360] OS: Linux, 5.4.77-5.3.0+git.a2e5dc80229e, #1-TorizonCore SMP Mon Jun 21 11:19:26 UTC 2021, armv7l
[11:35:14.362] Using config file '/etc/xdg/weston-dev//weston.ini'
[11:35:14.363] Output repaint window is 7 ms maximum.
[11:35:14.369] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-5/drm-backend.so'
[11:35:14.420] initializing drm backend
[11:35:14.422] logind: not running in a systemd session
[11:35:14.422] logind: cannot setup systemd-logind helper (-61), using legacy fallback
[11:35:14.452] no drm device found
[11:35:14.453] fatal: failed to create compositor backend
failed to restore keyboard mode: No such file or directory
failed to set KD_TEXT mode on tty: Operation not supported
Switching to VT 7
Date: 2021-08-03 UTC
[11:35:31.645] weston 5.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: unknown (not built from git or tarball)
[11:35:31.645] Command line: /usr/bin/weston
[11:35:31.645] OS: Linux, 5.4.77-5.3.0+git.a2e5dc80229e, #1-TorizonCore SMP Mon Jun 21 11:19:26 UTC 2021, armv7l
[11:35:31.647] Using config file '/etc/xdg/weston-dev//weston.ini'
[11:35:31.648] Output repaint window is 7 ms maximum.
[11:35:31.653] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-5/drm-backend.so'
[11:35:31.702] initializing drm backend
[11:35:31.708] logind: not running in a systemd session
[11:35:31.708] logind: cannot setup systemd-logind helper (-61), using legacy fallback
[11:35:31.731] no drm device found
[11:35:31.731] fatal: failed to create compositor backend
failed to restore keyboard mode: No such file or directory
failed to set KD_TEXT mode on tty: Operation not supported
and the output from kiosk:
colibri-imx6-10778387:~$ docker logs 7780a8663885
(chromium:1): Gtk-WARNING **: 11:34:46.101: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:34:56.748: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:35:05.709: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:35:14.651: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:35:23.570: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:35:30.870: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:35:39.658: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:35:51.298: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:36:08.458: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:36:38.382: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:37:34.023: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:38:38.423: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:39:42.811: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:40:47.088: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:41:51.467: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:42:55.842: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:44:00.231: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:45:05.000: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:46:10.017: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:47:14.427: cannot open display: :0
(chromium:1): Gtk-WARNING **: 11:48:18.815: cannot open display: :0
As before,the easyinstaller userinterface shows up on the HDMI display, but after installing any TorizonCore image, the screen shows a “No Signal” message. I also tried with the latest TorizonCore with Evaluation containers.
Hi @amueller,
Well it’s been a year since we discussed the original solution here and since then quite a lot has changed with the latest release of TorizonCore.
Just to name a few that I noticed. The overlay you’re using to disable VGA is no longer required. We also have ready made overlays now to enable HDMI interface you’re using please see here: Device Tree Overlays on Torizon | Toradex Developer Center
Furthermore in your compose file the weston and kiosk containers you’re using are deprecated and no longer being supported/updated.
- For the updated weston container see here: Debian Containers for Torizon | Toradex Developer Center
- For the updated kiosk container see here: Web Browser / Kiosk Mode with TorizonCore | Toradex Developer Center
- Then for an example compose file you can use this as a reference: torizon-samples/docker-compose.armhf.yml at bullseye · toradex/torizon-samples · GitHub
These are just the immediate things I noticed that are now outdated with your implementation. There may be other details that need to be updated but start with these for now.
Best Regards,
Jeremias
Hello Jeremias,
I got it working with those changes.
Thanks,
Andreas
Glad I could help out!
Best Regards,
Jeremias
Sorry for another follow-up, but I noticed that there is now a titlebar in the kiosk mode browser visible. Also, what appears to be a system panel is half visible at the top of the screen. I am fairly certain that wasn’t the case in ealrier versions. Is there a flag I’m missing?
version: "2.4"
services:
weston:
image: torizon/weston:2
# Required to get udev events from host udevd via netlink
network_mode: host
volumes:
- type: bind
source: /tmp
target: /tmp
- type: bind
source: /dev
target: /dev
- type: bind
source: /run/udev
target: /run/udev
cap_add:
- CAP_SYS_TTY_CONFIG
# Add device access rights through cgroup...
device_cgroup_rules:
# ... for tty0
- 'c 4:0 rmw'
# ... for tty7
- 'c 4:7 rmw'
# ... for /dev/input devices
- 'c 13:* rmw'
# ... for /dev/dri devices
- 'c 226:* rmw'
command: --developer weston-launch --tty=/dev/tty7 --user=torizon
healthcheck:
test: ["CMD", "test", "-S", "/tmp/.X11-unix/X0"]
interval: 5s
timeout: 4s
retries: 6
start_period: 10s
kiosk:
image: torizon/kiosk-mode-browser:2
security_opt:
- seccomp:unconfined
command: --window-mode http://toradex.com
shm_size: '256mb'
device_cgroup_rules:
# ... for /dev/dri devices
- 'c 226:* rmw'
volumes:
- type: bind
source: /tmp
target: /tmp
- type: bind
source: /var/run/dbus
target: /var/run/dbus
- type: bind
source: /dev/dri
target: /dev/dri
depends_on:
weston:
condition: service_healthy
networks:
- localnet
Well you have the web browser configured as a window with --window-mode which is why it’s showing the titlebar of the window. If you just want the webpage content to be displayed with no title-bar or window frame then omit the --window-mode argument.
Best Regards,
Jeremias
Ok, thank you! I expected it would show the full menu bar without any flags, so I didn’t even try that.
Glad I was able to assist!