INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Being booted out to log screen when running MC in Bookworm  (Read 1223 times)

Mastiff

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1977
  • The Multi-Zone Tzar
Being booted out to log screen when running MC in Bookworm
« on: October 23, 2023, 10:19:04 am »

I have set up Bookworm, and most stuff works as it should. But MC (last version) when it starts as a service (wich I have had it do for a couple of years now in different versions on the same Pi 4 in my boat), boots me out to the login screen, and when I log in again, the same thing happens. Running from the icon in the menu does not give me that problem. This is my service file, I don't know if there is somehing wrong there. It's the one I've been using all this time:

Code: [Select]
pi@MadMax:/usr/lib/systemd/system $ cat jriver.service
[Unit]
Description=JRiver
After=display-manager.service

[Service]
Type=simple
Environment=DISPLAY=:0
User=pi
ExecStart=/usr/bin/mediacenter31
Restart=always
RestartSec=10
KillSignal=SIGHUP
TimeoutStopSec=45
Nice=-15

[Install]
WantedBy=graphical.target

Can somebody tell me if there's somethign there that I need to change? I'm guessing it's the move to Wayland. I tried without the environment display 0 line, but I think it started without showing then, which is probably to be expected.
Logged
Tor with the Cinema Inferno & Multi-Zone Audio system

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5173
  • "Linux Merit Badge" Recipient
Re: Being booted out to log screen when running MC in Bookworm
« Reply #1 on: October 23, 2023, 07:57:02 pm »

So what you'll need to do is find out what the correct display number actually is on your desktop.  I suspect the display manager is using :0 and your desktop is on :1 or something, which is why it's kicking you out to the login screen every time.  When you're in a normal running session, open a terminal and type "env" and see what display your desktop is actually using, then try that in your service.
Logged

Mastiff

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1977
  • The Multi-Zone Tzar
Re: Being booted out to log screen when running MC in Bookworm
« Reply #2 on: October 24, 2023, 12:33:07 am »

Thanks for answering! But I don't think that's it. env shows this:

Code: [Select]
env
SHELL=/bin/bash
COLORTERM=truecolor
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_MENU_PREFIX=lxde-pi-
QT_WAYLAND_DISABLE_WINDOWDECORATION=1
LANGUAGE=nb_NO.UTF-8
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXKxfhxZ/agent.922
WLR_XWAYLAND=/usr/bin/xwayland-xauth
DESKTOP_SESSION=LXDE-pi-wayfire
SSH_AGENT_PID=973
NO_AT_BRIDGE=1
XCURSOR_SIZE=24
XDG_SEAT=seat0
PWD=/home/pi
LOGNAME=pi
XDG_SESSION_DESKTOP=LXDE-pi-wayfire
QT_QPA_PLATFORMTHEME=qt5ct
XDG_SESSION_TYPE=wayland
GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
XAUTHORITY=/home/pi/.Xauthority
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/pi
HOME=/home/pi
LANG=nb_NO.UTF-8
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.avif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:*~=00;90:*#=00;90:*.bak=00;90:*.old=00;90:*.orig=00;90:*.part=00;90:*.rej=00;90:*.swp=00;90:*.tmp=00;90:*.dpkg-dist=00;90:*.dpkg-old=00;90:*.ucf-dist=00;90:*.ucf-new=00;90:*.ucf-old=00;90:*.rpmnew=00;90:*.rpmorig=00;90:*.rpmsave=00;90:
_JAVA_AWT_WM_NONREPARENTING=1
VTE_VERSION=7006
WAYLAND_DISPLAY=wayland-1
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
TERM=xterm-256color
USER=pi
DISPLAY=:0
SHLVL=1
XDG_VTNR=7
XDG_SESSION_ID=1
XDG_RUNTIME_DIR=/run/user/1000
LC_ALL=nb_NO.UTF-8
XCURSOR_THEME=PiXflat
XDG_DATA_DIRS=/usr/local/share:/usr/share/raspi-ui-overrides:/usr/share:/usr/share/gdm:/var/lib/menu-xdg
WLR_DRM_NAME=/dev/dri/card0
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
GDMSESSION=LXDE-pi-wayfire
SAL_USE_VCLPLUGIN=gtk3
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
WAYFIRE_CONFIG_FILE=/home/pi/.config/wayfire.ini
GIO_LAUNCHED_DESKTOP_FILE_PID=203523
GIO_LAUNCHED_DESKTOP_FILE=/usr/share/raspi-ui-overrides/applications/lxterminal.desktop
TEXTDOMAIN=Linux-PAM
_=/usr/bin/env

