Bug 1575865

Summary: gchem3d and gcrystal does not start on wayland session
Product: [Fedora] Fedora Reporter: Basil Eric Rabi <ericbasil.rabi>
Component: gnome-chemistry-utilsAssignee: Julian Sikorski <belegdol>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: anto.trande, belegdol
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnome-chemistry-utils-0.14.17-32.fc35 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-24 02:43:52 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 Basil Eric Rabi 2018-05-08 06:29:59 UTC
Description of problem:
gchem3d and gcrystal does not start

Version-Release number of selected component (if applicable):
gnome-chemistry-utils-0.14.17-11.fc28.x86_64

How reproducible:
always

Comment 1 Ben Cotton 2019-05-02 21:44:14 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Basil Eric Rabi 2021-03-27 03:58:56 UTC
There seems to be a packaging patch for debian (https://salsa.debian.org/debichem-team/gnome-chemistry-utils/-/commit/694931319167f1e9317a3791281491610993b60b) to prevent crashing.

Comment 3 Julian Sikorski 2021-03-27 08:35:01 UTC
All this patch does is setting GDK_BACKEND=x11 before launching. Could you please test if it works for you? I was not having much success.

Comment 4 Basil Eric Rabi 2021-03-27 08:59:59 UTC
Yes. Running `GDK_BACKEND=x11 gcrystal` and `GDK_BACKEND=x11 gchem3d` in the terminal works for me.

Comment 5 Ben Cotton 2022-05-12 16:51:28 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Basil Eric Rabi 2022-05-13 00:40:52 UTC
Still an issue in f36 and the workaround fails now. Error now is weird:

$ gcrystal
gcrystal: error while loading shared libraries: libgcu-0.14.so.0: cannot open shared object file: No such file or directory

$ gchem3d
gchem3d: error while loading shared libraries: libgcugtk-0.14.so.0: cannot open shared object file: No such file or directory


However, those files exist:

# locate libgcu-0.14.so.0
/usr/lib64/gchemutils/libgcu-0.14.so.0
/usr/lib64/gchemutils/libgcu-0.14.so.0.14.17

# locate libgcugtk-0.14.so.0
/usr/lib64/gchemutils/libgcugtk-0.14.so.0
/usr/lib64/gchemutils/libgcugtk-0.14.so.0.14.17

Comment 7 Julian Sikorski 2022-05-13 15:18:19 UTC
I guess this commit is to blame:
https://src.fedoraproject.org/rpms/gnome-chemistry-utils/c/1cf90dfaeb67842320b245d55619b587f15702de
It should start if you use LD_LIBRARY_PATH. Looks like the GDK fix isn't in the commit even though it is mentioned in the changelog.

Comment 8 Fedora Update System 2022-05-15 09:49:40 UTC
FEDORA-2022-ec1254d4cc has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ec1254d4cc

Comment 9 Fedora Update System 2022-05-15 11:33:21 UTC
FEDORA-2022-0decee55e0 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0decee55e0

Comment 10 Fedora Update System 2022-05-16 02:28:39 UTC
FEDORA-2022-0decee55e0 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-0decee55e0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0decee55e0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2022-05-16 03:12:33 UTC
FEDORA-2022-ec1254d4cc has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-ec1254d4cc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ec1254d4cc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Basil Eric Rabi 2022-05-19 08:07:24 UTC
Issue is still present after the update.

Comment 13 Fedora Update System 2022-05-24 02:41:54 UTC
FEDORA-2022-ec1254d4cc has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2022-05-24 02:43:52 UTC
FEDORA-2022-0decee55e0 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.