Issue 100857 in chromium: Error initializing NSS with a persistent database: NSS error code: -8187

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: OS-Linux Area-Undefined Type-Bug Pri-2

New issue 100857 by delcyp...@gmail.com: Error initializing NSS with a
persistent database: NSS error code: -8187
http://code.google.com/p/chromium/issues/detail?id=100857

Chrome Version : Chromium 14.0.835.202
OS Version: Arch Linux x86_64 using KDE4.7.2
URLs (if applicable) : N/A
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: N/A
Firefox 4.x: N/A
IE 7/8/9: N/A

What steps will reproduce the problem?
1. Execute Chromium from terminal
$ chromium

What is the expected result?
Chromium should start without segfaulting!

What happens instead?
$ chromium
[2444:2452:579443487:ERROR:nss_util.cc(419)] Error initializing NSS with a
persistent database (sql:/home/dan/.pki/nssdb): NSS error code: -8187
[2444:2485:579525090:ERROR:x509_certificate_nss.cc(797)]
CERT_PKIXVerifyCert for s-static.ak.facebook.com failed err=-8181
[2444:2457:579574290:ERROR:cookie_monster.cc(1155)] Found 1 duplicate
cookies for host='rootmusic.com', with {name='__utmb',
domain='.rootmusic.com', path='/'}
[2444:2517:579612193:ERROR:syncapi.cc(1953)] Could not open share
for:delc...@gmail.com
Segmentation fault

I tried removing my profile ($ mv .config/chromium .config/chromium.old)
and moving the nssdb ($ mv .pki pki.old) and the following happened when
trying to execute chromium

* The following messages appear on the terminal
[2627:2635:1295090181:ERROR:web_data_service.cc(589)] Cannot initialize the
web database: 1
[2627:2640:1298926140:ERROR:nss_util.cc(419)] Error initializing NSS with a
persistent database (sql:/home/dan/.pki/nssdb): NSS error code: -8187

* A message box pops up with the message "Your Profile could not be opened
correctly". Please check that the profile exists and that you have
permission to read and write its contents".

* A welcome to Chromium window appears asking me to choose a search engine
but no search engines are listed so I can't click on anything.

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

I tried downgraded to chromium-11.0.696.57-1 and then executed chromium. It
started without segfaulting but some errors still appeared. I then upgraded
to 14.0.835.202 again and chromium started w/out segfaulting but these
error messages still persist

[3418:3431:1946555151:ERROR:nss_util.cc(419)] Error initializing NSS with a
persistent database (sql:/home/dan/.pki/nssdb): NSS error code: -8187
[3418:3431:1946606450:ERROR:cookie_monster.cc(1155)] Found 1 duplicate
cookies for host='google.com', with {name='__utmb', domain='.google.com',
path='/accounts/'}
[3418:3431:1946606747:ERROR:cookie_monster.cc(1155)] Found 1 duplicate
cookies for host='google.com', with {name='__utmb', domain='.google.com',
path='/mail/help/'}
[3418:3431:1946606771:ERROR:cookie_monster.cc(1155)] Found 1 duplicate
cookies for host='google.com', with {name='__utmb',
domain='plus.google.com', path='/'}
[3418:3431:1946607108:ERROR:cookie_monster.cc(1155)] Found 1 duplicate
cookies for host='rootmusic.com', with {name='__utmb',
domain='.rootmusic.com', path='/'}
[3418:3491:1946622653:ERROR:x509_certificate_nss.cc(797)]
CERT_PKIXVerifyCert for s-static.ak.facebook.com failed err=-8181

Unfortunately downgrading and then upgrading again has changed something
because chromium does not segfault for me anymore so I can't reproduce it.

[chro...@googlecode.com]

Comment #3 on issue 100857 by benjamin...@gmail.com: Error initializing NSS

with a persistent database: NSS error code: -8187
http://code.google.com/p/chromium/issues/detail?id=100857

I also have the exact same issue right now (consistent after reinstall the
same version of chromium 15.x and the nss package on archlinux).

It seems to be related to a permission issue as it runs fine when I start
chromium as root pointing to the users config folder...

I got the following output when running chromium from a terminal:
$ chromium
[3337:3346:2917156117:ERROR:nss_util.cc(417)] Error initializing NSS with a
persistent database (sql:/home/xxx/.pki/nssdb): NSS error code: -8187
Gkr-Message: secret service operation failed: The name
org.freedesktop.secrets was not provided by any .service files
[3337:3388:2917391998:ERROR:sync_manager.cc(927)] Could not open share
for:xxxxxxxxxx
[3405:3405:2917923958:ERROR:ipc_channel_posix.cc(190)] bind
/tmp/F99894AA5186527D8C147607EEFDD597BC98E3CB.15.0.874.121_service_ipc: Die
Adresse wird bereits verwendet
[3405:3405:2917924421:ERROR:service_ipc_server.cc(79)] Unable to open
service ipc channel named:
/tmp/F99894AA5186527D8C147607EEFDD597BC98E3CB.15.0.874.121_service_ipc
[3337:3337:2918007915:ERROR:CONSOLE(6196)] "Uncaught TypeError: Cannot set
property 'checked' of null", source: chrome://settings/options_bundle.js
(6196)
[3337:3337:2919868401:ERROR:ipc_channel_posix.cc(264)] connect
/tmp/F99894AA5186527D8C147607EEFDD597BC98E3CB.15.0.874.121_service_ipc:
Keine Berechtigung

I run into that issue on archlinux x64 with XFCE desktop.

[chro...@googlecode.com]

Comment #5 on issue 100857 by benjamin...@gmail.com: Error initializing NSS

with a persistent database: NSS error code: -8187
http://code.google.com/p/chromium/issues/detail?id=100857

Hi,
sorry I missed the strace hint on your first answer ...
I attached a trace, hope that will help. The error still remains and I
tried to open the sync options dialog in the strace powered instance.

Thanks for the help.

Attachments:
chromium_trace.log 1.8 MB

[chro...@googlecode.com]

Comment #6 on issue 100857 by w...@chromium.org: Error initializing NSS with

a persistent database: NSS error code: -8187
http://code.google.com/p/chromium/issues/detail?id=100857

benjamin.pabst85: thank you for the strace log. It shows the preparation
for initializing NSS (checking that the directory /home/xxx/.pki/nssdb
exists),
but does not show some operations that NSS does during initialization, such
as reading 1024 bytes from /dev/urandom or opening /var/tmp and /usr/tmp.
This means NSS_InitReadWrite must have failed very early.

To track this down will require running Chrome in a debugger and
single-stepping
after Chrome enters NSS_InitReadWrite. You can also set a conditional
breakpoint
in the PR_SetError function, with the condition code=-8187.

I don't know if you have the setup or time to do this kind of debugging.

[chro...@googlecode.com]

Comment #10 on issue 100857 by berumena...@gmail.com: Error initializing

NSS with a persistent database: NSS error code: -8187
http://code.google.com/p/chromium/issues/detail?id=100857

I've got this issue as well with chrome and chromium. Reinstalling and
deleting my profile has no effect on error messages. I'll like to help as
best I can to get this resolved.