I ran updates on my arch (6.18.45-1-lts) and cachy (7.2.0-1) machines this morning and found that today’s updates broke Kile 2.9.94 on both. GDB trace suggests that this crash is a result of the update to Okular 26.08.0
Starting program: /usr/bin/kile
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffec1ff6c0 (LWP 31171)]
[New Thread 0x7fffead576c0 (LWP 31172)]
[New Thread 0x7fffea5566c0 (LWP 31173)]
[New Thread 0x7fffe9b3d6c0 (LWP 31174)]
[New Thread 0x7fffe933c6c0 (LWP 31175)]
Thread 1 "kile" received signal SIGSEGV, Segmentation fault.
0x00007ffff5ac8aa8 in QAction::setEnabled(bool) () from /usr/lib/libQt6Gui.so.6
#0 0x00007ffff5ac8aa8 in QAction::setEnabled(bool) () at /usr/lib/libQt6Gui.so.6
#1 0x00007fffe88d1ea6 in Okular::Part::updateViewActions() () at /usr/lib/qt6/plugins/kf6/parts/okularpart.so
#2 0x00007fffe88cf869 in Okular::Part::Part(QObject*, QList<QVariant> const&) () at /usr/lib/qt6/plugins/kf6/parts/okularpart.so
#3 0x00007fffe88ee317 in ??? () at /usr/lib/qt6/plugins/kf6/parts/okularpart.so
#4 0x0000555555801ee8 in ??? ()
#5 0x000055555575e3e7 in ??? ()
#6 0x00005555556189b3 in ??? ()
#7 0x00007ffff4227d0e in ??? () at /usr/lib/libc.so.6
#8 0x00007ffff4227e4b in __libc_start_main () at /usr/lib/libc.so.6
#9 0x000055555561ab15 in ??? ()
the conclusion that the Okular update is supported by the issue being resolved when using okular-git-26.11.70_r11752.g325440424-1
is the above enough information for a bug report? I am unsure of how to get a clean backtrace given that using the git seems to fix the issue so any advise on how i would do so would be greatly appreciated