Bug 275303 - Crash when closing Akregator.
Summary: Crash when closing Akregator.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.6.6
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-09 20:35 UTC by P. Varet
Modified: 2017-01-07 22:28 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (3.86 KB, text/plain)
2012-07-18 09:21 UTC, Andrei Slavoiu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description P. Varet 2011-06-09 20:35:27 UTC
Application: akregator (1.6.6)
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic x86_64
Distribution: Ubuntu 11.04

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

I had just 'opened a tab in an external browser' and then closed Akregator before the operation was fully done. Tab had opened in external browser but not yet closed in Akregator. Upon closing, Akregator crashed.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f5471c917a0 (LWP 27472))]

Thread 2 (Thread 0x7f5452071700 (LWP 27476)):
#0  0x00007f546e81ef03 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f5468ff7104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f5468ff7639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f546f3f3446 in QEventDispatcherGlib::processEvents (this=0xeb7140, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f546f3c7882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f546f3c7abc in QEventLoop::exec (this=0x7f5452070db0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007f546f2de924 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:492
#7  0x00007f546f3a9c2f in QInotifyFileSystemWatcherEngine::run (this=0xe87060) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f546f2e1175 in QThreadPrivate::start (arg=0xe87060) at thread/qthread_unix.cpp:320
#9  0x00007f54694c2d8c in start_thread (arg=0x7f5452071700) at pthread_create.c:304
#10 0x00007f546e82c04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f5471c917a0 (LWP 27472)):
[KCrash Handler]
#6  0x0000000000ec5288 in ?? ()
#7  0x00007f546f3ce289 in QMetaObject::cast (this=0x7f54583996e0, obj=0xd55ef0) at kernel/qmetaobject.cpp:266
#8  0x00007f54581117dc in qobject_cast<Akregator::BrowserFrame*> (this=0xbc13c0, config=...) at /usr/include/qt4/QtCore/qobject.h:366
#9  Akregator::FrameManager::saveProperties (this=0xbc13c0, config=...) at ../../../akregator/src/framemanager.cpp:352
#10 0x00007f545813ef34 in Akregator::MainWidget::saveProperties (this=0x384ad80, config=...) at ../../../akregator/src/mainwidget.cpp:1133
#11 0x000000000040af01 in Akregator::MainWindow::saveProperties (this=0x8d2420, config=...) at ../../../akregator/src/mainwindow.cpp:145
#12 0x0000000000409cc2 in Akregator::MainWindow::autoSaveProperties (this=0x8d2420) at ../../../akregator/src/mainwindow.cpp:254
#13 0x000000000040a068 in Akregator::MainWindow::queryClose (this=0x8d2420) at ../../../akregator/src/mainwindow.cpp:215
#14 0x00007f5470b6be88 in KMainWindow::closeEvent (this=0x8d2420, e=0x7fff535e5250) at ../../kdeui/widgets/kmainwindow.cpp:594
#15 0x00007f546fdd9066 in QWidget::event (this=0x8d2420, event=0x7fff535e5250) at kernel/qwidget.cpp:8417
#16 0x00007f54701a251b in QMainWindow::event (this=0x8d2420, event=0x7fff535e5250) at widgets/qmainwindow.cpp:1480
#17 0x00007f5470ba1d8e in KXmlGuiWindow::event (this=0x8d2420, ev=0x7fff535e5250) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:126
#18 0x00007f546fd879e4 in QApplicationPrivate::notify_helper (this=0x8eff80, receiver=0x8d2420, e=0x7fff535e5250) at kernel/qapplication.cpp:4462
#19 0x00007f546fd8c3aa in QApplication::notify (this=<value optimized out>, receiver=0x8d2420, e=0x7fff535e5250) at kernel/qapplication.cpp:4341
#20 0x00007f5470aa6866 in KApplication::notify (this=0x7fff535e5c60, receiver=0x8d2420, event=0x7fff535e5250) at ../../kdeui/kernel/kapplication.cpp:311
#21 0x00007f546f3c849c in QCoreApplication::notifyInternal (this=0x7fff535e5c60, receiver=0x8d2420, event=0x7fff535e5250) at kernel/qcoreapplication.cpp:731
#22 0x00007f546fdd3a05 in sendEvent (this=0x93c110, mode=QWidgetPrivate::CloseWithSpontaneousEvent) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#23 QWidgetPrivate::close_helper (this=0x93c110, mode=QWidgetPrivate::CloseWithSpontaneousEvent) at kernel/qwidget.cpp:7825
#24 0x00007f546fe08d06 in translateCloseEvent (this=<value optimized out>, w=0x8d2420, event=<value optimized out>, passive_only=<value optimized out>) at kernel/qapplication_x11.cpp:5652
#25 QApplication::x11ClientMessage (this=<value optimized out>, w=0x8d2420, event=<value optimized out>, passive_only=<value optimized out>) at kernel/qapplication_x11.cpp:3137
#26 0x00007f546fe07238 in QApplication::x11ProcessEvent (this=0x7fff535e5c60, event=0x7fff535e5910) at kernel/qapplication_x11.cpp:3817
#27 0x00007f546fe2f162 in x11EventSourceDispatch (s=0x8e4cd0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#28 0x00007f5468ff6bcd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007f5468ff73a8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007f5468ff7639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007f546f3f33ef in QEventDispatcherGlib::processEvents (this=0x888990, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#32 0x00007f546fe2edfe in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x00007f546f3c7882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#34 0x00007f546f3c7abc in QEventLoop::exec (this=0x7fff535e5c10, flags=...) at kernel/qeventloop.cpp:201
#35 0x00007f546f3cbecb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#36 0x0000000000408f24 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../akregator/src/main.cpp:103

Reported using DrKonqi
Comment 1 Andrei Slavoiu 2012-07-18 09:21:24 UTC
Created attachment 72603 [details]
New crash information added by DrKonqi

kontact (4.8.3) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.2

- What I was doing when the application crashed:
Closed Kontact

- Unusual behavior I noticed:
Akregator was showing some feeds contain unread articles but when opening the feed there was no unread article. On other feeds it was imposible to mark articles as read, they just remained with the unread status.

-- Backtrace (Reduced):
#8  0x00007f45ebbd0efe in qobject_cast<Akregator::BrowserFrame*> (object=<optimized out>) at /usr/include/qt4/QtCore/qobject.h:380
#9  Akregator::FrameManager::saveProperties (this=0x1d63760, config=...) at /var/tmp/portage/kde-base/akregator-4.8.3/work/akregator-4.8.3/akregator/src/framemanager.cpp:361
#10 0x00007f45ec07a0c7 in Akregator::MainWidget::saveProperties (this=0x47db4e0, config=...) at /var/tmp/portage/kde-base/akregator-4.8.3/work/akregator-4.8.3/akregator/src/mainwidget.cpp:1147
#11 0x00007f45ec0735ba in Akregator::Part::autoSaveProperties (this=0x47a7fd0) at /var/tmp/portage/kde-base/akregator-4.8.3/work/akregator-4.8.3/akregator/src/akregator_part.cpp:802
#12 0x00007f45ec073659 in Akregator::Part::slotOnShutdown (this=0x47a7fd0) at /var/tmp/portage/kde-base/akregator-4.8.3/work/akregator-4.8.3/akregator/src/akregator_part.cpp:300
Comment 2 Denis Kurz 2016-09-24 19:43:50 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:28:51 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.