SUMMARY KDevelop 5.6.1 AppImage silently terminates when using "Open project" STEPS TO REPRODUCE 1. Start KDevelop 5.6.1 AppImage 2. Use "Open/Import Project" from "Project" menu OBSERVED RESULT Program silently terminated. When started from terminal gives error "Harfbuzz version too old". EXPECTED RESULT "Open project" dialog should open SOFTWARE/OS VERSIONS Linux: Debian 64 bit bullseye KDevelop 5.6.1 ADDITIONAL INFORMATION Previous version of KDevelop (AppImage 5.6.0) works normally.
please try this: ``` KDevelop-5.6.1-x86_64.AppImage --appimage-extract cd squashfs-root ./AppRun ``` then from somewhere else: ``` gdb --pid $(pidof AppRun.wrapped) ``` then trigger the crash and get a backtrace from the gdb console: ``` (gdb) thread apply all bt ``` I guess most/all symbols will be missing, but we should at least see where it's crashing (i.e. in which rough code area). Maybe that then allows us to see what's going on here. The harfbuzz thing is probably a red-herring. You could still try that by removing usr/lib/libharfbuzz.so usr/lib/libharfbuzz.so.0 from the squashfs-root and then launching AppRun again
KDevelop hangs when I use "gdb --pid $(pidof AppRun.wrapped)". Removing "usr/lib/libharfbuzz.so" and "usr/lib/libharfbuzz.so.0" didn't help.
OK, used command "gdb --pid $(pidof AppRun.wrapped) -ex cont" Here's output: apv@debian:~/kdevelop/squashfs-root$ gdb --pid $(pidof AppRun.wrapped) -ex cont GNU gdb (Debian 10.1-1.5) 10.1 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". Attaching to process 1264 [New LWP 1267] [New LWP 1268] [New LWP 1269] [New LWP 1270] [New LWP 1271] [New LWP 1272] [New LWP 1273] [New LWP 1280] [New LWP 1288] [New LWP 1289] [New LWP 1290] [New LWP 1291] [New LWP 1292] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". --Type <RET> for more, q to quit, c to continue without paging-- 0x00007fce2bb1439f in __GI___poll (fds=0x264e5b0, nfds=9, timeout=3989) at ../sysdeps/unix/sysv/linux/poll.c:29 29 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory. Continuing. [New Thread 0x7fcddaffd700 (LWP 1325)] [New Thread 0x7fcdda7fc700 (LWP 1326)] [New Thread 0x7fcdd9ffb700 (LWP 1327)] [New Thread 0x7fcdd97fa700 (LWP 1328)] [New Thread 0x7fcdd8ff9700 (LWP 1329)] Thread 1 "AppRun.wrapped" received signal SIGTRAP, Trace/breakpoint trap. 0x00007fce26ca798b in g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 (gdb) thread apply all bt Thread 19 (Thread 0x7fcdd8ff9700 (LWP 1329) "pool-AppRun.wra"): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x00007fce26cf0152 in g_cond_wait_until () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fce26c6e5d1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fce26cc899a in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007fce26cc7f5d in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007fce2aee0ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477 #6 0x00007fce2bb1ed8f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fcdd97fa700 (LWP 1328) "pool-AppRun.wra"): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x00007fce26cf0152 in g_cond_wait_until () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fce26c6e5d1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fce26cc899a in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007fce26cc7f5d in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007fce2aee0ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477 #6 0x00007fce2bb1ed8f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fcdd9ffb700 (LWP 1327) "pool-AppRun.wra"): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x00007fce26cf0152 in g_cond_wait_until () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fce26c6e5d1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fce26cc899a in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007fce26cc7f5d in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007fce2aee0ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477 #6 0x00007fce2bb1ed8f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 --Type <RET> for more, q to quit, c to continue without paging--
The SIGTRAP signal may indicate that GDB fails because of Bug 427246. What is the Qt version in the AppImage? If it is 5.15.2 or <5.15.0, then this is probably a different issue.
Qt version is 5.15.1
(In reply to arampl from comment #5) > Qt version is 5.15.1 Bug 427246 hampers generating backtraces for the KDevelop AppImage then. Apart from this bug, Qt 5.15.2 also fixes Bug 426070. If updating AppImage's Qt version to 5.15.2 is not difficult, it might be worth doing.
agreed, afaik we should get that easily via craft, I'll see when I find the time to look into this.
Hi, I encountered the same issue, and for your information, here is the complete error that is reported on the terminal: ``` (AppRun.wrapped:2201553): Pango-ERROR **: 13:59:27.214: Harfbuzz version too old (1.7.5) Trace/breakpoint trap (core dumped) ``` I think that the relevant info is that this error is coming from Pango. Maybe Pango was updated in the appimage but not harfbuzz, and so it is just that harfbuzz has to be updated also?
*** Bug 435463 has been marked as a duplicate of this bug. ***
Same behavior is also observable in Ubuntu 20.04.
I have the same issue on SLE15. The hint with the libraries was a good one. I noticed that the following: 824736 Nov 8 09:17 squashfs-root/usr/lib/libharfbuzz.so 665896 Nov 8 09:17 squashfs-root/usr/lib/libharfbuzz.so.0 The 5.6.1 app image comes with two different libharfbuzz.so versions! When using both time the smaller one the app does not start at all and when using two times the larger it does not crash anymore up but the menu bar font looks smaller.