| 1 |
El jue, 19-03-2020 a las 10:35 -0400, Mike Gilbert escribió: |
| 2 |
> On Thu, Mar 19, 2020 at 9:41 AM Mart Raudsepp <leio@g.o> wrote: |
| 3 |
> > Ühel kenal päeval, K, 18.03.2020 kell 16:43, kirjutas Mike Gilbert: |
| 4 |
> > > Seems good to me in principle, but I'm not sure it is something we |
| 5 |
> > > > should do until we haven't promoted this into a global USE flag. |
| 6 |
> > > |
| 7 |
> > > An alternative would be to add entries in package.use. |
| 8 |
> > |
| 9 |
> > Yeah, that'd be what it is now, just done in systemd profile, not most |
| 10 |
> > of the separate systemd profiles. |
| 11 |
> > |
| 12 |
> > > > With the disclaimer of not knowing anything about dbus[user- |
| 13 |
> > > > session] on |
| 14 |
> > > > a non-systemd system - maybe it's just time to make user-session |
| 15 |
> > > > unconditionally enabled on dbus (and then bluez) instead? |
| 16 |
> > > > All it seems to do (on a very quick look) is install some extra |
| 17 |
> > > > systemd |
| 18 |
> > > > files - can't they just be always installed (by always passing -- |
| 19 |
> > > > enable-user-session) and call it a day? |
| 20 |
> > > |
| 21 |
> > > It looks like user-session has no effect if systemd is not in use. |
| 22 |
> > > |
| 23 |
> > > On systems running systemd, having the units installed automatically |
| 24 |
> > > enables the systemd user bus, and the only way to disable it is to |
| 25 |
> > > mask the units. Having the user bus enabled generally prevents |
| 26 |
> > > display |
| 27 |
> > > managers and startx from starting individual session buses, since |
| 28 |
> > > they |
| 29 |
> > > will use the user bus instead. That's probably fine, but I wanted to |
| 30 |
> > > note it. |
| 31 |
> > |
| 32 |
> > So how about we try to just always enable this instead in dbus and |
| 33 |
> > bluez? Anyone got any objections, provided the below can be handled? |
| 34 |
> > |
| 35 |
> > I peeked at bluez, and there USE=user-session exists to apply a patch |
| 36 |
> > to unbreak things when user-session is disabled. Unfortunately it seems |
| 37 |
> > to be needed there for non-systemd systems as well. I think we should |
| 38 |
> > be able to figure things out to work in all situations there, or make |
| 39 |
> > it be applied for USE=-systemd only (that's already the case there, |
| 40 |
> > just it is not applied for USE="systemd -user-session" right now). |
| 41 |
> |
| 42 |
> I think we can apply |
| 43 |
> 0001-Allow-using-obexd-without-systemd-in-the-user-session-r2.patch |
| 44 |
> unconditionally. |
| 45 |
> |
| 46 |
> The patched unit should work just fine with systemd, provided the user |
| 47 |
> bus is available. |
| 48 |
> |
| 49 |
|
| 50 |
I agree, I see that also Debian is applying it unconditionally even when running |
| 51 |
systemd |
Archives