-
Notifications
You must be signed in to change notification settings - Fork 57
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
Crash at startup on Ubuntu 20.04 #150
Comments
Also crashes when started from an X.org session:
|
Can confirm the first crash. See https://forum.freecadweb.org/viewtopic.php?f=4&t=48540&p=415679#p415473
|
Can you have a look please @TheAssassin? Are you using Wayland @luzpaz? |
Can confirm the crash. Running xorg session. |
@probonopd sorry I missed this. I checked using:
and apparently I'm not using Wayland. |
Please try this and see whether it resolves the issue:
I suspect that |
Yes, the app starts up. |
I'm on KDE now and by mistake have started to use the bundled appimagelauncher. Can i still test the code above now or will that screw something up with the Launcher and the daemon? Appimages have now been auto-moved to /home/foo/Applications/ |
I'm not using appimagelauncher, but I hope it doesn't screw a simple operation like this one up. If it does, I'd consider it a bug ;-/ |
To everyone who ran into this issue, and for whom #150 (comment) works: Please test the Scribus AppImage from https://gitlab.com/scribus/scribus/-/jobs/artifacts/master/raw/Scribus-nightly-x86_64.AppImage?job=appimage%3Alinux and let us know whether it does or does not work on your system. This feedback would greatly help us in understanding what is going on. Thanks a lot! |
|
Maybe that's a stupid question, @probonopd but why don't you release a fixed appimage then? BTW, I just ran into this on Debian Buster with MATE running in X11 |
For anyone running into this, please try the workaround described in #150 (comment) and report back whether it resolves the issue for you. Thanks! |
#150 (comment) did resolve this for me on debian buster. This was the error message: |
`$ ./Scribus-nightly-x86_64.AppImage (ld-linux-x86-64.so.2:22506): Gtk-WARNING **: 21:33:05.181: libibus-1.0.so.5: cannot open shared object file: No such file or directory (ld-linux-x86-64.so.2:22506): Gtk-WARNING **: 21:33:05.181: Loading IM context type 'ibus' failed (ld-linux-x86-64.so.2:22506): Gtk-WARNING **: 21:33:05.182: libibus-1.0.so.5: cannot open shared object file: No such file or directory (ld-linux-x86-64.so.2:22506): Gtk-WARNING **: 21:33:05.182: Loading IM context type 'ibus' failed (ld-linux-x86-64.so.2:22506): Gtk-WARNING **: 21:33:05.207: libibus-1.0.so.5: cannot open shared object file: No such file or directory (ld-linux-x86-64.so.2:22506): Gtk-WARNING **: 21:33:05.207: Loading IM context type 'ibus' failed |
I'm having the issue as well in Fedora 33:
Solved it by applying the step: |
I confirm #150 (comment) fixes this issue, on Fedora 34 + Gnome + X.org. |
For anyone running into this, please try the workaround described in #150 (comment) and report back whether it resolves the issue for you. Thanks! |
#150 (comment) fixes the issue, Ubuntu 20.04.3, Gnome, X.org |
#150 (comment) fixed it for me as well |
also fixes for me on Debian Bookworm. |
Commenting here first, because issue/message looks similar to OP, although slightly different.
|
latest appimage debian11 version asofnow
i dont use any appimage starter or other whatsoever. |
How can we make 1000% sure that
won't end up in the AppImage? |
Please retry with https://github.com/AppImage/AppImageUpdate/releases/tag/continuous. |
It's pretty obvious from the build logs where these are coming from. linuxdeploy writes really concise logs. |
I mean, which package pulls them into the Docker container in the first place? I don't see them being proactively installed. |
How and why does that matter? Your last comment is about them ending up in the AppImage. This is what should be fixed. One should not rely on "the file is not here". We should just provide a solution for linuxdeploy/linuxdeploy-plugin-qt#109 IMO. |
Agree about linuxdeploy/linuxdeploy-plugin-qt#109 but am still curious why things like Gtk and those plugins are even downloaded by the CI in this repository, for a Qt-only app. |
My guess is they're Qt package dependencies. I didn't really check that, as I don't consider this all that relevant. Let's just discuss the Gtk+ platform theme bundling in linuxdeploy-plugin-qt instead. |
On the day on which Gtk is a dependency of Qt, I will stop using Qt. I promise ;-) |
You can't really call it a dependency. I think it's the Gtk+ users who want platform themes. They're reasonably well decoupled from the rest of Qt. Closing, as linuxdeploy-plugin-qt has been fixed. Will rebuild AppImageUpdate once the new binaries are available. |
Thank you very much @TheAssassin. |
The text was updated successfully, but these errors were encountered: