*** Bug 338692 has been marked as a duplicate of this bug. ***

*** Bug 338309 has been marked as a duplicate of this bug. ***

Same here on openSUSE 13.1 with KDE:Current.

Same here with Akregator 4:4.14.0-1 on Debian testing.

Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007fc78d1149ad in isSignalConnected (signal_index=7, this=0x20) at kernel/qobject_p.h:237
#7  QMetaObject::activate (sender=0x20725a0, m=m@entry=0x7fc78f14f900 <Akregator::Frame::staticMetaObject>, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fff71594770) at kernel/qobject.cpp:3472
#8  0x00007fc78ef362a2 in Akregator::Frame::signalCompleted (this=<optimized out>, _t1=0x20725a0) at moc_frame.cpp:200
#9  0x00007fc78ef2ba8b in Akregator::Frame::slotSetState (this=<optimized out>, state=state@entry=Akregator::Frame::Completed) at ../../../akregator/src/frame.cpp:94
#10 0x00007fc7743f0407 in Akregator::MainWidget::slotFetchingStopped (this=0x2064060) at ../../../akregator/src/mainwidget.cpp:808
#11 0x00007fc78d114c5c in QMetaObject::activate (sender=sender@entry=0x1efef00, m=m@entry=0x7fc78f14f940 <Akregator::FetchQueue::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3567
#12 0x00007fc78ef35d23 in Akregator::FetchQueue::signalStopped (this=this@entry=0x1efef00) at moc_fetchqueue.cpp:126
#13 0x00007fc78ef2b6b9 in Akregator::FetchQueue::slotAbort (this=this@entry=0x1efef00) at ../../../akregator/src/fetchqueue.cpp:68
#14 0x00007fc78ef2b73a in Akregator::FetchQueue::~FetchQueue (this=0x1efef00, __in_chrg=<optimized out>) at ../../../akregator/src/fetchqueue.cpp:50
#15 0x00007fc78ef2b7a9 in Akregator::FetchQueue::~FetchQueue (this=0x1efef00, __in_chrg=<optimized out>) at ../../../akregator/src/fetchqueue.cpp:53
#16 0x00007fc78ef2a5d9 in Akregator::Kernel::~Kernel (this=0x7fc78f151718 <Akregator::Kernel::self()::self>, __in_chrg=<optimized out>) at ../../../akregator/src/kernel.cpp:66
#17 0x00007fc78c469b39 in __run_exit_handlers (status=0, listp=0x7fc78c7d45a8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#18 0x00007fc78c469b85 in __GI_exit (status=<optimized out>) at exit.c:104
#19 0x00007fc78c453b4c in __libc_start_main (main=0x407230 <main(int, char**)>, argc=5, argv=0x7fff71594ab8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff71594aa8) at libc-start.c:321
#20 0x00000000004079ed in _start ()

On Debian testing I have the same problem with the same version (4.14) but with a little different error output

It happens every time I close (to exit, not minimize)  akregator

Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
[KCrash Handler]
#6  deref (this=0x340028) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:132
#7  QString::operator= (this=0x83f292c, other=...) at tools/qstring.cpp:1411
#8  0xb7630a45 in Akregator::Frame::slotSetStatusText(QString const&) () from /usr/lib/libakregatorprivate.so.4
#9  0xb005ac85 in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib/kde4/akregatorpart.so
#10 0xb007b4d9 in ?? () from /usr/lib/kde4/akregatorpart.so
#11 0xb6116aa2 in QMetaObject::activate (sender=0x823b2a8, m=0xb7658cdc <Akregator::FetchQueue::staticMetaObject>, local_signal_index=1, argv=0x0) at kernel/qobject.cpp:3567
#12 0xb763c012 in Akregator::FetchQueue::signalStopped() () from /usr/lib/libakregatorprivate.so.4
#13 0xb763076d in Akregator::FetchQueue::slotAbort() () from /usr/lib/libakregatorprivate.so.4
#14 0xb76307f8 in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4
#15 0xb763088a in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4
#16 0xb762f578 in Akregator::Kernel::~Kernel() () from /usr/lib/libakregatorprivate.so.4
#17 0xb5c74081 in __run_exit_handlers (status=status@entry=0, listp=0xb5dea3c4 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#18 0xb5c740dd in __GI_exit (status=0) at exit.c:104
#19 0xb5c5ca6b in __libc_start_main (main=0x804d940, argc=1, argv=0xbfb7e484, init=0x80504f0 <__libc_csu_init>, fini=0x8050560 <__libc_csu_fini>, rtld_fini=0xb77dac90 <_dl_fini>, stack_end=0xbfb7e47c) at libc-start.c:321
#20 0x0804e050 in _start ()

Created attachment 88651 [details]
New crash information added by DrKonqi

akregator (4.14) on KDE Platform 4.14.0 using Qt 4.8.5

Some more detailed backtrace after recompiling with optimizations turned off.

-- Backtrace (Reduced):
#6  isSignalConnected (signal_index=7, this=0x20) at kernel/qobject_p.h:239
[...]
#8  0x00007f20cd90d847 in Akregator::Frame::signalCompleted (this=0x1ba9470, _t1=0x1ba9470) at /var/tmp/portage/kde-base/akregator-4.14.0/work/akregator-4.14.0_build/akregator/src/moc_frame.cpp:200
#9  0x00007f20cd8ffd01 in Akregator::Frame::slotSetState (this=0x1ba9470, state=Akregator::Frame::Completed) at /var/tmp/portage/kde-base/akregator-4.14.0/work/akregator-4.14.0/akregator/src/frame.cpp:94
#10 0x00007f20b7152bb8 in Akregator::MainWidget::slotFetchingStopped (this=0x1a27d00) at /var/tmp/portage/kde-base/akregator-4.14.0/work/akregator-4.14.0/akregator/src/mainwidget.cpp:808
#11 0x00007f20b716b29a in Akregator::MainWidget::qt_static_metacall (_o=0x1a27d00, _c=QMetaObject::InvokeMetaMethod, _id=49, _a=0x7fffbf5a01b0) at /var/tmp/portage/kde-base/akregator-4.14.0/work/akregator-4.14.0_build/akregator/src/moc_mainwidget.cpp:190

git bisect says:

8fc0d948f6e12102d38228857d686e65158534eb is the first bad commit
commit 8fc0d948f6e12102d38228857d686e65158534eb
Author: David Faure <faure@kde.org>
Date:   Sun Apr 27 01:29:32 2014 +0200

    Port away from deprecated queryExit
    
    Tested with and without a systray icon.

:040000 040000 e425c0d07d25ce39877f12b1b7ef39749df19597 755be4ea07abce593157f1acce6bfcd968feb0b3 M      akregator

Same behavior for me on Archlinux and akregator 4.14

Application: Akregator (akregator), signal: Segmentation fault
[Current thread is 1 (process 4572)]

Thread 1 (process 4572):
#0  0x00007f3a829139ed in ?? ()
#1  0x0000000000000000 in ?? ()

Adding David Faure to CC (Maybe you know an easy fix?)

Same here on Gentoo amd64 with Akregator from both KDE SC 4.14 and 4.14.1.

*** Bug 339220 has been marked as a duplicate of this bug. ***

in 4.14.1 akregator still crashing

Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
[KCrash Handler]
#6  0xb60ff9c3 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#7  0xb7626639 in Akregator::Frame::signalCompleted(Akregator::Frame*) () from /usr/lib/libakregatorprivate.so.4
#8  0xb761ab0d in Akregator::Frame::slotSetState(Akregator::Frame::State) () from /usr/lib/libakregatorprivate.so.4
#9  0xafff2c5c in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib/kde4/akregatorpart.so
#10 0xb0013459 in ?? () from /usr/lib/kde4/akregatorpart.so
#11 0xb60ffaa2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#12 0xb7625f62 in Akregator::FetchQueue::signalStopped() () from /usr/lib/libakregatorprivate.so.4
#13 0xb761a6bd in Akregator::FetchQueue::slotAbort() () from /usr/lib/libakregatorprivate.so.4
#14 0xb761a748 in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4
#15 0xb761a7da in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4
#16 0xb76194c8 in Akregator::Kernel::~Kernel() () from /usr/lib/libakregatorprivate.so.4
#17 0xb5c5d081 in __run_exit_handlers (status=status@entry=0, listp=0xb5dd33c4 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#18 0xb5c5d0dd in __GI_exit (status=0) at exit.c:104
#19 0xb5c45a6b in __libc_start_main (main=0x804d940, argc=1, argv=0xbf8403f4, init=0x80504f0 <__libc_csu_init>, fini=0x8050560 <__libc_csu_fini>, rtld_fini=0xb77c4c90 <_dl_fini>, stack_end=0xbf8403ec) at libc-start.c:321
#20 0x0804e050 in _start ()

