Re: [systemd-devel] Issue with systemd-logind

2024-02-14 Thread Lennart Poettering
On Mi, 14.02.24 15:03, Akshaya Maran (akshayamara...@gmail.com) wrote:

> Hi,
>
> I am trying to run weston11.0.1 using systemd logind launcher but got this 
> error
> " logind: failed to get session seat
> logind: cannot setup systemd-logind helper error:"

This looks like an error message from some weston thing. Please ask
that community for help.

Lennart

--
Lennart Poettering, Berlin


[systemd-devel] Issue with systemd-logind

2024-02-14 Thread Akshaya Maran
Hi,

I am trying to run weston11.0.1 using systemd logind launcher but got this error
" logind: failed to get session seat
logind: cannot setup systemd-logind helper error:"

I referred to yocto build . I added
weston.service,weston.socket,weston-autologin,weston-start and other
files attached and
exported a few variables . And also created weston user . Should I run
in root/ weston user ?
When I tried to boot , I could see a log for loginctl seat0  but not
attached to the loginctl session.

Am I missing any additional packages or services or any files that
need to be added  ??

I am attaching my log and files I used . Can you please help me to
understand and  solve this issue?

Thanks,
Akshaya


weston_log_14_2_24
Description: Binary data


profile
Description: Binary data
# This is a system unit for launching Weston with auto-login as the
# user configured here.
#
# Weston must be built with systemd support, and your weston.ini must load
# the plugin systemd-notify.so.
[Unit]
Description=Weston, a Wayland compositor, as a system service
Documentation=man:weston(1) man:weston.ini(5)
Documentation=http://wayland.freedesktop.org/

# Make sure we are started after logins are permitted.
Requires=systemd-user-sessions.service
After=systemd-user-sessions.service

# If Plymouth is used, we want to start when it is on its way out.
After=plymouth-quit-wait.service

# D-Bus is necessary for contacting logind. Logind is required.
Wants=dbus.socket
After=dbus.socket

# Ensure the socket is present
Requires=weston.socket

# Since we are part of the graphical session, make sure we are started before
# it is complete.
Before=graphical.target

# Prevent starting on systems without virtual consoles, Weston requires one
# for now.
ConditionPathExists=/dev/tty0

[Service]
# Requires systemd-notify.so Weston plugin.
Type=notify
EnvironmentFile=/etc/default/weston
ExecStart=/usr/bin/weston --modules=systemd-notify.so

# Optional watchdog setup
#TimeoutStartSec=60
#WatchdogSec=20

# The user to run Weston as.
User=weston
Group=weston

# Make sure the working directory is the users home directory
WorkingDirectory=/home/weston

# Set up a full user session for the user, required by Weston.
PAMName=weston-autologin

# A virtual terminal is needed.
TTYPath=/dev/tty7
TTYReset=yes
TTYVHangup=yes
TTYVTDisallocate=yes

# Fail to start if not controlling the tty.
StandardInput=tty-fail
StandardOutput=journal
StandardError=journal

# Log this user with utmp, letting it show up with commands 'w' and 'who'.
UtmpIdentifier=tty7
UtmpMode=user

[Install]
# Note: If you only want weston to start on-demand, remove this line with a
# service drop file
WantedBy=graphical.target
[Unit]
Description=Weston socket
RequiresMountsFor=/run

[Socket]
ListenStream=/run/wayland-0
SocketMode=0775
SocketUser=weston
SocketGroup=wayland
RemoveOnStop=yes

[Install]
WantedBy=sockets.target



weston-start
Description: Binary data


weston-autologin
Description: Binary data


init
Description: Binary data


weston.ini
Description: Binary data