Bug 1917602

Summary:	ungoogled-chromium AppImage cannot be launched
Product:	[Fedora] Fedora	Reporter:	kerigto90 <otgjikeerinnu>
Component:	libatomic_ops	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	33	CC:	dan, lkundrak, paulo.cesar.pereira.de.andrade, praiskup, rdieter
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-19 15:30:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description kerigto90 2021-01-18 21:45:43 UTC

Description of problem:
On Fedora 33 (GNOME) it is not possible to start ungoogled-chromium AppImage. Neither in Files nor via Terminal.

Version-Release number of selected component (if applicable):

How reproducible:
Always: the issue is observed each time.

Steps to Reproduce:
1. Download ungoogled-chromium AppImage
https://ungoogled-software.github.io/ungoogled-chromium-binaries/ ->

Linux AppImage 64-bit -> 87.0.4280.141-1.1 ->

https://github.com/LordTwix/ungoogled-chromium-binaries/releases/download/87.0.4280.141-1.1/ungoogled-chromium_87.0.4280.141-1.1_linux.AppImage

2. Open GNOME Terminal in Fedora 33 (GNOME) and drag and drop (with the mouse) the ungoogled-chromium AppImage to GNOME Terminal.

3. This output appears in Terminal:
[fedora@localhost ~]$ '/home/fedora/Downloads/ungoogled-chromium_87.0.4280.141-1.1_linux.AppImage'
/tmp/.mount_ungoogtyZUdM/opt/google/chrome/chrome: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory

Actual results:
ungoogled-chromium AppImage cannot be launched.

Expected results:
ungoogled-chromium AppImage can be launched just like other AppImage applications.

Additional info:
I also tried to install libatomic.so.1 in Terminal.
[fedora@localhost ~]$ sudo dnf install libatomic.so.1

But the problem remains, the same as what I wrote in Steps to reproduce in point 3.

The problem should be fixed by default for the next Fedora version so that new users can start their AppImage applications immediately.

Comment 1 Dan Horák 2021-01-19 10:34:00 UTC

I believe this is a problem of this particular AppImage, it should bundle libatomic_ops if it needs it. See https://github.com/AppImage/pkg2appimage/blob/master/excludelist for a list of system libraries.

Comment 2 kerigto90 2021-01-19 13:57:59 UTC

(In reply to Dan Horák from comment #1)
> I believe this is a problem of this particular AppImage, it should bundle
> libatomic_ops if it needs it. See
> https://github.com/AppImage/pkg2appimage/blob/master/excludelist for a list
> of system libraries.

Hello,

I found the problem in Fedora 33 (GNOME) is missing this package by default: libatomic

Just typed this in the Terminal and it was installed: 

[fedora@localhost ~]$ sudo dnf install libatomic

Package           Architecture   Version                 Repository       Size
================================================================================
Installing:
 libatomic         x86_64         10.2.1-9.fc33           updates          42 k


This means the problem can be fixed automatically by default for users without additional install if next Fedora major version has libatomic integrated.

Comment 3 kerigto90 2021-01-19 14:00:46 UTC

After installing libatomic I was able to launch the ungoogled-chromium AppImage without any problems. There was no error message in Terminal.

Can you also test it on your Fedora system, if this is solved for you when you installed libatomic?

Comment 4 Dan Horák 2021-01-19 15:30:58 UTC

Please report the issue to the ungoogled-chromium project, Fedora can't install random libraries by default, but the AppImage must bundle them.