FS#28120 - Chromium fails to sync with google account

Attached to Project: Arch Linux
Opened by Alexis Ntounas (axelgr) - Thursday, 26 January 2012, 17:51 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 01 March 2012, 21:36 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When I start Chromium I get a message

Your profile could not be opened correctly.
Some resources maybe not avaliable. Check if the profile exists and if you are allowed to read and write the content

Trying to sync with my Google account doesn't work.

I have tried deleting my profile, uninstalling and installing chromium, deleting ~/.pki but with no result.

This is the console output:

$ chromium
[7683:7696:6357384848:ERROR:web_data_service.cc(643)] Cannot initialize the web database: 1
[7683:7700:6362625307:ERROR:nss_util.cc(417)] Error initializing NSS with a persistent database (sql:/home/*****/.pki/nssdb): NSS error code: -8187

I am using Chromium 16.0.912.77 x86_64 and my system is fully updated.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Thursday, 01 March 2012, 21:36 GMT
Reason for closing:  Not a bug
Comment by Alexis Ntounas (axelgr) - Tuesday, 31 January 2012, 16:09 GMT
After upgrading to KDE 4.8, uninstalling chromium, deleting ~/.config/chromium and re-installing it the problem is solved.
Comment by Tomasz Żok (tzok) - Thursday, 01 March 2012, 18:57 GMT
  • Field changed: Percent Complete (100% → 0%)
The problem appeared for me suddenly without me doing anything with chromium files. I tried clearing the profile, downgrading chromium. I get the following error when trying to run chromium:

[4829:4836:2428108934:ERROR:object_proxy.cc(239)] Failed to call method: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
[4829:4839:2428277168:ERROR:keyword_table.cc(605)] Can't write default search id backup.
[4829:4839:2428277268:ERROR:keyword_table.cc(474)] Failed to update default search id backup.
[4829:4839:2428277492:ERROR:web_data_service.cc(677)] Cannot initialize the web database: 1
[4829:4845:2433203603:ERROR:nss_util.cc(472)] Error initializing NSS with a persistent database (sql:/home/tzok/.pki/nssdb): NSS error code: -8187
[4829:4829:2436247159:ERROR:profile_impl.cc(1030)] Could not initialize login database.
Comment by Tomasz Żok (tzok) - Thursday, 01 March 2012, 19:15 GMT
Hi,

I have requested reopening of this ticket a week or two ago. Since then I found the source of problem. It was my root partition having no free space. I had difficulties solving the problem, because chromium profile was on a different partition mounted as /home which had gigabytes of free space. It seems that chromium requires also disk space on root /. Maybe something in /var, I don't know for sure - but since I freed the disk space, it is now working flawlessly.

Sorry that the bug was reopened then. I could not give this comment to the request for reopen. Now that I wrote it, the ticket can be closed again.
Comment by Evangelos Foutras (foutrelis) - Thursday, 01 March 2012, 21:35 GMT
Thanks for the update.

Loading...