Bug 347011 - Akregator crashes several times at start before working correct.
Summary: Akregator crashes several times at start before working correct.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-01 14:36 UTC by Anton Steiner
Modified: 2018-02-01 09:47 UTC (History)
1 user (show)

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 Anton Steiner 2015-05-01 14:36:13 UTC
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f55330027c0 (LWP 10541))]

Thread 3 (Thread 0x7f550bd40700 (LWP 10552)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f55146d806f in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f55146d80a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f552aa830a4 in start_thread (arg=0x7f550bd40700) at pthread_create.c:309
#4  0x00007f552fad004d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f5509f0e700 (LWP 10589)):
#0  0x00007f552fac750d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f552a59bee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f552a59bffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f55306e6d37 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007f55306b6271 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x00007f55306b65d5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007f55305aae99 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007f55305ad70f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007f552aa830a4 in start_thread (arg=0x7f5509f0e700) at pthread_create.c:309
#9  0x00007f552fad004d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f55330027c0 (LWP 10541)):
[KCrash Handler]
#6  0x00007f553112694f in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x00007f5531126a9f in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#8  0x00007f5531128ada in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9  0x00007f55311269ee in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x00007f5531126a9f in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x00007f5531128ada in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00000000004081af in _start ()

Reproducible: Always

Steps to Reproduce:
1. Start akregator (again, again)
2.
3.

Actual Results:  
Akregator crashes serveral times (about 2-6 times) before starting correct. 

Expected Results:  
Start without crashes :-)

Akregator Version: 4.14.2
OS: Linux (x86_64) release 3.16.0-4-amd64
Comment 1 Denis Kurz 2017-06-23 20:03:07 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.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 oportunity 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:47:43 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.