Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: gnome-keyring (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1712607

Title:
  gnome keyring goes awol after a few logout/logins

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  First symptom noticed: That *sometimes* after logging in, owncloud-
  client would fail to connect to the server, after a delay asking
  instead for a password with the message something like (sorry don't
  have it in front of me) "keyring service unavailable".

  Second symptom, on trying to start Google Chrome (Chromium too), it
  would fail to sign in to my Google account for sync, with a long delay
  on startup while it gives up on that.

  This never happens on the first login session since the last boot. It
  may not happen on the second, but usually by the third login, it
  happens. I'm not certain of the pattern except it seems always to be
  fine in the *first* session.

  A reboot seemed to be needed to resolve this. But just now I tried
  instead from the commandline:

  gnome-keyring-daemon -r -f

  I'm sure -d would do too, but I wanted to watch it. Sure enough on
  trying to relaunch owncloud-client, I am *then* asked for my password
  to unlock the keyring as, it says, it didn't get unlocked when I
  logged in. Then both owncloud-client and google-chrome are now able to
  sign in, and I see associated messages from the gnome-keyring-daemon
  in the terminal where I'm running it.

  Presumably the daemon is not being reliably relaunched when needed, on
  successive logins to the gnome desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 23 16:38:04 2017
  InstallationDate: Installed on 2017-07-30 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to artful on 2017-08-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1712607/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to