[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

2018-04-25 Thread Billy Braga
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
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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


[Desktop-packages] [Bug 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu

2017-11-01 Thread Billy Braga
I experience this with Chrome 63 beta and Ubuntu 16.04 all up to date as
of today.

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

Title:
  chrome-browser makes gnome-keyring-daemon use 100% cpu

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 13.04, when starting the chromium browser, the
  gnome-keyring-daemon runs at full CPU load and the chromium-browser
  has no access to the stored passwords.

  The issue seems to be known
  (https://code.google.com/p/chromium/issues/detail?id=98601). I'm
  personally a bit surprised that Ubuntu 13.04 was released with such a
  serious problem.

  The frequently proposed workaround (e.g.
  https://plus.google.com/110130355317073712944/posts/PckhFj5HUn4)
  doesn't work because (a) there is no .gnome2/keyrings any more and (b)
  it's rather inresponsible to store your passwords unencryted.

  I found that killing gnome-keyring-server several times eventually gives you 
a working system.
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mnl   18759 F pulseaudio
  CRDA:
   country DE:
(2400 - 2483 @ 40), (N/A, 20)
(5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
(5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
(5470 - 5725 @ 40), (N/A, 26), DFS
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140
  InstallationDate: Installed on 2010-11-10 (900 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD)
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-19-generic i686
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice 
wireshark
  WifiSyslog: Apr 29 07:28:34 lipp-nb wpa_supplicant[1803]: wlan0: WPA: Group 
rekeying completed with c0:25:06:24:93:e1 [GTK=CCMP]
  dmi.bios.date: 12/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDD Ver. F.20
  dmi.board.name: 30DD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.23
  dmi.chassis.asset.tag: CNU9326SJY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6730b (GB990EA#ABD)
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1174162/+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