Bug 200660 - Akregator crash with new feed
Summary: Akregator crash with new feed
Status: RESOLVED DUPLICATE of bug 194591
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-18 15:50 UTC by Francesco Betti Sorbelli
Modified: 2009-07-18 17: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 Francesco Betti Sorbelli 2009-07-18 15:50:09 UTC
Version:           1.4.50 (using KDE 4.2.96)
OS:                Linux
Installed from:    Debian testing/unstable Packages

This crash occurred from kde 4.2 to 4.2.96. If I add a new feed (suppose kernel.org), when fetching info for the first time and I select a whatever news, Akregator crash if I select the tree root in a feed list.

This problem found also in a normal situation.

See please my video :)
Comment 1 Christophe Marin 2009-07-18 15:57:14 UTC
(In reply to comment #0)

> This problem found also in a normal situation.
> 
> See please my video :)

What we need is a backtrace. Please read : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

You need to install the debug package for kdepim first.
Comment 2 Francesco Betti Sorbelli 2009-07-18 16:02:15 UTC
http://www.youtube.com/watch?v=jCimq3-b_k8(In reply to comment #1)
> (In reply to comment #0)
> 
> > This problem found also in a normal situation.
> > 
> > See please my video :)
Here the video:
http://www.youtube.com/watch?v=jCimq3-b_k8

> 
> What we need is a backtrace. Please read :
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
> 
> You need to install the debug package for kdepim first.
I need a one or two hours for download this package (anche dependences) :(
Comment 3 Dario Andres 2009-07-18 16:49:14 UTC
@Francesco: install the "kdepim-dbg" package and when you get the crash handler dialog, click the "Developer Information" tab, and then copy the backtrace and paste it here. Thanks!
Comment 4 Francesco Betti Sorbelli 2009-07-18 17:01:49 UTC
(In reply to comment #3)
> @Francesco: install the "kdepim-dbg" package and when you get the crash handler
> dialog, click the "Developer Information" tab, and then copy the backtrace and
> paste it here. Thanks!

Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0xb4852710 (LWP 18887))]

Thread 2 (Thread 0xb0620b90 (LWP 17607)):
#0  0xb7f73424 in __kernel_vsyscall ()
#1  0xb51c5272 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb6aee7b4 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
#3  0xb765f4dc in QWaitConditionPrivate::wait (this=0xa524ac0, mutex=0xa524abc, time=30000) at thread/qwaitcondition_unix.cpp:85
#4  QWaitCondition::wait (this=0xa524ac0, mutex=0xa524abc, time=30000) at thread/qwaitcondition_unix.cpp:159
#5  0xb7654cfe in QThreadPoolThread::run (this=0xa526750) at concurrent/qthreadpool.cpp:140
#6  0xb765e522 in QThreadPrivate::start (arg=0xa526750) at thread/qthread_unix.cpp:188
#7  0xb51c1495 in start_thread () from /lib/i686/cmov/libpthread.so.0
#8  0xb6adfa1e in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4852710 (LWP 18887)):
[KCrash Handler]
#6  0xb0808d65 in Akregator::Article::title (this=0xa99db98) at ../../../akregator/src/article.cpp:375
#7  0xb081481e in Private (this=0xa638378, articles_=..., qq=0xa61bd70) at ../../../akregator/src/articlemodel.cpp:66
#8  0xb0814958 in ArticleModel (this=0xa61bd70, articles=..., parent=0x0) at ../../../akregator/src/articlemodel.cpp:69
#9  0xb083591b in Akregator::SelectionController::articleHeadersAvailable (this=0xa3afd58, job=0xa93db40) at ../../../akregator/src/selectioncontroller.cpp:200
#10 0xb0835c67 in Akregator::SelectionController::qt_metacall (this=0xa3afd58, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfd5c3fc) at ./selectioncontroller.moc:86
#11 0xb7764ad3 in QMetaObject::activate (sender=0xa93db40, from_signal_index=4, to_signal_index=4, argv=0xbfd5c3fc) at kernel/qobject.cpp:3112
#12 0xb7765722 in QMetaObject::activate (sender=0xa93db40, m=0xb7a749c8, local_signal_index=0, argv=0xbfd5c3fc) at kernel/qobject.cpp:3186
#13 0xb791b1f3 in KJob::finished (this=0xa93db40, _t1=0xa93db40) at ./kjob.moc:167
#14 0xb791b4dd in KJob::emitResult (this=0xa93db40) at ../../kdecore/jobs/kjob.cpp:302
#15 0xb080e60a in Akregator::ArticleListJob::doList (this=0xa93db40) at ../../../akregator/src/articlejobs.cpp:190
#16 0xb080e743 in Akregator::ArticleListJob::qt_metacall (this=0xa93db40, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfd5c508) at ./articlejobs.moc:215
#17 0xb7764ad3 in QMetaObject::activate (sender=0xa678878, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#18 0xb7765722 in QMetaObject::activate (sender=0xa678878, m=0xb783fd88, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#19 0xb776a7e7 in QSingleShotTimer::timeout (this=0xa678878) at .moc/release-shared/qtimer.moc:76
#20 0xb776a90c in QSingleShotTimer::timerEvent (this=0xa678878) at kernel/qtimer.cpp:298
#21 0xb775fb6f in QObject::event (this=0xa678878, e=0xbfd5c98c) at kernel/qobject.cpp:1074
#22 0xb6d8f7d4 in QApplicationPrivate::notify_helper (this=0x9d4bde0, receiver=0xa678878, e=0xbfd5c98c) at kernel/qapplication.cpp:4056
#23 0xb6d9793e in QApplication::notify (this=0xbfd5cd3c, receiver=0xa678878, e=0xbfd5c98c) at kernel/qapplication.cpp:3603
#24 0xb7c4cebd in KApplication::notify (this=0xbfd5cd3c, receiver=0xa678878, event=0xbfd5c98c) at ../../kdeui/kernel/kapplication.cpp:302
#25 0xb774f96b in QCoreApplication::notifyInternal (this=0xbfd5cd3c, receiver=0xa678878, event=0xbfd5c98c) at kernel/qcoreapplication.cpp:610
#26 0xb777e301 in QCoreApplication::sendEvent (this=0x9d4d5f4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#27 QTimerInfoList::activateTimers (this=0x9d4d5f4) at kernel/qeventdispatcher_unix.cpp:572
#28 0xb777a8a0 in timerSourceDispatch (source=0x9d4d5c0) at kernel/qeventdispatcher_glib.cpp:165
#29 0xb520d368 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb52108c3 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0xb5210a48 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb777a7f8 in QEventDispatcherGlib::processEvents (this=0x9d1e9c8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#33 0xb6e2ef85 in QGuiEventDispatcherGlib::processEvents (this=0x9d1e9c8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#34 0xb774dfba in QEventLoop::processEvents (this=0xbfd5cbb0, flags=...) at kernel/qeventloop.cpp:149
#35 0xb774e402 in QEventLoop::exec (this=0xbfd5cbb0, flags=...) at kernel/qeventloop.cpp:201
#36 0xb7750859 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0xb6d8f657 in QApplication::exec () at kernel/qapplication.cpp:3525
#38 0x0804bd40 in main (argc=1, argv=0xbfd5cf34) at ../../../kontact/src/main.cpp:218
Comment 5 Dario Andres 2009-07-18 17:06:25 UTC
The backtrace is like bug 194591. Merging. Thanks

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