David, any harm if we revert the mentioned commit?

Created attachment 88947 [details]
New crash information added by DrKonqi

akregator (4.14.1) on KDE Platform 4.14.1 using Qt 4.8.6

Crash on close and when leaving (log out) session.

-- Backtrace (Reduced):
#7  0x00007fe16b66a1e2 in Akregator::Frame::signalCompleted (this=<optimized out>, _t1=0x1d6fdf0) at /chakra/desktop-testing/kdepim/src/build/akregator/src/moc_frame.cpp:200
#8  0x00007fe16b65fa7b in Akregator::Frame::slotSetState (this=<optimized out>, state=state@entry=Akregator::Frame::Completed) at /chakra/desktop-testing/kdepim/src/kdepim-4.14.1/akregator/src/frame.cpp:94
#9  0x00007fe152835c47 in Akregator::MainWidget::slotFetchingStopped (this=0x1d6b280) at /chakra/desktop-testing/kdepim/src/kdepim-4.14.1/akregator/src/mainwidget.cpp:808
[...]
#11 0x00007fe16b669c63 in Akregator::FetchQueue::signalStopped (this=<optimized out>) at /chakra/desktop-testing/kdepim/src/build/akregator/src/moc_fetchqueue.cpp:126
#12 0x00007fe16b65f6a9 in Akregator::FetchQueue::slotAbort (this=this@entry=0x1cfd860) at /chakra/desktop-testing/kdepim/src/kdepim-4.14.1/akregator/src/fetchqueue.cpp:68

BTW:
Did someone else noticed how the crash reporter can freeze you KDE session on logout?
I get the crash report message (from Akregator) each time I want to shut down the PC and if I don't click within ~10seconds everything freezes and I can only hard-reset/power off my PC ... :-(.

I can confirm, autostart akregator at every login with this bug it's became a pain during every shutdown

You can add "--nocrashhandler" to the option of the desktop file, this way akregator will not show the crash handler on logout.

(In reply to Eugenio from comment #17)
> You can add "--nocrashhandler" to the option of the desktop file, this way
> akregator will not show the crash handler on logout.
Aha, good to know, thanks.

Still this behavior sounds like another bug to me...

*** Bug 340040 has been marked as a duplicate of this bug. ***

Reproduced (using Xephyr to test logging out and debug the issue).

Akregator::MainWidget::slotOnShutdown deletes m_mainFrame, and later on Akregator::MainWidget::slotFetchingStopped (triggered by the global object FetchQueue being deleted) uses m_mainFrame.

Easy to fix with m_mainFrame = 0 and a null check, but this sounds like the mainwidget isn't getting deleted anymore, so I'll check that.

Git commit c5b703e7c1a3f5da43a3864536cfa606d112d60a by David Faure.
Committed on 17/10/2014 at 19:19.
Pushed by dfaure into branch 'KDE/4.14'.

Fix crash on logout.

Turns out the check for kapp->sessionSaving inside queryExit was confusing,
it's actually false when aboutToQuit() leads to queryExit, even during logout.
So always delete the part in slotOnShutdown, called by aboutToQuit().
FIXED-IN: 4.14.3

M  +3    -0    akregator/src/mainwidget.cpp

http://commits.kde.org/kdepim/c5b703e7c1a3f5da43a3864536cfa606d112d60a

With special thanks to Martin Walch for the bisect!

Git commit b92a3688d91d76b7c0ffcb3775b232ed96062fc9 by David Faure.
Committed on 21/10/2014 at 07:22.
Pushed by dfaure into branch 'KDE/4.14'.

Delete the part from the mainwindow, not from the mainwidget.

This is a fix for "kontact crashes on quit" introduced by c5b703e7c
because I confused mainwindow and mainwidget. It restores a behavior
closer to before 8fc0d948f6e1, where the part was deleted by the mainwindow.

M  +0    -2    akregator/src/mainwidget.cpp
M  +7    -0    akregator/src/mainwindow.cpp
M  +1    -0    akregator/src/mainwindow.h

http://commits.kde.org/kdepim/b92a3688d91d76b7c0ffcb3775b232ed96062fc9

*** Bug 340586 has been marked as a duplicate of this bug. ***

*** Bug 340939 has been marked as a duplicate of this bug. ***

*** Bug 340967 has been marked as a duplicate of this bug. ***

*** Bug 341101 has been marked as a duplicate of this bug. ***

Created attachment 90614 [details]
New crash information added by DrKonqi

akregator (4.14.2) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed:
closin' it.
nothing more else than closing it.
Really, just closing it! (asks for more words, or I can't send the bug report :-))

-- Backtrace (Reduced):
#6  0x00007f139be89782 in Akregator::Frame::signalCompleted(Akregator::Frame*) () from /usr/lib/libakregatorprivate.so.4
#7  0x00007f139be805b8 in Akregator::Frame::slotSetState(Akregator::Frame::State) () from /usr/lib/libakregatorprivate.so.4
#8  0x00007f138133d1f7 in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib/kde4/akregatorpart.so
[...]
#10 0x00007f139be80039 in Akregator::FetchQueue::slotAbort() () from /usr/lib/libakregatorprivate.so.4
#11 0x00007f139be800aa in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4

@diego
Please see the bug description. This was fixed in Version 4.14.3 (and the fix works).

So please update your software or ask you sysadmin to do so.

(In reply to richardlm from comment #29)
> @diego
> Please see the bug description. This was fixed in Version 4.14.3 (and the
> fix works).
> 
> So please update your software or ask you sysadmin to do so.

I can see the fix is back from January. Any idea when this will hit the Kubuntu PPA or Kubuntu Backports?

Besides that: Does Akregator have a maintainer at all? I've been very happy with it for many years, but now it has just stalled, and the bugs keep piling up.

My C++/Qt "skills" are pre-millenium change, so I'm afraid I can't take the torch myself :P

No, Akregator is available for adoption. If you cannot maintain it yourself, we have to wait until we find someone who has the time and expertize to do it.

Regarding packages for 4.14.3, please ask on the forums of your distribution.

*** Bug 353094 has been marked as a duplicate of this bug. ***

This problem is, apparently, NOT FIXED, since it happens here every time I close Akregator. Here is the "two-star" backtrace I am getting in the hope it helps:

Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f26cd049471 in isSignalConnected (signal_index=7, this=0x9) at kernel/qobject_p.h:237
#7  QMetaObject::activate (sender=0x2c21360, m=m@entry=0x7f26cf088900 <Akregator::Frame::staticMetaObject>, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7ffff39a5c90) at kernel/qobject.cpp:3472
#8  0x00007f26cee6ef62 in Akregator::Frame::signalCompleted (this=<optimized out>, _t1=0x2c21360) at moc_frame.cpp:200
#9  0x00007f26cee6481b in Akregator::Frame::slotSetState (this=<optimized out>, state=state@entry=Akregator::Frame::Completed) at ../../../akregator/src/frame.cpp:94
#10 0x00007f26b44353c7 in Akregator::MainWidget::slotFetchingStopped (this=0x7e5090) at ../../../akregator/src/mainwidget.cpp:808
#11 0x00007f26cd04971c in QMetaObject::activate (sender=sender@entry=0x882690, m=m@entry=0x7f26cf088940 <Akregator::FetchQueue::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3567
#12 0x00007f26cee6e9e3 in Akregator::FetchQueue::signalStopped (this=this@entry=0x882690) at moc_fetchqueue.cpp:126
#13 0x00007f26cee64449 in Akregator::FetchQueue::slotAbort (this=this@entry=0x882690) at ../../../akregator/src/fetchqueue.cpp:68
#14 0x00007f26cee644ca in Akregator::FetchQueue::~FetchQueue (this=0x882690, __in_chrg=<optimized out>) at ../../../akregator/src/fetchqueue.cpp:50
#15 0x00007f26cee64539 in Akregator::FetchQueue::~FetchQueue (this=0x882690, __in_chrg=<optimized out>) at ../../../akregator/src/fetchqueue.cpp:53
#16 0x00007f26cee63389 in Akregator::Kernel::~Kernel (this=0x7f26cf08a718 <Akregator::Kernel::self()::self>, __in_chrg=<optimized out>) at ../../../akregator/src/kernel.cpp:66
#17 0x00007f26cc39cb29 in __run_exit_handlers (status=0, listp=0x7f26cc70a5a8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#18 0x00007f26cc39cb75 in __GI_exit (status=<optimized out>) at exit.c:104
#19 0x00007f26cc386b4c in __libc_start_main (main=0x407240 <main(int, char**)>, argc=5, argv=0x7ffff39a5fd8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffff39a5fc8) at libc-start.c:321
#20 0x00000000004079fd in _start ()

This problem is, apparently, NOT FIXED, since it happens here every time I close Akregator. Here is the "two-star" backtrace I am getting in the hope it helps:

Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f26cd049471 in isSignalConnected (signal_index=7, this=0x9) at kernel/qobject_p.h:237
#7  QMetaObject::activate (sender=0x2c21360, m=m@entry=0x7f26cf088900 <Akregator::Frame::staticMetaObject>, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7ffff39a5c90) at kernel/qobject.cpp:3472
#8  0x00007f26cee6ef62 in Akregator::Frame::signalCompleted (this=<optimized out>, _t1=0x2c21360) at moc_frame.cpp:200
#9  0x00007f26cee6481b in Akregator::Frame::slotSetState (this=<optimized out>, state=state@entry=Akregator::Frame::Completed) at ../../../akregator/src/frame.cpp:94
#10 0x00007f26b44353c7 in Akregator::MainWidget::slotFetchingStopped (this=0x7e5090) at ../../../akregator/src/mainwidget.cpp:808
#11 0x00007f26cd04971c in QMetaObject::activate (sender=sender@entry=0x882690, m=m@entry=0x7f26cf088940 <Akregator::FetchQueue::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3567
#12 0x00007f26cee6e9e3 in Akregator::FetchQueue::signalStopped (this=this@entry=0x882690) at moc_fetchqueue.cpp:126
#13 0x00007f26cee64449 in Akregator::FetchQueue::slotAbort (this=this@entry=0x882690) at ../../../akregator/src/fetchqueue.cpp:68
#14 0x00007f26cee644ca in Akregator::FetchQueue::~FetchQueue (this=0x882690, __in_chrg=<optimized out>) at ../../../akregator/src/fetchqueue.cpp:50
#15 0x00007f26cee64539 in Akregator::FetchQueue::~FetchQueue (this=0x882690, __in_chrg=<optimized out>) at ../../../akregator/src/fetchqueue.cpp:53
#16 0x00007f26cee63389 in Akregator::Kernel::~Kernel (this=0x7f26cf08a718 <Akregator::Kernel::self()::self>, __in_chrg=<optimized out>) at ../../../akregator/src/kernel.cpp:66
#17 0x00007f26cc39cb29 in __run_exit_handlers (status=0, listp=0x7f26cc70a5a8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#18 0x00007f26cc39cb75 in __GI_exit (status=<optimized out>) at exit.c:104
#19 0x00007f26cc386b4c in __libc_start_main (main=0x407240 <main(int, char**)>, argc=5, argv=0x7ffff39a5fd8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffff39a5fc8) at libc-start.c:321
#20 0x00000000004079fd in _start ()

(In reply to Alexis Kauffmann from comment #34)
> This problem is, apparently, NOT FIXED, since it happens here every time I
> close Akregator. Here is the "two-star" backtrace I am getting in the hope
> it helps:

Alexis, the bug here was definitely resolved in kdepim version 4.14.3. Which version of kdepim do you use?

Created attachment 98340 [details]
New crash information added by DrKonqi

akregator (4.14.1) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed: 
I simply closed the application. No problem when the application was open and running

-- Backtrace (Reduced):
#7  0x00007fb63503ff62 in Akregator::Frame::signalCompleted(Akregator::Frame*) () from /usr/lib/libakregatorprivate.so.4
#8  0x00007fb63503581b in Akregator::Frame::slotSetState(Akregator::Frame::State) () from /usr/lib/libakregatorprivate.so.4
#9  0x00007fb61a38f3c7 in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib/kde4/akregatorpart.so
[...]
#11 0x00007fb635035449 in Akregator::FetchQueue::slotAbort() () from /usr/lib/libakregatorprivate.so.4
#12 0x00007fb6350354ca in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4