|
From: | muradm |
Subject: | bug#56971: greeter user permissions are not enough to talk with seatd |
Date: | Sun, 07 Aug 2022 23:48:36 +0300 |
User-agent: | mu4e 1.8.7; emacs 29.0.50 |
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:
Point is not that "there are any/others affected", the point is, thatAm Freitag, dem 05.08.2022 um 09:48 +0300 schrieb muradm:But it is greetd that does, no? If there are other greeting mechanisms currently packaged in Guix falling short of this, please do tell.Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes: > Am Donnerstag, dem 04.08.2022 um 15:52 +0300 schrieb muradm: > >> > Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> > > writes:> >> > > [...] [L]ooking at the two patches, it appears they are > > > to> > > be used in combination? > > >> > No, technically they are not strongly dependent on each > > other,> > could be applied one after another in no particular order.> > After both are applied, in cooperation they address this > > issue. > This is what I'm saying, albeit in different words. As far > as I> understand, neither of these patches really accomplishes > anything if> not put together. Thus, you more or less opened three issues > to> address one.Really I don't know what to comment here else. My analysis showed two independent issues, one is that seatd should have a declaredgroup so that users of it could join it. This issues is notspecific to greetd/greeter in any way. Any other greeting mechanismcould fall short on this.
seatd is providing and interface, and currently it has a problem, which is wrong permission.
And second, greeter today required conditional group to interact with seatd, or it could be any other group like input, usb, modem or elseIt is not really a problem, but an observation. I personally think a single series that has both patches would have been more visible than this thing split across three topics for two patches. There is a small overhead if you have to consider merges and blocks, even if debbugsdepending on user setup. Solutions are offered accordingly. Third issue, this bug I was asked to open. I don't understand, is it a sin to have multiple issues, or what is the problem here?supports them.
This is phylosophical topic, which I suppose is not in the scope.
Cheers
signature.asc
Description: PGP signature
[Prev in Thread] | Current Thread | [Next in Thread] |