[kontact] [Bug 320247] New: Kmail2 crash when using folder quick search bar
https://bugs.kde.org/show_bug.cgi?id=320247 Bug ID: 320247 Summary: Kmail2 crash when using folder quick search bar Classification: Unclassified Product: kontact Version: 4.10.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: future...@delorean.net Application: kontact (4.10.3) KDE Platform Version: 4.10.3 release 563 Qt Version: 4.8.4 Operating System: Linux 3.7.10-1.4-desktop x86_64 Distribution: openSUSE 12.3 (x86_64) -- Information about the crash: As I started to type in the folder quick search bar, the Kmail2 crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f04ea6fd7c0 (LWP 13851))] Thread 4 (Thread 0x7f04ce186700 (LWP 13852)): #0 0x7f04e1e4b964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f04e6e642f0 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f04e6e64329 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f04e1e47e0f in start_thread () from /lib64/libpthread.so.0 #4 0x7f04e7c447dd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f048d883700 (LWP 13853)): #0 0x7f04e1e4b964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f04e6be2157 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f04e6e8b81e in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f04e1e47e0f in start_thread () from /lib64/libpthread.so.0 #4 0x7f04e7c447dd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f047c15c700 (LWP 13856)): #0 0x7f04e7c3b87d in poll () from /lib64/libc.so.6 #1 0x7f04e0e3baa4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f04e0e3bbc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f04e90732e6 in QEventDispatcherGlib::processEvents (this=0x7f04740008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f04e9043adf in QEventLoop::processEvents (this=this@entry=0x7f047c15bdc0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f04e9043d68 in QEventLoop::exec (this=0x7f047c15bdc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f04e8f460f0 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #7 0x7f04e8f490cc in QThreadPrivate::start (arg=0x1377da0) at thread/qthread_unix.cpp:338 #8 0x7f04e1e47e0f in start_thread () from /lib64/libpthread.so.0 #9 0x7f04e7c447dd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f04ea6fd7c0 (LWP 13851)): [KCrash Handler] #6 0x7f04e9a958ed in sibling (acolumn=optimized out, arow=optimized out, this=optimized out) at /usr/include/QtCore/qabstractitemmodel.h:396 #7 KSelectionProxyModelPrivate::mapTopLevelToSource (this=this@entry=0x1d399f0, row=5, column=0) at /usr/src/debug/kdelibs-4.10.3/kdeui/itemviews/kselectionproxymodel.cpp:1625 #8 0x7f04e9a95b13 in KSelectionProxyModel::mapToSource (this=0x1d34300, proxyIndex=...) at /usr/src/debug/kdelibs-4.10.3/kdeui/itemviews/kselectionproxymodel.cpp:2151 #9 0x7f04e9a905fd in KSelectionProxyModel::data (this=0x1d34300, index=..., role=57) at /usr/src/debug/kdelibs-4.10.3/kdeui/itemviews/kselectionproxymodel.cpp:2255 #10 0x7f04e42653db in Akonadi::FavoriteCollectionsModel::data (this=0x1d34300, index=..., role=optimized out) at /usr/src/debug/kdepimlibs-4.10.3/akonadi/favoritecollectionsmodel.cpp:224 #11 0x7f04e90382cf in data (arole=optimized out, this=optimized out) at kernel/qabstractitemmodel.h:402 #12 QPersistentModelIndex::data (this=optimized out, role=optimized out) at kernel/qabstractitemmodel.cpp:388 #13 0x7f04e42c509d in Akonadi::DelegateAnimator::timerEvent (this=0x1d39e20, event=optimized out) at /usr/src/debug/kdepimlibs-4.10.3/akonadi/progressspinnerdelegate.cpp:63 #14 0x7f04e90595ac in QObject::event (this=0x1d39e20, e=optimized out) at kernel/qobject.cpp:1165 #15 0x7f04e83ee86c in QApplicationPrivate::notify_helper (this=this@entry=0x137dd70, receiver=receiver@entry=0x1d39e20, e=e@entry=0x7fff45c5a920) at kernel/qapplication.cpp:4562 #16 0x7f04e83f2ceb in QApplication::notify (this=0x7fff45c5ad20, receiver=0x1d39e20, e=0x7fff45c5a920) at kernel/qapplication.cpp:4423 #17 0x7f04e9aab146 in KApplication::notify (this=0x7fff45c5ad20, receiver=0x1d39e20, event=0x7fff45c5a920) at /usr/src/debug/kdelibs-4.10.3/kdeui/kernel/kapplication.cpp:311 #18 0x7f04e9044d8e in QCoreApplication::notifyInternal (this=0x7fff45c5ad20, receiver=0x1d39e20, event=0x7fff45c5a920) at kernel/qcoreapplication.cpp:946 #19 0x7f04e9075b61 in sendEvent (event=0x7fff45c5a920, receiver=optimized out) at kernel/qcoreapplication.h:231 #20 QTimerInfoList::activateTimers (this=0x1375c60) at kernel/qeventdispatcher_unix.cpp:637 #21 0x7f04e9072c54 in timerSourceDispatch
[Akonadi] [Bug 318281] KMail doesn´t respond: ItemRetrieverException : Unable to retrieve item from resource
https://bugs.kde.org/show_bug.cgi?id=318281 luisfe lftab...@yahoo.es changed: What|Removed |Added CC||lftab...@yahoo.es --- Comment #4 from luisfe lftab...@yahoo.es --- I can confirm this behavior with kde master compiled over debian stable. -- 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 320260] New: kwallet asks for password each time kmail is started
https://bugs.kde.org/show_bug.cgi?id=320260 Bug ID: 320260 Summary: kwallet asks for password each time kmail is started Classification: Unclassified Product: kmail2 Version: 4.10.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mtm...@freemail.hu With the old kmail it was possible to store pop3 and imap passwords in the config file. Kmail2 requires the use of kwallet, for which I had to set an empty password, because I don't want to type a password each time I start kmail. Is the new method more secure or less secure? 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
[Akonadi] [Bug 320180] continuous network traffic generated
https://bugs.kde.org/show_bug.cgi?id=320180 --- Comment #1 from miklos mtm...@freemail.hu --- Created attachment 80068 -- https://bugs.kde.org/attachment.cgi?id=80068action=edit wireshark-kmail.png I monitored it with Wireshark for a while. It seems that immediately after client hello the client closes the connection (FIN), and initiates a new connection. Then comes an application data from the server in the old connection for which the client answers with RST (stupid *and* rude). This goes on in an infinite loop until I kill the akonadi_imap process or I have kmail restart it in the settings dialog. -- 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
[kdelibs] [Bug 272413] Akonadi crash
https://bugs.kde.org/show_bug.cgi?id=272413 David Edmundson k...@davidedmundson.co.uk changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #2 from David Edmundson k...@davidedmundson.co.uk --- Marking as waiting for information from comment #1 -- 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 320180] continuous network traffic generated
https://bugs.kde.org/show_bug.cgi?id=320180 --- Comment #2 from miklos mtm...@freemail.hu --- Now I see that I forgot the best part of it: interval mail checking is not enabled, so it shouldn't even do anything in the first place. Especially if kmail is already closed. -- 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
[akregator] [Bug 320267] New: mk4storage plugin crash in akregator
https://bugs.kde.org/show_bug.cgi?id=320267 Bug ID: 320267 Summary: mk4storage plugin crash in akregator Classification: Unclassified Product: akregator Version: 4.10.3 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ross...@inwind.it Application: akregator (4.10.3) KDE Platform Version: 4.10.3 (Compiled from sources) Qt Version: 4.8.4 Operating System: Linux 3.10.0-rc2-wl-00351-gf7b2164 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I'm just trying to start akregator after the system have crashed due to a kernel bug. It seems the akregator data or similar got corrupted because at each startup I get the crash. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [KCrash Handler] #6 __memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:98 #7 0x7fc2579e8fab in c4_Column::CopyData (this=0x4d7bd48, to_=optimized out, from_=1044480, count_=2286) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/plugins/mk4storage/metakit/src/column.cpp:304 #8 0x7fc2579e9900 in c4_Column::Grow (this=0x4d7bd48, off_=optimized out, diff_=14) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/plugins/mk4storage/metakit/src/column.cpp:555 #9 0x7fc2579f1515 in c4_FormatB::SetOne (this=0x4d7bd30, index_=42775, xbuf_=..., ignoreMemos_=optimized out) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/plugins/mk4storage/metakit/src/format.cpp:607 #10 0x7fc2579f1641 in c4_FormatS::Set (this=optimized out, index_=optimized out, buf_=...) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/plugins/mk4storage/metakit/src/format.cpp:862 #11 0x7fc257a020f8 in c4_Sequence::Set (this=0x4e5abc0, index_=42775, prop_=..., buf_=...) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/plugins/mk4storage/metakit/src/viewx.cpp:334 #12 0x7fc2579f9be0 in c4_HashViewer::SetItem (this=0x5584d60, row_=42775, col_=1, buf_=...) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/plugins/mk4storage/metakit/src/remap.cpp:365 #13 0x7fc257a024d2 in c4_Sequence::SetAt (this=0x574a210, index_=42775, newElem_=...) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/plugins/mk4storage/metakit/src/viewx.cpp:103 #14 0x7fc257a07bc1 in SetAt (newElem_=..., index_=42775, this=optimized out) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/plugins/mk4storage/metakit/include/mk4.inl:88 #15 Akregator::Backend::FeedStorageMK4Impl::setTitle (this=0x4e599a0, guid=..., title=...) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/plugins/mk4storage/feedstoragemk4impl.cpp:475 #16 0x7fc27517c98b in Akregator::Article::Private::Private (this=0x1984efb0, article=..., feed_=optimized out, archive_=optimized out) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/src/article.cpp:179 #17 0x7fc27517d760 in Akregator::Article::Article (this=0x7fff3a5bc360, article=..., feed=0x4e5a350) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/src/article.cpp:245 #18 0x7fc275180f5e in Akregator::Feed::appendArticles (this=0x4e5a350, feed=...) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/src/feed.cpp:482 #19 0x7fc2751823eb in Akregator::Feed::fetchCompleted (this=0x4e5a350, l=optimized out, doc=..., status=optimized out) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3/akregator/src/feed.cpp:678 #20 0x7fc27518276c in Akregator::Feed::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at /mnt/data/portage/kde-base/akregator-4.10.3/work/akregator-4.10.3_build/akregator/src/feed.moc:87 #21 0x7fc2733bfc71 in QMetaObject::activate (sender=0x4764c00, m=optimized out, local_signal_index=optimized out, argv=0x7fff3a5bc6e0) at kernel/qobject.cpp:3539 #22 0x7fc26f2710c2 in Syndication::Loader::loadingComplete (this=optimized out, _t1=0x4764c00, _t2=..., _t3=Syndication::Success) at /var/tmp/portage/kde-base/kdepimlibs-4.10.3/work/kdepimlibs-4.10.3_build/syndication/moc_loader.cpp:105 #23 0x7fc26f2c588f in Syndication::Loader::slotRetrieverDone (this=0x4764c00, data=..., success=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.10.3/work/kdepimlibs-4.10.3/syndication/loader.cpp:157 #24 0x7fc26f27116d in Syndication::Loader::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at
[Akonadi] [Bug 289097] error Unable to fetch item from backend when entering IMAP folder
https://bugs.kde.org/show_bug.cgi?id=289097 Kapcsándi István istvan.kapcsa...@gmail.com changed: What|Removed |Added CC|istvan.kapcsa...@gmail.com | -- 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
[knode] [Bug 8206] offline functionality
https://bugs.kde.org/show_bug.cgi?id=8206 Richard L richard.l...@gmail.com changed: What|Removed |Added CC||richard.l...@gmail.com -- 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 316816] New mail notification is always delayed
https://bugs.kde.org/show_bug.cgi?id=316816 miklos mtm...@freemail.hu changed: What|Removed |Added CC||mtm...@freemail.hu --- Comment #2 from miklos mtm...@freemail.hu --- In kmail1 there was no delay, yet all filters were correctly applied between fetching the mail and displaying the notification. BTW fetching the mail was about 1 second from 3 pop3 and 2 imap accounts, now with akonadi it's about 10 times slower. How can this bug be reopened? -- 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
[knode] [Bug 8206] offline functionality
https://bugs.kde.org/show_bug.cgi?id=8206 --- Comment #19 from Richard L richard.l...@gmail.com --- (In reply to comment #18) Any news for the offline functionality? Not *yet*! ;-) Actually, is there currently (as of 2013) an active dev for Knode? -- 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 320272] New: Crash while entering google account data
https://bugs.kde.org/show_bug.cgi?id=320272 Bug ID: 320272 Summary: Crash while entering google account data Classification: Unclassified Product: Akonadi Version: 4.10 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Google Resource Assignee: dvra...@redhat.com Reporter: k...@hoffmanndigital.de CC: kdepim-bugs@kde.org Application: akonadi_googlecalendar_resource (4.10) KDE Platform Version: 4.10.2 release 1 Qt Version: 4.8.4 Operating System: Linux 3.7.10-1.4-desktop x86_64 Distribution: openSUSE 12.3 (x86_64) -- Information about the crash: - What I was doing when the application crashed: type in my account data for google account the second time after relogin to the PC It's happend just a second after confirming the authorization token from the login before. The crash can be reproduced sometimes. -- Backtrace: Application: Google Calendars and Tasks (akonadi_googlecalendar_resource), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f8a132d4780 (LWP 1324))] Thread 4 (Thread 0x7f89fdd37700 (LWP 8508)): #0 0x7f8a0ec4e964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8a0a5417c7 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f8a0a5417f9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f8a0ec4ae0f in start_thread () from /lib64/libpthread.so.0 #4 0x7f8a0fe817dd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f89fd41e700 (LWP 8509)): #0 0x7f8a0fe7887d in poll () from /lib64/libc.so.6 #1 0x7f8a0e0feaa4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8a0e0febc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8a1270e1f6 in QEventDispatcherGlib::processEvents (this=0x7f89f80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f8a126de9ef in QEventLoop::processEvents (this=this@entry=0x7f89fd41de00, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f8a126dec78 in QEventLoop::exec (this=0x7f89fd41de00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f8a125e10f0 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #7 0x7f8a125e40cc in QThreadPrivate::start (arg=0x29f1280) at thread/qthread_unix.cpp:338 #8 0x7f8a0ec4ae0f in start_thread () from /lib64/libpthread.so.0 #9 0x7f8a0fe817dd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f89b7663700 (LWP 9645)): #0 0x7f8a0fe7887d in poll () from /lib64/libc.so.6 #1 0x7f8a0e0feaa4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8a0e0febc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8a1270e1f6 in QEventDispatcherGlib::processEvents (this=0x7f89a8002c50, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f8a126de9ef in QEventLoop::processEvents (this=this@entry=0x7f89b7662e00, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f8a126dec78 in QEventLoop::exec (this=0x7f89b7662e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f8a125e10f0 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #7 0x7f8a125e40cc in QThreadPrivate::start (arg=0x36b5210) at thread/qthread_unix.cpp:338 #8 0x7f8a0ec4ae0f in start_thread () from /lib64/libpthread.so.0 #9 0x7f8a0fe817dd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8a132d4780 (LWP 1324)): [KCrash Handler] #6 QSharedDataPointer (o=..., this=0x748c28f0) at /usr/include/QtCore/qshareddata.h:93 #7 assignEntityPrivate (one=..., other=...) at /usr/src/debug/kdepimlibs-4.10.2/akonadi/entity.cpp:49 #8 0x7f8a12d8829d in Akonadi::Entity::Entity (this=0x298a160, other=...) at /usr/src/debug/kdepimlibs-4.10.2/akonadi/entity.cpp:56 #9 0x7f8a12d9df22 in Akonadi::Entity::setParentCollection (this=0x748c29c0, parent=...) at /usr/src/debug/kdepimlibs-4.10.2/akonadi/entity.cpp:199 #10 0x0042115f in ?? () #11 0x7f8a126f51af in QMetaObject::activate (sender=0x28b8b50, m=optimized out, local_signal_index=optimized out, argv=0x748c2bf0) at kernel/qobject.cpp:3548 #12 0x7f8a11292c8f in KJob::finished (this=this@entry=0x28b8b50, _t1=_t1@entry=0x28b8b50) at /usr/src/debug/kdelibs-4.10.2/build/kdecore/kjob.moc:187 #13 0x7f8a11292ed5 in KJob::emitResult (this=0x28b8b50) at /usr/src/debug/kdelibs-4.10.2/kdecore/jobs/kjob.cpp:316 #14 0x7f8a126f51af in QMetaObject::activate (sender=0x2909460, m=optimized out, local_signal_index=optimized out, argv=0x748c2d50) at kernel/qobject.cpp:3548 #15 0x7f8a10cde872 in KGAPI::AccessManager::requestFinished(KGAPI::Request*) () from /usr/lib64/libkgapi.so.0 #16 0x7f8a10ce36b0 in ?? () from /usr/lib64/libkgapi.so.0 #17 0x7f8a126f51af in QMetaObject::activate
[knode] [Bug 8206] offline functionality
https://bugs.kde.org/show_bug.cgi?id=8206 --- Comment #20 from Christophe Giboudeaux cgiboude...@gmx.com --- No, he's not active since... ages -- 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 319033] Akonadi/IMAP crashed after canceling dozens of certificate-accept dialogues
https://bugs.kde.org/show_bug.cgi?id=319033 --- Comment #3 from Christopher Yeleighton giecr...@stegny.2a.pl --- Created attachment 80082 -- https://bugs.kde.org/attachment.cgi?id=80082action=edit New crash information added by DrKonqi akonadi_imap_resource (4.10) on KDE Platform 4.10.2 release 1 using Qt 4.8.4 - What I was doing when the application crashed: I started the new account wizard to add an IMAP account based on my e-mail address. -- Backtrace (Reduced): #7 0x7ff01b7644b7 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=0x7ff01b789d3e sslErrorHandlerResponse, obj=optimized out) at /usr/include/QtCore/qobjectdefs.h:434 #8 KIMAP::SessionPrivate::handleSslError (this=0x173c6b0, errorData=...) at /usr/src/debug/kdepimlibs-4.10.2/kimap/session.cpp:121 #9 0x7ff01cd4268e in QObject::event (this=0x16793e0, e=optimized out) at kernel/qobject.cpp:1203 #10 0x7ff01beba86c in QApplicationPrivate::notify_helper (this=this@entry=0x139d5c0, receiver=receiver@entry=0x16793e0, e=e@entry=0x7ff00411e780) at kernel/qapplication.cpp:4562 #11 0x7ff01bebeceb in QApplication::notify (this=0x7fffe30683e0, receiver=0x16793e0, e=0x7ff00411e780) at kernel/qapplication.cpp:4423 -- 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 312074] kmail can not detect mailing lists in imap folders
https://bugs.kde.org/show_bug.cgi?id=312074 --- Comment #8 from Colin J Thomson co...@g6avk.demon.co.uk --- OK, just had some Email in from a non yahoogroup with my dIMAP account and detection of that mailing list worked no problem, here are the relevent parts of the header: Reply-To:*-* *-*@hotmail.com List-Id: knightsqrss_cnts.be.cnts.be List-Unsubscribe: http://mail.cnts.be/mailman/options/knightsqrss_cnts.be, mailto:knightsqrss-requ...@cnts.be?subject=unsubscribe List-Archive: http://mail.cnts.be/mailman/private/knightsqrss_cnts.be/ List-Post: mailto:knightsq...@cnts.be List-Help: mailto:knightsqrss-requ...@cnts.be?subject=help List-Subscribe: http://mail.cnts.be/mailman/listinfo/knightsqrss_cnts.be, mailto:knightsqrss-requ...@cnts.be?subject=subscribe -- 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 320280] New: External Editor Launched Prematurely and Without Signature
https://bugs.kde.org/show_bug.cgi?id=320280 Bug ID: 320280 Summary: External Editor Launched Prematurely and Without Signature Classification: Unclassified Product: kmail2 Version: 4.10.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: gtwilli...@gmail.com Selecting Message - New Message results in the composition window and immediately starts the external editor. This is different from all previous releases. I used to have to place the cursor into the edit area and hit any key to launch my editor. Furthermore, the edit buffer I get omits my signature. I have to type it in by hand. If I save and exit my editor and then press a key in the composer area again, the full edit buffer, including my signature is loaded in my editor. Reproducible: Always Steps to Reproduce: 1. Configure an external editor for the composer 2. Either reply to a message or create a new message 3. Actual Results: Composer window is displayed and the external editor is started immediately. The editor's buffer does not contain the signature that appears in the composer window. Expected Results: The composer window is started and the focus is in the headers. I can complete the subject and headers and then move to the edit area and hit a key to start the external editor. The external editor will contain my signature. Platform Version 4.10.3 $ kmail --version Qt: 4.8.4 KDE Development Platform: 4.10.3 KMail: 4.10.3 $ uname -a Linux vfr 3.8.9-200.fc18.x86_64 #1 SMP Fri Apr 26 12:50:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ -- 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 320272] Crash while entering google account data
https://bugs.kde.org/show_bug.cgi?id=320272 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jekyll Wu adap...@gmail.com --- *** This bug has been marked as a duplicate of bug 301647 *** -- 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
