Description of problem:
after creating a model in openscad, one cannot export it as STL since the file dialog box doesn't open.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open openscad
2. cube([1, 1, 1]);
3. F6 for render
4. F7 for export to STL
5. no export/save as dialog box
unable to export STL
file dialog box allows me to specify directory + file name and export STL
when hitting F7, the openscad window quickly "flashes" (probably losing and regaining focus) and the 'window indicator' in the top left corner of gnome shell switches from 'org.openscad.openscad' to 'Portal'. Also some warnings when starting openscad in a terminal:
QSocketNotifier: Can only be used with threads started with QThread
GLEW Error: Unknown error
Unsupported modifier, resource creation failed.
XXX: resource creation failed
I can reproduce this. The Save as dialog is also broken.
I've been trying to test other Qt apps. Meshlab won't even start with: Error: GLEW initialization failed: Unknown error.
CloudCompare displays a notification "Portal, save is ready" but does not open the save dialog. Since this is about the second, I will reassign this to Qt.
Will leave the severity as urgent, as this seems to have an impact on many apps and we are reaching the final freeze soon.
I will open a separate bugzilla for meshlab (and investigate the similar error message in openscad later).
This indeed looks like a duplicate of 2068041, https://bodhi.fedoraproject.org/updates/FEDORA-2022-f8681a48e6 somehow makes it work.
But it still displays: "The folder contents could not be displayed." clicking OK displays the content. Chromium does not do this, I've seen it in cloudcompare and openscad.
Hence, not marking it as a duplicate yet.
Created attachment 1870631 [details]
Screenshot of the error
> Meshlab won't even start with: Error: GLEW initialization failed: Unknown error.
Reported as bz2072095.
Requesting a freeze exception, as this probably affects some apps on some of the Live Labs and hence cannot be fixed with an update. If I find some affected app on a blocking media, I will request a blocker, but this is unlikely.
Apps affected found:
Apps not affected:
mu (but the save as dialog opens behind the editor)
krita (the save as dialog does not look GNOME-native, but looks like some old/custom qt dialog)
scribus (the save as dialog does not look GNOME-native, but looks like some old/custom qt dialog)
cura is also affected
(seems like anything that has to do with 3D printing is :D)
Discussed in ticket: https://pagure.io/fedora-qa/blocker-review/issue/719
The decision to classify this bug as an AcceptedFreezeException was made:
"It affects bunch of applications present in some of our deliverables and so can't be fixed by a post-release update. Also poses low-risk as it doesn't affect any applications present on our blocking deliverables."
OK, I see the GTK crash is fixed, but xdg-desktop-portal-gnome still does not work.
I don't see any relevant upstream bug report for this, though. Next step would be to report a bug to upstream xdg-desktop-portal-gnome, assuming this happens in many Qt apps and not just one.
I found this at least in:
Reported to https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/29
Back to NEW, the patch does not seem to fix this.
42.1 makes the error no longer appear right away, but it still appears after Ctrl+V into the filename prompt
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 '36'.
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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora Linux 36 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.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.
Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.
If you are unable to reopen this bug, please file a new report against an
Thank you for reporting this bug and we are sorry it could not be fixed.