Application: ark (2.19) KDE Platform Version: 4.14.6 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 3.19.1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I opened a zip file. I clicked a rdf file inside it. It opened with akregator. when I closed akregator, ark crashed. -- Backtrace: Application: Ark (ark), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [KCrash Handler] #6 0x00007f5218d82096 in Akregator::Frame::slotSetState(Akregator::Frame::State) () from /usr/lib/libakregatorprivate.so.4 #7 0x00007f5219023447 in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib/kde4/akregatorpart.so #8 0x00007f522c327d9c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #9 0x00007f5218d81ce9 in Akregator::FetchQueue::slotAbort() () from /usr/lib/libakregatorprivate.so.4 #10 0x00007f5218d81d6a in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4 #11 0x00007f5218d81dd9 in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4 #12 0x00007f5218d80c29 in Akregator::Kernel::~Kernel() () from /usr/lib/libakregatorprivate.so.4 #13 0x00007f522bb10db2 in __run_exit_handlers () from /usr/lib/libc.so.6 #14 0x00007f522bb10e05 in exit () from /usr/lib/libc.so.6 #15 0x00007f522bafb807 in __libc_start_main () from /usr/lib/libc.so.6 #16 0x000000000040a7d9 in _start () Reported using DrKonqi
any chance you can send me the zip file? even if it only has the rdf file in the archive.
I sent it to your email. Thank you very much.
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.