Bug 340040 - Akregator Crashes on exit
Summary: Akregator Crashes on exit
Status: RESOLVED DUPLICATE of bug 336417
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mint (Ubuntu based) Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-10-17 05:18 UTC by Bhaskar Divya
Modified: 2014-10-17 12:49 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 Bhaskar Divya 2014-10-17 05:18:03 UTC
Application: akregator (4.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic x86_64
Distribution: Linux Mint 17 Qiana

-- Information about the crash:
- What I was doing when the application crashed:

Closed the Akregator app. Just after closing it, it says Segfaults.

The crash can be reproduced every time.

-- Backtrace:
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 0x7faabe8c4800 (LWP 10371))]

Thread 2 (Thread 0x7faa997f8700 (LWP 10379)):
#0  0x00007faab5faa62a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007faab5faa989 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007faab5f68699 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007faab5f68f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007faab5f690ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007faabcd197be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007faabcceb0af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007faabcceb3a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007faabcbe7c5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007faabcccc823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007faabcbea32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007faab6639182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#12 0x00007faabb45bfbd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7faabe8c4800 (LWP 10371)):
[KCrash Handler]
#5  0x00007faabcd00607 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007faabddb0782 in Akregator::Frame::signalCompleted(Akregator::Frame*) () from /usr/lib/libakregatorprivate.so.4
#7  0x00007faabdda75b8 in Akregator::Frame::slotSetState(Akregator::Frame::State) () from /usr/lib/libakregatorprivate.so.4
#8  0x00007faaa32661f7 in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib/kde4/akregatorpart.so
#9  0x00007faabcd0087a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007faabdda7039 in Akregator::FetchQueue::slotAbort() () from /usr/lib/libakregatorprivate.so.4
#11 0x00007faabdda70aa in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4
#12 0x00007faabdda7119 in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4
#13 0x00007faabdda60d9 in Akregator::Kernel::~Kernel() () from /usr/lib/libakregatorprivate.so.4
#14 0x00007faabb39d149 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#15 0x00007faabb39d195 in exit () from /lib/x86_64-linux-gnu/libc.so.6
#16 0x00007faabb382ecc in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#17 0x0000000000407edb in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 336417.

Possible duplicates by query: bug 338692, bug 338309, bug 336417.

Reported using DrKonqi
Comment 1 Christoph Feck 2014-10-17 12:49:42 UTC

*** This bug has been marked as a duplicate of bug 336417 ***