~kennylevinsen/greetd-devel

Fwd: greetd crashing on 0.9.0 immediately after login

Details
Message ID
<CAPc+dh=d-WqoqNprTefrVB0O52kkVcLwE_FBfK2iLH4810jOww@mail.gmail.com>
DKIM signature
missing
Download raw message
Forwarding to list too (oops).

---------- Forwarded message ---------
From: Jeff Peeler <jpeeler@gmail.com>
Date: Tue, Jul 4, 2023 at 4:55 PM
Subject: Re: greetd crashing on 0.9.0 immediately after login
To: Kenny Levinsen <kl@kl.wtf>


On Sun, Jul 2, 2023 at 5:14 AM Kenny Levinsen <kl@kl.wtf> wrote:
>
> On 7/1/23 22:59, Jeff Peeler wrote:
> > Not sure if this is the best place to report this? I've configured
> > greetd to use tuigreet. Immediately after logging in I get the error -
> > read main panicked at 'unable to exec: EACCESS'
>
> That's execve failing to exec /bin/sh to run your session command line
> (https://git.sr.ht/~kennylevinsen/greetd/tree/67eaa39b936e07e4415497031efcfc74178469da/item/greetd/src/session/worker.rs#L271).
>
> As per `man 2 execve`, these are possible causes for that error:
>
> - Search permission is denied on a component of the path prefix of
> pathname or the name of a script interpreter.  (See also
> path_resolution(7).)
>
> - The file or a script interpreter is not a regular file.
>
> - Execute permission is denied for the file or a script or ELF interpreter.
>
> - The filesystem is mounted noexec.
>
> Seeing that an absolute path to /bin/sh is used, PATH shouldn't matter.
> If you use Fedora or similar, maybe you are dealing with an SELinux
> situation?

Ah yes, it was an SELinux issue. I'll make sure to notify the upstream
packager to get it sorted.
Reply to thread Export thread (mbox)