Failed to open google chrome. Error /usr/bin/google-chrome: /usr/lib/x86_64-linux-gnu/libnss3.so: version `NSS_3.22' not found (required by /usr/bin/google-chrome)
Reported by
goreakan...@gmail.com,
Nov 22
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Steps to reproduce the problem: Tried to install new chrome using link Followed step from https://askubuntu.com/questions/510056/how-to-install-google-chrome but chrome not installed properly. Moreever received error "/usr/bin/google-chrome: /usr/lib/x86_64-linux-gnu/libnss3.so: version `NSS_3.22' not found (required by /usr/bin/google-chrome)". Now chrome doesn't open What is the expected behavior? Chrome should work normally. What went wrong? Chrome doesn't open. ERROR: /usr/bin/google-chrome: /usr/lib/x86_64-linux-gnu/libnss3.so: version `NSS_3.22' not found (required by /usr/bin/google-chrome) Did this work before? N/A Chrome version: 52.0 Channel: n/a OS Version: 10.0 Flash Version:
,
Nov 22
,
Nov 26
goreakankshaashok10@ Thanks for the issue. Tested this issue on Ubuntu 17.10 and Windows 10 on the latest Stable 70.0.3538.110 and Canary 72.0.3622.0 and unable to reproduce this issue. Could install Chrome without any issues and could launch it by following the steps mentioned in the above given link. As per comment #1, as this issue is reproduced on Debian GNU/Linux 8 (jessie) 64-bit, this setup is not available at TE end to test and confirm. Hence adding 'TE-NeedsTriageFromHYD' label and requesting Inhouse team to look into the issue and help in further triaging. Thanks..
,
Nov 26
Can you check if there are any OS updates available, if so install them and try again. If that doesn't help, can you tell us what is the version of your libnss3 package? (run "dpkg -l libnss3")
,
Dec 3
Which nss version are you running? You could check it by run "dpkg -l libnss3" on terminal. Please try to upgrade your nss package if possible and see if that solves your problem. Thanks!
,
Dec 12
Ping regarding the information requested in comment #4/5. We won't be able to proceed further without it and will need to close the bug if we don't hear back.
,
Jan 7
Ping timeout. Can't proceed without further information. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by goreakan...@gmail.com
, Nov 22