[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"

[K G]

https://bugs.kde.org/show_bug.cgi?id=383710

--- Comment #9 from K G <govik at wp.pl> ---
I'm not sure if it's relevant for this bug but it is for sure relevant to bug
384975 marked as duplicate. 

The problem is that akregator kpart is initialized twice, recursively. (See
attached trace #45 and #5) 

Akregator::MainWindow::loadPart() is called twice. Because of that in
ActionManagerImpl we have corrupted reference to d->actionCollection that
causes dump on calling setArticleActionsEnabled. 

The reason of recursive initialization seams to be method
Akregator::MainWindow::saveProperties() that is called by QtWebEngine before
kpart if fully initialized. The simplest solution would be  to remove
initialization of kpart from this method and returning if kpart it's not
initialized. Or skipping initialization only in such case if possible.

-- 
You are receiving this mail because:
You are the assignee for the bug.