| Summary: | AppImage fails to start with message "Illegal instruction" / Since Version 22.04.3 | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | bwack <hansdals> |
| Component: | Setup & Installation | Assignee: | Jean-Baptiste Mardelle <jb> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | beneehayah, fritzibaby |
| Priority: | NOR | ||
| Version: | 22.12.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
kdenlive-23.08.4-x86_64-A.AppImage starts with X.org display setting
My display drivers and GFX card |
||
|
Description
bwack
2022-12-29 12:52:05 UTC
Might be related https://github.com/blakeblackshear/frigate/issues/1999 frei0r-plugins causes pidgin not to start. Could be related: https://bugs.archlinux.org/task/16389?project=0&order=id&sort=desc&status%5B0%5D=closed&string=frei0r-plugins I have exactly the same issue. Running the AppImage 22.04.3 in a virtual box. My computer is from 2011 too. On a newer computer the 22.04.3 AppImage runs in a virtual machine. I guess it’s a hardware incompatibility. The difference is that my PC run on BIOS and the other PC run on UEFI. How old is your PC and does it run on UEFI? *** Bug 461770 has been marked as a duplicate of this bug. *** (In reply to emohr from comment #4) > The difference is that my PC run on BIOS and the other PC run on UEFI. How > old is your PC and does it run on UEFI? It's almost been a year since I reported this issue. I have BIOS only. The problem seems to be caused by changing the way kde builds Kdenlive. It could just probably be fixed with a simple CFLAG unless it will affect the performance of those computers that utilize this (illegal) instruction. Funnily, I got it started. It got me thinking, that this libfrei0r bigsh0t plugin was loaded in runtime, and if I just removed it it would work. So I did Downloads/kdenlive-22.12.2-x86_64.AppImage --appimage-extract cd squashfs-root find usr -name big* find usr -name big* -delete ./AppRun and it runs! LOL Interesting. Could you test with the actual 23.08.4 version if it happens as well. Maybe update to Ubuntu 22.04.3 LTS or 23.10.1 first as some parts from the OS is needed to run the AppImage. (In reply to emohr from comment #8) > Interesting. Could you test with the actual 23.08.4 version if it happens as > well. Maybe update to Ubuntu 22.04.3 LTS or 23.10.1 first as some parts from > the OS is needed to run the AppImage. $ Downloads/kdenlive-23.08.4-x86_64-A.AppImage The X11 connection broke: No error (code 0) XIO: fatal IO error 2 (No such file or directory) on X server ":1" after 354 requests (354 known processed) with 0 events remaining. hans@marvin:~$ I'm on Ubuntu 20. I think I will let this machine stay at that. I also tested this at work, on my workstation with ubuntu22, and a Intel i5-7600. There, this appimage, and the one originally mentioned, starts fine. Ps. nig_sh0t does not exist in this new appimage. Created attachment 164537 [details]
kdenlive-23.08.4-x86_64-A.AppImage starts with X.org display setting
Created attachment 164538 [details]
My display drivers and GFX card
(In reply to emohr from comment #8) > Interesting. Could you test with the actual 23.08.4 version if it happens as > well. Maybe update to Ubuntu 22.04.3 LTS or 23.10.1 first as some parts from > the OS is needed to run the AppImage. I managed to get 23.08.4 started after changing to X.org display driver (see attachments). It also did render a video clip just fine. Now, with X.org driver running, I have low display resolution and video tearing effect on videoplayback (vlc, youtube etc). I get an error in "addition settings" on ubuntu when trying to apply the nvidia driver that used to use. I'll figure it out eventually, but it is a bit daunting at the moment thinking of how to get my display back in order. other observation, echo $DISPLAY shows :1. I vaguely remember that this variable was not set, and I also remember that my nvidia configuration had :0 as display id. Hence the error message "XIO: fatal IO error 2 (No such file or directory) on X server ":1"". I'm sorry, DISPLAY variable shows :1 with nvidia driver settings as well. I managed to switch back to my nvidia driver now. I have a similar issue on my Desktop PC with an NVidia card. Could you test if the following workaround works for you: ./kdenlive-23.08.4-A-x86_64.AppImage --appimage-extract cd squashfs-root source ./apprun-hooks/craft-runenv-hook.sh ./usr/bin/kdenlive OK I tried.
hans@marvin:~/Downloads$ cd squashfs-root/
hans@marvin:~/Downloads/squashfs-root$ source ./apprun-hooks/craft-runenv-hook.sh
hans@marvin:~/Downloads/squashfs-root$ ./usr/bin/kdenlive
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by ./usr/bin/kdenlive)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libKF5KIOCore.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libKF5Service.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libKF5WindowSystem.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libKF5ConfigWidgets.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libQt5Xml.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libKF5ConfigCore.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libKF5CoreAddons.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libQt5Quick.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libQt5Widgets.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libQt5Qml.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libQt5Network.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libQt5Core.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libQt5Core.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libQt5WaylandClient.so.5)
./usr/bin/kdenlive: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /home/hans/Downloads/squashfs-root/usr/bin/../lib/libicuuc.so.71)
(the program ends here)
I also tried using libstdc++ that comes with the appimage
hans@marvin:~/Downloads/squashfs-root$ source ./apprun-hooks/linuxdeploy-plugin-checkrt.sh
hans@marvin:~/Downloads/squashfs-root$ ./usr/bin/kdenlive
The X11 connection broke: No error (code 0)
XIO: fatal IO error 39 (Directory not empty) on X server ":1"
after 355 requests (355 known processed) with 0 events remaining.
I have installed Ubuntu 24 on my old computer, and now kdenlive latest appimage is working fine. You can close this issue if you like. Thank you for the feedback. I close this bug for the time beeing. If it still appears in the latest version, please feel free to re-open it and update the affected version number. |