As you can see, the 0 is correct. Or do you mean the
Code: [Select]
WAYLAND_DISPLAY=wayland-1? I tried to set it to 1 in the service file, but I didn't see Media Center at all then. I am doing this over Wayvnc, but I am controlling the actual desktop with the VNC.
Logged
Tor with the Cinema Inferno & Multi-Zone Audio system

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5173
  • "Linux Merit Badge" Recipient
Re: Being booted out to log screen when running MC in Bookworm
« Reply #3 on: October 24, 2023, 07:20:51 pm »

Thanks for answering! But I don't think that's it. env shows this:

Code: [Select]
env
SHELL=/bin/bash
COLORTERM=truecolor
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_MENU_PREFIX=lxde-pi-
QT_WAYLAND_DISABLE_WINDOWDECORATION=1
LANGUAGE=nb_NO.UTF-8
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXKxfhxZ/agent.922
WLR_XWAYLAND=/usr/bin/xwayland-xauth
DESKTOP_SESSION=LXDE-pi-wayfire
SSH_AGENT_PID=973
NO_AT_BRIDGE=1
XCURSOR_SIZE=24
XDG_SEAT=seat0
PWD=/home/pi
LOGNAME=pi
XDG_SESSION_DESKTOP=LXDE-pi-wayfire
QT_QPA_PLATFORMTHEME=qt5ct
XDG_SESSION_TYPE=wayland
GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
XAUTHORITY=/home/pi/.Xauthority
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/pi
HOME=/home/pi
LANG=nb_NO.UTF-8
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.avif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:*~=00;90:*#=00;90:*.bak=00;90:*.old=00;90:*.orig=00;90:*.part=00;90:*.rej=00;90:*.swp=00;90:*.tmp=00;90:*.dpkg-dist=00;90:*.dpkg-old=00;90:*.ucf-dist=00;90:*.ucf-new=00;90:*.ucf-old=00;90:*.rpmnew=00;90:*.rpmorig=00;90:*.rpmsave=00;90:
_JAVA_AWT_WM_NONREPARENTING=1
VTE_VERSION=7006
WAYLAND_DISPLAY=wayland-1
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
TERM=xterm-256color
USER=pi
DISPLAY=:0
SHLVL=1
XDG_VTNR=7
XDG_SESSION_ID=1
XDG_RUNTIME_DIR=/run/user/1000
LC_ALL=nb_NO.UTF-8
XCURSOR_THEME=PiXflat
XDG_DATA_DIRS=/usr/local/share:/usr/share/raspi-ui-overrides:/usr/share:/usr/share/gdm:/var/lib/menu-xdg
WLR_DRM_NAME=/dev/dri/card0
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
GDMSESSION=LXDE-pi-wayfire
SAL_USE_VCLPLUGIN=gtk3
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
WAYFIRE_CONFIG_FILE=/home/pi/.config/wayfire.ini
GIO_LAUNCHED_DESKTOP_FILE_PID=203523
GIO_LAUNCHED_DESKTOP_FILE=/usr/share/raspi-ui-overrides/applications/lxterminal.desktop
TEXTDOMAIN=Linux-PAM
_=/usr/bin/env

As you can see, the 0 is correct. Or do you mean the
Code: [Select]
WAYLAND_DISPLAY=wayland-1? I tried to set it to 1 in the service file, but I didn't see Media Center at all then. I am doing this over Wayvnc, but I am controlling the actual desktop with the VNC.

Ok that looks like a different issue than the one I thought.  Can you connect to the Pi directly with a monitor and keyboard to see if you have the same issue?
Logged

Mastiff

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1977
  • The Multi-Zone Tzar
Re: Being booted out to log screen when running MC in Bookworm
« Reply #4 on: October 25, 2023, 02:22:03 am »

Oh, sorry. I sould have said that. The same thing happens when I'm not connected with VNC, when it has a keyboard and a monitor.

Edit: To see that it isn't a one-off problem I'll install Bookworm on the car's Pi 4 (both are 4 gig RAM if that matters) and see if the same thing happens.
Logged
Tor with the Cinema Inferno & Multi-Zone Audio system

BryanC

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2554
Re: Being booted out to log screen when running MC in Bookworm
« Reply #5 on: October 25, 2023, 08:14:18 am »

installJRMC uses an Xauthority env on Debian/Ubuntu, not sure if that's the culprit but it's missing in your service file:

"Environment=XAUTHORITY=/home/user/.Xauthority"
Logged

Mastiff

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1977
  • The Multi-Zone Tzar
Re: Being booted out to log screen when running MC in Bookworm
« Reply #6 on: October 25, 2023, 09:37:03 am »

There is no .Xauthority directory under the user (pi). Can that be the problem? I added the line, with home/pi instead of  home/user, I assume that would be correct.

Edit: Oh, another thing: When I get booted to the log in screen, everything else stops abruptly. Docker containers shut down, but not in a nice way. And VNC stops working, so if I don't have a keyboard and a monitor on the Pi, I have to ssh in and first stop jriver (the service), disable it (so it doesn't start again when I log back in) and use raspi-config to enable the VNC server.
Logged
Tor with the Cinema Inferno & Multi-Zone Audio system

BryanC

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2554
Re: Being booted out to log screen when running MC in Bookworm
« Reply #7 on: October 25, 2023, 11:53:02 am »

It's a file, not a directory. If it's not present then it must be created with xauth, ex:

Code: [Select]
HOST="workstation" # hostname
DISPLAY=":0" # display for MC
xauth generate "$DISPLAY" . trusted
xauth add "$HOST$DISPLAY" . "$(xxd -l 16 -p /dev/urandom)"
Logged

Mastiff

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1977
  • The Multi-Zone Tzar
Re: Being booted out to log screen when running MC in Bookworm
« Reply #8 on: October 25, 2023, 02:08:28 pm »

Sorry, my bad. I was looking for a directory, yeah. The hidden file is there. And I tried with a new Pi now. Same type, Pi 4 4 gig RAM. I burnt the OS, did an upgrade and used your script to install. Same problem, only worse. Even the icon version booted me to log in screen, and  this time I had an error while trying to activate WayVNC:

Code: [Select]
<ERROR: ../src/main.c: 386: Failed to connect to WAYLAND_DISPLAY="wayland-1"                 │                                                          │
ERROR: ../src/main.c: 387: Ensure wayland is running with that display name─┘
ERROR: ../src/main.c: 1391: Failed to initialise wayland
To get that working again I had to use the mouse and keyboard, log in and do the raspi-config. This time the error was:

Code: [Select]
<Warning: ../src/ctl-server.c: 703: Deleting stale control socket path "/run/user/1000/wayvncctl"
But then the VNC works. This is the bash history, I don't think there's anything wonky there. I change the config file of WayVNC to run without security, because the Pi's are behind pfSense (the boat, when it's even connected to the Net while docked) and OpenWRT (the car) firewalls.

Code: [Select]
sudo mousepad .config/wayvnc/config
sudo apt-get update
sudo apt-get full-upgrade
reboot
sudo apt-get remove geany
reboot
sudo apt autoremove
wget -q "http://dist.jriver.com/mediacenter@jriver.com.gpg.key" -O- | sudo apt-key add -
sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter31.list -O /etc/apt/sources.list.d/mediacenter31.list
curl -O https://git.bryanroessler.com/bryan/installJRMC/raw/master/installJRMC
chmod +x ./installJRMC
./installJRMC
sudo usermod -aG audio pi
./mcreg.sh
reboot

Edit: Just saw something, when I opened the wayvnc config file to check that I hadn't messed up there:
Code: [Select]
pi@Mastiffmobilen:~ $ sudo mousepad .config/wayvnc/config
error: XDG_RUNTIME_DIR is invalid or not set in the environment.

I guess that has something to do with it. So when doing the Bookworm installation it seems like something is not done right.
Logged
Tor with the Cinema Inferno & Multi-Zone Audio system

Mastiff

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1977
  • The Multi-Zone Tzar
Re: Being booted out to log screen when running MC in Bookworm
« Reply #9 on: October 26, 2023, 02:57:01 am »

Did another test just now, turned the Pi over from Wayland to X11. No problems at all there, so it has something to do with Wayland.
Logged
Tor with the Cinema Inferno & Multi-Zone Audio system

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5173
  • "Linux Merit Badge" Recipient
Re: Being booted out to log screen when running MC in Bookworm
« Reply #10 on: October 26, 2023, 02:21:31 pm »

Did another test just now, turned the Pi over from Wayland to X11. No problems at all there, so it has something to do with Wayland.

So one thing to know is that when a wayland compositor crashes it tends to just kill all of the programs running in the graphical scope (unlike when an xserver crashes), which would explain your "crashing out of other programs, but not in a nice way" behavior.  So I suspect that the wayland session is crashing for some reason and then you return to the login screen because there isn't anything else around anymore.  Why MC would be crashing the wayland session (and only when started via service, but not via an icon) is truly a mystery.  I assume there are no hints in the logs with journalctl -p err?

Logged

Mastiff

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1977
  • The Multi-Zone Tzar
Re: Being booted out to log screen when running MC in Bookworm
« Reply #11 on: October 27, 2023, 10:14:56 am »

Actually as I wrote in the previous messages, it crashed the Docker containers. They do not run graphically. And the last Pi I installed crashed to login when launching from an icon as well. I didn't think about journalctl, silly me... Here's the output for the jriver service, from it started and until I stopped it over ssh:

Code: [Select]
okt. 27 17:05:14 Mastiffmobilen systemd[1]: jriver.service: Consumed 2.962s CPU time.
okt. 27 17:05:14 Mastiffmobilen systemd[1]: Starting jriver.service - JRiver...
okt. 27 17:05:34 Mastiffmobilen systemd[1]: Started jriver.service - JRiver.
okt. 27 17:05:34 Mastiffmobilen mediacenter31[4294]: MediaCenter: Unable to open the X display device :0
okt. 27 17:05:34 Mastiffmobilen systemd[1]: jriver.service: Deactivated successfully.
okt. 27 17:05:44 Mastiffmobilen systemd[1]: jriver.service: Scheduled restart job, restart counter is at 2.
okt. 27 17:05:44 Mastiffmobilen systemd[1]: Stopped jriver.service - JRiver.
okt. 27 17:05:44 Mastiffmobilen systemd[1]: Starting jriver.service - JRiver...
okt. 27 17:06:05 Mastiffmobilen systemd[1]: Started jriver.service - JRiver.
okt. 27 17:06:05 Mastiffmobilen mediacenter31[4431]: MediaCenter: Unable to open the X display device :0
okt. 27 17:06:05 Mastiffmobilen systemd[1]: jriver.service: Deactivated successfully.
okt. 27 17:06:15 Mastiffmobilen systemd[1]: jriver.service: Scheduled restart job, restart counter is at 3.
okt. 27 17:06:15 Mastiffmobilen systemd[1]: Stopped jriver.service - JRiver.
okt. 27 17:06:15 Mastiffmobilen systemd[1]: Starting jriver.service - JRiver...
okt. 27 17:06:35 Mastiffmobilen systemd[1]: Started jriver.service - JRiver.
okt. 27 17:06:35 Mastiffmobilen mediacenter31[4680]: MediaCenter: Unable to open the X display device :0
okt. 27 17:06:35 Mastiffmobilen systemd[1]: jriver.service: Deactivated successfully.
okt. 27 17:06:45 Mastiffmobilen systemd[1]: jriver.service: Scheduled restart job, restart counter is at 4.
okt. 27 17:06:45 Mastiffmobilen systemd[1]: Stopped jriver.service - JRiver.
okt. 27 17:06:45 Mastiffmobilen systemd[1]: Starting jriver.service - JRiver...
okt. 27 17:07:05 Mastiffmobilen systemd[1]: Started jriver.service - JRiver.
okt. 27 17:07:05 Mastiffmobilen mediacenter31[4824]: MediaCenter: Unable to open the X display device :0
okt. 27 17:07:05 Mastiffmobilen systemd[1]: jriver.service: Deactivated successfully.
okt. 27 17:07:15 Mastiffmobilen systemd[1]: jriver.service: Scheduled restart job, restart counter is at 5.
okt. 27 17:07:15 Mastiffmobilen systemd[1]: Stopped jriver.service - JRiver.
okt. 27 17:07:15 Mastiffmobilen systemd[1]: Starting jriver.service - JRiver...
okt. 27 17:07:26 Mastiffmobilen systemd[1]: jriver.service: Control process exited, code=killed, status=1/HUP
okt. 27 17:07:26 Mastiffmobilen systemd[1]: jriver.service: Failed with result 'signal'.
okt. 27 17:07:26 Mastiffmobilen systemd[1]: Stopped jriver.service - JRiver.
lines 9-37/37 (END)

This may show even more, it has some error messages:

Code: [Select]
pi@Mastiffmobilen:~ $ journalctl -n 500 --no-pager
okt. 27 17:07:15 Mastiffmobilen systemd[1]: Stopped jriver.service - JRiver.
okt. 27 17:07:15 Mastiffmobilen systemd[1]: Starting jriver.service - JRiver...
okt. 27 17:07:17 Mastiffmobilen systemd[1]: glances.service: Scheduled restart job, restart counter is at 11.
okt. 27 17:07:17 Mastiffmobilen systemd[1]: Stopped glances.service - Glances i Docker.
okt. 27 17:07:17 Mastiffmobilen systemd[1]: Starting glances.service - Glances i Docker...
okt. 27 17:07:18 Mastiffmobilen sshd[4923]: Accepted password for pi from 192.168.2.85 port 62825 ssh2
okt. 27 17:07:18 Mastiffmobilen sshd[4923]: pam_unix(sshd:session): session opened for user pi(uid=1000) by (uid=0)
okt. 27 17:07:18 Mastiffmobilen systemd[1]: homeassistant.service: Scheduled restart job, restart counter is at 11.
okt. 27 17:07:18 Mastiffmobilen systemd[1]: nodered.service: Scheduled restart job, restart counter is at 11.
okt. 27 17:07:18 Mastiffmobilen systemd[1]: Stopped homeassistant.service - Home Assistant i Docker.
okt. 27 17:07:18 Mastiffmobilen systemd[1]: Starting homeassistant.service - Home Assistant i Docker...
okt. 27 17:07:18 Mastiffmobilen systemd[1]: Stopped nodered.service - Node-RED i Docker.
okt. 27 17:07:18 Mastiffmobilen systemd[1]: Starting nodered.service - Node-RED i Docker...
okt. 27 17:07:18 Mastiffmobilen systemd-logind[536]: New session 5 of user pi.
okt. 27 17:07:18 Mastiffmobilen systemd[1]: Started session-5.scope - Session 5 of User pi.
okt. 27 17:07:18 Mastiffmobilen sshd[4923]: pam_env(sshd:session): deprecated reading of user environment enabled
okt. 27 17:07:18 Mastiffmobilen wireplumber[1809]: listen(): Adressen er allerede i bruk
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: src/profile.c:register_profile() :1.60 tried to register 0000111f-0000-1000-8000-00805f9b34fb which is already registered
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: src/profile.c:register_profile() :1.60 tried to register 0000111e-0000-1000-8000-00805f9b34fb which is already registered
okt. 27 17:07:18 Mastiffmobilen wireplumber[1809]: RegisterProfile() failed: org.bluez.Error.NotPermitted
okt. 27 17:07:18 Mastiffmobilen wireplumber[1809]: RegisterProfile() failed: org.bluez.Error.NotPermitted
okt. 27 17:07:18 Mastiffmobilen wireplumber[1809]: Trying to use legacy bluez5 API for LE Audio - only A2DP will be supported. Please upgrade bluez5.
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/ldac
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSink/aptx_hd
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/aptx_hd
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSink/aptx
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/aptx
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSink/sbc
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/sbc
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSink/sbc_xq
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/sbc_xq
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/aptx_ll_1
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/aptx_ll_0
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/faststream
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/faststream_duplex
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSink/opus_05
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/opus_05
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSink/opus_05_duplex
okt. 27 17:07:18 Mastiffmobilen bluetoothd[815]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource/opus_05_duplex
okt. 27 17:07:18 Mastiffmobilen systemd[1]: zwavejsui.service: Scheduled restart job, restart counter is at 11.
okt. 27 17:07:18 Mastiffmobilen systemd[1]: Stopped zwavejsui.service - Z-Wave JS UI i Docker.
okt. 27 17:07:18 Mastiffmobilen systemd[1]: Starting zwavejsui.service - Z-Wave JS UI i Docker...
okt. 27 17:07:26 Mastiffmobilen sudo[4994]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/systemctl stop jriver
okt. 27 17:07:26 Mastiffmobilen sudo[4994]: pam_unix(sudo:session): session opened for user root(uid=0) by pi(uid=1000)
okt. 27 17:07:26 Mastiffmobilen systemd[1]: jriver.service: Control process exited, code=killed, status=1/HUP
okt. 27 17:07:26 Mastiffmobilen systemd[1]: jriver.service: Failed with result 'signal'.
okt. 27 17:07:26 Mastiffmobilen systemd[1]: Stopped jriver.service - JRiver.
okt. 27 17:07:26 Mastiffmobilen sudo[4994]: pam_unix(sudo:session): session closed for user root

And again the last 100, when doing another attempt, and this time it didn't crash when the service starts, but it seems to stop Docker services. Can this be a Docker vs. MC problem?

Code: [Select]
pi@Mastiffmobilen:~ $ journalctl -n 100 --no-pager
okt. 27 17:17:19 Mastiffmobilen systemd[4024]: Activating special unit exit.target...
okt. 27 17:17:19 Mastiffmobilen systemd[4024]: Stopped target default.target - Main User Target.
okt. 27 17:17:19 Mastiffmobilen systemd[4024]: Stopping dbus.service - D-Bus User Message Bus...
okt. 27 17:17:19 Mastiffmobilen systemd[4024]: Stopping gvfs-daemon.service - Virtual filesystem service...
okt. 27 17:17:19 Mastiffmobilen systemd[4024]: Stopping pipewire-pulse.service - PipeWire PulseAudio...
okt. 27 17:17:19 Mastiffmobilen systemd[4024]: Stopped dbus.service - D-Bus User Message Bus.
okt. 27 17:17:19 Mastiffmobilen systemd[4024]: Stopped pipewire-pulse.service - PipeWire PulseAudio.
okt. 27 17:17:19 Mastiffmobilen systemd[4024]: Stopping wireplumber.service - Multimedia Service Session Manager...
okt. 27 17:17:20 Mastiffmobilen systemd[1]: run-user-106-gvfs.mount: Deactivated successfully.
okt. 27 17:17:20 Mastiffmobilen wireplumber[4043]: stopped by signal: Terminert
okt. 27 17:17:20 Mastiffmobilen wireplumber[4043]: disconnected from pipewire
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Stopped gvfs-daemon.service - Virtual filesystem service.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Stopped wireplumber.service - Multimedia Service Session Manager.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: wireplumber.service: Consumed 1.021s CPU time.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Stopping pipewire.service - PipeWire Multimedia Service...
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Stopped pipewire.service - PipeWire Multimedia Service.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Removed slice session.slice - User Core Session Slice.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: session.slice: Consumed 1.372s CPU time.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Stopped target basic.target - Basic System.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Stopped target paths.target - Paths.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Stopped target sockets.target - Sockets.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Stopped target timers.target - Timers.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Closed dbus.socket - D-Bus User Message Bus Socket.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Closed dirmngr.socket - GnuPG network certificate management daemon.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Closed gcr-ssh-agent.socket - GCR ssh-agent wrapper.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Closed gnome-keyring-daemon.socket - GNOME Keyring daemon.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Closed pipewire-pulse.socket - PipeWire PulseAudio.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Closed pipewire.socket - PipeWire Multimedia System Socket.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Closed pk-debconf-helper.socket - debconf communication socket.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Removed slice app.slice - User Application Slice.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Reached target shutdown.target - Shutdown.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Finished systemd-exit.service - Exit the Session.
okt. 27 17:17:20 Mastiffmobilen systemd[4024]: Reached target exit.target - Exit the Session.
okt. 27 17:17:20 Mastiffmobilen systemd[1]: user@106.service: Deactivated successfully.
okt. 27 17:17:20 Mastiffmobilen systemd[1]: Stopped user@106.service - User Manager for UID 106.
okt. 27 17:17:20 Mastiffmobilen systemd[1]: user@106.service: Consumed 2.303s CPU time.
okt. 27 17:17:20 Mastiffmobilen systemd[1]: Stopping user-runtime-dir@106.service - User Runtime Directory /run/user/106...
okt. 27 17:17:20 Mastiffmobilen systemd[1]: run-user-106.mount: Deactivated successfully.
okt. 27 17:17:20 Mastiffmobilen systemd[1]: user-runtime-dir@106.service: Deactivated successfully.
okt. 27 17:17:20 Mastiffmobilen systemd[1]: Stopped user-runtime-dir@106.service - User Runtime Directory /run/user/106.
okt. 27 17:17:20 Mastiffmobilen systemd[1]: Removed slice user-106.slice - User Slice of UID 106.
okt. 27 17:17:20 Mastiffmobilen systemd[1]: user-106.slice: Consumed 5.675s CPU time.
okt. 27 17:17:22 Mastiffmobilen systemd[1]: Started glances.service - Glances i Docker.
okt. 27 17:17:23 Mastiffmobilen systemd[1]: Started homeassistant.service - Home Assistant i Docker.
okt. 27 17:17:23 Mastiffmobilen systemd[1]: Started nodered.service - Node-RED i Docker.
okt. 27 17:17:23 Mastiffmobilen docker[9825]:  Container Glances  Running
okt. 27 17:17:23 Mastiffmobilen systemd[1]: glances.service: Deactivated successfully.
okt. 27 17:17:23 Mastiffmobilen systemd[1]: Started zwavejsui.service - Z-Wave JS UI i Docker.
okt. 27 17:17:23 Mastiffmobilen docker[9892]:  Container Homeassistant  Running
okt. 27 17:17:23 Mastiffmobilen systemd[1]: homeassistant.service: Deactivated successfully.
okt. 27 17:17:23 Mastiffmobilen docker[9879]:  Container Node-RED  Running
okt. 27 17:17:23 Mastiffmobilen systemd[1]: nodered.service: Deactivated successfully.
okt. 27 17:17:23 Mastiffmobilen docker[9922]:  Container Z-Wave-JS-UI  Running
okt. 27 17:17:24 Mastiffmobilen systemd[1]: zwavejsui.service: Deactivated successfully.
okt. 27 17:17:25 Mastiffmobilen PackageKit[9270]: get-updates transaction /39_eaacebea from uid 1000 finished with success after 6762ms
okt. 27 17:17:26 Mastiffmobilen sudo[9973]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/systemctl start jriver
okt. 27 17:17:26 Mastiffmobilen sudo[9973]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
okt. 27 17:17:26 Mastiffmobilen systemd[1]: Starting jriver.service - JRiver...
okt. 27 17:17:33 Mastiffmobilen systemd[1]: glances.service: Scheduled restart job, restart counter is at 41.
okt. 27 17:17:33 Mastiffmobilen systemd[1]: Stopped glances.service - Glances i Docker.
okt. 27 17:17:33 Mastiffmobilen systemd[1]: Starting glances.service - Glances i Docker...
okt. 27 17:17:33 Mastiffmobilen systemd[1]: homeassistant.service: Scheduled restart job, restart counter is at 41.
okt. 27 17:17:33 Mastiffmobilen systemd[1]: nodered.service: Scheduled restart job, restart counter is at 41.
okt. 27 17:17:33 Mastiffmobilen systemd[1]: Stopped homeassistant.service - Home Assistant i Docker.
okt. 27 17:17:33 Mastiffmobilen systemd[1]: Starting homeassistant.service - Home Assistant i Docker...
okt. 27 17:17:33 Mastiffmobilen systemd[1]: Stopped nodered.service - Node-RED i Docker.
okt. 27 17:17:33 Mastiffmobilen systemd[1]: Starting nodered.service - Node-RED i Docker...
okt. 27 17:17:34 Mastiffmobilen systemd[1]: zwavejsui.service: Scheduled restart job, restart counter is at 41.
okt. 27 17:17:34 Mastiffmobilen systemd[1]: Stopped zwavejsui.service - Z-Wave JS UI i Docker.
okt. 27 17:17:34 Mastiffmobilen systemd[1]: Starting zwavejsui.service - Z-Wave JS UI i Docker...
okt. 27 17:17:43 Mastiffmobilen systemd[1]: Started glances.service - Glances i Docker.
okt. 27 17:17:43 Mastiffmobilen docker[9999]:  Container Glances  Running
okt. 27 17:17:43 Mastiffmobilen systemd[1]: glances.service: Deactivated successfully.
okt. 27 17:17:44 Mastiffmobilen systemd[1]: Started homeassistant.service - Home Assistant i Docker.
okt. 27 17:17:44 Mastiffmobilen systemd[1]: Started nodered.service - Node-RED i Docker.
okt. 27 17:17:44 Mastiffmobilen systemd[1]: Started zwavejsui.service - Z-Wave JS UI i Docker.
okt. 27 17:17:44 Mastiffmobilen docker[10035]:  Container Homeassistant  Running
okt. 27 17:17:44 Mastiffmobilen docker[10040]:  Container Node-RED  Running
okt. 27 17:17:44 Mastiffmobilen systemd[1]: homeassistant.service: Deactivated successfully.
okt. 27 17:17:44 Mastiffmobilen systemd[1]: nodered.service: Deactivated successfully.
okt. 27 17:17:44 Mastiffmobilen docker[10071]:  Container Z-Wave-JS-UI  Running
okt. 27 17:17:44 Mastiffmobilen systemd[1]: zwavejsui.service: Deactivated successfully.
okt. 27 17:17:46 Mastiffmobilen systemd[1]: Started jriver.service - JRiver.
okt. 27 17:17:46 Mastiffmobilen sudo[9973]: pam_unix(sudo:session): session closed for user root
okt. 27 17:17:53 Mastiffmobilen systemd[1]: glances.service: Scheduled restart job, restart counter is at 42.
okt. 27 17:17:53 Mastiffmobilen systemd[1]: Stopped glances.service - Glances i Docker.
okt. 27 17:17:53 Mastiffmobilen systemd[1]: Starting glances.service - Glances i Docker...
okt. 27 17:17:54 Mastiffmobilen systemd[1]: homeassistant.service: Scheduled restart job, restart counter is at 42.
okt. 27 17:17:54 Mastiffmobilen systemd[1]: nodered.service: Scheduled restart job, restart counter is at 42.
okt. 27 17:17:54 Mastiffmobilen systemd[1]: Stopped homeassistant.service - Home Assistant i Docker.
okt. 27 17:17:54 Mastiffmobilen systemd[1]: Starting homeassistant.service - Home Assistant i Docker...
okt. 27 17:17:54 Mastiffmobilen systemd[1]: Stopped nodered.service - Node-RED i Docker.
okt. 27 17:17:54 Mastiffmobilen systemd[1]: Starting nodered.service - Node-RED i Docker...
okt. 27 17:17:54 Mastiffmobilen systemd[1]: zwavejsui.service: Scheduled restart job, restart counter is at 42.
okt. 27 17:17:54 Mastiffmobilen systemd[1]: Stopped zwavejsui.service - Z-Wave JS UI i Docker.
okt. 27 17:17:54 Mastiffmobilen systemd[1]: Starting zwavejsui.service - Z-Wave JS UI i Docker...
Logged
Tor with the Cinema Inferno & Multi-Zone Audio system

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5173
  • "Linux Merit Badge" Recipient
Re: Being booted out to log screen when running MC in Bookworm
« Reply #12 on: October 27, 2023, 10:35:26 pm »

So not to ask a silly question, but are you keeping an eye on your memory usage with all those services running on a Pi?  Like you've got a lot of things running and are seeing some weird non-deterministic behavior and I wonder if you're running out of memory, which will often cause jriver or a wayland session to crash. 

I'm not really a docker expert (I avoid it when possible), but if I were in your spot, I'd probably turn off all the docker stuff as a test, and then if jriver works normally I'd turn on the docker services one at a time until things break to see what the issue is.
Logged

Mastiff

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1977
  • The Multi-Zone Tzar
Re: Being booted out to log screen when running MC in Bookworm
« Reply #13 on: October 28, 2023, 02:21:51 am »

As for the Docker  stuff I avoided it like a plague until Home Assistant became impossible to keep updated with a regular/core installation because of the weird dependencies. Then I went all in, and all my necessary stuff went Docker Compose. So Home Assistant, Node-RED, Glances (which monitors the Pi for memory use, temperature and so on), Z-Wave JS UI, Telldus Core (which is impossible to run on anything newer then Stretch without Docker) and SignalK in the boat (navigation and boat monitoring). The best thing is that setting up a working pi takes me max an hour from I put the SD Card in the Pi since I can copy the directories with Docker-Compose YML files and the data from the mentioned programs directly from a working setup to the new one and have everything up and running in the time it takes Docker to download, unpack and create the images and then start up the containers.

