Control: tags -1 +patch
Hey,
thanks, for the backtrace. This helps to track this down.
I can reproduce this, but currently I can't test the patch for it. But this
only happens if akregator is started as single application. My normal way to
use akregator is via kontact and this way it does not crash.
I looks that we have to test the partenNode if this is a valid
pointer.Akregator::SubscriptionListModel::index
Akregator::SubscriptionListModel::index
add this add line 248:
if (!parentNode) {
return QModelIndex();
}
Regards,
sandro
Am Freitag, 2. September 2016, 00:30:05 CEST schrieb Ismael Bejarano:
> Hola Maximiliano!
>
> On Thu, Sep 1, 2016 at 6:20 AM, Maximiliano Curia <maxy@debian.org> wrote:
> > ¡Hola Ismael!
> >
> > El 2016-08-30 a las 01:13 -0300, Ismael escribió:
> >> Package: akregator Version: 4:16.04.3-1 Severity: grave Justification:
> causes non-serious data loss
>
> >> * What led up to the situation?
> >>
> >> Since a recent upgrade (less than a month ago). After reading a feed
>
> when closing Akregator it will crash without saving feeds state. The next
> time it will load like it didn't fetch any feed.
>
> >> * What exactly did you do (or not do) that was effective (or
>
> ineffective)?
>
> >> If I remaing in the welcome page I can synchronize without problems, and
>
> Akregator will close correctly.
>
> >> But If I read a post from a feed or load the list of post in a folder.
>
> It will crash when closing Akregator.
>
> >> * What was the outcome of this action?
> >>
> >> Run under gdb generates the following stack trace
> >>
> >>
> >> #0 0x00007fffd4079f48 in Akregator::SubscriptionListModel::index(int,
>
> int, QModelIndex const&) const () from
> /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so #1
> 0x00007ffff5dac951 in QTreeView::isRowHidden(int, QModelIndex const&)
> const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
>
> > Thanks for the report. I can't reproduce the issue here, and sadly the
>
> gdb output sent doesn't have enough debugging information. Could you please
> install akregator-dbgsym, and qtbase5-dbg and run it under gdb again?
>
> > The -dbgsym packages are in separated repositories, so you'll probably
>
> need to add:
> > deb http://debug.mirrors.debian.org/debian-debug unstable-debug main
> > to your sources.list. (For more information [1])
> >
> > Also, kde applications are heavily threaded so you'll need to ask gdb to
>
> produce a backtrace for each thread, this can be achieved with:
> > (gdb) thread apply all backtrace
> > (For more information [2])
> >
> > Happy hacking,
> > [1]: https://wiki.debian.org/AutomaticDebugPackages
>
> > [2]:
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_usef
> ul_crash_reports
> > --
> > "EIEIO Go home and have a glass of warm, dairy-fresh milk"
> > -- The GNU C Library Reference Manual, Chapter 2.2, Error Codes
> > Saludos /\/\ /\ >< `/
>
> Here is a backtrace with requested info in an attachment.
>
> Like Alexandre said it only happen when you read an article. In my case is
> not 100% but only one or two times it didn't crash.
>
> Also tried with a fresh account with only planet.debian.org and it still
> crashed in the same place.
>
> If you need more info just let me know.
>
> Regards
>
> Ismael
Attachment:
signature.asc
Description: This is a digitally signed message part.