Skip to content
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

Closed
MannyC opened this issue Aug 15, 2017 · 16 comments
Closed

dbus-user-session dependency causes issues with chrome #358

MannyC opened this issue Aug 15, 2017 · 16 comments
Labels

Comments

@MannyC
Copy link

MannyC commented Aug 15, 2017

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

@EricMCarroll
Copy link

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.

@z3ntu
Copy link
Member

z3ntu commented Aug 23, 2017

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 :/

@aldencolerain
Copy link

@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?

@z3ntu
Copy link
Member

z3ntu commented Aug 26, 2017

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...

@terricain
Copy link
Member

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

@Zerophase
Copy link
Contributor

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.

@terricain
Copy link
Member

terricain commented Sep 19, 2017

Weird

@ptrvilya
Copy link

ptrvilya commented Oct 2, 2017

There's a workaround:
gnome-keyring-daemon &
[From askubuntu]

@z3ntu
Copy link
Member

z3ntu commented Oct 3, 2017

@EchoCloud and rest here:
Please try the debs and reboot (note: they are only for 16.04!)
1604debs.tar.gz

They are based on the contents in the PR #402

@ghost
Copy link

ghost commented Oct 18, 2017

I installed the daily version from ppa:openrazer/daily on Ubuntu 16.04.3 and dbus-user-session was installed too. Is this expected?

@ssnl
Copy link

ssnl commented Oct 18, 2017

Also interested in the correct way to install these.

@KazWolfe
Copy link
Contributor

I found that installing the drivers will install dbus-user-session, but you can just uninstall it immediately afterwards without anything complaining:

sudo apt remove dbus-user-session

Note that this may not work for you depending on your config, but it's worth a shot.

@z3ntu
Copy link
Member

z3ntu commented Oct 18, 2017

Found the issue why launchpad is failing my check: make[1]: lsb_release: Command not found. Will fix that.

@z3ntu
Copy link
Member

z3ntu commented Oct 18, 2017

Should be fixed in 980462d (so in tomorrows build)

@ghost
Copy link

ghost commented Oct 19, 2017

It works well for me now. Thank you!

@z3ntu
Copy link
Member

z3ntu commented Nov 14, 2017

v2.1 is out

@z3ntu z3ntu closed this as completed Nov 14, 2017
@z3ntu z3ntu removed the Unreleased label Mar 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

9 participants