But it doesn't really come into this, because as you can see in my message nr. 8:
Quote
And I tried with a new Pi now. Same type, Pi 4 4 gig RAM. I burnt the OS, did an upgrade and used your script to install. Same problem, only worse. Even the icon version booted me to log in screen, and  this time I had an error while trying to activate WayVNC
So this was before I even installed Docker.

And memory and CPU use the last 24 hours (the drop at 4 is a scheduled reboot every  night, sort of a self-healing I use on every Pi I have). I don't think this should be a problem. The graph is Glances seen through Home Assistant.

Oh, and if it helps, I could do an image backup of the Pi with only MC running in service mode (with the password changed, of course) and let you download it from my FTP, if you want to see if you have the same problem. PM me if that's something you'd like to try.
Logged
Tor with the Cinema Inferno & Multi-Zone Audio system

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13487
Re: Being booted out to log screen when running MC in Bookworm
« Reply #14 on: November 02, 2023, 06:10:40 pm »

This is totally not in my wheelhouse but could you run tigervnc-standalone-server?
That will run as the "Primary" X server. You need no other. Then display:0 should work fine.
Logged

BryanC

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2554
Re: Being booted out to log screen when running MC in Bookworm
« Reply #15 on: November 04, 2023, 09:29:48 am »

Code: [Select]
MediaCenter: Unable to open the X display device :0

This is your problem. Either the display doesn't exist (never created or crashed) or it's a different number and you'll need to set it appropriately in the service file. If you can get to the display then just `echo $DISPLAY`.

Or you can try running installJRMC, it can create a proper standalone vnc display server for MC to run merrily inside, and the appropriate service files to start it at boot.

Code: [Select]
./installJRMC --install repo --service jriver-xvnc --service-type system
Let me know how it goes.
Logged

Mastiff

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1977
  • The Multi-Zone Tzar
Re: Being booted out to log screen when running MC in Bookworm
« Reply #16 on: December 06, 2023, 07:07:05 am »

I apologize for the long silence here. First there was a period of so bad weather that I had to put the boat in the storm harbor I use, where I have no access to the Pi. Then I have been to busy to think about it for a couple of weeks. But I experimented a bit more and it seems clear that the VNC is problem. I tried to install Tiger VNC's scraping server, but it didn't work out. I could never get that to start reliably as a service. Then I tried with Nomachine instead of VNC, and by using a dummy HDMI plug I finally got it working. But it's a bit too much hazzle, and the text is annoyingly fuzzy, so I went back to X11 instead of Wayland. Now I'm just going to use that until RealVNC has something that works with Wayland, they have promised to have that ready some time in the first half of 2024. Thanks for the patience and advice, y'all!  ;D
Logged
Tor with the Cinema Inferno & Multi-Zone Audio system
Pages: [1]   Go Up