Issue 72525 in chromium: Error initializing NSS with a persistent database / chromium sync broken

324 views
Skip to first unread message

chro...@googlecode.com

unread,
Feb 10, 2011, 12:57:38 AM2/10/11
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: OS-Linux Area-Undefined Type-Bug Pri-2

New issue 72525 by volt...@gmail.com: Error initializing NSS with a
persistent database / chromium sync broken
http://code.google.com/p/chromium/issues/detail?id=72525

Chrome Version (from the about:version page): 9.0.597.84 (Developer Build 0)
Is this the most recent version: Yes
OS+ version: Arch Linux
CPU architecture (32-bit / 64-bit): 64-bit
Window manager: DWM
URLs (if relevant): Any URL
Behavior in Linux Firefox: N/A
Behavior in Windows Chrome (if you have access to it): N/A

What steps will reproduce the problem?
1. Run chromium from a terminal
2. Navigate to a web page, any page will do
3. Observe standard output
4. Go to Preferences -> Personal Stuff -> Set Up Sync
5. Enter Google account information and click "Sign In"

What is the expected result?
No errors should be thrown. Sync should sign into Google account and pull
sync data.

What happens instead?
When the browser is first launched and I navigate to any page the standard
output lists the following error messages:
[23857:23870:14330856550:ERROR:base/nss_util.cc(234)] Error initializing
NSS with a persistent database (sql:/home/*****/.pki/nssdb): NSS error code
-8187
SQLite write error in seekAndWrite, cnt == 4, rc == -1, errno == 28
SQLite write error in seekAndWrite, cnt == 4, rc == -1, errno == 28

The SQLite write errors repeat as I navigate to different webpages.

When I try to sign into Chromium sync, the preferences window changes
to "Account sign-in details are not yet entered." and the following error
is output to the terminal:

SQLite write error in seekAndWrite, cnt == 512, rc == -1, errno == 28
SQLite write error in seekAndWrite, cnt == 28, rc == -1, errno == 28
[24951:25334:14767465832:ERROR:chrome/browser/sync/engine/syncapi.cc(1520)]
Could not open share for:*****@gmail.com

I tried to alleviate this issue by reinstalling chromium, nss, sqlite, and
nspr. I tried deleting my chromium profile directory as well as the
~/.pki/nssdb directory. Permissions on the ~/.pki/nssdb directory seem to
be fine:

drwx------ 2 ***** users 4096 Feb 6 09:25 .
drwx------ 3 ***** users 4096 Feb 6 09:22 ..
-rw------- 1 ***** users 9216 Feb 6 09:25 cert9.db
-rw------- 1 ***** users 11264 Feb 6 09:25 key4.db
-rw------- 1 ***** users 441 Feb 6 09:25 pkcs11.txt

The problem I have described above stated when I upgraded from chromium
8.0.552.237 to 9.0.597.84. The browser complained that my old configuration
could not be used in the new version. At this point I cleared my
~/.config/chrome/Default directory hoping that I could start with a fresh
config and sync my preferences and bookmarks back.

The problem I described above is not consistent across multiple computers
running Arch Linux. I have a different system with the same software where
chromium behaves normally.


Please provide any additional information below. Attach a screenshot
and backtrace if possible.

Additional Software Information:
Webkit version 534.13, nss version 3.12.9, sqlite3 3.7.5, Linux kernel
2.6.37

chro...@googlecode.com

unread,
Feb 10, 2011, 1:05:49 AM2/10/11
to chromi...@chromium.org

chro...@googlecode.com

unread,
Feb 10, 2011, 11:08:14 PM2/10/11
to chromi...@chromium.org

Comment #4 on issue 72525 by volt...@gmail.com: Error initializing NSS with
a persistent database / chromium sync broken
http://code.google.com/p/chromium/issues/detail?id=72525

Updating chromium to version 9.0.597.94 resolved the issue completely.
Thank you for your time and sorry about the noise. I'd like to request the
closure of this issue.

chro...@googlecode.com

unread,
Feb 11, 2011, 12:02:26 AM2/11/11
to chromi...@chromium.org
Updates:
Status: WontFix

Comment #5 on issue 72525 by w...@chromium.org: Error initializing NSS with

a persistent database / chromium sync broken
http://code.google.com/p/chromium/issues/detail?id=72525

That's strange. I don't know why 9.0.597.94 resolved the issue.

Marked the bug WontFix (for "obsolete").

chro...@googlecode.com

unread,
Feb 11, 2011, 12:46:09 PM2/11/11
to chromi...@chromium.org

Comment #6 on issue 72525 by volt...@gmail.com: Error initializing NSS with
a persistent database / chromium sync broken
http://code.google.com/p/chromium/issues/detail?id=72525

I have a feeling it was a distribution related issue. After I reported the
database problems here, a few packages (notably NSS and sqlite3) have been
updated by Arch Linux maintainers. Finally, chromium was updated yesterday
to 9.0.597.94. Maybe the recompile against the latest dependencies fixed
the issue, whatever it was in the first place.

I'll update this ticket if I come across the errors again.

chro...@googlecode.com

unread,
Jun 8, 2011, 10:43:23 AM6/8/11
to chromi...@chromium.org

Comment #7 on issue 72525 by ashaihul...@gmail.com: Error initializing NSS
with a persistent database / chromium sync broken
http://code.google.com/p/chromium/issues/detail?id=72525

For very long time I have same issue when trying to get to ssl powerred
sites:

Error initializing NSS with a persistent database

(sql:/home/***/.pki/nssdb) [29211:29254:39974460903:ERROR:nss_util.cc(397)]
Error initializing NSS without a persistent database: NSS error code: -5925

Every simple http site works well. Tryed to reinstall nss many times, but
didn't help.
Maybe problems in linux distribution? I use OpenSuse 11.4

Today i installed version 12.0.742.91-87961, and have the same problem. I
will be grateful if you can say how I can fix it.

chro...@googlecode.com

unread,
Jun 8, 2011, 11:27:34 AM6/8/11
to chromi...@chromium.org

Comment #8 on issue 72525 by w...@chromium.org: Error initializing NSS with
a persistent database / chromium sync broken
http://code.google.com/p/chromium/issues/detail?id=72525

ashaihul...: thank you for the comment. Your problem seems
different from the problem reported by volt... (for example,
the error code is different). So it is best to assume it's
a different bug.

Please open a new bug report with your comment 7, and email
me the bug number, and I'll follow up there. Thanks.

Reply all
Reply to author
Forward
0 new messages