linux-traipu team mailing list archive

[Ldardini <1174162@xxxxxxxxxxxxxxxxxx>]

I am experiencing this problem too, but I have made some tests and
checks and maybe a workaround is available. I have verified while the
gnome-keyring is at 100%, google chorme is recovering the stored
password from Google and storing into the keyring, like they were
absent. It seems google chrome was unable to use the previously stored
one and pull all again from Google. I have enabled the automatic login
and when google chrome starts, it asks for the password to unlock the
keyring. Just avoid that and start google chrome after you have already
unlocked the keyring, maybe just terminating your session and logging
again with the password, skipping the automatic login.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1174162

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

Status in Chromium Browser:
  Unknown
Status in GNOME keyring services:
  New
Status in “chromium-browser” 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:
   USER        PID 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-firmware                            1.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