Could be similar to bug 342381 but I never had a corrupted feeds.opml in KDE4. On each akregator crash, even if no feed was added/deleted/changed/whatever, akregator claims feeds.opml is corrupted. Nothing really useful in the output except this # akregator 10:08:25 - akregator(10070) - : QObject::connect: No such signal QDBusAbstractInterface::iconChanged(bool,QString,QString) in /kde/src/5/kdepim/akregator/src/feediconmanager.cpp:78 10:08:26 - akregator(10070) - khtml::CachedCSSStyleSheet::checkNotify: finishedLoading "file:///kde/inst/5/master/share/kf5/infopage/kde_infopage.css" 10:08:26 - akregator(10070) - khtml::CachedCSSStyleSheet::checkNotify: finishedLoading "file:///kde/inst/5/master/share/akregator/about/akregator.css" 10:08:26 - akregator(10070) - : QWidget::paintEngine: Should no longer be called 10:08:26 - akregator(10070) - : QWidget::paintEngine: Should no longer be called 10:08:26 - akregator(10070) - : QWidget::paintEngine: Should no longer be called 10:08:26 - akregator(10070) - : QWidget::paintEngine: Should no longer be called 10:08:26 - akregator(10070) - : QWidget::paintEngine: Should no longer be called 10:08:26 - akregator(10070) - : QWidget::paintEngine: Should no longer be called 10:08:26 - akregator(10070) - : QWidget::paintEngine: Should no longer be called 10:08:26 - akregator(10070) - : "Tag 'qt' is not defined in message {<__kuit_internal_top__><qt><p>XML parsing error in line 2, column 1 of /home/kro...}." 10:08:26 - akregator(10070) - : "Tag 'p' is not defined in message {<__kuit_internal_top__><qt><p>XML parsing error in line 2, column 1 of /home/kro...}." 10:08:26 - akregator(10070) - : "Tag 'p' is not defined in message {<__kuit_internal_top__><qt><p>XML parsing error in line 2, column 1 of /home/kro...}." I've no idea what the truncated filename is. Suggestions ?
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.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 opportunity 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.
I too observe feeds.opml being reported corrupted. Happened to me again just now when I booted my computer today. I don't remember Akregator crashing yesterday when I logged out yesterday. But it is possible that I didn't close Akregator before shutting down from KDE. But I am unable to reproduce this problem by forcefully terminating Akrgator with "kill -9". Using Akregator v5.5.1, KDE Frameworks 5.36.0, Qt 5.7.1 (built against 5.7.1), Fedora 26, x86_64
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!