As noted in Bug #99873, many session services are named in a non-canonical way. One thing we can do to make this better is: if a directory in the search path contains a canonically-named service and a non-canonically-named service for the same well-known bus name, we should prefer the canonically-named one, instead of just taking whichever comes first in readdir() order.
To be clear, you mean to order by (search path, is canonically named?) rather than (is canonically named?, search path), right? The current behaviour is (search path, random).
(In reply to Philip Withnall from comment #1) > To be clear, you mean to order by (search path, is canonically named?) > rather than (is canonically named?, search path), right? The current > behaviour is (search path, random). Yes. A non-canonically-named service in /usr/local should still beat a canonically-named service in /usr.
Created attachment 129772 [details] [review] activation: Add support for enforcing strict naming on .service files This is done on a per-directory basis. The use of the BusContext here means we have to make the activation test a little more realistic, by providing a non-NULL BusContext. --- Move BusServiceDirFlags in BusServiceDirectory from previous commit to here. Add bug references. Log a _dbus_verbose() for Bug #99873 for now.
Comment on attachment 129772 [details] [review] activation: Add support for enforcing strict naming on .service files Sigh, wrong bug.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/dbus/dbus/issues/169.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.