This is not fixed. What we have is a reliable workaround to a bug which
apparently affects all Ubuntu 16.04 LTS users with the dbus-user-session
package installed.
Flatpak packages provided by the PPA at
https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak (and possibly
others) indirectly de
I can't believe all it took was to do:
sudo apt purge dbus-user-session
Thanks to whoever discovered this!
Sidenote: My Yandex browser now launches instantaneously rather than
taking atleast half a minute to open up.
This fix was definitely a good find
--
You received this bug notification be
I can confirm as well that removing dbus-user-session and reboot worked
like a charm. Thx all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
To man
again, confirming: `sudo apt-get remove --purge dbus-user-session` and
reboot resolved it for me on Ubuntu 16.04. No side-effects. On reboot,
the Passwords>Login keyring was available, where before it wasn't.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was having the same symptoms on my laptop (first, on debian stretch and then
ubuntu 16.04 LTS).
I had neither installed flatpak nor dbus-user-session, and the
gnome-keyring-daemon proposed workaround fixes didn't work for me.
I eventually found that it came from a CUPS configuration file
(/etc
I'm having this problem on a machine that doesn't have dbus-user-session
installed, nor it ever had it installed.
The problem started to appear after installing Google Chrome (although
it was quite fresh: I hadn't use it for anything else, apart from
opening Firefox to download Chrome).
Note: it
$ sudo apt-get remove --purge dbus-user-session
followed by a reboot fixed it!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
To manage notificatio
An easy workaround, while waiting a fix, is to add a startup application
with this command
/usr/bin/gnome-keyring-daemon *
You will be required to re-enter the password once logged, but it should
work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
It might have changed in the newer releases of Ubuntu, but on 16.04
(Unity desktop) `dbus-user-session` is NOT installed by default and NOT
a dependency of any standard packages.
I myself got it as dependency of Anbox. Now that this is gone, the only
remaining thing that points to this package is
Thank you, I really don't think that this is a good solution
On 07/18/2017 03:53 PM, Gunnar Hjalmarsson wrote:
> dbus-user-session is a dependency of the desktop meta packages, so
> uninstalling it means that you on Unity uninstall ubuntu-session and
> ubuntu-desktop, on GNOME Flashback you uninst
dbus-user-session is a dependency of the desktop meta packages, so
uninstalling it means that you on Unity uninstall ubuntu-session and
ubuntu-desktop, on GNOME Flashback you uninstall gnome-session-flashback
etc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I've not tried it yet, but I'm sure that uninstalling dbus-user-session
works as a workaround. what concerns me is what consequences will this
have. I checked 16.10 and 17.04 and both have dbus-user-session
installed by default. When I install chrome I don't seem to get the same
issues. I haven't i
Same here. Uninstalling dbus-user-session solved the issue.
Thanks to all contributors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
To manage no
I can also confirm that un-installing dbus-user-session solved the
issue.
Does flatpak always install it / or only some app's ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-ke
I can now confirm that these instructions have worked for me. Thank you
all. I did change my password as suggested in comment #74 by
bytecommander.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16898
I can also confirm that removing dbus-user-session fixes this issues,
and it was installed with flatpak. The steps in #67 got everything back
to normal. Thanks to Eberhard and 513G3 for the solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I can confirm that removing the dbus-user-session and reverting a
workaround (calling the gnome-keyring-daemon --replace --foreground)
solved the issue. There was no xdg-desktop-portal or xdg-desktop-portal-
gtk packages in my case. I suppose the dbus-user-session was installed
with the flatpak. Ub
Seems to me like `dbus-user-session` was the real culprit causing all the
trouble.
I got it installed with anbox and that is when the problem started.
I got my keyring daemon to correctly start, the Login keyring to unlock
automatically while still being encrypted with my account password again
t
All I have running is /usr/bin/gnome-keyring-daemon --daemonize --login
The files in your /etc/xdg/autostart look fine
Just need to make sure you're not starting gnome-keyring anywhere else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I added a bad command line into the GUI and .config/autostart file to be
sure that it could not run the command to start the daemon.
upon reboot I still see two daemons running, one with my username as owner and
one with lightdm as owner.
I'm still getting the same behavior of slow launch of term
Thank you, @leftyfb.
I'm seeing some strange behavior when deleting the files in
~/.config/autostart/
I can delete the file. If I open the GUI for startup Applications it
has a line for gnome-keyring-daemon --start --components=ssh which seems
unrelated to the text file in ~/.config/autostart.
@antonioshadji
I had to undo the workarounds in order for it to stop asking for
passwords at login:
In /etc/xdg/autostart/gnome-keyring-ssh.desktop
I originally replaced:
Exec=/usr/bin/gnome-keyring-daemon --start --components=ssh
with
#Exec=/usr/bin/gnome-keyring-daemon --daemonize --compone
Removing flatpak/dbus-user-session did not change anything for me on
16.04.2. dbus-user-session was first installed on May 8th 2017 in
conjunction with an upgrade of flatpak (and other software) as can be
seen in attached apt history log entry.
flatpak list
org.pitivi.Pitivi/x86_64/stable
org.gno
Removing dbus-user-session resolved my issue. It got added when I
temporarily installed anbox. There was no xdg-desktop-portal or xdg-
desktop-portal-gtk installed or available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Thanks all!
I uninstalled my flatpak apps, flatpak, and dbus-user-session... then
rebooted and all's well. Uninstalling with --purge seems to have taken
care of the /etc file markuslet pointed to.
$ flatpak list
$ flatpak --system uninstall com.xamarin.MonoDevelop
$ flatpak --system uninstall or
The Status dropdown is for "Affects" and flatpak affects this issue (not
that it's the sole culprit).
** Changed in: flatpak (Ubuntu)
Status: Invalid => Confirmed
** Also affects: dbus
Importance: Undecided
Status: New
--
You received this bug notification because you are a mem
Finally, this fixed the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
To manage notifications about this bug go to:
https://bugs.launchpad
Thanks for everyone who helped
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
To manage notifications about this bug go to:
https://bugs.launchpad.n
That finally solved it for me, thank you @Eberhard and @all for looking
into this and sharing your insights!
A few notes:
* in addition, I manually deleted file /etc/X11/Xsession.d/20dbus_xdg-
runtime which comes with package dbus-user-session (and is actually the
only file of the package) but wa
I could work around this problem by uninstalling dbus-user-session (and
its dependendants xdg-desktop-portal and xdg-desktop-portal-gtk). Those
packages came in through flatpak.
Thanks to Olaf who brought me on the right track
(https://forum.ubuntuusers.de/topic/gnome-keyring-daemon-doppelt/)
--
To illustrate an other side-effect :
coeurnoir@Asgard:~$ deja-dup --backup
** (deja-dup:2774): WARNING **: AssistantOperation.vala:732: Erreur lors
de l'appel de StartServiceByName pour org.freedesktop.secrets :
GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate
service 'org.free
…flatpak may not be the source problem but it seems to bring something
that helps highlighting the problem… ( I suspect some gnome-related
parameters ).
I assume some other ppa's as well can bring the same problem, maybe by
comparing them we could narrow down a culprit ?
I can also confirm that o
Thanks for testing, looks like several different bugs are mixed up here
(or it's just me posting a similar problem in the wrong bug report...).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Ti
In my case, the problem appears also for the new clean user. I tried a
new standard user without password, a new standard user with password
and a new administrator user with password, but it did the same in all
cases.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@all: Please try if the problem appears for a new clean user. In my case
it didn't so I suspect that it is related to some configuration files in
~/.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16898
It may not be flatpak on its own, but the machine I installed (and later
removed and purged) flatkpak on this problem exists. (So a correlation
does seem to exist) It might have something to do with other PPAs or how
packages you install from external PPAs affect the system. The only
major changes
FWIW, my problem started after installing PPAs about a week before I
first posted here (June 17). I just checked my /etc/apt/sources.list
and it was last modified June 10. Perhaps it is coincidence... but
right when some PPAs went in, my problem started.
--
You received this bug notification be
@MikeRushton... do you have any PPAs installed on your machines without
flatpak?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
To manage notificati
It does not have anything to do with flatpack or pitivi. I have several
machines experiencing this issue and have never installed either of the
mentioned packages on any of them in any point in time.
** Changed in: flatpak (Ubuntu)
Status: New => Invalid
--
You received this bug notificat
** Also affects: flatpak (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
To manage notifications
For what it's worth, as other users already mentioned that, the issue
appeared after I installed flatpack and pitivi (yesterday). I
uninstalled both of them and cleaned remaining files but the problem
still occurs...
Flatpak might be related to the issue, or at least one of the triggers.
--
You
Is this any useful https://bugzilla.gnome.org/show_bug.cgi?id=784514 ?
** Bug watch added: GNOME Bug Tracker #784514
https://bugzilla.gnome.org/show_bug.cgi?id=784514
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
…for a couple of hours then chromium says ( something like ) Error
occurs when trying to open your profile.
** Attachment added: "chromium having problem to open profile"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+attachment/4908915/+files/Capture%20du%202017-07-04%
This bug also prevents Deja-dup / duplicity from working.
Launching manually from terminal
gnome-keyring-daemon
seems to help a little.
When launching chromium password is asked but after that chromium and
any other app's seem to work fine.
** Attachment added: "if of any help ps -fux"
h
A followup on my report about skypeonlinux: It looks like the problem is
related to some user config in this case. If I create a clean user,
gnome-keyring works as expected. However, I wasn't able to find where
exactly the problematic configuration file is located yet.
--
You received this bug no
Well… now the problem happens on all the users-sessions but the error
message is little different :
alessandra@Asgard:~$ chromium-browser
Using PPAPI flash.
--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so
--ppapi-flash-version=
Gkr-Message: secret service operation failed: Di
Affected here on Ubuntu 16.04 Unity.
I noticed it on trying to launch chromium-browser, it takes very long
with errors
coeurnoir@Asgard:~$ chromium-browser
Using PPAPI flash.
--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so
--ppapi-flash-version=
Gkr-Message: secret service o
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gn
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
The problem really is isolated to gnome-keyring (as OP and others
stated).
Here's my workaround for Chrome... it might help others (like Photon).
But in the end it is only a workaround. It does demonstrate that if you
bypass the display manager (lightdm, gdm) triggering the gnome-keyring
for you,
I need to correct my previous statement. It looks like skypeforlinux is
actually starting the
gnome-keyring-daemon --start --foreground --components=secrets
command line, it is not there at boot. The
gnome-keyring-daemon --daemonize --login
command line seems to sometimes be there and somet
I experience the same problem on Manjaro Linux with gnome-keyring
3.20.0+57+g9db67ef6 and skypeforlinux. So it seems to be a bug in gnome-
keyring, not in Ubuntu's package.
Some observations (citing my post on the Manjaro forums
https://forum.manjaro.org/t/skypeforlinux-weird-and-inconsistent-
aut
For reference... https://github.com/karma-runner/karma-chrome-
launcher/issues/76
** Bug watch added: github.com/karma-runner/karma-chrome-launcher/issues #76
https://github.com/karma-runner/karma-chrome-launcher/issues/76
--
You received this bug notification because you are a member of Ubun
This is affecting basic NetworkManager use cases. It's impossible to
connect to any password protected wifi. I'd bet this bug is the cause of
many other requiring access to the keyring storage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
The following seems to have got me running normally again. Working on the
theory the keyring file was somehow corrupted, I deleted the keyring file...
rm ~/.local/share/keyrings/login.keyring
...and rebooted. A new keyring file has been generated and everything looks
good for now!
--
You rece
On my machine I'm unable to get any of the above workarounds to unlock the
keyring. Entering...
gnome-keyring-daemon --replace --foreground --components=secrets,ssh,pcks11
...ends in the terminal hanging at "SSH_AUTH_SOCK=/run/user/1000/keyring/ssh".
--
You received this bug notification becaus
Maybe a clearer capture of something amiss... logging in and out and in
repeatedly causes the keyring daemon process to be started again and
again (as lightdm and as the user). Please see attached.
** Attachment added: "log_in_and_out.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyri
I uncovered another problematic side effect but I am unsure of the
significance; perhaps this will trigger an idea for someone
There are three user accounts on my box. Here's a flow:
1) Reboot box
2) Sign in as user 1
3) Examine running processes (as MikeD mentioned in #33) and observe two
k
The only "permanent" (well, it still asks for the password once when
opening google-chrome after login) workaround I found was creating a
startup item as described here: https://askubuntu.com/a/911896.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I am experiencing the same issue on one of my two machines. The 'Password and
Keys' padlock icon next to 'Login' remains locked even with the correct
password, and I'm unable to use Chrome, access e-mail etc..
I'm no expert but, in case it helps, these are two differences between the two
machin
Although chromium-browser is affected by the issue, it doesn't appear to
be the cause of the issue itself (other apps like gnome-terminal appear
to be similarly affected), so I'm marking this bug invalid for chromium-
browser.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => In
I've installed the flatpak (and added the PPA) quite recently, but
uninstalling the package didn't solve the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring
This has manifested itself on a machine with a fresh install of 16.04.2
with nothing installed but google chrome. I have 2 other machines with
this issue and neither have ever had the flatpak PPA enabled or anything
installed from it.
--
You received this bug notification because you are a member
I also had the flatpak PPA, I removed it but the situation didn't
improve, I also reinstalled the gnome-keyring package with no luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gno
I agree with comments #25 and #26. It's likely a red herring, but this
issue arose for me right after I installed the flatpak PPA and a pile of
mono/M$ stuff. I still figure that those actions are orthogonal, but
just in case everyone else recently installed similar stuff or a new PPA
or...
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Ti
Hans' observation that this is not impacting all of his machines is
consistent with my experience of this issue. I have three Ubuntu
machines and this is only impacting one of them. It is driving me nuts
because the machine that is impacted is my main laptop. My server and my
test machine which wou
What is odd is that it does not occur on all Ubuntu installations. I
have a 2nd Ubuntu machine that does not suffer from this issue. What
could possibly be different between a computer that exhibit this problem
and another? I do not recall having played with any configuration file
that relates t
This also affects chromium-browser installed from Ubuntu repository.
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Well, this bug also is affecting me, I used the workaround in #10 and it works,
but I still need to put my password in order to unlock the "Login" Keyring (My
system don't have autologin enabled btw), the weird thing is that this system
is fresh installed (no more than a week) and It was working
I am having this problem as well to the point that I can't use my
desktop. The only solution I have found is to install a different
distro or version of Ubuntu other than 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Same problem here:
Google-chrome is affected.
Skypeforlinux doesn't remember the password anymore
UnityMail is affected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring no
same for me here
by starting with the terminal
$google-chrome
[6136:6136:0528/125519.901742:ERROR:browser_main_loop.cc(279)] Gtk: Im
Modulpfad »adwaita« konnte keine Themen-Engine gefunden werden,
[6136:6136:0528/125519.902002:ERROR:browser_main_loop.cc(279)] Gtk: Im
Modulpfad »adwaita« konnte k
I have this problem too. With mysql-workbench, connecting to remote
servers from file manager and other programs. The workaround from some
upper posts restores functionality.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Opera is also affected by this issue. Takes almost a minute to load
whereas Firefox loads in under five seconds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlock
I use KeePass 2 on Mono so I'm not too bothered by this. Wifi and
NetworkManager still have problems though.
On Google Chrome and likely Chromium I fixed the 2 minute start wait by
adding --password-store=basic the command line. You can add it the Exec
entry in your desktop file or by editing the
I was wondering if there is anything I can to help regress the issue?
Even if it is just trying to load various different older versions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libgnome-keyring (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Ti
Sorry, I should have been more constructive with my comment. The
workaround in #10 seems to partially work. It doesn't allow the "login"
password keychain to be unlocked on login, but it at least let you see
the passwords in seahorse so that it can be unlocked manually - which in
turn prevents appl
I've recently started getting this issue too. What is going on?? Ubuntu
shouldn't be doing this on the LTS.
** Also affects: libgnome-keyring (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Well, I mean workaround by "fix" word. This workaround is the shortest,
cleanest and working think I've seen about this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyrin
That is not a fix. It is a workaround. On boot, my system has gnome-
keyring-daemon running which needs to be killed and restarted without
--login in order to function. This was working a couple weeks ago. There
should be no "fixes" the user need to do to regain this functionality.
--
You receive
This askUbuntu answer actually fixed the issue cleanly
https://askubuntu.com/a/911755/61218. The solution is adding a startup
item with this commandline
gnome-keyring-daemon --replace --foreground
--components=secrets,ssh,pcks11
--
You received this bug notification because you are a member
vinagre is also affected, running gnome-keyring-daemon restores the
normal behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
To manage notifi
This causes problems in other applications, too. I get constant requests
from Evolution to enter my credentials (although they are stored in the
keyring). The Nextcloud client asks for a(n actually stored) password as
well.
All requests disappear if I start gnome-keyring-daemon manually from the
c
I'm also seeing slow response to taking a screenshot with shortcut keys.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
To manage notifications abou
I'm also seeing slow startup in chrome/chromium, and gnome-terminal
using keyboard shortcut.
When launching chromium-browser from command line I see the following
messages:
Using PPAPI flash.
--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so
--ppapi-flash-version=
[3823:3823:05
** Summary changed:
- ubuntu 16.04 Chrome and Chromium asking for keyring.
+ gnome-keyring not unlocked on boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlock
89 matches
Mail list logo
