[Akonadi] [Bug 397140] New: akonadi gets stuck downloading new emails
https://bugs.kde.org/show_bug.cgi?id=397140 Bug ID: 397140 Summary: akonadi gets stuck downloading new emails Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: aar...@doofus.org Target Milestone: --- I consistently have problems where akonadi gets stuck downloading emails for my work email account. I see this problem with multiple computers. I have to manually run 'akonadictl restart' in order for it to begin picking up new email messages again. I have run akonadictl fsck and akonadictl vacuum on multiple occasions and that does not help. This has been going on for at least a couple of years and I'm currently running 17.12.3 as is shipped with OpenSUSE 15.0. My email account is hosted by Microsoft's office365 service. I have a lot of emails, with over 58,800 emails in my inbox, most marked read. I rarely, if ever, see this problem with my home imap server where I have several hundred thousand emails stored which uses Cyrus imap. I can reproduce this problem with three different computers. For office365 the connection uses STARTTLS with plain authentication. The server info is: IMAP4 IMAP4REV1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+ -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397131] New: kmail crash due to MonitorPrivate::emitItemsNotification accessing empty items
https://bugs.kde.org/show_bug.cgi?id=397131
Bug ID: 397131
Summary: kmail crash due to
MonitorPrivate::emitItemsNotification accessing empty
items
Product: Akonadi
Version: GIT (master)
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: kol...@aon.at
Target Milestone: ---
I see kmail crashing after todays update (akonadi @
f7ce8ab4af83b8a64e97e2a8f11c21674cde826c)
The problem is in akonadis MonitorPrivate::emitItemsNotification
implementation, which gets called in line 555 via
if (!items.isEmpty() || itemNtf.operation() ==
Protocol::ItemChangeNotification::Remove || !fetchItems()) {
someoneWasListening = emitItemsNotification(itemNtf, items, parent,
destParent);
}
so obviously items CAN be empty (which it is in the crash case), but
emitItemsNotification()
in line 1064 (and others) uses
case Protocol::ItemChangeNotification::Add:
return emitToListeners(::itemAdded, its.first(), col);
and Qt asserts due to the first() call on the empty list.
The stack I have here is:
1 raise
0x7fa2fad6df67
2 abort
0x7fa2fad6f33a
3 qt_message_fatal qlogging.cpp
1842 0x7fa2fba08f1c
4 QMessageLogger::fatal qlogging.cpp
880 0x7fa2fba08f1c
5 qt_assert qglobal.cpp
3188 0x7fa2fba08576
6 QVector::first qvector.h
237 0x7fa2f48bb98e
7 Akonadi::MonitorPrivate::emitItemsNotification monitor_p.cpp
1064 0x7fa2f48b0f90
8 Akonadi::MonitorPrivate::emitNotification monitor_p.cpp
555 0x7fa2f48ae94c
9 Akonadi::MonitorPrivate::dispatchNotifications monitor_p.cpp
1000 0x7fa2f48b58c5
10 Akonadi::MonitorPrivate::slotNotifymonitor_p.cpp
969 0x7fa2f48b532a
11 Akonadi::MonitorPrivate::handleCommandsmonitor_p.cpp
864 0x7fa2f48b4963
12 Akonadi::Monitor::qt_static_metacall moc_monitor.cpp
338 0x7fa2f48a18b3
13 QObject::event qobject.cpp
1251 0x7fa2fbc07f76
14 QApplicationPrivate::notify_helper qapplication.cpp
3728 0x7fa2fc9821ac
15 QApplication::notify qapplication.cpp
3487 0x7fa2fc988b52
16 QCoreApplication::notifyInternal2 qcoreapplication.cpp
1048 0x7fa2fbbdc8f5
17 QCoreApplication::sendEventqcoreapplication.h
234 0x7fa2fbbdf2be
18 QCoreApplicationPrivate::sendPostedEvents qcoreapplication.cpp
1745 0x7fa2fbbdf2be
19 QEventDispatcherUNIX::processEventsqeventdispatcher_unix.cpp
466 0x7fa2fbc2c5c4
20 QUnixEventDispatcherQPA::processEvents qunixeventdispatcher.cpp 68
0x7fa2d1fbc34d
--
You are receiving this mail because:
You are the assignee for the bug.
[kontact] [Bug 397124] New: Can't select contact at contact list (on click nothing happens)
https://bugs.kde.org/show_bug.cgi?id=397124 Bug ID: 397124 Summary: Can't select contact at contact list (on click nothing happens) Product: kontact Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: contacts Assignee: kdepim-bugs@kde.org Reporter: criss...@gmx.de Target Milestone: --- Created attachment 114283 --> https://bugs.kde.org/attachment.cgi?id=114283=edit Screen shot of kaddressbook with marker I open kaddressbook to lookup contact data. If I click on a contact entry (see red area on attached image), nothing happens instead of showing the details of selected contact. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 395675] Timezone Does not sync correctly via caldav
https://bugs.kde.org/show_bug.cgi?id=395675 --- Comment #2 from Christoph Feck --- For KDE software that has multiple maintainers, it could be from a few hours upto a few days before someone looks at it. For KDE software that has a single maintainer, it could be several days upto several weeks. For KDE software that has no maintainer, it can be up to several years for someone to notice. Note that korganizer doesn't currently have a maintainer. -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 334138] when creates a new note knotes create two and then a warning appear and the note is not saved
https://bugs.kde.org/show_bug.cgi?id=334138 Christoph Feck changed: What|Removed |Added Version Fixed In|5.8.0 |5.9.0 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 396573] Akonadi is utterly broken for an IMAP account since 5.8.2
https://bugs.kde.org/show_bug.cgi?id=396573 --- Comment #3 from Martin Ottmar --- Almost two months without my favorite IMAP account. :-O Akonadi has been "fixed" by adding iptables permanent DROP rule for OUTPUT packets to the broken IMAP server. It "fixes" everything strange meant above, except the IMAP account itself, of course, which behaves as disconnected now. So, akonadi and the KDE workspace are usable together again. -- You are receiving this mail because: You are the assignee for the bug.
