Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#35976 - [chromium] [nss] segfault in libnss3.so when starting Chromium

Attached to Project: Arch Linux
Opened by Jose M Rodriguez (foxaxel) - Saturday, 29 June 2013, 11:36 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 30 June 2013, 10:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Since a few updates I have found that it is not possible for me to use Chromium, it refuses to start with a Segmentation Fault:

$ chromium
Segmentation fault (core dumped)

The output in dmesg is as follows:

[ 1181.675332] Chrome_IOThread[2974]: segfault at 68 ip 00007f68eae1ff93 sp 00007f68bdff9188 error 6 in libnss3.so[7f68eadcd000+136000]

There are 2 attached files: 130629-chromium-strace and 130629-chromium-gdb

$ strace /usr/lib/chromium/chromium 2&> 130629-chromium-strace
Segmentation fault (core dumped)

I have tried with google-chrome and the behavior is the same. I tried hard to look for solutions over Internet and by myself but I have no idea about how to fix this.

I am able to debug it if you give me a few tips, e.g. packages needed.


Additional info:

extra/nss 3.14.3-3 [installed]
extra/nss-mdns 0.10-5 [installed]
extra/chromium 28.0.1500.52-1 [installed]


Thanks

   130629-chromium-gdb (3 KiB)
   130629-chromium-strace (168 KiB)
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Sunday, 30 June 2013, 10:20 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Solved by removing the $HOME/.pki directory.
Comment by Evangelos Foutras (foutrelis) - Sunday, 30 June 2013, 02:45 GMT
Does this also happen with a clean profile?

Test with: chromium --user-data-dir=$(mktemp -d)
Comment by Jose M Rodriguez (foxaxel) - Sunday, 30 June 2013, 08:26 GMT
Yes, it does.

$ chromium --user-data-dir=$(mktemp -d)
Segmentation fault (core dumped)

I also tried to clean everything with the steps in the second post here https://bbs.archlinux.org/viewtopic.php?id=151904 :

% pacman -Rscn chromium
% sudo updatedb
% locate chromium (and removed every file found)
% pacman -S chromium
% chromium

It does not work.
Comment by Evangelos Foutras (foutrelis) - Sunday, 30 June 2013, 09:13 GMT
Could you also test with a new user account to check if it's an issue with any data in your $HOME?
Comment by Jose M Rodriguez (foxaxel) - Sunday, 30 June 2013, 09:39 GMT
Congratulations, I have created another user and it works. Do you have any idea about what can be affecting Chromium?

Thanks.
Comment by Jose M Rodriguez (foxaxel) - Sunday, 30 June 2013, 10:13 GMT
I found the problem, it was in the .pki folder. I made a backup of the folder and removed it and now Chromium works fine.

I think I cannot share this folder as it is related with keys and security, am I right?

Thank you very much.
Comment by Evangelos Foutras (foutrelis) - Sunday, 30 June 2013, 10:13 GMT
Since this seems to be related to nss, I'd start by removing the $HOME/.pki directory.

No idea what's going on though; it would take some poking around with gdb and debug builds of chromium and/or nss to figure out why it's segfaulting.
Comment by Evangelos Foutras (foutrelis) - Sunday, 30 June 2013, 10:18 GMT
Yes, I think it's best not to share the .pki/nssdb directory as it can store personal certificates and private keys.

Glad it's fixed, I'll go ahead and close this.

Loading...