-
Notifications
You must be signed in to change notification settings - Fork 107
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
On Fedora 33 the daemon cannot connect to DBus #453
Comments
I don't know if it helps, but, do you mind to test this: https://stackoverflow.com/questions/11170118/dbus-systembus-policies ? |
I've noticed that the build directory has this structure: build/ So I've copied those files under /usr/share It turned out to be a naive move... My installation has SELinux enabled which broke dbus and made the system unbootable. I managed to recover it, but clearly it's a bit more complicated than this. At least when SELinux is on. Edit: one possible solution could be disabling SELinux and copying those files again into /usr/share. If anybody has more experience/knowledge of SELinux and wants to suggest how to proceed, I'm happy to discuss it. |
Built on Fedora 33 as well. Attempting to connect just cycles through connecting -> disconnecting -> VPN is off. (tried with both selinux enabled/disabled) ~/.local/share/mozillavpn.txt:
|
I managed to build the client on Fedora 33 without particular problems.
When I try to run it I have this error:
This is clearly due to some more restrictive policy on Fedora. Does anybody know how to fix it?
Note: the log file /root/.local/share/mozillavpn.txt contains exactly the same output as above.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: