akregator crashed with SIGSEGV in KActionCollection::action()

[Laurent Bonnaud]

I was selecting a feed just after startup.
This was after a system restart following a Plasma crash.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: akregator 4:17.04.3-0ubuntu1
Uname: Linux 4.13.4-041304-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Oct 3 10:38:01 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/akregator
ProcCmdline: akregator -session 10dbdee967000150669343700000218090010_1506694678_940536
Signal: 11
SourcePackage: akregator
StacktraceTop:
 KActionCollection::action(QString const&) const () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
 Akregator::ActionManagerImpl::setArticleActionsEnabled (this=0x561fed7fc830, enabled=<optimized out>) at ./src/actions/actionmanagerimpl.cpp:646
 Akregator::ArticleViewerWidget::slotShowSummary (this=0x561fed84d480, node=node@entry=0x561fed9c1950) at ./src/articleviewerwidget.cpp:194
 Akregator::MainWidget::slotNodeSelected (this=0x561fed7eef50, node=0x561fed9c1950) at ./src/mainwidget.cpp:694
 QtPrivate::QSlotObjectBase::call (a=0x7ffdad63a200, r=0x561fed7eef50, this=0x561fed84a9e0) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101
Title: akregator crashed with SIGSEGV in KActionCollection::action()
UpgradeStatus: Upgraded to artful on 2017-09-29 (3 days ago)
UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare staff sudo

[Laurent Bonnaud (laurent-bonnaud)]

Link to upstream bug (I could not add it to launchpad):

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

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed, since the report is ill-formed. Perhaps the report data got
modified?

  size does not fit in an int

If you encounter the crash again, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Laurent Bonnaud (laurent-bonnaud)]

The "size does not fit in an int" error message is an apport problem and the stack trace I uploaded is perfectly correct.

[Laurent Bonnaud (laurent-bonnaud)]

Confirmed because the upstream tracker has several duplicates of this bug.