Hey! thanks for replying my post!!There's an important piece of information you haven't told us: in what way is it "not working..."?
If you don't know or if it just isn't running you need to find out why. If you don't know that, all anyone can do is guess.
Start by capturing any errors from your service (hint: look in the systemd journal) and any thrown by your script (hint redirect stderr to a file).
You could do worse that referring to the troubleshooting advice in Running A Program At Start Up A Beginner's Guide
I've seen you in some posts regarding to this topic, so thank you for the support you've given to this forum.
This is not working beacause, when I reboot my raspberry, systemd doesn't seam to run chromium automatically, it still appears the terminal.
Until/unless you find and post the error(s) all I can do is refer to my post above. There are many possible reasons why it might be failing to launch. If I guess and , as is likely, guess wrong that'll waste a lot of both our time.
I executed the next line on mi raspberryCode:
/usr/bin/labwc
and it opened the link on chromium (The one I specified on my autostart script).
Not the same situation as when running from systemd. Under systemd the pwd may be different, your startup scripts (.bashrc etc) have not been run, the system wide version of those scripts also have not been run, and your process is not attached to a terminal.
However, when I run the same line on my remoted computer (ssh)This is what I get:Code:
/usr/bin/labwcSe me ocurrió correr /usr/bin/labwc y si cargó la pagina de Chromium, eso me hace pensar que no hay problema con el script. Sin embargo, al correr /usr/bin/labwc de forma remota en mi computadora (ssh) me sigue apareciendo este error. 00:00:00.000 [libseat] [libseat/backend/seatd.c:308] Could not poll connection: Broken pipe
00:00:00.001 [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
00:00:00.001 [libseat] [seatd/seat.c:61] Could not open tty0 to update VT: Permission denied
00:00:00.001 [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
00:00:00.001 [libseat] [seatd/seat.c:72] Could not open terminal for VT 0: Permission denied
00:00:00.001 [libseat] [seatd/seat.c:461] Could not open VT for client
00:00:00.001 [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
00:00:00.001 [libseat] [seatd/seat.c:86] Could not open terminal to clean up VT 0: Permission denied
00:00:10.011 [backend/backend.c:105] Timeout waiting session to become active
00:00:10.011 [backend/backend.c:407] Failed to start a DRM session
00:00:10.011 [../src/server.c:468] unable to create backend
Some friendly trouble-shooting help
===================================
If a seat could not be created, this may be caused by lack of permission to the
seat, input and video groups. If you are using a systemd setup, try installing
polkit (sometimes called policykit-1). For other setups, search your OS/Distro's
documentation on how to use seatd, elogind or similar. This is likely to involve
manually adding users to groups.
If the above does not work, try running with `WLR_RENDERER=pixman labwc` in
order to use the software rendering fallback
00:00:10.014 [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
00:00:10.014 [libseat] [seatd/seat.c:86] Could not open terminal to clean up VT 0: Permission denied
Looks like security issues. I wouldn't expect starting labwc, wayfire, or X11 for that matter to be possible from an ssh session. You need to be logged in on the console (i.e. a directly connected keyboard and monitor).
Note: section 5.2.4 of my guide (see link above) explains how to do what you want when using X11. I don't know the required incantations for labwc.
Statistics: Posted by thagrol — Mon Oct 13, 2025 11:38 pm