This also happens in disco dingo (19.04). Only solution is running
`gnome-keyring-daemon` on a terminal.
Uninstalling `dbus-user-session` or doing `sudo apt-get install
--reinstall ca-certificates` doesn't do anything.
--
You received this bug notification because you are a member of Desktop
As with comment #107, `sudo apt-get install --reinstall ca-certificates`
was the only fix for me. Removing/re-installing/re-configuring dbus-
user-session didn't help. This points to there being two issues. Neither
issue is related to chrome.
--
You received this bug notification because you are
Hi guys,
This bug is still present on latest versions (seahorse 3.30).
Why is assigned to chromium-browser package?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Could this be an incompatibility between i386 and amd64 packages? I
have trouble adding my keys via ssh-add and after reading some comments
here and elsewhere gave removing dbus-user-session a try. My computer
is amd64 with i386 foreign arch. dbus-user-session was replaced with
Ran into this after installing dbus-user-session in order to support
systemd user services that raise notifiers via dbus.
Notifiers didn't arrive via my desktop so I presume it just creates a
whole other session somewhere and talks to that. My service worked (when
it was previously crashing
Billy, please file a new bug for your issue with specific details about
what you're experiencing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring
I still experience this bug in 18.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on xenial when dbus-user-session is
Every time I turn around, I have a no failure related to gnome-keyring.
After having Chromium running for a few minutes it hangs again for a
minute or so with the same error message:
Gkr-Message: secret service operation failed: Did not receive a reply.
Possible causes include: the remote
After killing and restarting the keyring which fixed Network Manager,
then Chromium developed a slow start problem caused by gnome-keyring.
smm@laptop ~
$ chromium-browser --enable-logging=stderr
ATTENTION: default value of option force_s3tc_enable overridden by environment.
Gkr-Message: secret
Running "chromium-browser --enable-logging=stderr" results in:
$ chromium-browser --enable-logging=stderr
ATTENTION: default value of option force_s3tc_enable overridden by environment.
I'm also running the gnome-keyring-daemon in the foreground and see this
message:
**
Olivier:
1) Yes
2) Yes
3) Yes
4) I'll have to log out and/or reboot to get it back into that state. Will
post when I get a chance to do that.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Thanks for the feedback Stephen. This thread has become very long and
it's hard to extract the relevant information, so just to make sure that
I fully understand the issue:
- can you confirm that chrom{e,ium} takes a long time to open (in the
original description it was 2 minutes, is this the
- I'm seeing slow downs.
- I'm not using automatic login.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on xenial when
> This bug is not resolved. Seeing it under 16.04LTS without
> dbus-user-session or flatpak installed.
I can reliably reproduce the issue of the keyring not being
automatically unlocked at startup in an up-to-date 16.04 VM without
dbus-user-session installed. Not seeing any application slowdown
> I do not feel comfortable removing dbus-user-session as a workaround
Nothing in Ubuntu 16.04 LTS uses dbus-user-session. It is completely
safe to remove it there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
> Also, on a side-note, does anyone know the exact details of what the
> password-store argument does? For example, if I turn password saving
> in Chromium off and don't use Google/Chrome sync, am I "safe" to log
> into websites without my passwords being stored in plain-text on my
> hard drive
This bug is not resolved. Seeing it under 16.04LTS without dbus-user-
session or flatpak installed.
smm@laptop /var/log
$ sudo apt list --installed |grep dbus-user-session
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
smm@laptop /var/log
$ sudo apt list
Any update on this issue? I do not feel comfortable removing dbus-user-
session as a workaround, and I have simply added --password-store=basic
as an argument for Chromium/Chrome for now. However that is not
completely suitable even though I only use Chromium/Chrome as a
secondary browser, and I
Also, openrazer & polychromatic no longer have the dependency on dbus-
user-session. Thanks to the maintainers of these packages.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Reinstalling the ca-certificates did not work for me.
Only removing dbus-user-session works around the problem for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
After trying multiple options in this thread. I found that reinstalling the
ca-certificates fixed this for me.
sudo apt-get install --reinstall ca-certificates
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
Chrome/Chromium should probably not wait that long if keyring is not
available. If it is not running, then it is not running, end of story.
Chromium should just proceed launching instead of bothering user with
behavior like this.
--
You received this bug notification because you are a member of
1. apt-get install dbus-user-session
2. reboot
3. confirm flatpak not installed:
emc@emc-office:~$ which flatpak
4. Check reverse dependancies and ensure there is nothing dependant on
it
emc@emc-office:~$ apt-rdepends --reverse dbus-user-session
Reading package lists... Done
Building dependency
Jeremy,
razer-daemon committer identifies they are expressing a package
dependency correctly, and if installing dbus-user-session causes chrome
to break, that's not a driver/package problem. They have a point.
https://github.com/terrycain/razer-drivers/issues/358
I would like to say that I am
$ apt rdepends dbus-user-session
dbus-user-session
Reverse Depends:
|Suggests: dbus
Depends: anbox-common
|Suggests: dbus
|Suggests: dbus
Which I understand is not an official package and in my case, is no
longer installed. The point is, dbus-user-session is an official package
and causes
Mike, what is the output of this command:
apt rdepends dbus-user-session
** Project changed: dbus => meta-gnome3 (Ubuntu)
** No longer affects: meta-gnome3 (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: meta-gnome3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
This bug was not only related to Flatpak. I have never
installed/used/heard of Flapak before I filed this bug. Maybe this bug
should be filed against dbus-user-session.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
Eric, please contact the distributor/maintainer for razer-daemon and
polychromatic since those packages are not provided by Ubuntu.
I'm closing this bug since the issue was specific to the Flatpak PPA and
that was resolved there weeks ago.
** Changed in: flatpak (Ubuntu)
Status: Confirmed
Rocko, please file a different bug for that issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on xenial when dbus-user-session is
I also have this issue in Ubuntu 17.10 (running gdm/gnome-shell).
Uninstalling dbus-user-session isn't really an option, because tons of
apps depend on it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Uninstalling polychromatic, razer-daemon, and then dbus-user-session
resolved the chrome problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not
It turns out the workaround does resolve the long pause, but does not
result in correct operation. Chrome has chrome sync not functioning, and
gnome-encfs mounts fail unless manually mounted using gnome-encfs-
manager
--
You received this bug notification because you are a member of Desktop
I can replicate this problem on 16.04.3 after upgrade from 16.04.2.
However, the package dragging in dbus-user-session are different in my
case:
$ apt-rdepends --reverse dbus-user-session
Reading package lists... Done
Building dependency tree
Reading state information... Done
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Since there are multiple packages that depend on dbus-user-session,
there's really no need to mention a single package in the title.
** Summary changed:
- gnome-keyring not unlocked on xenial when dbus-user-session is installed,
which flatpak depends on
+ gnome-keyring not unlocked on xenial
** Summary changed:
- gnome-keyring not unlocked on boot
+ gnome-keyring not unlocked on xenial when dbus-user-session is installed,
which flatpak depends on
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
37 matches
Mail list logo
