Bug 355227 - Akregator hangs when it charges a feed
Summary: Akregator hangs when it charges a feed
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Chakra Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-11-12 09:02 UTC by dmythos76
Modified: 2018-02-01 09:48 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dmythos76 2015-11-12 09:02:34 UTC
Application: akregator (5.0.2)

Qt Version: 5.5.1
Operating System: Linux 4.1.4-1-CHAKRA x86_64
Distribution: "Chakra"

-- Information about the crash:
- What I was doing when the application crashed: I was trying to read a news when, suddenly, the program crashed. I try to run again Akregator, and then, it asks me if I want to restore the session or not. I tried both options, but in the two, the program crashes soon after.

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdb89edb840 (LWP 1658))]

Thread 2 (Thread 0x7fdb696e0700 (LWP 1659)):
#0  0x00007fdb865b918d in poll () at /usr/lib/libc.so.6
#1  0x00007fdb7ce0b9f2 in  () at /usr/lib/libxcb.so.1
#2  0x00007fdb7ce0d56f in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x00007fdb6a7f2329 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x00007fdb86ec6b7e in  () at /usr/lib/libQt5Core.so.5
#5  0x00007fdb7f2f0464 in start_thread () at /usr/lib/libpthread.so.0
#6  0x00007fdb865c212d in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7fdb89edb840 (LWP 1658)):
[KCrash Handler]
#6  0x00007fdb6818a007 in  () at /usr/lib/qt5/plugins/akregatorpart.so
#7  0x00007fdb681c929f in Akregator::MainWidget::saveProperties(KConfigGroup&) () at /usr/lib/qt5/plugins/akregatorpart.so
#8  0x00007fdb681c2f44 in  () at /usr/lib/qt5/plugins/akregatorpart.so
#9  0x00007fdb681c2fd9 in  () at /usr/lib/qt5/plugins/akregatorpart.so
#10 0x00007fdb681c3638 in  () at /usr/lib/qt5/plugins/akregatorpart.so
#11 0x00007fdb681c3689 in  () at /usr/lib/qt5/plugins/akregatorpart.so
#12 0x00007fdb870d636a in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5
#13 0x00007fdb870d6c0f in QObject::destroyed(QObject*) () at /usr/lib/libQt5Core.so.5
#14 0x00007fdb8810109d in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5
#15 0x00007fdb681cca39 in Akregator::MainWidget::~MainWidget() () at /usr/lib/qt5/plugins/akregatorpart.so
#16 0x00007fdb870d7250 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#17 0x00007fdb8810570b in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5
#18 0x00007fdb880c298c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#19 0x00007fdb880c7e66 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#20 0x00007fdb870a7beb in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#21 0x00007fdb870a9fe6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#22 0x00007fdb870fe183 in  () at /usr/lib/libQt5Core.so.5
#23 0x00007fdb7d64aa1d in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#24 0x00007fdb7d64ad08 in  () at /usr/lib/libglib-2.0.so.0
#25 0x00007fdb7d64adbc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#26 0x00007fdb870fe58f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#27 0x00007fdb870a55ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#28 0x00007fdb870ad57c in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#29 0x0000000000409900 in main ()

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 20:22:01 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:48:42 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.