You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues and found none that matched mine
Describe the feature
/etc is a very special thing in debian-based systems and storing files there implies that those may not be removed on package removal unless purge is done.
This may be a problem in authd because we still list the broker as installed even though it's not there anymore.
Describe the ideal solution
While authd maybe could do some better sanity check on available brokers in the bus, it's probably better to use other paths such as /usr/lib or /usr/share as the place where we look for the brokers.d folder to prevent being broken or not-well-working because of leftovers of configuration files.
Alternatives and current workarounds
No response
Ubuntu users: System information and logs
No response
Non Ubuntu users: System information and logs
No response
Relevant information
No response
Double check your logs
I have redacted any sensitive information from the logs
The text was updated successfully, but these errors were encountered:
Is there an existing request for this feature?
Describe the feature
/etc
is a very special thing in debian-based systems and storing files there implies that those may not be removed on package removal unless purge is done.This may be a problem in authd because we still list the broker as installed even though it's not there anymore.
Describe the ideal solution
While authd maybe could do some better sanity check on available brokers in the bus, it's probably better to use other paths such as
/usr/lib
or/usr/share
as the place where we look for thebrokers.d
folder to prevent being broken or not-well-working because of leftovers of configuration files.Alternatives and current workarounds
No response
Ubuntu users: System information and logs
No response
Non Ubuntu users: System information and logs
No response
Relevant information
No response
Double check your logs
The text was updated successfully, but these errors were encountered: