https://bugs.kde.org/show_bug.cgi?id=429677
--- Comment #3 from Alexander Lohnau <alexander.loh...@gmx.de> --- >Alex, any chance some of your commits during 5.76 development to KNewStuff >might be the culprit here? It might be, because the timer logic got refactored, there is a separate bug about this. This part of the stacktrace is relevant. >#9 0x00007f5de9fea28b in QObject::killTimer(int) (this=this@entry=0x64ff4b0, >id=7274604) at kernel/qobject.cpp:1795 >#10 0x00007f5de9ff4c99 in QTimer::stop() (this=this@entry=0x64ff4b0) at >>kernel/qtimer.cpp:243 >#11 0x00007f5de9ff4d0f in QTimer::start() (this=0x64ff4b0) at >>kernel/qtimer.cpp:211 >#12 0x00007f5de90ecfec in >>KNSCore::Cache::registerChangedEntry(KNSCore::EntryInternal const&) >>(this=0x6582170, entry=...) at >/home/koder/Kode/kdegit/kf5/frameworks/knewstuff/src/core/cache.cpp:294 Also it is known that it can cause issues when the dialog gets opened, but closed before being done with the initializing and then reopened. (Just the QWidgets one). -- You are receiving this mail because: You are watching all bug changes.
