Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67907 - [kiten] Segfault after latest kde frameworks updates in kconfig - rebuild needed?

Attached to Project: Arch Linux
Opened by Anonymous Submitter - Tuesday, 15 September 2020, 19:39 GMT
Last edited by Antonio Rojas (arojas) - Friday, 18 September 2020, 05:41 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

On a (timestamp: now) current Arch system, kiten segfaults immediately after starting in kf5configcore. Possibly a rebuild is needed? Worked totally fine previously.

(gdb) run
Starting program: /usr/bin/kiten
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7ffff21e8640 (LWP 112589)]
[New Thread 0x7ffff08df640 (LWP 112590)]
[New Thread 0x7fffe9a2a640 (LWP 112593)]
[New Thread 0x7fffe9229640 (LWP 112594)]
[New Thread 0x7fffe8a28640 (LWP 112595)]
[New Thread 0x7fffdffff640 (LWP 112596)]

Thread 1 "kiten" received signal SIGSEGV, Segmentation fault.
0x00007ffff6bf3c0f in KConfigBase::hasGroup(char const*) const () from /usr/lib/libKF5ConfigCore.so.5
(gdb) backtrace
#0 0x00007ffff6bf3c0f in KConfigBase::hasGroup(char const*) const () from /usr/lib/libKF5ConfigCore.so.5
#1 0x0000555555570ca6 in ?? ()
#2 0x00007ffff68e7143 in ?? () from /usr/lib/libQt5Core.so.5
#3 0x00007ffff68d871f in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#4 0x00007ffff7456752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#5 0x00007ffff68abcda in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#6 0x00007ffff6903cc5 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5
#7 0x00007ffff6904572 in ?? () from /usr/lib/libQt5Core.so.5
#8 0x00007ffff5017bfc in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#9 0x00007ffff50691f9 in ?? () from /usr/lib/libglib-2.0.so.0
#10 0x00007ffff5016421 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#11 0x00007ffff6904941 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#12 0x00007ffff68aa65c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#13 0x00007ffff68b2af4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#14 0x0000555555568801 in ?? ()
#15 0x00007ffff6278152 in __libc_start_main () from /usr/lib/libc.so.6
#16 0x000055555556889e in ?? ()

accidentally, drkonqi fails to collect debug information.

Deleting all kiten configuration in ~/.config yielded no improvement.

Additional info:
* package version(s) kiten 20.08.1-1 kconfig 5.74.0-1
* config and/or log files etc.
* link to upstream bug report, if any: none

Steps to reproduce:

Launch kiten by running "kiten" from the app launcher or the terminal
This task depends upon

Closed by  Antonio Rojas (arojas)
Friday, 18 September 2020, 05:41 GMT
Reason for closing:  Fixed
Additional comments about closing:  kiten 20.08.1-2
Comment by Antonio Rojas (arojas) - Tuesday, 15 September 2020, 20:37 GMT
Can't reproduce. Please build kconfig with debug symbols to get a better backtrace.
Comment by Anonymous Submitter - Thursday, 17 September 2020, 17:48 GMT
Compiling packages other than kconfig with debug symbols would require a build server because my old PC can't handle C++ compilation so well. Here's with kconfig debug info. Wonder how I can get frame #1 resolved better? Is it located in qt5core too?

Thread 1 "kiten" received signal SIGSEGV, Segmentation fault.
0x00007ffff6bdcb6e in KConfigBase::hasGroup (this=0x0, group=0x55555557b4bc "app") at /tmp/kconfig/src/kconfig-5.74.0/src/core/kconfigbase.cpp:22
22 {
(gdb) backtrace
#0 0x00007ffff6bdcb6e in KConfigBase::hasGroup (this=0x0, group=0x55555557b4bc "app") at /tmp/kconfig/src/kconfig-5.74.0/src/core/kconfigbase.cpp:22
#1 0x0000555555570ca6 in ?? ()
#2 0x00007ffff68c8143 in ?? () from /usr/lib/libQt5Core.so.5
#3 0x00007ffff68b971f in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#4 0x00007ffff7451752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#5 0x00007ffff688ccda in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#6 0x00007ffff68e4cc5 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5
#7 0x00007ffff68e5572 in ?? () from /usr/lib/libQt5Core.so.5
#8 0x00007ffff4ff8bfc in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#9 0x00007ffff504a1f9 in ?? () from /usr/lib/libglib-2.0.so.0
#10 0x00007ffff4ff7421 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#11 0x00007ffff68e5941 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#12 0x00007ffff688b65c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#13 0x00007ffff6893af4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#14 0x0000555555568801 in ?? ()
#15 0x00007ffff6259152 in __libc_start_main () from /usr/lib/libc.so.6
#16 0x000055555556889e in ?? ()
Comment by Antonio Rojas (arojas) - Thursday, 17 September 2020, 18:38 GMT
Please test this package

https://pkgbuild.com/~arojas/kiten-20.08.1-1.1-x86_64.pkg.tar.zst
Comment by Anonymous Submitter - Thursday, 17 September 2020, 20:28 GMT
The package above fixes the issue; after installing kiten starts normally again.

Loading...