I noticed that akregator complains about ~/.local/share/akregator/data/feeds.opml not containing valid data. Looking at that file: It just cotains one byte 0x0a. Akregator is always removing that data when it is closed completely. (Next start it will complain about the opml file. When I restore it from backup it still warns about an unclean closure before.) I am pretty sure that this was not the case with gcc-6.3.0. But I currently only have 5.4.0 (as safe fallback), compiling just akregator with this version and the issue is gone.
Created attachment 491342 [details] emerge --info of working system Works fine here, same versions of gcc and akregator. Must be something else that breaks it. You should post the output of `emerge --info akregator gcc` on your system.
Not sure if this is GCC-6 related but it's reported upstream: https://bugs.kde.org/show_bug.cgi?id=381929
I updated to qt-5.9.1 quite some time ago, but i first encountered the problem with akregator 4 days ago. That was the time I upated to gcc-6.4 and rebuild world. The latter could have caused it as well...
Created attachment 491572 [details] emerge --info
It may not fix your problem, but please try akregator-17.08.1-r1 as soon as it hits your mirror (it has a crash/corruption fix from upstream).
Does this also affect 17.04.3 ?
(In reply to Markus from comment #3) > I updated to qt-5.9.1 quite some time ago, but i first encountered the > problem with akregator 4 days ago. That was the time I upated to gcc-6.4 and > rebuild world. The latter could have caused it as well... Upstream bug report specifically mentions it started to happen after Qt 5.8 to 5.9.1 upgrade, and that's the thing you have in common. Can you please report back if this happens with Qt 5.9.2 as well?
I upgraded from 5.7.1 to 5.9.2 and after a reboot the feeds list was gone. I restored from an incomplete backup. Surprisingly, after a second reboot all feeds were restored.
That sounds more like a configuration migration problem than one with gcc-6.
I have the same problem after updating qt to 5.9.2. I only have GCC 5.4 installed, so in my case it is not related to GCC. I think that recompiling akregator with 5.9.2 is the source of the problem. Recompiling again and now it does not start (probably related to update kde-frameworks to .39). I am waiting to finishing updating to try to recompile again.
OK, as explained in https://bugs.kde.org/show_bug.cgi?id=378513 dissabling the "title bar menu" in Systemsettings --> Application Style --> Widget Style --> Fine Tuning --> Set "Menubar Style" to "Title Bar Button" solve the issue for me. It is a pity, but I can live without it.
(In reply to cruzki from comment #11) > OK, as explained in > > https://bugs.kde.org/show_bug.cgi?id=378513 > > dissabling the "title bar menu" in Systemsettings --> Application Style --> > Widget Style --> Fine Tuning --> Set "Menubar Style" to "Title Bar Button" > solve the issue for me. It is a pity, but I can live without it. OK it seems to be two completely different bugs: one is the corruption of the feeds when they are saved by akregator at close and the other is the corruption of the menus when open akregator with corrupted feeds and the taskbar app-menu. Sorry for introducing noise in the bug.
I have not faced this bug for quite some time. (over three weeks) Actually not after the update of kde-apps/akonadi-17.08.1 to 17.08.1-r1 (and dev-libs/nspr-4.16 => 4.17 & dev-libs/nss-3.32.1 => 3.33). (Those updates were merged in the possible timeframe.) Only valid when the corruption really happened on every shutdown and was no race condition... (In the meantime I updated to 17.08.2 / 5.39.0 / 5.11.1.)
It just happend again. (Now at 17.08.2 / 5.39.0 / 5.11.3.)
17.11.80 is no different :( What is more - after trying some "workarounds" in linked bug I am now left without menu bar in KMail and Akregator and no shortcut nor any other trick I've tried brings them back :(
Qt-5.9.3 is now in tree, so the obvious thing to do is try and upgrade.
The same crashes with Qt 5.9.3 and 17.11.90(RC)
I can confirm that akregator starts with '...did not close correctly. Would you like to restore the session?'. But actual feed corruption I have not seen for a long time. Can anyone confirm *feed corruption* with kde-apps-17.12.1 and Qt-5.9.3?
Yes continuously. I think that in the past month only two or three times I have been able to open it without feed corruption.
Last time I saw the corrupted feeds.opml was mid december. Just before the update to 17.12. (But I already had periods of no corruption of up to 6 weeks before.) Upstream looks promising, though.
I still have that issue each time I (re)boot my notebook (akregator-17.12.1 with qt-5.9.3)
Both linked upstream bugs now contain a patch each I encourage you all to test.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5174fc8a806c010723c285d5915c15281626a9af commit 5174fc8a806c010723c285d5915c15281626a9af Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2018-02-11 22:14:17 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2018-02-11 22:14:53 +0000 kde-apps/akregator: Try to fix feedlist corruption and crashes Bug: https://bugs.gentoo.org/629548 Package-Manager: Portage-2.3.24, Repoman-2.3.6 kde-apps/akregator/akregator-17.12.2.ebuild | 5 +++++ .../akregator/files/akregator-17.12.2-crashfix.patch | 16 ++++++++++++++++ .../files/akregator-17.12.2-feedlist-corruption.patch | 17 +++++++++++++++++ 3 files changed, 38 insertions(+)}
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/kde.git/commit/?id=8122fa968fff3a1a9cbd47d589cef16226103b05 commit 8122fa968fff3a1a9cbd47d589cef16226103b05 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2018-02-15 15:22:13 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2018-02-15 15:31:58 +0000 kde-apps/akregator: Try to fix crashes w/ global menu Bug: https://bugs.gentoo.org/629548 Package-Manager: Portage-2.3.24, Repoman-2.3.6 kde-apps/akregator/akregator-17.12.49.9999.ebuild | 2 ++ kde-apps/akregator/akregator-9999.ebuild | 2 ++ .../akregator/files/akregator-17.12.2-crashfix.patch | 16 ++++++++++++++++ 3 files changed, 20 insertions(+)}
Stabilisation will happen in bug 642854.
This problem is not fixed. Qt-5.9 landed in stable yesterday but akregator is still at akregator-17.08.3. That ebuild doesn't have any patch for this problem. Instant loss of all feeds for everyone running stable.
