Summary: | Akregator freezes on exit, no changes saved | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Benjamin M <alvanx> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | grave | ||
Priority: | NOR | ||
Version: | 4.13 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Benjamin M
2014-04-29 16:57:32 UTC
I forgot to mention 2 points: 1. Firstly, this bug started occurring in 4.12, so it's not version-related. Secondly, I believe it could have started around the time when I first attempted to exit out of the tab mentioned above, a few days ago, which could confirm this conclusion. 2. Related bugs could be: https://bugs.kde.org/show_bug.cgi?id=283988 (crash on close tab), or these two older reports on crashes on exit: https://bugs.kde.org/show_bug.cgi?id=301214 , https://bugs.kde.org/show_bug.cgi?id=193780 . Though note that I am describing a freeze, NOT a crash. An update: I am now experiencing a similar problem with another open tab. I can definitely say that pipelight is not the culprit as akregator still crashes when I disable the silverlight plugin. (The problem I had initially reported went away at one point when akregator simply loaded without the problematic tab open, for reasons I don't know.) Meanwhile, I have found a workaround for those with tabs that crash akregator. Go to .kde4/share/apps/akregator/ and delete or rename the file "crashed", which saves open tabs at the time of your crash. With the file gone, akregator will load without your troublesome tab. This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |