Getting GUI interface after using systemctl stop

[GitRayc]

Picframe working well and autostarts as per install

After using he systemctl stop command it stops as it should and returns me to the command prompt in pi4

If is use startx to get the Gui interface again it doesn't work. I get some errors complaining about x11

How can I invoked the GUI interface from command line after stopping the picframe service?

New install on pi4 with bookworm.

Thanks Ray

[GitRayc]

Sorry should have mentioned I used the version of bookworm for pi4 from pi imager that is labeled recommended. I think it might be the light version? Maybe that does not include the x11 libraries?

[paddywwoof]

I'm away at the moment so can't test but try wayfire-pi. I think startx does still work but you would have to comment the line we added to /home/pi/.config/wayfire.ini that tells it not to use X11

[GitRayc]

so issued command to stop slideshow Returned me to command prompt.

Issued command wayfire-pi

That resulted in a number of permission denied errors. EE 27-11-23 20:00:46.433 - [libseat] [common/terminal.c:162] Could not open target tty: Permission denied EE 27-11-23 20:00:46.433 - [libseat] [seatd/seat.c:61] Could not open tty0 to update VT: Permission denied EE 27-11-23 20:00:46.433 - [libseat] [common/terminal.c:162] Could not open target tty: Permission denied EE 27-11-23 20:00:46.433 - [libseat] [seatd/seat.c:72] Could not open terminal for VT 0: Permission denied EE 27-11-23 20:00:46.433 - [libseat] [seatd/seat.c:461] Could not open VT for client EE 27-11-23 20:00:46.433 - [libseat] [common/terminal.c:162] Could not open target tty: Permission denied EE 27-11-23 20:00:46.433 - [libseat] [seatd/seat.c:86] Could not open terminal to clean up VT 0: Permission denied EE 27-11-23 20:00:56.444 - [backend/backend.c:114] Timeout waiting session to become active EE 27-11-23 20:00:56.444 - [backend/backend.c:352] Failed to start a DRM session EE 27-11-23 20:00:56.444 - [src/main.cpp:144] Fatal error: Segmentation fault EE 27-11-23 20:00:56.508 - #1 wf::print_trace(bool) ??:? addr2line: ',': No such file addr2line: ',': No such file EE 27-11-23 20:00:56.536 - #2 xSx xSx EE 27-11-23 20:00:56.568 - #3 wlr_backend_get_drm_fd ??:? EE 27-11-23 20:00:56.604 - #4 main ??:? EE 27-11-23 20:00:56.920 - #5 __libc_start_call_main ../sysdeps/unix/sysv/linux/aarch64/libc-start.c:74 EE 27-11-23 20:00:57.123 - #6 call_init ../csu/libc-start.c:128 EE 27-11-23 20:00:57.145 - #7 _start ??:?

Would be really nice to be able to launch GUI after quitting slideshow.. And of course cant launch GUI at start because slideshow is set to startup at boot which I want

Ray

[GitRayc]

If it matters: pi@raspberrypi:~ $ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"

[GitRayc]

And: pi@raspberrypi:~ $ dpkg -l | grep xorg ii xorg-sgml-doctools 1:1.11-1.1 all Common tools for building X.Org SGML documentation ii xserver-xorg 1:7.7+23 arm64 X.Org X server ii xserver-xorg-core 2:21.1.7-3+rpt1+deb12u2 arm64 Xorg X server - core server ii xserver-xorg-input-all 1:7.7+23 arm64 X.Org X server -- input driver metapackage ii xserver-xorg-input-libinput 1.2.1-1+b1 arm64 X.Org X server -- libinput input driver ii xserver-xorg-video-all 1:7.7+23 arm64 X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu 23.0.0-1 arm64 X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati 1:19.1.0-3 arm64 X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev 1:0.5.0-2 arm64 X.Org X server -- fbdev display driver ii xserver-xorg-video-fbturbo 1.20210602~095927+1+bookworm arm64 X.Org X server -- fbturbo display driver ii xserver-xorg-video-nouveau 1:1.0.17-2 arm64 X.Org X server -- Nouveau display driver ii xserver-xorg-video-radeon 1:19.1.0-3 arm64 X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-vesa 1:2.5.0-1+b1 arm64 X.Org X server -- VESA display driver pi@raspberrypi:~ $ echo $XDG_SESSION_TYPE tty pi@raspberrypi:~ $

[GitRayc]

Sorry to bother.  Which line would I comment?Sent from my iPhone. Ray C.On Nov 26, 2023, at 10:06 AM, Paddy @.***> wrote: I'm away at the moment so can't test but try wayfire-pi. I think startx does still work but you would have to comment the line we added to /home/pi/.config/wayfire.ini that tells it not to use X11

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[paddywwoof]

Hi, sorry not to get back to you earlier. Some of those wayfire-pi errors looked bad ([src/main.cpp:144] Fatal error: Segmentation fault .. but what do you expect with cpp - nightmare language that it is) It might be possible to fix them by running sudo wayfire-pi but maybe you can achieve your desired result by not setting the raspi-config option to boot to desktop. That would mean that the whole OS desktop loads, which is a bit of extra load and delay, but once the slideshow is running, it's not using any processor time, just a chunk of memory.

I will play around on my RPi 4 here and see what you need to put into .config/wayfire.ini and so on, and let you know.

Paddy