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
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.
There seems to be a packaging patch for debian (https://salsa.debian.org/debichem-team/gnome-chemistry-utils/-/commit/694931319167f1e9317a3791281491610993b60b) to prevent crashing.
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.
Yes. Running `GDK_BACKEND=x11 gcrystal` and `GDK_BACKEND=x11 gchem3d` in the terminal works for me.
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.
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
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.
FEDORA-2022-ec1254d4cc has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ec1254d4cc
FEDORA-2022-0decee55e0 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0decee55e0
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.
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.
Issue is still present after the update.
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.
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.