-
-
Notifications
You must be signed in to change notification settings - Fork 522
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
dbus-user-session dependency causes issues with chrome #358
Comments
I can confirm that removing razer-daemon, polychromatic and dbus-user-session resolves the gnome-keyring and chrome issue in 16.04.3. Right now removing dbus-user-session forces the removal of its dependencies, namely razer-daemon and polychromatic. |
That's how much I love Ubuntu. Having millions of bug reports that never get any attention from people that fix stuff... Unfortunately we can't really do much if the distro is broken :/ |
@z3ntu I'm in the same boat trying to run Ubuntu and the razor drivers. Is dbus-user-session a hard dependency are there any alternatives or workarounds anyone has gotten to work? |
It would be nice to have. Another method of autostarting the daemon would be putting the razer-daemon.desktop file in the repository into /etc/xdg/autostart/ and removing the dbus-user-session package. I don't know if this can be achieved with dpkg packages but maybe... |
I thought about this the other day, worse case we could just used xdg for all of ubuntu till we can drop 16.04 |
I'll have to figure out how my driver is getting loaded. I removed udev from my startup, and every thing still gets bound correctly every boot. |
Weird |
There's a workaround: |
@EchoCloud and rest here: They are based on the contents in the PR #402 |
I installed the daily version from ppa:openrazer/daily on Ubuntu 16.04.3 and dbus-user-session was installed too. Is this expected? |
Also interested in the correct way to install these. |
I found that installing the drivers will install
Note that this may not work for you depending on your config, but it's worth a shot. |
Found the issue why launchpad is failing my check: |
Should be fixed in 980462d (so in tomorrows build) |
It works well for me now. Thank you! |
v2.1 is out |
This isn't exactly the driver's fault, but at the moment on Ubuntu 16.04 installing the dbus-user-session package causes gnome-keyring not to unlock on boot, which causes Chrome to take ages to start and not unlock your passwords.
As dbus-user-session is not a default package it's likely that the driver package will end up installing it. If it breaks chrome it will probably appear to the user as if it was the driver package that caused the issue.
Uninstalling dbus-user-session "fixes" the issue, but I've yet to test whether razer-drivers will continue to work (currently uninstalled on my system).
This is probably pretty common at the moment, so may be worth documenting on the website, or at least here in this issue.
gnome-keyring issue tracker has more info here: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825
The text was updated successfully, but these errors were encountered: