Issue metadata
Sign in to add a comment
|
RPM installation gets hung when installing google-chrome-stable
Reported by
claude.g...@gmail.com,
Jun 27 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce the problem: 1. yum install google-chrome-stable-67.0.3396.99-1.x86_64.rpm 2. 3. What is the expected behavior? Google chrome is installed What went wrong? Command line blocked and the process will never terminate. If an old version of the Google-Linux GPG key is installed on the system, the post installation script of the RPM is trying to erase the old key, and reinstall the new version. Regression has been added last year (2017-07-27 19:15:20) by Michael Moss for correcting bug 677046, on //src/chrome/installer/linux/common/rpm.include. The small comment in the patch is not really correct. The "rpm -e" will not fail, but will block, until the lock file created by "yum install" disappear ( -> never ). Did this work before? Yes ??? regression added 2017-07-27 Chrome version: 67.0.3396.99 Channel: stable OS Version: CentOS 7.5 Flash Version: - Issue related : https://access.redhat.com/solutions/3255491.
,
Jun 28 2018
As per comments #0 the issue seems to be related to RPM installation which is out of scope for TE team .Hence adding label TE-NeedsTriageHelp. Thanks..!
,
Jul 3
Routing this issue to Inhouse team where the test environment is available to test and confirm the same, hence adding TE-NeedsTriageFromHYD label to it. Thanks!
,
Jul 4
Thanks for filing the issue! Tested in chrome # 67.0.3396.99 on Fedora 25 and Opensuse 42.3 and not able to reproduce the issue.Please find the screen shots for your reference. @claude.gygax: Could you please let me know if i have missed anything and if possible,Please Re-check once in latest chrome builds(Beta / Dev)and let us know the observations of the issue which would help us to triage the issue further. Thanks in Advance!
,
Jul 6
Hi,
On my side, to solve the problem, I had updated the Google RPM Signing key on my installation servers ( Spacewalk ) with the latest key.
So I had some problems to reproduce the BUG...
I have finally found the old Google 2016 signing key on a previously installed machine ( attached file : GOOGLE-2016-Signing.key ).
To reproduce the issue, you need 2 conditions :
- An old GOOGLE key (2016/2017) must be installed on your system
- Should be the first installation of Google-Chrome on your system.
To reproduce these conditions :
---------------------
# Remove previously existing google keys
KEY_PACKAGE="gpg-pubkey-d38b4796-570c8cd3"
rpm -e --allmatches ${KEY_PACKAGE}
# Import Google Chrome 2016 (or 2017) signing key
rpm --import GOOGLE-2016-Signing.key
# First Google-Chrome installation
rm -rf /etc/default/google-chrome
-------------------
Then, install Google-Chrome ( any version of 2018 ) :
yum install google-chrome-stable-67.0.3396.99-1.x86_64.rpm
,
Jul 6
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 12
claude.gygax@ Thanks for the update. As per comment #5, adding 'TE-NeedsTriageFromHYD' and requesting for help in further triaging, as Google key is unavailable at TE end. Thanks..
,
Jul 17
Thanks for the update! tested as per comment#5 in Non corp systems but getting permission denied error message(In-house team not having the RPM installation corp systems).Hence adding the respective label for it to triage further. Thank You! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Jun 27 2018