Summary: | Akregator sends Connection: keep-alive but gives error dialog when server replies Connection: close | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Dave Rutherford <dave> |
Component: | internal browser | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | thomas.lindroth |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Dave Rutherford
2007-08-09 17:29:12 UTC
When initially reported, this bug threw at most one application-modal error message at me per page, but shortly thereafter would often throw four. There may have been a change of content in the pages I'm viewing. Today this bug has escalated. Now I'm seeing app-modal error windows that can be moved around, repainted, anything except dismissed. They don't go away if clicked upon, the window decoration does nothing. I can't get around this error in any way, anymore. Please.. tell me where in the code this is coming from, so I can rip out its heart. I'm experiencing sort of the same problem. I don't use any redirection or local webserver. Instead I get this problem from regular feeds on the net. I'm using Akregator 1.6.6, Kde 4.6.3 and when I use the "load the full website when reading arcticle" option I get swamped by "Connection to host url.com is broken." dialogs when the website is loaded. The site most likely got broken links but I don't need a modal popup telling me about it for every broken link on the site. This feed demonstrate the problem: http://feedblog.ameba.jp/rss/ameblo/amimaeda-blog/rss20.xml 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. |