-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File Save Dialog on Ubuntu 22.04 #12438
Comments
I've also just realized that if I overwrite an existing file, I have to confirm it twice--one confirmation from the system file select dialog, and then a second confirmation dialog from Cura |
I dont even get notification, pressing button does nothing. I'm on Xubuntu so I probably don't have that type of notification popup, I have notification in top-bar but that gives nothing. Previous version of Cura 4.12 had every filedialog working, you could open files and save them no issue. |
It's the same on Fedora 36. The save dialog pops up in the background, the system is sending a notification and there is no predefined filename. I started cura from command line for stdout:
|
Duplicate of #12266 |
Application Version
5.0.0
Platform
Ubuntu 22.04
Printer
Voron
Reproduction steps
Running the latest 5.0.0 AppImage on Ubuntu (with the LD_PRELOAD fix from issue #12359) and I've noticed that the save file dialog after slicing is behaving oddly. To reproduce, just slice a model and hit the "Save to Disk" button
Actual results
First, instead of the file selector dialog popping up and taking focus, I just get a system notification that it's ready.
Clicking the notification takes me to the file dialog, which is now missing the prefilled suggested file name
Expected results
The file select dialog should pop up and take focus on its own, and it should prepopulate with a suggested file name
Checklist of files to include
Additional information & file uploads
Nothing pops up in the terminal when opening the save dialog, but here's my command line in case there's anything helpful there
The text was updated successfully, but these errors were encountered: