¡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_useful_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 /\/\ /\ >< `/
Attachment:
signature.asc
Description: PGP signature