I am not familiar with Braille devices, but a few things stood out to me in the discussion here.
On Wed, Jan 14, 2026 at 20:08:22 +0100, Samuel Thibault wrote: > Adrian Vovk, le mer. 14 janv. 2026 12:28:51 -0500, a ecrit: > > This applies to any session service. Dconf. gnome-settings-daemon. Etc > > So we just decided to stop being able to do concurrency, ok. Services that support concurrency would need to use a per-session directory/scoping for any resources they provide. DBus paths (either the bus itself or the exposed objects/interfaces), socket paths, etc. Do they do so? > > Pipewire is related to the graphical session because it's tied to a seat. > > Yes, to a seat, but not to a particular session which is graphical. It > can be used just all the same in a text console etc. Which is very > different from a tray icon which is meaning less on a text console, and > clearly for a graphical session. But devices are revoked when switching session. Or should they, perhaps, be more associated with the user of the session instead? Either way, anything using the resource(s) need to agree with logind's behavior. --Ben
