You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting up PrusaSlicer-2.7.0-rc2+linux-x64-GTK3-202311211232.AppImage (and other images and binaries), there is always a flood of Gtk-CRITICAL & GLib-GObject-CRITICAL. Simply starting the slicer and not doing anything, this is the output:
I had always assumed this was known and ignored, but looking through the issues, it seems it has not been reported once. If the slicer is not started from the command line, it might be wholly invisible to most everyone so I decided to report it.
Project file & How to reproduce
Just start Prusa-Slicer on Linux.
Checklist of files included above
Project file
Screenshot
Version of PrusaSlicer
2.7.0-rc2
Operating system
Debian unstable
Printer model
XL
The text was updated successfully, but these errors were encountered:
Description of the bug
When starting up PrusaSlicer-2.7.0-rc2+linux-x64-GTK3-202311211232.AppImage (and other images and binaries), there is always a flood of
Gtk-CRITICAL
&GLib-GObject-CRITICAL
. Simply starting the slicer and not doing anything, this is the output:I had always assumed this was known and ignored, but looking through the issues, it seems it has not been reported once. If the slicer is not started from the command line, it might be wholly invisible to most everyone so I decided to report it.
Project file & How to reproduce
Just start Prusa-Slicer on Linux.
Checklist of files included above
Version of PrusaSlicer
2.7.0-rc2
Operating system
Debian unstable
Printer model
XL
The text was updated successfully, but these errors were encountered: