Bug 2159281 - unable to install google-chrome
Summary: unable to install google-chrome
Keywords:
Status: CLOSED DUPLICATE of bug 2149762
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Blaha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F38FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2023-01-09 10:00 UTC by lnie
Modified: 2023-01-11 00:38 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-11 00:38:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journal (325.20 KB, text/plain)
2023-01-09 10:00 UTC, lnie
no flags Details

Description lnie 2023-01-09 10:00:50 UTC
Created attachment 1936750 [details]
journal

Description of problem:
Unable to install google-chrome using dnf/Software
[lnie@localhost-live ~]$ sudo dnf install google-chrome-stable

Fedora - Rawhide - Developmental packages for t 786 kB/s |  65 MB     01:25    
Fedora - Modular Rawhide - Developmental packag 1.8 MB/s | 2.3 MB     00:01    
google-chrome                                   3.0 kB/s | 3.6 kB     00:01    
Dependencies resolved.
================================================================================
 Package                 Arch      Version               Repository        Size
================================================================================
Installing:
 google-chrome-stable    x86_64    108.0.5359.124-1      google-chrome     92 M
Installing dependencies:
 liberation-fonts        noarch    1:2.1.5-3.fc37        rawhide          7.8 k

Transaction Summary
================================================================================
Install  2 Packages

Total download size: 92 M
Installed size: 300 M
Is this ok [y/N]: Operation aborted.


Version-Release number of selected component (if applicable):
dnf-4.14.0-1.fc38.noarch
gnome-software-43.2-1.fc38.x86_64
PackageKit-1.2.5-2.fc37.x86_64


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fedora Blocker Bugs Application 2023-01-09 10:43:19 UTC
Proposed as a Blocker for 38-final by Fedora user lnie using the blocker tracking app because:

 seems affects:
For all release-blocking desktop / arch combinations, the following applications must start successfully and withstand a basic functionality test

Comment 2 Panu Matilainen 2023-01-09 11:19:35 UTC
Google Chrome is not installable by default in rawhide because of the weak DSA/SHA1 crypto used to sign the package, see eg https://bugzilla.redhat.com/show_bug.cgi?id=2149762

The above description does not look like that issue though. If dnf really quits on its own at the y/n prompt then that'd be something different.

Comment 3 Marek Blaha 2023-01-09 12:33:29 UTC
Hi, I've just checked and the issue I hit is the one with gpg check:

# dnf install google-chrome-stable
Dependencies resolved.
=========================================================================================
 Package                     Arch   Version                          Repository     Size
=========================================================================================
Installing:
 google-chrome-stable        x86_64 108.0.5359.124-1                 google-chrome  92 M
Installing dependencies:
------ 8< ------
Transaction Summary
=========================================================================================
Install  170 Packages

Total size: 207 M
Installed size: 756 M
Is this ok [y/N]: y
Downloading Packages:
------ 8< ------
(168/170): google-chrome-stable-108.0.5359.124-1.x86_64.  49 MB/s |  92 MB     00:01
------ 8< ------
Problem opening package google-chrome-stable-108.0.5359.124-1.x86_64.rpm
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

@lnie can you please verify that this is the issue?

Comment 4 lnie 2023-01-10 02:16:25 UTC
Just checked,yes,that's the issue

Comment 5 Adam Williamson 2023-01-11 00:38:45 UTC

*** This bug has been marked as a duplicate of bug 2149762 ***


Note You need to log in before you can comment on or make changes to this bug.