Description of problem: I have one x86-64 machine (Intel CPU) running Fedora 30, on which Gambas IDE is installed and invokable. On another machine (AMD CPU) Fedora 31 is installed and although Gambas3 is installed it will not run. The icon is present but the IDE never loads and an "OOPS" message notification appears. Version-Release number of selected component (if applicable): gambas3-ide.x86_64 3.12.2-2.fc31 How reproducible: Tried twice: install, uninstall and reinstall over period of two weeks Steps to Reproduce: 1.As SU: "DNF install gambas3-ide" 2.Activities / Gambas3 / click on icon 3. Actual results: Notification: "OOPS! Looks like Gambas3 crashed. Try again? Expected results: Gambas splash screen followed by IDE Additional info:
I can't reproduce this on my Fedora 31 system. Can you try the following: 1. As root, run: dnf reinstall gambas3 2. From a terminal window, launch gambas3. If it crashes there, it should provide more output for me to try to debug the issue.
I can reproduce this now. Gambas3 is very dependent on X11, it will not run on wayland.
*** Bug 1776023 has been marked as a duplicate of this bug. ***
*** Bug 1815531 has been marked as a duplicate of this bug. ***
Upstream for gambas3 suggests that the failure to launch is due to bugs in xorg-x11-server-Xwayland, as it should be properly handling all of the X11 calls in the gambas3 code. Reassigning.
(In reply to Tom "spot" Callaway from comment #5) > Upstream for gambas3 suggests that the failure to launch is due to bugs in > xorg-x11-server-Xwayland, as it should be properly handling all of the X11 > calls in the gambas3 code. Reassigning. That's a bit nonsensical I'm afraid, Xwayland *is* a complete X11 server (it actually shares the same code with Xorg). The problem here is not Xwayland for the simple reason that gambas3 uses Qt which, on F31, uses its own Qt Wayland native backend. In other words, by default, gambas3 runs natively on Wayland and Xwayland is not involved. But if you force Qt to use X11 (and hence Xwayland) with this: $ QT_QPA_PLATFORM=xcb gambas3 it works fine, meaning that the issue is either in gambas3 or in Qt, but not in Xwayland. Can you please reassign this bug back?
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
In digging, this looks to be a QT failure on Wayland with the native platform (not xcb), rather than a gambas3 failure. Reassigning to qt.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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.
*** Bug 1894269 has been marked as a duplicate of this bug. ***
This is still an issue in Fedora 33.
This needs to be reassigned to Fedora 33 or it will close. I am not able to reassign it.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.