Q4OS Forum

Mr.Mark

Member

Registered: 2016-02-03

Posts: 98

Default Keyring

How can I eliminate the default keyring request when opening Chrome. This happened after the most recent update. I would just like to eliminate/disable it.

Last edited by Mr.Mark (2016-09-07 03:32)

rafaelramos

Member

From: Brazil

Registered: 2016-07-19

Posts: 146

Re: Default Keyring

Try Just click "OK" button, without value in the fields...

Rademes

Member

From: Latvia

Registered: 2015-12-13

Posts: 637

Re: Default Keyring

Try Just click "OK" button, without value in the fields...

That does NOT working! I have this annoying window every time I start Chromium, and already removed tdewalletmanager-trinity, but it still appears every time even if I click cancel. That became after latest update. How to get rid of it?
Update: This window appears even when I open page without password fields in it, so I assume this is a bug.

Last edited by Rademes (2016-09-07 12:47)

---

Attachments:
warnings1.png, Size: 33.05 KiB, Downloads: 696

---

Before asking for help please read this topic: https://www.q4os.org/forum/viewtopic.php?id=3502   If you have problems with WiFi network, try to install the Network Manager using Q4OS Software Centre.

q4osteam

Q4OS Team

Registered: 2015-12-06

Posts: 4,501

Website

Re: Default Keyring

It's about Chrome/Chromium issue described here - https://bugs.chromium.org/p/chromium/is … ?id=643189 . According to Chrome developers, the issue should be fixed in the next Chrome/Chromium revision 53.0.2785.98 during the next week.

If you want to fix it immediately, the only workaround is to run Chrome/Chromium with '--password-store=basic' commandline switch.

q4osteam

Q4OS Team

Registered: 2015-12-06

Posts: 4,501

Website

Re: Default Keyring

There is another quick workaround to disable the Chrome keyring dialog, you could remove 'gnome-keyring' package from your system:
$ sudo apt-get remove gnome-keyring

q4osteam

Q4OS Team

Registered: 2015-12-06

Posts: 4,501

Website

Re: Default Keyring

New Chrome revision 53.0.2785.101 is available in repositories. The issue should be resolved after the Chrome update and reboot. Please do report, if issue persists.