Installing Google Chrome in Fedora Workstation 39

For Fedora workstation 39 to install Google Chrome I downloaded the .rpm file from the official page and executed the sudo dnf install google-chrome-stable_current_x86_64.rpm command and appears the following:

sudo dnf install google-chrome-stable_current_x86_64.rpm
[sudo] password for manueljordan: 
Fedora 39 - x86_64 - Updates                                                                                                 18 kB/s |  51 kB     00:02    
Last metadata expiration check: 0:00:01 ago on Sat 06 Jan 2024 09:54:14 AM -05.
Dependencies resolved.
============================================================================================================================================================
 Package                                    Architecture                 Version                                   Repository                          Size
============================================================================================================================================================
Installing:
 google-chrome-stable                       x86_64                       120.0.6099.199-1                          @commandline                       102 M
Installing dependencies:
 liberation-fonts                           noarch                       1:2.1.5-7.fc39                            fedora                             7.5 k

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

Total size: 102 M
Total download size: 7.5 k
Installed size: 323 M
Is this ok [y/N]: y
Downloading Packages:
liberation-fonts-2.1.5-7.fc39.noarch.rpm                                                                                     17 kB/s | 7.5 kB     00:00    
------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                       5.0 kB/s | 7.5 kB     00:01     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                                    1/1 
  Installing       : liberation-fonts-1:2.1.5-7.fc39.noarch                                                                                             1/2 
  Running scriptlet: google-chrome-stable-120.0.6099.199-1.x86_64                                                                                       2/2 
  Installing       : google-chrome-stable-120.0.6099.199-1.x86_64                                                                                       2/2 
  Running scriptlet: google-chrome-stable-120.0.6099.199-1.x86_64                                                                                       2/2 
error: can't create transaction lock on /usr/lib/sysimage/rpm/.rpm.lock (Resource temporarily unavailable)
error: /tmp/google.sig.HT3hKB: key 1 import failed.
error: can't create transaction lock on /usr/lib/sysimage/rpm/.rpm.lock (Resource temporarily unavailable)
error: /tmp/google.sig.HT3hKB: key 2 import failed.

  Verifying        : liberation-fonts-1:2.1.5-7.fc39.noarch                                                                                             1/2 
  Verifying        : google-chrome-stable-120.0.6099.199-1.x86_64                                                                                       2/2 

Installed:
  google-chrome-stable-120.0.6099.199-1.x86_64                                    liberation-fonts-1:2.1.5-7.fc39.noarch                                   

Complete!

Observe from above the error messages, just in case when the sudo dnf install google-chrome-stable_current_x86_64.rpm command is executed again and appears the following:

sudo dnf install google-chrome-stable_current_x86_64.rpm
google-chrome                                                                                                               5.0 kB/s | 1.3 kB     00:00    
Package google-chrome-stable-120.0.6099.199-1.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

Through Show Apps is possible open in peace Google Chrome (but not used by complete yet). Therefore:

  • Can I ignore in peace those error messages?
  • Why appears that error messages? I mean can you explain the reason of each error message?

You should not ignore those error messages.

  • to install a package you should use the appropriate repository, (for google-chrome that is google-chrome.repo) to ensure that you get the relevant security keys, which help to prevent installing a malicious rpm file.

  • you may have incorrect selinux labels or permissions. Compare with labels and permissions on my Workstation 39:

% ls -ldZ /usr/lib/sysimage/rpm/
drwxr-xr-x. 1 root root system_u:object_r:rpm_var_lib_t:s0 174 Dec 21 16:04 /usr/lib/sysimage/rpm/
% ls -lZ /usr/lib/sysimage/rpm/
total 200812
-rw-r--r--. 1 root root system_u:object_r:rpm_var_lib_t:s0 205598720 Jan  6 11:18 rpmdb.sqlite
-rw-r--r--. 1 root root system_u:object_r:rpm_var_lib_t:s0     32768 Jan  6 21:37 rpmdb.sqlite-shm
-rw-r--r--. 1 root root system_u:object_r:rpm_var_lib_t:s0         0 Jan  6 11:18 rpmdb.sqlite-wal
1 Like

And why not a flatpak? Google Chrome

You should not ignore those error messages

Agree, that’s why I created this post. Even when Chrome runs I got these messages

to install a package you should use the appropriate repository, (for google-chrome that is google-chrome.repo ) to ensure that you get the relevant security keys, which help to prevent installing a malicious rpm file

Agree, but remember, I downloaded the rpm file from the official source - Google Chrome - The Fast & Secure Web Browser Built to be Yours - I did do the same approach for Ubuntu to get the .deb file in peace.

you may have incorrect selinux labels or permissions. Compare with labels and permissions on my Workstation 39:

Thanks for this point, executing your same commands I got:

ls -ldZ /usr/lib/sysimage/rpm/
drwxr-xr-x. 1 root root system_u:object_r:rpm_var_lib_t:s0 174 Dec 23 18:06 /usr/lib/sysimage/rpm/

ls -lZ /usr/lib/sysimage/rpm/
total 130016
-rw-r--r--. 1 root root system_u:object_r:rpm_var_lib_t:s0 133103616 Jan  7 09:24 rpmdb.sqlite
-rw-r--r--. 1 root root system_u:object_r:rpm_var_lib_t:s0     32768 Jan  7 09:24 rpmdb.sqlite-shm
-rw-r--r--. 1 root root system_u:object_r:rpm_var_lib_t:s0         0 Jan  7 09:24 rpmdb.sqlite-wal

Not sure if that data is OK or not. Could you bring some guidance pls?

And why not a flatpak? Google Chrome

In Ubuntu is possible install software through snap (either command or GUI snapstore) is quickly but the programs open slow. So I use the apt and dpkg commands in peace. So far my unique exception was VLC.

Even if it would not happen for flatpack I used the rpm from the source.

Installing simple packages from an archive without using the distro package manager can work, but a) unless you check package integrity manually, you are taking risks that package managers help minimize, and b) may not correctly identify dependencies (e.g., where the 3rd party repo provides a non-free library with capabilities not present in the distro version). Post-install, the package manager saves you from having to manually track updates and bug fixes. There is a reason distros put a lot of effort into package management.

1 Like

Installing simple packages from an archive without using the distro package manager can work, but a) unless you check package integrity manually, you are taking risks that package managers help minimize, and b) may not correctly identify dependencies (e.g., where the 3rd party repo provides a non-free library with capabilities not present in the distro version). Post-install, the package manager saves you from having to manually track updates and bug fixes. There is a reason distros put a lot of effort into package management.

Thanks for the explanation … Yes. So far I had 1 situation when a .deb file rose some problems about dependency but was fixed with an extra parameter or with the apt command.

Just applying a simple thought: why for the beginning and so far Google offers Chrome to be installed through the rpm and deb files if exists the mentioned repositories?

Otherwise, the transaction lock happens when something else is already accessing the resource in the background - the package manager in gnome?
You have to wait a while.

1 Like

Otherwise, the transaction lock happens when something else is already accessing the resource in the background the package manager in gnome? You have to wait a while.

Can you pls expand a little more the idea?

Not sure if it is the same case as ubuntu about: when is executed the sudo apt update command sometimes report errors about blocking because other software is running - I did do realize it is when internally the Software app is running behind the scenes checking if exists something to update.

Yes exactly.