Bug 196716

Summary: reading feeds as html pages block kontact ui
Product: [Applications] akregator Reporter: freeman3
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: kde, osterfeld
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description freeman3 2009-06-16 09:07:14 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    SuSE RPMs

the ui is frozen when akgregator is loading new page after click on feed article title. the page should be loading in the background
Comment 1 Frank Osterfeld 2009-06-27 22:33:46 UTC
Website loading is indeed done in the background and always was - so I wonder how it comes that you experience such a freeze. Can you give an example link?
Comment 2 freeman3 2009-06-28 13:13:46 UTC
it happens every several links
i don't know why but fox example when i click on a link and click on a button to switch back to emails, it switches when the page finishes loading.
i'm on windows now, will try to check logs or something
Comment 3 Rolf Eike Beer 2009-09-19 18:01:20 UTC
http://www.deister-leine-zeitung.de/cms_media/xml/40_Deister-Leine-Zeitung-Wennigsen.xml

I see the freeze on nearly every link I open from there. While hanging a strace to the kontact process gives that over and over again:

--- SIGALRM (Alarm clock) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
poll([{fd=5, events=POLLIN}], 1, 25000) = ? ERESTART_RESTARTBLOCK (To be restarted)

File descriptor 5 is a socket. I'm not absolutely sure but I think it's a dbus one.

I just had the same freeze when opening the page as one tab of many in Konqueror but I can't reproduce it there reliable. This may either be something completely different or it might be related to KHTML.
Comment 4 Denis Kurz 2016-09-24 19:43:45 UTC
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.
Comment 5 Denis Kurz 2017-01-07 21:54:15 UTC
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.