OK on a new install on 2 x86_64 systems. I also did a reinstall of Fedoara 44 on one.
No problem on one. Also no problem on 2 laptops upgraded from Fedor 43.
# dnf install google-chrome-stable
Updating and loading repositories:
Repositories loaded.
Package Arch Version Repository Size
Installing:
google-chrome-stable x86_64 0:148.0.7778.96-1 google-chrome 405.0 MiB
Installing dependencies:
liberation-fonts-all noarch 1:2.1.5-15.fc44 fedora 0.0 B
Transaction Summary:
Installing: 2 packages
Total size of inbound packages is 128 MiB. Need to download 128 MiB.
After this operation, 405 MiB extra will be used (install 405 MiB, remove 0 B).
Is this ok [y/N]: y
[1/2] liberation-fonts-all-1:2.1.5-15.fc44.noarch 100% | 63.5 KiB/s | 7.9 KiB | 00m00s
[2/2] google-chrome-stable-0:148.0.7778.96-1.x86_64 100% | 41.6 MiB/s | 127.9 MiB | 00m03s
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2/2] Total 100% | 33.2 MiB/s | 127.9 MiB | 00m04s
Running transaction
[1/4] Verify package files 100% | 6.0 B/s | 2.0 B | 00m00s
[2/4] Prepare transaction 100% | 12.0 B/s | 2.0 B | 00m00s
[3/4] Installing liberation-fonts-all-1:2.1.5-15.fc44.noarch 100% | 3.5 KiB/s | 124.0 B | 00m00s
[4/4] Installing google-chrome-stable-0:148.0.7778.96-1.x86_64 100% | 28.5 MiB/s | 405.1 MiB | 00m14s
>>> Running %post scriptlet: google-chrome-stable-0:148.0.7778.96-1.x86_64
>>> Finished %post scriptlet: google-chrome-stable-0:148.0.7778.96-1.x86_64
>>> Scriptlet output:
>>> error: can't create transaction lock on /usr/lib/sysimage/rpm/.rpm.lock (Resource temporarily unavailable)
>>> error: can't create transaction lock on /usr/lib/sysimage/rpm/.rpm.lock (Resource temporarily unavailable)
>>> error: can't create transaction lock on /usr/lib/sysimage/rpm/.rpm.lock (Resource temporarily unavailable)
>>> error: /tmp/google.sig.sFkNgi: key 1 import failed.
>>>
Complete!
No, I was asking if you could check what had that /usr/lib/sysimage/rpm/.rpm.lock file open.
It might have just been a transitory problem due to some background process checking for updates.
Personally, I like to set metadata_timer_sync=0 /etc/dnf/dnf.conf so that there is one less thing randomly (and pointlessly) eating tons of CPU cycles, memory, and storage I/O on my PC.
If you keep running file </path/from/previous/result, I think you should eventually get to the following:
$ file /opt/google/chrome/google-chrome
/opt/google/chrome/google-chrome: Bourne-Again shell script, ASCII text executable
In that shell script, I see these lines:
# Use system xdg utilities. But first create mimeapps.list if it doesn't
# exist; some systems have bugs in xdg-mime that make it fail without it.
xdg_app_dir="${XDG_DATA_HOME:-$HOME/.local/share/applications}"
mkdir -p "$xdg_app_dir"
[ -f "$xdg_app_dir/mimeapps.list" ] || touch "$xdg_app_dir/mimeapps.list"
I wonder if you could have lauched google-chrome in such a way that, although it was running as “root”, $HOME (or $XDG_DATA_HOME) was either empty or still set to your normal user’s home directory? If so, the above lines of code might have created files under your personal home directory that are (incorrectly) owned by root. The consequence of that might be that all future invocations of google-chrome could only be done by root. Moral of the story: NEVER run random programs as root. GUI programs, especially, should never be run as root (and a web browser is an especially bad thing to run as root because it automatically downloads and runs code from the world wide web).
Edit: If you create a new user account, then can you launch google-chrome as that user?
I took the liberty to reformat your requests. This way we can see straight what you pasted and what is written by you. With bigger text blocks scrolling around in the topic is much easier.
You can do this too, while clicking on the </> in the top menu of the discourse editor and past into it as shown:
I see the same error with both installing and upgrading google-chrome-stable. It appears to be a transitory issue (message) that has no effect on the installation or upgrade of the system or any packages that I have found.
I suspect this may be an issue in the way the google-chrome-stable package is created and not an actual error for the system.
