I use Nvidia graphics card with proprietary drivers (from RPMFusion).
Earlier with Fedora 26, when deleting multiple articles on Akregator, I often (but not always) used to get the message "desktop effects were restarted due to a graphics reset" from plasma. But plasma used to come back up and apart from the irritation, it wasn't doing major harm.
Now with Fedora 27, I have the similar problem, but then plasma does not come beck up. It just hangs. I can switch to another VT and if I switch back, I see the mouse pointer on a black background. I can move the pointer around and it changes (to pointy-hand, cursor etc) based on where I keep it, indicating that underneath the black background, the applications are still active.
So far, the only recovery I've been able to find is doing "init 3" followed by "init 5" to get back the login screen.
I can reproduce this at will by simply deleting a few articles on Akregator.
I made an observation regarding the problem. I have almost 40 feeds. But the problem is only with Slashdot feed. Deleting an article from Slashdot is slow. If I select 10 articles from Slashdot feed and press delete, it takes couple of seconds for deletion. And once I delete one or more articles from Slashdot feed, then deleting articles of other feeds also start having the same delay problem. Restarting Akregator is the only way to solve this.
In my experience, this 'lag' in deleting articles is related to the graphics reset issue. As long as I don't delete any articles from Slashdot, Akregator is very well behaved.
I can reproduce the problem at will:
1. View any article from Slashdot feed.
2. View any article that has a video embedded (Youtube video, for example). The video does not play in the Akrgeator view area though.
After step 1 or step 2, all subsequent delete operations (of articles from any feed) become very slow and cause graphics reset if too many articles are deleted together
I could not reproduce this with Akregator 5.15.0 on AMD graphics (mesa). Syam, do you still get this bug?
No. I can no longer reproduce this. I still have NVidia proprietary drivers but I no longer have this issue.
Thanks for the update; changing status.