Bug 198029 - Akregator crash when moving feed from one folder to another
Summary: Akregator crash when moving feed from one folder to another
Status: RESOLVED DUPLICATE of bug 200354
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-27 05:48 UTC by Sunil Khiatani
Modified: 2009-07-16 00:06 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 Sunil Khiatani 2009-06-27 05:48:22 UTC
Application that crashed: kontact
Version of the application: 4.3.0 pre
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2))
Qt Version: 4.5.0
Operating System: Linux 2.6.28-13-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
Imported feed from konqueror (Gizmodo)
imported feed from konqueror (Sony Ericsson unofficial blog)
switched to kontact
moved feed 'Gizmodo' from 'Imported Feeds' folder to 'Gadgets' folder
moved feed 'Sony Ericsson unofficial blog' from 'Imported Feeds' folder to 'Gadgets' folder
kontact crashes

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 0 (LWP 4315)]

Thread 3 (Thread 0xabaf6b90 (LWP 18636)):
#0  0xb7ff3430 in __kernel_vsyscall ()
#1  0xb511c412 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb5942344 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb5b2d98c in QWaitCondition::wait (this=0xa1fbb50, mutex=0xa1fbb4c, time=30000) at thread/qwaitcondition_unix.cpp:85
#4  0xb5b22e76 in QThreadPoolThread::run (this=0xa47e998) at concurrent/qthreadpool.cpp:140
#5  0xb5b2c96e in QThreadPrivate::start (arg=0xa47e998) at thread/qthread_unix.cpp:189
#6  0xb51184ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb593349e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xacb66b90 (LWP 18657)):
#0  0xb7ff3430 in __kernel_vsyscall ()
#1  0xb511c412 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb5942344 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb5b2d98c in QWaitCondition::wait (this=0xa1fbb50, mutex=0xa1fbb4c, time=30000) at thread/qwaitcondition_unix.cpp:85
#4  0xb5b22e76 in QThreadPoolThread::run (this=0xbf20930) at concurrent/qthreadpool.cpp:140
#5  0xb5b2c96e in QThreadPrivate::start (arg=0xbf20930) at thread/qthread_unix.cpp:189
#6  0xb51184ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb593349e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4830b30 (LWP 4315)):
[KCrash Handler]
#6  0xa930ee18 in Akregator::Article::link () from /usr/lib/kde4/akregatorpart.so
#7  0xa936487e in ?? () from /usr/lib/kde4/akregatorpart.so
#8  0xa9364c8e in ?? () from /usr/lib/kde4/akregatorpart.so
#9  0xb5c36ca8 in QMetaObject::activate (sender=0xb08b570, from_signal_index=4, to_signal_index=4, argv=0xbfa0e8dc) at kernel/qobject.cpp:3069
#10 0xb5c37932 in QMetaObject::activate (sender=0xb08b570, m=0xb5fb7da8, local_signal_index=0, argv=0xbfa0e8dc) at kernel/qobject.cpp:3143
#11 0xb5e5d833 in KJob::finished (this=0xb08b570, _t1=0xb08b570) at /build/buildd/kde4libs-4.2.90/obj-i486-linux-gnu/kdecore/kjob.moc:167
#12 0xb5e5db1d in KJob::emitResult (this=0xb08b570) at /build/buildd/kde4libs-4.2.90/kdecore/jobs/kjob.cpp:302
#13 0xa9313a0a in ?? () from /usr/lib/kde4/akregatorpart.so
#14 0xa9313b45 in ?? () from /usr/lib/kde4/akregatorpart.so
#15 0xb5c36ca8 in QMetaObject::activate (sender=0xaf87900, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#16 0xb5c37932 in QMetaObject::activate (sender=0xaf87900, m=0xb5d12908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143
#17 0xb5c3c0a7 in QSingleShotTimer::timeout (this=0xaf87900) at .moc/release-shared/qtimer.moc:76
#18 0xb5c3c1cc in QSingleShotTimer::timerEvent (this=0xaf87900) at kernel/qtimer.cpp:298
#19 0xb5c3115f in QObject::event (this=0xaf87900, e=0xbfa0ee6c) at kernel/qobject.cpp:1082
#20 0xb6100e9c in QApplicationPrivate::notify_helper (this=0x918c738, receiver=0xaf87900, e=0xbfa0ee6c) at kernel/qapplication.cpp:4084
#21 0xb610919e in QApplication::notify (this=0xbfa0f118, receiver=0xaf87900, e=0xbfa0ee6c) at kernel/qapplication.cpp:3631
#22 0xb6d26e8d in KApplication::notify (this=0xbfa0f118, receiver=0xaf87900, event=0xbfa0ee6c) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kapplication.cpp:302
#23 0xb5c20a3b in QCoreApplication::notifyInternal (this=0xbfa0f118, receiver=0xaf87900, event=0xbfa0ee6c) at kernel/qcoreapplication.cpp:602
#24 0xb5c4fd71 in QTimerInfoList::activateTimers (this=0x918f474) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#25 0xb5c4c4e0 in timerSourceDispatch (source=0x918f440) at kernel/qeventdispatcher_glib.cpp:164
#26 0xb4ce6b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb4cea0eb in ?? () from /usr/lib/libglib-2.0.so.0
#28 0xb4cea268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0xb5c4c438 in QEventDispatcherGlib::processEvents (this=0x91a0538, flags={i = -1079971864}) at kernel/qeventdispatcher_glib.cpp:323
#30 0xb61a2365 in QGuiEventDispatcherGlib::processEvents (this=0x91a0538, flags={i = -1079971816}) at kernel/qguieventdispatcher_glib.cpp:202
#31 0xb5c1f06a in QEventLoop::processEvents (this=0xbfa0f090, flags={i = -1079971752}) at kernel/qeventloop.cpp:149
#32 0xb5c1f4aa in QEventLoop::exec (this=0xbfa0f090, flags={i = -1079971688}) at kernel/qeventloop.cpp:200
#33 0xb5c21959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#34 0xb6100d17 in QApplication::exec () at kernel/qapplication.cpp:3553
#35 0x0804bfef in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-06-27 18:12:10 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You need to install the "kdepim-dbg" package.
Thanks
Comment 2 Christophe Marin 2009-07-04 13:11:56 UTC
Changing the bug status until we get a backtrace (see comment #1)
Comment 3 Dario Andres 2009-07-15 22:50:13 UTC
Probably related to bug 200354
Comment 4 Christophe Marin 2009-07-16 00:06:50 UTC

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