AppImageLauncher: [Settings] Crash on Debian stable (with non-Qt desktop)
Just been trying the settings dialog (installed via the bionic package) and there’s some serious issues with the settings dialog:
That /path should not be shown there, it’s a hidden default value because putting some value in there helps with Qt Designer. It’s replaced during runtime.
It just froze after some time, so I had to kill the process. On a subsequent try, I could get a little further and hit the “choose path” button, which led to this state:
@azubieta, you’re the Qt expert, any ideas? This is kinda bad…
About this issue
- Original URL
- State: open
- Created 5 years ago
- Comments: 31 (15 by maintainers)
Commits related to this issue
- Try to force non-native file chooser Contributes to #218. — committed to TheAssassin/AppImageLauncher by TheAssassin 5 years ago
Interesting. Now, AppImageLauncher itself doesn’t require a static
zlib, libappimage has been linking to it statically all the time. IMO static linking is overrated, andzlibitself is actually on our blacklist of libraries to be bundled.I’ll reopen the issue and hopefully will get to testing the difference today. Thanks for the information.
Here’s the bug report I opened: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1838891
By the way does anyone know a way to disable the gtk3 plugin through an environment variable or something? Preloading a fake gtk3 library helps to force the qt file dialog to pop up: