Bug 318038

Summary:	crash when Akregator (embedded in Ark) is closed from systray (Kubuntu 12.10)
Product:	[Applications] akregator	Reporter:	Keren Sky <keren_sky>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	kde-bugs.9ek5t
Priority:	NOR
Version:	4.10.5
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Keren Sky 2013-04-08 14:17:34 UTC

Application: ark (2.19)
KDE Platform Version: 4.10.2
Qt Version: 4.8.3
Operating System: Linux 3.5.0-27-generic x86_64
Distribution: Ubuntu 12.10

-- Information about the crash:
- What I was doing when the application crashed: I opened an .xpi file using Ark. I clicked on the install.rdf file. It opened/previewed w/in Ark using Akregator.  I subsequently minimized the Ark window for approximately an hour, then leftclicked the Akregator icon in the systray (lefted-handed mouse).  I clicked quit. Next a crash handler window came up, indicating Ark had crashed. 

- Custom settings of the application:

-- Backtrace:
Application: Ark (ark), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd1308e5780 (LWP 11114))]

Thread 3 (Thread 0x7fd125a01700 (LWP 11119)):
#0  0x00007fd1381c2313 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007fd13493bd84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fd13493bea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fd138942c16 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007fd1389132bf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x00007fd138913548 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007fd138814b10 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007fd1388f39af in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007fd138817aec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007fd134e0be9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007fd1381cdccd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fd11f770700 (LWP 14139)):
#0  0x00007fd134978e38 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fd13493b623 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fd13493bcab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fd13493bea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fd138942c16 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x00007fd1389132bf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007fd138913548 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007fd138814b10 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007fd1388f39af in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007fd138817aec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007fd134e0be9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#11 0x00007fd1381cdccd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fd1308e5780 (LWP 11114)):
[KCrash Handler]
#5  0x00007fd138929d09 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007fd11e87f642 in Akregator::Frame::signalCompleted(Akregator::Frame*) () from /usr/lib/libakregatorprivate.so.4
#7  0x00007fd11e87f66a in Akregator::Frame::slotSetState(Akregator::Frame::State) () from /usr/lib/libakregatorprivate.so.4
#8  0x00007fd11ed26336 in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib/kde4/akregatorpart.so
#9  0x00007fd138929f5f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007fd11e87eb89 in Akregator::FetchQueue::slotAbort() () from /usr/lib/libakregatorprivate.so.4
#11 0x00007fd11e87ed09 in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4
#12 0x00007fd11e87ed79 in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4
#13 0x00007fd11e87d44d in Akregator::Kernel::~Kernel() () from /usr/lib/libakregatorprivate.so.4
#14 0x00007fd138115901 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#15 0x00007fd138115985 in exit () from /lib/x86_64-linux-gnu/libc.so.6
#16 0x00007fd1380fb774 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#17 0x000000000040ab59 in _start ()

Reported using DrKonqi

Comment 1 G360 2013-07-17 00:27:34 UTC

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

ark (2.19) on KDE Platform 4.10.5 using Qt 4.8.5

- What I was doing when the application crashed:
Same as the original bug reporter. Preview a rdf file from within Ark, Akregator opens, then after closing it, Ark crashes.

- Custom settings of the application:
The file association for rdf files, under the Embedding tag, aKregatorPart (kregator_part) was selected as default. A better option should be katepart, although Ark should not crash when using some odd embedded application.

-- Backtrace (Reduced):
#7  0xb015fa85 in Akregator::Frame::signalCompleted(Akregator::Frame*) () from /usr/lib/libakregatorprivate.so.4
#8  0xb015fb0c in Akregator::Frame::slotSetState(Akregator::Frame::State) () from /usr/lib/libakregatorprivate.so.4
#9  0xafe1c3f8 in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib/kde4/akregatorpart.so
[...]
#12 0xb015e9b5 in Akregator::FetchQueue::signalStopped() () from /usr/lib/libakregatorprivate.so.4
#13 0xb015eeba in Akregator::FetchQueue::slotAbort() () from /usr/lib/libakregatorprivate.so.4

Comment 2 Denis Kurz 2016-09-24 19:45:32 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 3 Denis Kurz 2017-01-07 22:29:27 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.