You are not logged in.

#1 2024-04-27 04:10:24

RoKoInfo
Member
Registered: 2020-09-11
Posts: 4

[Solved] greetd/agreety: 0.10.0-1 vs. 0.9.0-3

Dear Archers,

I use greetd/agreety to start a rootless X, which worked fine using 0.9.0-3, but does not work on 0.10.0-1. When using the latter, Xorg.0.log complains about permission denied on /dev/tty0, which is indeed correct. However, a downgrade of greetd/agreety brings the intended function back. In this case, X runs on /dev/tty1, with adjusted owner.

Question Is this intended behavior of the new version of greetd, or a bug?

Thank you in advance, best regards
RoKoInfo

Last edited by RoKoInfo (2024-04-28 09:32:55)

Offline

#2 2024-04-27 07:31:02

seth
Member
Registered: 2012-09-03
Posts: 51,842

Offline

#3 2024-04-27 08:56:56

RoKoInfo
Member
Registered: 2020-09-11
Posts: 4

Re: [Solved] greetd/agreety: 0.10.0-1 vs. 0.9.0-3

I gave .xserverrc a fast try, however, it did not work immediately. I don't think, that I spend more time fiddling around with it, I just keep greetd downgraded to 0.9.0. I am fine with it, and it seems that the next minor upgrade should do the trick.

Thank you for the prompt reply.

Offline

#4 2024-04-27 14:58:29

seth
Member
Registered: 2012-09-03
Posts: 51,842

Re: [Solved] greetd/agreety: 0.10.0-1 vs. 0.9.0-3

Can you control it w/ https://git.sr.ht/~kennylevinsen/greetd … 0020cec92c ?

it seems that the next minor upgrade should do the trick

Removing $XDG_VTNR is likely the cause but you don't know.
If you want to use xserverrc (and assuming you're using xinit/startx) try to hardcode the value, $XDG_VTNR cannot work because greetd currently clears that.

Offline

#5 2024-04-28 07:16:03

RoKoInfo
Member
Registered: 2020-09-11
Posts: 4

Re: [Solved] greetd/agreety: 0.10.0-1 vs. 0.9.0-3

The solution of choice now is a hard-coded vt 1 in xserverrc, and greetd 0.10.0. Thanks again for your fast support.

Offline

#6 2024-04-28 07:27:47

seth
Member
Registered: 2012-09-03
Posts: 51,842

Re: [Solved] greetd/agreety: 0.10.0-1 vs. 0.9.0-3

\o/
Also confirms it's the issue already addressed upstream -  don't forget to unhardcode the value after the next update.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

Board footer

Powered by FluxBB