[Bug 270223] New: Kontact crashed after I added a feed and updated several feeds
Janet
bugzilla at kerridis.de
Wed Apr 6 15:08:26 BST 2011
https://bugs.kde.org/show_bug.cgi?id=270223
Summary: Kontact crashed after I added a feed and updated
several feeds
Product: kontact
Version: 4.4.10
Platform: Debian unstable
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs at kde.org
ReportedBy: bugzilla at kerridis.de
Application: kontact (4.4.10)
KDE Platform Version: 4.6.1 (4.6.1)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-2.slh.3-aptosid-686 i686
Distribution (Platform): Debian unstable
-- Information about the crash:
Before the application crashed I added a new feed to akregator. I pulled in the
latest entries of the last three days. Then I hit F5 to refresh the feed and it
pulled in the older content. This content incorrectly is shown with no date and
time 00:59 though some weeks old (akregator 1.6.6).
The I switched to some other feeds in akregator and hit F5 again. And suddenly,
maybe 3-5 minutes after I have added the new feed, kontact crashed.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0xb2edba10 (LWP 6351))]
Thread 3 (Thread 0xa73f7b70 (LWP 6463)):
#0 0xb773f424 in __kernel_vsyscall ()
#1 0xb4379f7f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2 0xb5e27e0d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3 0xab9522a3 in vlc_cond_wait () from /usr/lib/libvlccore.so.4
#4 0x09478d88 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Thread 2 (Thread 0xa1ef2b70 (LWP 13478)):
#0 0xb773f424 in __kernel_vsyscall ()
#1 0xb437a482 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2 0xb5e27e64 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
#3 0xb5ff462f in wait (this=0x8edea0c, mutex=0x8edea08, time=30000) at
thread/qwaitcondition_unix.cpp:86
#4 QWaitCondition::wait (this=0x8edea0c, mutex=0x8edea08, time=30000) at
thread/qwaitcondition_unix.cpp:160
#5 0xb5fe7b01 in QThreadPoolThread::run (this=0x8e90d30) at
concurrent/qthreadpool.cpp:140
#6 0xb5ff3fd2 in QThreadPrivate::start (arg=0x8e90d30) at
thread/qthread_unix.cpp:320
#7 0xb4375955 in start_thread () from /lib/i686/cmov/libpthread.so.0
#8 0xb5e1ae7e in clone () from /lib/i686/cmov/libc.so.6
Thread 1 (Thread 0xb2edba10 (LWP 6351)):
[KCrash Handler]
#7 0xa6faee45 in Akregator::Article::title() const () from
/usr/lib/kde4/akregatorpart.so
#8 0xa6fb9079 in
Akregator::ArticleModel::Private::Private(QList<Akregator::Article> const&,
Akregator::ArticleModel*) () from /usr/lib/kde4/akregatorpart.so
#9 0xa6fb9258 in
Akregator::ArticleModel::ArticleModel(QList<Akregator::Article> const&,
QObject*) () from /usr/lib/kde4/akregatorpart.so
#10 0xa6fd886b in ?? () from /usr/lib/kde4/akregatorpart.so
#11 0xa6fd8bdf in ?? () from /usr/lib/kde4/akregatorpart.so
#12 0xb60f027a in QMetaObject::metacall (object=0x96e2b40,
cl=QMetaObject::InvokeMetaMethod, idx=15, argv=0xbffb2a48) at
kernel/qmetaobject.cpp:237
#13 0xb610015d in QMetaObject::activate (sender=0x9898dd8, m=0xb64a0b88,
local_signal_index=0, argv=0xbffb2a48) at kernel/qobject.cpp:3278
#14 0xb6349b03 in KJob::finished (this=0x9898dd8, _t1=0x9898dd8) at
./kjob.moc:173
#15 0xb6349d1c in KJob::emitResult (this=0x9898dd8) at
../../kdecore/jobs/kjob.cpp:310
#16 0xa6fb32aa in ?? () from /usr/lib/kde4/akregatorpart.so
#17 0xa6fb33e1 in ?? () from /usr/lib/kde4/akregatorpart.so
#18 0xb60f027a in QMetaObject::metacall (object=0x9898dd8,
cl=QMetaObject::InvokeMetaMethod, idx=26, argv=0xbffb2b9c) at
kernel/qmetaobject.cpp:237
#19 0xb610015d in QMetaObject::activate (sender=0x95e5c68, m=0xb6223444,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3278
#20 0xb61061d7 in QSingleShotTimer::timeout (this=0x95e5c68) at
.moc/release-shared/qtimer.moc:82
#21 0xb610628c in QSingleShotTimer::timerEvent (this=0x95e5c68) at
kernel/qtimer.cpp:308
#22 0xb60fee44 in QObject::event (this=0x95e5c68, e=0xbffb30cc) at
kernel/qobject.cpp:1181
#23 0xb660eb54 in QApplicationPrivate::notify_helper (this=0x847cc30,
receiver=0x95e5c68, e=0xbffb30cc) at kernel/qapplication.cpp:4462
#24 0xb66137de in QApplication::notify (this=0xbffb3414, receiver=0x95e5c68,
e=0xbffb30cc) at kernel/qapplication.cpp:3862
#25 0xb716fb1a in KApplication::notify (this=0xbffb3414, receiver=0x95e5c68,
event=0xbffb30cc) at ../../kdeui/kernel/kapplication.cpp:311
#26 0xb60e9bfb in QCoreApplication::notifyInternal (this=0xbffb3414,
receiver=0x95e5c68, event=0xbffb30cc) at kernel/qcoreapplication.cpp:731
#27 0xb6119fa1 in sendEvent (this=0x847fb74) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#28 QTimerInfoList::activateTimers (this=0x847fb74) at
kernel/qeventdispatcher_unix.cpp:604
#29 0xb6116c17 in timerSourceDispatch (source=0x847fba8) at
kernel/qeventdispatcher_glib.cpp:184
#30 idleTimerSourceDispatch (source=0x847fba8) at
kernel/qeventdispatcher_glib.cpp:231
#31 0xb4020252 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#32 0xb4020a30 in ?? () from /lib/libglib-2.0.so.0
#33 0xb4020ce4 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#34 0xb611732c in QEventDispatcherGlib::processEvents (this=0x8475da0,
flags=...) at kernel/qeventdispatcher_glib.cpp:422
#35 0xb66c2985 in QGuiEventDispatcherGlib::processEvents (this=0x8475da0,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#36 0xb60e8da9 in QEventLoop::processEvents (this=0xbffb3374, flags=...) at
kernel/qeventloop.cpp:149
#37 0xb60e904a in QEventLoop::exec (this=0xbffb3374, flags=...) at
kernel/qeventloop.cpp:201
#38 0xb60edabf in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#39 0xb660c997 in QApplication::exec () at kernel/qapplication.cpp:3736
#40 0x0804b86b in _start ()
This bug may be a duplicate of or related to bug 194591.
Possible duplicates by query: bug 269978, bug 269572, bug 268980, bug 266898,
bug 264868.
Reported using DrKonqi
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Kdepim-bugs
mailing list