-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always run anaconda private dbus session #1369
Always run anaconda private dbus session #1369
Conversation
jenkins, test this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me otherwise. Thank you!
data/dbus/session.conf
Outdated
|
||
Author(s): Jiri Konecny <jkonecny@redhat.com | ||
--> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, change the name of the file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The config file looks to be too strict, but that is fine for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can change the policy anytime we want.
74329fb
to
9078a4b
Compare
Configurations are placed in /usr/share/anaconda/dbus/confs DBus service files are placed in /usr/share/ananconda/dbus/services And main configuration file is placed in /usr/share/anaconda/dbus Thanks to this change we can setup permission as we need and change them when we need. Also it will avoid situations when user connects to a module and change its settings in an unexpected way. As a bonus for debugging we can easily trace traffic on our DBus without interference of other services. Related: rhbz#1551096
Do not use DBUS_SESSION_BUS_ADDRESS anymore because we now have our private session in all cases. Related: rhbz#1551096
We don't need this when we are running our own DBus session all the time. Resolves: rhbz#1551096
The process python object return None if the process is still running not otherwise.
9078a4b
to
20858c5
Compare
UPDATED:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me now.
We have our private DBus with our specific configuration.
Our private DBus is launched every time when Anaconda is started.
We are using our dbus variable instead of
DBUS_SESSION_BUS_ADDRESS
.