[Bug 288370] New: akregator crash on startup
https://bugs.kde.org/show_bug.cgi?id=288370 Summary: akregator crash on startup Product: akregator Version: 1.6.6 Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: n...@leverton.org Application: akregator (1.6.6) KDE Platform Version: 4.7.2 (4.7.2) Qt Version: 4.7.3 Operating System: Linux 3.1.0-1-amd64 x86_64 Distribution: Debian GNU/Linux testing (wheezy) -- Information about the crash: I started akregator for the first time, with my old feed information from KDE3 still present in .kde. Kde4's akregator just crashes on startup using it. Let me know if you want a copy of the feed into and I'll attach it. Even if the feed data has a problem, it shoudn't just crash, but make some effort to tell you what problem and which feed so that I could try to fix it without losing several years worth of marked article archives. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [KCrash Handler] #6 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:32 #7 0x7f1d1206a283 in c4_String::c4_String (this=0x7fff679ff9a0, p=0x7961646f742f6d6f Address 0x7961646f742f6d6f out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/string.cpp:129 #8 0x7f1d1206caf7 in c4_Property::c4_Property (this=0x7fff679ff9d0, type_=optimized out, name_=0x7961646f742f6d6f Address 0x7961646f742f6d6f out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1100 #9 0x7f1d1205e51c in c4_IntProp (name_=optimized out, this=0x7fff679ff9d0) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:524 #10 f4_CreateFormat (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1228 #11 0x7f1d1206d9fd in PropIndex (prop_=..., this=0x3828780) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:292 #12 c4_Sequence::PropIndex (this=0x3828780, prop_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:285 #13 0x7f1d1206dac4 in c4_Sequence::Set (this=0x3828780, index_=4413, prop_=..., buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:325 #14 0x7f1d120656f0 in c4_HashViewer::SetItem (this=0x3828d80, row_=4413, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/remap.cpp:366 #15 0x7f1d1206dfa2 in c4_Sequence::SetAt (this=0x3827490, index_=4413, newElem_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:104 #16 0x7f1d12073772 in SetAt (newElem_=..., index_=4413, this=optimized out) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:89 #17 Akregator::Backend::FeedStorageMK4Impl::setHash (this=0x3824b50, guid=optimized out, hash=42484) at ../../../../akregator/plugins/mk4storage/feedstoragemk4impl.cpp:463 #18 0x7f1d13d79704 in Akregator::Article::Private::Private (this=0x2811100, article=..., feed_=optimized out, archive_=optimized out) at ../../../akregator/src/article.cpp:175 #19 0x7f1d13d7a660 in Akregator::Article::Article (this=0x7fff67a00090, article=..., feed=0x3824ab0) at ../../../akregator/src/article.cpp:245 #20 0x7f1d13d8736e in Akregator::Feed::appendArticles (this=0x3824ab0, feed=optimized out) at ../../../akregator/src/feed.cpp:481 #21 0x7f1d13d3 in Akregator::Feed::fetchCompleted (this=0x3824ab0, l=optimized out, doc=..., status=optimized out) at ../../../akregator/src/feed.cpp:677 #22 0x7f1d13d88c7d in Akregator::Feed::qt_metacall (this=0x3824ab0, _c=QMetaObject::InvokeMetaMethod, _id=11, _a=0x7fff67a003c0) at ./feed.moc:112 #23 0x7f1d2ac20b1a in QMetaObject::activate (sender=0x6630eb0, m=optimized out, local_signal_index=optimized out, argv=0x7fff67a003c0) at kernel/qobject.cpp:3278 #24 0x7f1d138f8c42 in Syndication::Loader::loadingComplete (this=optimized out, _t1=0x6630eb0, _t2=optimized out, _t3=Syndication::Success) at ./loader.moc:91 #25 0x7f1d138f967f in Syndication::Loader::slotRetrieverDone (this=0x6630eb0, data=..., success=optimized out) at ../../syndication/loader.cpp:157 #26 0x7f1d138f9a8d in Syndication::Loader::qt_metacall (this=0x6630eb0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff67a00580) at ./loader.moc:79 #27 0x7f1d2ac20b1a in QMetaObject::activate (sender=0x66fc820, m=optimized out, local_signal_index=optimized out, argv=0x7fff67a00580) at kernel/qobject.cpp:3278 #28 0x7f1d138fc1d3 in Syndication::DataRetriever::dataRetrieved (this=optimized out, _t1=optimized out, _t2=true) at ./dataretriever.moc:85 #29 0x7f1d138fc410 in Syndication::FileRetriever::slotResult (this=0x66fc820, job=0x66fb400) at ../../syndication/dataretriever.cpp:132 #30 0x7f1d138fc5c3 in Syndication::FileRetriever::qt_metacall (this=0x66fc820, _c=QMetaObject::InvokeMetaMethod,
[Bug 289698] New: Akregator crash when marking folder full of feeds as read.
https://bugs.kde.org/show_bug.cgi?id=289698 Summary: Akregator crash when marking folder full of feeds as read. Product: akregator Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: n...@leverton.org Application: akregator (4.7.3) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-14-generic-pae i686 Distribution: Ubuntu 11.10 -- Information about the crash: My feeds are organised into by-topic folders. Whilst browsing through my feeds, I unfolded one folder that is not currently relevant to me, looked which of the feeds had articles, folded it again and used the context menu to mark them read. Akregator crashed as attached. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [Current thread is 1 (Thread 0xb37e1730 (LWP 9361))] Thread 2 (Thread 0xad049b70 (LWP 9371)): #0 0xb46bed10 in __GI_clock_gettime (clock_id=1, tp=0xad049008) at ../sysdeps/unix/clock_gettime.c:116 #1 0xb62177d5 in do_gettime (frac=0xad049000, sec=0xad048ff8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb62ea4b6 in QTimerInfoList::updateCurrentTime (this=0x9914934) at kernel/qeventdispatcher_unix.cpp:339 #4 0xb62ea80a in QTimerInfoList::timerWait (this=0x9914934, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0xb62e9053 in timerSourcePrepareHelper (src=optimized out, timeout=0xad04910c) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb62e90ed in timerSourcePrepare (source=0x9914900, timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:169 #7 0xb489388c in g_main_context_prepare (context=0x96052d8, priority=0xad049168) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:2762 #8 0xb4894637 in g_main_context_iterate (context=0x96052d8, block=1, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3069 #9 0xb4894c2a in g_main_context_iteration (context=0x96052d8, may_block=1) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3152 #10 0xb62e9b37 in QEventDispatcherGlib::processEvents (this=0x95e7170, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0xb62ba1dd in QEventLoop::processEvents (this=0xad049290, flags=...) at kernel/qeventloop.cpp:149 #12 0xb62ba421 in QEventLoop::exec (this=0xad049290, flags=...) at kernel/qeventloop.cpp:201 #13 0xb61bd90b in QThread::exec (this=0x99906b8) at thread/qthread.cpp:498 #14 0xb629ae2d in QInotifyFileSystemWatcherEngine::run (this=0x99906b8) at io/qfilesystemwatcher_inotify.cpp:248 #15 0xb61c07b3 in QThreadPrivate::start (arg=0x99906b8) at thread/qthread_unix.cpp:331 #16 0xb496bd31 in start_thread (arg=0xad049b70) at pthread_create.c:304 #17 0xb5f270ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb37e1730 (LWP 9361)): [KCrash Handler] #7 0xb23132f4 in c4_Property::c4_Property (this=0xbfad6d3c, type_=73 'I', name_=0x0) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1105 #8 0xb2306b71 in c4_IntProp (name_=optimized out, this=0xbfad6d3c) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:523 #9 f4_CreateFormat (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1227 #10 0xb2307243 in c4_HandlerSeq::CreateHandler (this=0xa1dcaa8, prop_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:130 #11 0xb231446c in PropIndex (prop_=..., this=0xa1dcaa8) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:291 #12 c4_Sequence::PropIndex (this=0xa1dcaa8, prop_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:284 #13 0xb2314572 in c4_Sequence::Set (this=0xa1dcaa8, index_=1252, prop_=..., buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:324 #14 0xb2311a9b in SetData (buf_=..., this=optimized out) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:425 #15 c4_View::SetItem (this=0xa23fe54, row_=1252, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:230 #16 0xb230ce48 in c4_HashViewer::SetItem (this=0xa23fe50, row_=1252, col_=21, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/remap.cpp:365 #17 0xb22fe58f in DoSet (buf_=..., col_=optimized out, row_=1252, this=optimized out) at ../../../../akregator/plugins/mk4storage/metakit/src/custom.cpp:153 #18 c4_CustomHandler::Set (this=0xa1ae0e0, index_=1252, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/custom.cpp:68 #19 0xb2314b62 in c4_Sequence::SetAt (this=0xa2131b0, index_=1252, newElem_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:103 #20 0xb231a1f7 in SetAt (newElem_=..., index_=1252,
[Bug 289698] Akregator crash when marking folder full of feeds as read.
https://bugs.kde.org/show_bug.cgi?id=289698 --- Comment #1 from Nick Leverton nick leverton org 2011-12-23 22:32:57 --- Did not happen again when I restarted akregator and visited this folder first. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295001] New: Akonadi IMAP agent crash when trying to stop it after network interruption
https://bugs.kde.org/show_bug.cgi?id=295001 Summary: Akonadi IMAP agent crash when trying to stop it after network interruption Product: Akonadi Version: 4.7 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: IMAP resource AssignedTo: er...@kde.org ReportedBy: n...@leverton.org CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_imap_resource (4.7) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-16-generic-pae i686 Distribution: Ubuntu 11.10 -- Information about the crash: The IMAP connection had been interrupted by a network outage and I was getting floods of IMAP connection unavailable notifications from KDE notification manager (literally, piling up as fast as I could acknowledge them). Closed kmail but the floods continued, even after IMAP connection was available again. I used akonadiconsole to try to restart my IMAP agent with no change. Then selected Abort for the IMAP agent and it crashed. I've not experienced these symptoms (message floods or akonadi agent crash) before, despite the network being interrupted twice per day as I take the laptop between home and work. What was unusual this time was that the local LAN connection remained up (as the outage was caused by IT department breaking stuff elsewhere). -- Backtrace: Application: AceAxis of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault [Current thread is 1 (Thread 0xb4c18710 (LWP 17045))] Thread 9 (Thread 0xb23ffb70 (LWP 1940)): #0 0xb570dd10 in __GI_clock_gettime (clock_id=1, tp=0xb23ff028) at ../sysdeps/unix/clock_gettime.c:116 #1 0xb73d17d5 in do_gettime (frac=0xb23ff020, sec=0xb23ff018) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb74a44b6 in QTimerInfoList::updateCurrentTime (this=0x8aefbc4) at kernel/qeventdispatcher_unix.cpp:339 #4 0xb74a480a in QTimerInfoList::timerWait (this=0x8aefbc4, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0xb74a3053 in timerSourcePrepareHelper (src=optimized out, timeout=0xb23ff12c) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb74a30ed in timerSourcePrepare (source=0x8aefb90, timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:169 #7 0xb565388c in g_main_context_prepare (context=0x8af36b0, priority=0xb23ff188) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:2762 #8 0xb5654637 in g_main_context_iterate (context=0x8af36b0, block=1, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3069 #9 0xb5654c2a in g_main_context_iteration (context=0x8af36b0, may_block=1) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3152 #10 0xb74a3b37 in QEventDispatcherGlib::processEvents (this=0x88668d0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0xb74741dd in QEventLoop::processEvents (this=0xb23ff2b0, flags=...) at kernel/qeventloop.cpp:149 #12 0xb7474421 in QEventLoop::exec (this=0xb23ff2b0, flags=...) at kernel/qeventloop.cpp:201 #13 0xb737790b in QThread::exec (this=0x8b59d68) at thread/qthread.cpp:498 #14 0xb7454e2d in QInotifyFileSystemWatcherEngine::run (this=0x8b59d68) at io/qfilesystemwatcher_inotify.cpp:248 #15 0xb737a7b3 in QThreadPrivate::start (arg=0x8b59d68) at thread/qthread_unix.cpp:331 #16 0xb57c4d31 in start_thread (arg=0xb23ffb70) at pthread_create.c:304 #17 0xb59060ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Backtrace stopped: Not enough registers or memory available to unwind further Thread 8 (Thread 0xb383fb70 (LWP 23228)): #0 0xb57c7d44 in __pthread_mutex_unlock_usercnt (mutex=0x8affa54, decr=1) at pthread_mutex_unlock.c:52 #1 0xb5913f54 in pthread_mutex_unlock (mutex=0x8affa54) at forward.c:184 #2 0xb5653f1f in g_main_context_check (context=0x8affa50, max_priority=2147483647, fds=0xb240bda8, n_fds=1) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:2957 #3 0xb56548f0 in g_main_context_iterate (context=0x8affa50, block=-1251593440, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3086 #4 0xb5654c2a in g_main_context_iteration (context=0x8affa50, may_block=1) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3152 #5 0xb74a3b37 in QEventDispatcherGlib::processEvents (this=0x8e24b98, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0xb74741dd in QEventLoop::processEvents (this=0xb383f2d0, flags=...) at kernel/qeventloop.cpp:149 #7 0xb7474421 in QEventLoop::exec (this=0xb383f2d0, flags=...) at kernel/qeventloop.cpp:201 #8 0xb737790b in QThread::exec (this=0x8b34758) at thread/qthread.cpp:498 #9 0xb66d64d0 in KIMAP::SessionThread::run (this=0x8b34758) at ../../kimap/sessionthread.cpp:169 #10 0xb737a7b3 in QThreadPrivate::start (arg=0x8b34758) at thread/qthread_unix.cpp:331 #11 0xb57c4d31 in start_thread (arg=0xb383fb70) at pthread_create.c:304 #12 0xb59060ce in clone ()
[Bug 286692] Kmail doesn't show attachment icon in message list.
https://bugs.kde.org/show_bug.cgi?id=286692 Nick Leverton n...@leverton.org changed: What|Removed |Added CC||n...@leverton.org -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 286692] Kmail doesn't show attachment icon in message list.
https://bugs.kde.org/show_bug.cgi?id=286692 --- Comment #3 from Nick Leverton n...@leverton.org --- Confirmed in 4.7.4. Also, setting the quick-search status dropdown to attachments doesn't show any mails - seems like it could be related. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 288268] imap agents crash when network connection gets closed
https://bugs.kde.org/show_bug.cgi?id=288268 Nick Leverton n...@leverton.org changed: What|Removed |Added CC||n...@leverton.org -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 293893] Useless error messages
https://bugs.kde.org/show_bug.cgi?id=293893 Nick Leverton n...@leverton.org changed: What|Removed |Added CC||n...@leverton.org --- Comment #2 from Nick Leverton n...@leverton.org --- Both errors confirmed here. Our Exchange server is hopelessly unreliable (well what would you expect) and the admins restart it on a whim, sometimes several times a day. Every time they do, my DIMAP Akonadi resources either silently become disconnected and never reconnect, or loudly squirt out a dozen errors every minute. I'm not sure which is worse but neither is good :-( -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 293893] Useless error messages
https://bugs.kde.org/show_bug.cgi?id=293893 --- Comment #4 from Nick Leverton n...@leverton.org --- Currently on 4.8.3, and have been generally tracking KDE stable via Ubuntu kde PPA. We only got the (ptui) exchange server recently so I can't go back much before 4.7.2 but this issue is certainly current. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 293893] Useless error messages
https://bugs.kde.org/show_bug.cgi?id=293893 --- Comment #5 from Nick Leverton n...@leverton.org --- By coincidence I just had this issue again whilst responding. It may be related to the caldav link perhaps rather than dimap, since they both go to the same server. After an overnight interruption to the connection, I have closed and exited kontact (not even running in system tray), and run akonadictl stop, but the flood of Unknown error: unable to list item parts is *still* going on :-( I restarted akonadi using systemsettings PIM framework, and both korganizer and plasma-desktop have now put up Fetch job error dialogue boxes with the same unable to list item parts message. What can be producing it, how can I help you debug this issue ? The cpu is being slugged to 100%, and the continuing popups severely interrupt my work. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295622] Select two folders then move them to another sub sub folders crash
https://bugs.kde.org/show_bug.cgi?id=295622 --- Comment #21 from Nick Leverton n...@leverton.org --- Created attachment 72150 -- https://bugs.kde.org/attachment.cgi?id=72150action=edit New crash information added by DrKonqi kontact (4.8.4) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.1 As with other reports, I had recently moved a folder (by GUI dragging) from a lower level to a parent of the original location. This is on a DIMAP resource. The crash didn't happen immediately but only when I created a new empty folder soon afterwards, I don't know whether that is coincidence or not. -- Backtrace (Reduced): #7 QModelIndex (other=..., this=0xbff4dd20) at ../../include/QtCore/../../src/corelib/kernel/qabstractitemmodel.h:65 #8 QSortFilterProxyModel::parent (this=0x8d13220, child=...) at itemviews/qsortfilterproxymodel.cpp:1659 #9 0xb73c9708 in parent (this=0xbff4dd70) at /usr/include/qt4/QtCore/qabstractitemmodel.h:393 #10 KIdentityProxyModel::parent (this=0x8b39908, child=...) at ../../kdeui/itemviews/kidentityproxymodel.cpp:358 #11 0xb73c9708 in parent (this=0xbff4ddd0) at /usr/include/qt4/QtCore/qabstractitemmodel.h:393 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295622] Select two folders then move them to another sub sub folders crash
https://bugs.kde.org/show_bug.cgi?id=295622 Nick Leverton n...@leverton.org changed: What|Removed |Added CC||n...@leverton.org -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 286692] Kmail doesn't show attachment icon in message list.
https://bugs.kde.org/show_bug.cgi?id=286692 --- Comment #5 from Nick Leverton n...@leverton.org --- Yep I confirm that for me (see comment #3) the lack of icons is on an Exchange DIMAP server. Having read #4 I also setup a local DIMAP server on my Linux mailbox as a test, and that *does* get icons. Unfortunately I can't wire-trace the Exchange IMAP conversation as it uses SSL. Can I get a trace out of Akonadi or something ? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 163573] Akregator crashed while clicking an article title
https://bugs.kde.org/show_bug.cgi?id=163573 --- Comment #34 from Nick Leverton n...@leverton.org --- Created attachment 72591 -- https://bugs.kde.org/attachment.cgi?id=72591action=edit New crash information added by DrKonqi akregator (1.6.6) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2 - What I was doing when the application crashed: I had just done a full refresh, which seemed to have finished. In the tree pane on the left I had a closed folder of feeds that I'm not interested in at the moment, so I right-clicked on the folder and pressed mark feed read. Akregator immediately crashed. When I've had this problem before over the last 3 years it's been blamed on corrupt files imported from KDE3 but I don't believe this is correct: 1, last time I imported from KDE3 I spent some time checking the metakit archives out with metakit tools, and no problems were apparent 2. this only ever happened once for each feed, and almost never happened first time into the feed but only at some random time later. so it's not a corruption of the feed itself as that would cause akregator to crash every time, but something about the feed that catches akregator on the hop when it is doing some other task at the same time 2. this hasn't happened since then in eight months of daily use of KDE4 akregator, but is apparently still an occasional issue. The crash is not reproducible at will but will occur sooner or later. -- Backtrace (Reduced): #6 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:43 #7 0x7eff66a47ba1 in c4_String::c4_String (this=0x7fff24cc73f0, p=0x70747468002f3532 Address 0x70747468002f3532 out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/string.cpp:131 #8 0x7eff66a49dd7 in c4_Property::c4_Property (this=0x7fff24cc7420, type_=optimized out, name_=0x70747468002f3532 Address 0x70747468002f3532 out of bounds) at ../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1100 #9 0x7eff66a3fbec in c4_IntProp (name_=optimized out, this=0x7fff24cc7420) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:524 #10 f4_CreateFormat (prop_=..., seq_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1228 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 303758] New: Flashplayer related crash still happens in QtWebkit 2.2
https://bugs.kde.org/show_bug.cgi?id=303758 Bug ID: 303758 Severity: crash Version: 1.6.6 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Flashplayer related crash still happens in QtWebkit 2.2 Classification: Unclassified OS: Linux Reporter: n...@leverton.org Hardware: Debian testing Status: UNCONFIRMED Component: general Product: akregator Application: akregator (1.6.6) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.2 Operating System: Linux 3.2.0-3-amd64 x86_64 Distribution: Debian GNU/Linux testing (wheezy) -- Information about the crash: - What I was doing when the application crashed: I had just resumed the laptop from sleep mode so I presume that displays were being refreshed etc. Akregator spontaneously crashed (I had been viewing some pages last night which probably had embedded Flash objects). #267526 suggests that this crash was an upstream issue fixed in QtWebkit 2.1, however I have QtWebkit 2.2 so perhaps it is still outstanding ? -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f9bab6c7760 (LWP 12165))] Thread 7 (Thread 0x7f9b8af33700 (LWP 12166)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f9b8d554c0d in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f9b8df15280) at wtf/FastMalloc.cpp:2499 #2 0x7f9b8d554d19 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at wtf/FastMalloc.cpp:1622 #3 0x7f9ba2ef6b50 in start_thread (arg=optimized out) at pthread_create.c:304 #4 0x7f9ba81ce6dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 6 (Thread 0x7f9b8a632700 (LWP 12167)): #0 0x7f9ba81c3a93 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=6592) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f9ba2a294d4 in g_main_context_poll (n_fds=1, fds=0x7f9b84002980, timeout=6592, context=0x7f9b84000970, priority=optimized out) at /tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3440 #2 g_main_context_iterate (context=context@entry=0x7f9b84000970, block=block@entry=1, dispatch=dispatch@entry=1, self=error reading variable: Unhandled dwarf expression opcode 0xfa) at /tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3141 #3 0x7f9ba2a295f4 in g_main_context_iteration (context=0x7f9b84000970, may_block=1) at /tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #4 0x7f9ba8dc2306 in QEventDispatcherGlib::processEvents (this=0x24fef50, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f9ba8d9292f in QEventLoop::processEvents (this=this@entry=0x7f9b8a631e40, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f9ba8d92bb8 in QEventLoop::exec (this=0x7f9b8a631e40, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f9ba8c95d70 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7f9ba8c98d0b in QThreadPrivate::start (arg=0x25275c0) at thread/qthread_unix.cpp:307 #9 0x7f9ba2ef6b50 in start_thread (arg=optimized out) at pthread_create.c:304 #10 0x7f9ba81ce6dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 5 (Thread 0x7f9b3a3b1700 (LWP 12228)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f9b3fb4c4fc in ?? () from /usr/lib/flashplugin-nonfree/libflashplayer-11.2.202.236.so #2 0x7f9b3f79a5f0 in ?? () from /usr/lib/flashplugin-nonfree/libflashplayer-11.2.202.236.so #3 0x7f9b3fb4c75c in ?? () from /usr/lib/flashplugin-nonfree/libflashplayer-11.2.202.236.so #4 0x7f9b3fb4ccae in ?? () from /usr/lib/flashplugin-nonfree/libflashplayer-11.2.202.236.so #5 0x7f9ba2ef6b50 in start_thread (arg=optimized out) at pthread_create.c:304 #6 0x7f9ba81ce6dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 4 (Thread 0x7f9b39bb0700 (LWP 12229)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f9b3fb4c4fc in ?? () from /usr/lib/flashplugin-nonfree/libflashplayer-11.2.202.236.so #2 0x7f9b3f79a5f0 in ?? () from /usr/lib/flashplugin-nonfree/libflashplayer-11.2.202.236.so #3 0x7f9b3fb4c75c in ?? () from /usr/lib/flashplugin-nonfree/libflashplayer-11.2.202.236.so #4 0x7f9b3fb4ccae in ?? () from /usr/lib/flashplugin-nonfree/libflashplayer-11.2.202.236.so #5 0x7f9ba2ef6b50 in start_thread (arg=optimized out) at pthread_create.c:304 #6 0x7f9ba81ce6dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 3 (Thread 0x7f9b376a8700 (LWP 12230)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at
[Bug 284527] Error when changing an imap folder's identity (Unknown command SETANNOTATION)
https://bugs.kde.org/show_bug.cgi?id=284527 Nick Leverton n...@leverton.org changed: What|Removed |Added CC||n...@leverton.org --- Comment #2 from Nick Leverton n...@leverton.org --- This notification is given any time I use the Properties dialogue on an IMAP resource, even if I make no changes or only change a local property (such as the local name). -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 284527] Error when changing an imap folder's identity (Unknown command SETANNOTATION)
https://bugs.kde.org/show_bug.cgi?id=284527 --- Comment #3 from Nick Leverton n...@leverton.org --- Version is 4.9.0, apols for forgetting to say. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 286692] Kmail doesn't show attachment icon in message list.
https://bugs.kde.org/show_bug.cgi?id=286692 --- Comment #6 from Nick Leverton n...@leverton.org --- This is still a problem with Exchange IMAP accounts in KDE 4.9 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 305987] New: Could not create collection when adding new top-level mailbox for IMAP account:
https://bugs.kde.org/show_bug.cgi?id=305987 Bug ID: 305987 Severity: normal Version: 4.9.0 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Could not create collection when adding new top-level mailbox for IMAP account: Classification: Unclassified OS: Linux Reporter: n...@leverton.org Hardware: Ubuntu Packages Status: UNCONFIRMED Component: folders Product: kmail2 To reproduce: Configure an IMAP resource (doesn't seem to matter whether online or disconnected, This issue occurs with both Exchange IMAP and Dovecot IMAP). Right click on the account's top-level folder and choose Add folder Expected result: New mailbox is created on the IMAP server and on the local resource. Actual result: New folder is created on the IMAP server but does not appear locally. Akonadi repeatedly gives an error Could not create collection. Akonadi error log contains repeated entries : Error during executing query INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, cachePolicyInherit) VALUES (:0, :1, :2, :3, :4, :5) : Duplicate entry '189-DovecotTopLevel' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement the 189 and the DovecotTopLevel string obviously vary depending on parent ID and name of created mailbox. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 306746] New: Kontact (organiser) crash whilst editing recurring todo
https://bugs.kde.org/show_bug.cgi?id=306746 Bug ID: 306746 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact (organiser) crash whilst editing recurring todo Classification: Unclassified OS: Linux Reporter: n...@leverton.org Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9) KDE Platform Version: 4.9.00 Qt Version: 4.8.2 Operating System: Linux 3.2.0-30-generic-pae i686 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I have a weekly TODO which I had just edited to reduce it from two days to 1 (as it never takes 2 days). Somehoe this ended up with a duplicate entry of the todo item - one spanning both days and the other only the one day per week. The month view confirmed that this was the case each week. I right-clicked on the two-day todo task and selected delete. Kontact crashed as attached. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb218d9c0 (LWP 12888))] Thread 4 (Thread 0xafae1b40 (LWP 12889)): #0 0xb7788424 in __kernel_vsyscall () #1 0xb36b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0xb60b53dc in __pthread_cond_wait (cond=0xb5f64a30, mutex=0xb5f64a18) at forward.c:139 #3 0xb5833263 in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb5f5f940) at wtf/FastMalloc.cpp:2495 #4 0xb583337f in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb5f5f940) at wtf/FastMalloc.cpp:1618 #5 0xb3995d4c in start_thread (arg=0xafae1b40) at pthread_create.c:308 #6 0xb60a7ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 3 (Thread 0xaf1c0b40 (LWP 12890)): #0 0xb36e7dcd in __GI_clock_gettime (clock_id=1, tp=0xaf1c0008) at ../sysdeps/unix/clock_gettime.c:116 #1 0xb630e3b5 in do_gettime (frac=0xaf1c, sec=0xaf1bfff8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb63f8866 in QTimerInfoList::updateCurrentTime (this=0xae802074) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb63f8bba in QTimerInfoList::timerWait (this=0xae802074, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0xb63f7463 in timerSourcePrepareHelper (src=optimized out, timeout=0xaf1c00ec) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb38c2872 in g_main_context_prepare (context=0xae8004e0, priority=0xaf1c0148) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:2836 #7 0xb38c2faf in g_main_context_iterate (dispatch=1, block=1, context=0xae8004e0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3126 #8 g_main_context_iterate (context=0xae8004e0, block=1, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #9 0xb38c3201 in g_main_context_iteration (context=0xae8004e0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #10 0xb63f7f27 in QEventDispatcherGlib::processEvents (this=0xae800468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #11 0xb63c37ed in QEventLoop::processEvents (this=0xaf1c0270, flags=...) at kernel/qeventloop.cpp:149 #12 0xb63c3a89 in QEventLoop::exec (this=0xaf1c0270, flags=...) at kernel/qeventloop.cpp:204 #13 0xb62ac9ec in QThread::exec (this=0x9e45a18) at thread/qthread.cpp:501 #14 0xb62acadb in QThread::run (this=0x9e45a18) at thread/qthread.cpp:568 #15 0xb62afe80 in QThreadPrivate::start (arg=0x9e45a18) at thread/qthread_unix.cpp:307 #16 0xb3995d4c in start_thread (arg=0xaf1c0b40) at pthread_create.c:308 #17 0xb60a7ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xacbf9b40 (LWP 12903)): #0 __libc_disable_asynccancel (oldtype=optimized out) at ../nptl/cancellation.c:83 #1 0xb6097184 in read () at ../sysdeps/unix/syscall-template.S:82 #2 0xb39016ae in read (__nbytes=16, __buf=0xacbf907c, __fd=optimized out) at /usr/include/i386-linux-gnu/bits/unistd.h:45 #3 g_wakeup_acknowledge (wakeup=0xae8015d8) at /build/buildd/glib2.0-2.32.3/./glib/gwakeup.c:212 #4 0xb38c2bd2 in g_main_context_check (context=0xac2004e0, max_priority=2147483647, fds=0xac202278, n_fds=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:2980 #5 0xb38c3042 in g_main_context_iterate (dispatch=1, block=-1282602416, context=0xac2004e0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3143 #6 g_main_context_iterate (context=0xac2004e0, block=-1282602416, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #7 0xb38c3201 in g_main_context_iteration (context=0xac2004e0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #8 0xb63f7f27 in QEventDispatcherGlib::processEvents (this=0xac200468,
[Bug 287140] editing a new time-planing item crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=287140 Nick Leverton n...@leverton.org changed: What|Removed |Added CC||n...@leverton.org -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 287140] editing a new time-planing item crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=287140 --- Comment #14 from Nick Leverton n...@leverton.org --- Created attachment 74028 -- https://bugs.kde.org/attachment.cgi?id=74028action=edit New crash information added by DrKonqi kontact (4.9.1) on KDE Platform 4.9.1 using Qt 4.8.2 - What I was doing when the application crashed: Creating a new Time Tracker item (I haven't used this feature before so have no tracker items at present). I entered the title and description but when i clicked on edit times, kontact crashed as attached. -- Backtrace (Reduced): #7 timetrackerstorage::rawevents (this=0xb407ba0) at ../../ktimetracker/timetrackerstorage.cpp:323 #8 0xa6fc6a42 in historydialog::listallevents (this=0xb5db488) at ../../ktimetracker/historydialog.cpp:105 #9 0xa6fc8b82 in historydialog::historydialog (this=0xb5db488, parent=0xb5690b8) at ../../ktimetracker/historydialog.cpp:85 #10 0xa6f9d6ab in EditTaskDialog::on_edittimespushbutton_clicked (this=0x9ef9ba8) at ../../ktimetracker/edittaskdialog.cpp:103 #11 0xa6f97e4d in EditTaskDialog::qt_static_metacall (_o=optimized out, _id=optimized out, _a=optimized out, _c=optimized out) at moc_edittaskdialog.cpp:52 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 307145] New: Kontact todo summary doesn't exclude unstarted items when configured to do so
https://bugs.kde.org/show_bug.cgi?id=307145 Bug ID: 307145 Severity: minor Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact todo summary doesn't exclude unstarted items when configured to do so Classification: Unclassified OS: Linux Reporter: n...@leverton.org Hardware: Ubuntu Packages Status: UNCONFIRMED Component: summary Product: kontact I created a TODO item with a start date in the future. I configured kontact to exclude unstarted todos from the summary page. However the item was still shown there. I changed away from the summary and back to force a refresh, which sometimes seems to be necessary, but the item was still wrongly shown. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 308070] New: Kmail crash on deleting last search folder
https://bugs.kde.org/show_bug.cgi?id=308070 Bug ID: 308070 Severity: crash Version: 4.9.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crash on deleting last search folder Classification: Unclassified OS: Linux Reporter: n...@leverton.org Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9.2) KDE Platform Version: 4.9.2 Qt Version: 4.8.2 Operating System: Linux 3.2.0-31-generic-pae i686 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Kontact/kmail was being incredibly slow in showing me existing mails from my supposedly cached dimap mailbox (even though it shouldn't have had to) so I quit and restarted it. (not that a restart helps, this symptom has only arisen since upgrading to kdepim 4.9 but I haven't narrowed down yet whether it's kontact itself, the exchange connector or Exchange itself. will bug the whole degraded performance issue in 4.9 separately when I have more info). After the restart i did some more very slow browsing and then got fed up so tried to delete the last search. as i thought maybe kontact was still trying to refresh that. Nothing happened so I deleted the last search folder again. 3 or 4 minutes later kontact crashed as attached Nick -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb212f9c0 (LWP 8773))] Thread 4 (Thread 0xafa83b40 (LWP 8774)): #0 0xb7732424 in __kernel_vsyscall () #1 0xb393e96b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0xb605d85c in __pthread_cond_wait (cond=0xb5f07a30, mutex=0xb5f07a18) at forward.c:139 #3 0xb57d6263 in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb5f02940) at wtf/FastMalloc.cpp:2495 #4 0xb57d637f in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb5f02940) at wtf/FastMalloc.cpp:1618 #5 0xb393ad4c in start_thread (arg=0xafa83b40) at pthread_create.c:308 #6 0xb604ff4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 3 (Thread 0xaf162b40 (LWP 8775)): #0 0xb368cdcd in __GI_clock_gettime (clock_id=1, tp=0xaf162008) at ../sysdeps/unix/clock_gettime.c:116 #1 0xb62b73b5 in do_gettime (frac=0xaf162000, sec=0xaf161ff8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb63a16f6 in QTimerInfoList::updateCurrentTime (this=0xae802074) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb63a1a4a in QTimerInfoList::timerWait (this=0xae802074, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0xb63a02f3 in timerSourcePrepareHelper (src=optimized out, timeout=0xaf1620ec) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb3867872 in g_main_context_prepare (context=0xae8004e0, priority=0xaf162148) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:2836 #7 0xb3867faf in g_main_context_iterate (dispatch=1, block=1, context=0xae8004e0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3126 #8 g_main_context_iterate (context=0xae8004e0, block=1, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #9 0xb3868201 in g_main_context_iteration (context=0xae8004e0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #10 0xb63a0db7 in QEventDispatcherGlib::processEvents (this=0xae800468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #11 0xb636c67d in QEventLoop::processEvents (this=0xaf162270, flags=...) at kernel/qeventloop.cpp:149 #12 0xb636c919 in QEventLoop::exec (this=0xaf162270, flags=...) at kernel/qeventloop.cpp:204 #13 0xb62559ec in QThread::exec (this=0xa04e320) at thread/qthread.cpp:501 #14 0xb6255adb in QThread::run (this=0xa04e320) at thread/qthread.cpp:568 #15 0xb6258e80 in QThreadPrivate::start (arg=0xa04e320) at thread/qthread_unix.cpp:307 #16 0xb393ad4c in start_thread (arg=0xaf162b40) at pthread_create.c:308 #17 0xb604ff4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xacba5b40 (LWP 8785)): #0 0xb393dc64 in __pthread_mutex_unlock_usercnt (mutex=0xac200550, decr=1) at pthread_mutex_unlock.c:52 #1 0xb605dab4 in pthread_mutex_unlock (mutex=0xac200550) at forward.c:184 #2 0xb38a7410 in g_mutex_unlock (mutex=0xac2004e0) at /build/buildd/glib2.0-2.32.3/./glib/gthread-posix.c:227 #3 0xb3867f9f in g_main_context_iterate (dispatch=1, block=1, context=0xac2004e0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3124 #4 g_main_context_iterate (context=0xac2004e0, block=1, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #5 0xb3868201 in g_main_context_iteration (context=0xac2004e0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #6 0xb63a0db7 in
[Bug 308070] Kmail crash on deleting last search folder
https://bugs.kde.org/show_bug.cgi?id=308070 --- Comment #1 from Nick Leverton n...@leverton.org --- Created attachment 74420 -- https://bugs.kde.org/attachment.cgi?id=74420action=edit .xsession-errors around the time of the crash. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 310700] New: Multiple actions in one filter not applied correctly
https://bugs.kde.org/show_bug.cgi?id=310700 Bug ID: 310700 Severity: normal Version: 4.9 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Multiple actions in one filter not applied correctly Classification: Unclassified OS: Linux Reporter: n...@leverton.org Hardware: Ubuntu Packages Status: UNCONFIRMED Component: Mail Filter Agent Product: Akonadi I have a filter which contains two actions: Mark as - Read Move into - deleted items Mail which matches the filter is moved but it is not marked as read (or possibly the mark is not saved before moving, I don't know the implementation details). I don't remember the exact versions but up to somewhere about 4.5 this worked as expected. In (I think) 4.6 or 4.7 it broke as at present. I didn't get round to bugging that before 4.8 came out, when it started working as expected again. However in 4.9 it is once again broken in the same manner as previously. This is a DIMAP account on an Exchange IMAP server, the filter is marked as apply to incoming messages, from all accounts. I have tried deleting and recreating the filter but it makes no difference. Reproducible: Always Steps to Reproduce: Create a filter Subject contains: mail-subject-i-dont-care-about Actions: Mark As, Read Move Into folder, Deleted items Receive a mail which matches this filter. Actual Results: Mail is moved to Deleted items but remains Unread Expected Results: Mail is moved to Deleted items and marked as Read -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 310700] Multiple actions in one filter not applied correctly
https://bugs.kde.org/show_bug.cgi?id=310700 --- Comment #1 from Nick Leverton n...@leverton.org --- Still an issue in 4.9.97 RC2. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 310700] Multiple actions in one filter not applied correctly
https://bugs.kde.org/show_bug.cgi?id=310700 --- Comment #2 from Nick Leverton n...@leverton.org --- Still an issue in 4.10, unfortunately. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 310700] Multiple actions in one filter not applied correctly
https://bugs.kde.org/show_bug.cgi?id=310700 --- Comment #4 from Nick Leverton n...@leverton.org --- Hi Laurent, my problematic filter is: Filter Criteria: Match all Subject: contains: sometext Subject: does not contain: Re: Filter Actions: Mark As: Read Move Into Folder: DIMAPaccount/Deleted Items Advanced Options: Apply to incoming: from all Apply on manual filtering -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 293633] KMail asked for an IMAP password, entered and crashed
https://bugs.kde.org/show_bug.cgi?id=293633 Nick Leverton n...@leverton.org changed: What|Removed |Added CC||n...@leverton.org -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 293633] KMail asked for an IMAP password, entered and crashed
https://bugs.kde.org/show_bug.cgi?id=293633 --- Comment #22 from Nick Leverton n...@leverton.org --- Created attachment 77608 -- https://bugs.kde.org/attachment.cgi?id=77608action=edit New crash information added by DrKonqi akonadi_imap_resource (4.10) on KDE Platform 4.10.00 using Qt 4.8.3 - What I was doing when the application crashed: Kmail had been idle on the desktop overnight and at some point it had popped up an authorisation failure (suspect our mail admins were doing some maintenance). I re-entered the password and kmail crashed as attached. An earlier report asked if this was still happening; I unfortunately can confirm that this happened with 4.10. -- Backtrace (Reduced): #8 0xb72e59ca in QObject::connect (sender=0x8d2df20, signal=0x80add64 2stateChanged(KIMAP::Session::State,KIMAP::Session::State), receiver=0x8d52c88, method=0x80add20 1onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State), type=Qt::AutoConnection) at kernel/qobject.cpp:2549 #9 0x0809d2e8 in SessionPool::onPasswordRequestDone (this=this@entry=0x8d52c88, resultType=0, password=...) at ../../../resources/imap/sessionpool.cpp:335 #10 0x0809dd4c in SessionPool::qt_static_metacall (_o=0x8d52c88, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfaeb2c4) at ./sessionpool.moc:94 [...] #12 0x080886af in PasswordRequesterInterface::done (this=0x8d52d38, _t1=0, _t2=...) at ./passwordrequesterinterface.moc:118 #13 0x080663cf in SettingsPasswordRequester::onPasswordRequestCompleted (this=0x8d52d38, password=..., userRejected=false) at ../../../resources/imap/settingspasswordrequester.cpp:89 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 310700] Multiple actions in one filter not applied correctly
https://bugs.kde.org/show_bug.cgi?id=310700 --- Comment #6 from Nick Leverton n...@leverton.org --- Created attachment 77838 -- https://bugs.kde.org/attachment.cgi?id=77838action=edit Export of all filters -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 310700] Multiple actions in one filter not applied correctly
https://bugs.kde.org/show_bug.cgi?id=310700 --- Comment #7 from Nick Leverton n...@leverton.org --- I've just realised kmail offers an export filter button so I'm attaching the results of that. Since the above I've added spam filters using the Spam wizard. These are in the export also. Now I am getting two copies of each detected spam in the JunkMail folder. There is one which has passed through spamc and been wrapped, and this is correctly marked read. There is also one copy which has no spamc headers or wrapping and this is not marked read. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 305987] Could not create collection when adding new top-level mailbox for IMAP account:
https://bugs.kde.org/show_bug.cgi?id=305987 --- Comment #8 from Nick Leverton n...@leverton.org --- Still happening in 4.10.0, I'm afraid. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 279115] Standard Mailing list doesn't thread properly
https://bugs.kde.org/show_bug.cgi?id=279115 Nick Leverton n...@leverton.org changed: What|Removed |Added CC||n...@leverton.org --- Comment #7 from Nick Leverton n...@leverton.org --- Still an issue in 4.11.1.For instance if you are added to a BZ (any bug on any bugzilla, not just KDE's) at some point after the bug was opened, kmail will ignore the References header and will show any subsequent mails from that bug as individual at the top level, instead of threading them. This results in the unthreaded mails flooding out the view of the mailbox. My threading settings are set to Perfect, References and Subject -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 286692] Kmail doesn't show attachment icon in message list.
https://bugs.kde.org/show_bug.cgi?id=286692 --- Comment #10 from Nick Leverton n...@leverton.org --- Still an issue in 4.11.1. It seems that Kmail and/or Akonadi is trying to do something but DIMAP Exchange is replying with an error, as I am now getting the following notification when I do anything that involves a property change Resource: Store failed, server replied A001710 BAD Command Argument Error: 11 The A-number varies, I've seen A001710, A001871 and A05, presumably that is IMAP ID-related. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail] [Bug 129973] References threading breaks when original message is not available
https://bugs.kde.org/show_bug.cgi?id=129973 Nick Leverton n...@leverton.org changed: What|Removed |Added CC||n...@leverton.org --- Comment #2 from Nick Leverton n...@leverton.org --- Still an issue in 4.11.1 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail] [Bug 245924] KMail becomes very slow by rare symbols in email
https://bugs.kde.org/show_bug.cgi?id=245924 --- Comment #2 from Nick Leverton n...@leverton.org --- Created attachment 82371 -- https://bugs.kde.org/attachment.cgi?id=82371action=edit Demonstration mbox file. Still an issue in KDE 4.11.1. Good spot that the problem is the renderer, but problem there is that Kmail doesn't seem to allow choosing webkit, and always uses khtml. (if I'm wrong then tell me how !). So html mails with even a few non-Western chars (in my case Korean) can take a substantial time to render, during which time Kmail2 is frozen and unresponsive. See the attached sample, which has been anonymised by replacing Latin characters with 'x' but leaving the Korean ones in place. When choosing this mail to display, Kmail2 hangs stone cold unresponsive for almost 30 seconds until it has rendered it. I do have suitable fonts installed. Perhaps this bug should be duplicated, once for kmail to use a better renderer and once for khtml to fix its issue ? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 310700] Multiple actions in one filter not applied correctly
https://bugs.kde.org/show_bug.cgi?id=310700 Nick Leverton n...@leverton.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Nick Leverton n...@leverton.org --- Seems to be fixed in 4.11.2, thankyou. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 350139] Akregator Crashes when open specific article
https://bugs.kde.org/show_bug.cgi?id=350139 Nick Leverton n...@leverton.org changed: What|Removed |Added CC||n...@leverton.org --- Comment #1 from Nick Leverton n...@leverton.org --- This crash looks to be in libjasper, not in KDE's own code. I recently bugged a very similar crash as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792226 Is jasper still maintained upstream ? It has had no release for 8 years, despite being the subject of many CVEs, and has no bugzilla. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail] [Bug 130773] unread messages in ignored threads are not marked as read on IMAP server
https://bugs.kde.org/show_bug.cgi?id=130773 Nick Leverton <n...@leverton.org> changed: What|Removed |Added CC||n...@leverton.org --- Comment #19 from Nick Leverton <n...@leverton.org> --- This is still an issue in KDE 4.14. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 212897] Option to mark ignored messages read
https://bugs.kde.org/show_bug.cgi?id=212897 Nick Leverton <n...@leverton.org> changed: What|Removed |Added CC||n...@leverton.org --- Comment #6 from Nick Leverton <n...@leverton.org> --- Seems to have missed the cut for kmail on KDE4, any chance of getting this done before KDE5 please ? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 163573] Akregator crashed while clicking an article title
https://bugs.kde.org/show_bug.cgi?id=163573 --- Comment #37 from Nick Leverton <n...@leverton.org> --- I too have had no occurrence since updating to akregator 4.14, happy to mark it closed. -- You are receiving this mail because: You are the assignee for the bug.
