[Akonadi] [Bug 410872] Kmail reports "Could not read the password" when trying to set an IMAP account online
https://bugs.kde.org/show_bug.cgi?id=410872 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.
[kontact] [Bug 377916] reverse order of events in summary
https://bugs.kde.org/show_bug.cgi?id=377916 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 405922] Very frequent akonadi crash in QLocale::dayName
https://bugs.kde.org/show_bug.cgi?id=405922 David Faure changed: What|Removed |Added CC||fa...@kde.org Summary|Very frequent akonadi crash |Very frequent akonadi crash ||in QLocale::dayName -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 419836] Events with empty UID are present in akonadi console but not showing up in the calendar
https://bugs.kde.org/show_bug.cgi?id=419836 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #8 from Raúl --- Bumped. Debian sid. Kontact 5.14.1 (20.04.0) KDE Frameworks 5.70.0 Qt 5.14.2 I can see the events on akonadiconsole but not on korganizer. I have copied the payload of a working and non-working event in some files which I can send privately to someone interested in debugging this issue. Regards, -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404533] akonadi crashes during startup after non-clean closing of previous X session
https://bugs.kde.org/show_bug.cgi?id=404533 --- Comment #3 from Ahmad Samir --- Thanks for the feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404533] akonadi crashes during startup after non-clean closing of previous X session
https://bugs.kde.org/show_bug.cgi?id=404533 Erik Quaeghebeur changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Erik Quaeghebeur --- (In reply to Ahmad Samir from comment #1) > Is this still an issue? No. I haven't had such a crash recently. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404533] akonadi crashes during startup after non-clean closing of previous X session
https://bugs.kde.org/show_bug.cgi?id=404533 Ahmad Samir changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||a.samir...@gmail.com --- Comment #1 from Ahmad Samir --- Is this still an issue? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409383] akonadi_davgroupware_resource always crashes on startup
https://bugs.kde.org/show_bug.cgi?id=409383 Ahmad Samir changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||a.samir...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Ahmad Samir --- Do you still see this issue? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 425976] mysql.err.old contains lots of errors: "Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varcha
https://bugs.kde.org/show_bug.cgi?id=425976
gran...@tempmail.de changed:
What|Removed |Added
CC||gran...@tempmail.de
--- Comment #2 from gran...@tempmail.de ---
Fixed by:
akonadictl stop
/usr/bin/mysqld --defaults-file=/home/${USER}/.local/share/akonadi/mysql.conf
--datadir=/home/${USER}/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-${USER}-mysql.socket &
mysql --socket=/tmp/akonadi-${USER}-mysql.socket -e 'create database mysql'
mysql_upgrade --socket=/tmp/akonadi-${USER}-mysql.socket
mysqladmin --socket=/tmp/akonadi-${USER}-mysql.socket shutdown
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 426366] New: Can only select 64 folders in search
https://bugs.kde.org/show_bug.cgi?id=426366
Bug ID: 426366
Summary: Can only select 64 folders in search
Product: kmail2
Version: 5.15.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: search
Assignee: kdepim-bugs@kde.org
Reporter: gran...@tempmail.de
Target Milestone: ---
kmail2 5.15.1 (20.08.1)
1. Open search
2. select specific folders
3. select 65 or more
4. dont comment on my amount of folders...
Error:
DATABASE ERROR:
Error code: "1406"
DB error: "Data too long for column 'queryCollections' at row 1"
Error text: "Data too long for column 'queryCollections' at row 1 QMYSQL3:
Unable to execute statement"
Values: QMap((":0", QVariant(QString, ""))(":1", QVariant(QString, ""))(":10",
QVariant(int, -1))(":11", QVariant(int, -1))(":12", QVariant(bool,
false))(":13", QVariant(QString, ""))(":14", QVariant(QString, "{\n
\"limit\": -1,\n\"negated\": false,\n\"rel\": 0,\n\"subTerms\": [\n
{\n\"negated\": false,\n\"rel\": 1,\n
\"subTerms\": [\n{\n\"cond\": 5,\n
\"key\": \"from\",\n\"negated\": false,\n
\"value\": \"something\"\n}\n]\n
}\n]\n}\n"))(":15", QVariant(QString, ""))(":16", QVariant(QString, "130
131 132 133 134 135 136 138 139 140 141 142 143 144 146 147 148 149 150 151 152
153 155 156 157 158 159 160 161 170 171 172 173 174 175 176 187 188 189 190 190
191 191 192 192 193 194 194 196 196 198 199 200 201 202 203 204 217 333 334 335
336 337 338 339"))(":17", QVariant(bool, true))(":18", QVariant(qlonglong,
343))(":2", QVariant(QString, "@something"))(":3", QVariant(qlonglong,
1))(":4", QVariant(qlonglong, 1))(":5", QVariant(bool, true))(":6",
QVariant(int, 2))(":7", QVariant(int, 2))(":8", QVariant(int, 2))(":9",
QVariant(bool, true)))
Query: "UPDATE CollectionTable SET remoteId = :0, remoteRevision = :1, name =
:2, parentId = :3, resourceId = :4, enabled = :5, syncPref = :6, displayPref =
:7, indexPref = :8, cachePolicyInherit = :9, cachePolicyCheckInterval = :10,
cachePolicyCacheTimeout = :11, cachePolicySyncOnDemand = :12,
cachePolicyLocalParts = :13, queryString = :14, queryAttributes = :15,
queryCollections = :16, isVirtual = :17 WHERE ( id = :18 )"
By trial and error combined with bisection :D I came to the conclusion that 65
folders is too much (value 16 (obviously a list of folders) has 65 words, 260
bytes)
With 64 folders it works - could also be a string length problem (but 260 seems
to be a weird boundary - 64 is more sympathic due to the fact that it's a power
of 2)
--
You are receiving this mail because:
You are the assignee for the bug.
[Akonadi] [Bug 409621] new calendar folder not shown on server
https://bugs.kde.org/show_bug.cgi?id=409621 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com, ||vkra...@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409782] Akonadi server crashed on boot
https://bugs.kde.org/show_bug.cgi?id=409782 Ahmad Samir changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Ahmad Samir --- Setting needsinfo. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426363] KMail Showing No Folders or Messages on Startup
https://bugs.kde.org/show_bug.cgi?id=426363 star.b...@posteo.co changed: What|Removed |Added CC||star.b...@posteo.co -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426363] New: KMail Showing No Folders or Messages on Startup
https://bugs.kde.org/show_bug.cgi?id=426363 Bug ID: 426363 Summary: KMail Showing No Folders or Messages on Startup Product: kmail2 Version: 5.15.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: star.b...@posteo.co Target Milestone: --- SUMMARY Since updating to KMail 5.15.1, upon start the UI shows no folders or messages. STEPS TO REPRODUCE 1. Open KMail 2. UI is blank with no messages or folders available to navigate through OBSERVED RESULT No content, either main email account, folders or messages shown in main interface. See https://i.imgur.com/qJh3SrH.png EXPECTED RESULT Regular usage of KMail, including checking, viewing and actioning messages and navigating between account folders. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro-ARM KDE edition (Kernel ver 5.8.3-2-MANJARO-ARM) (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Running on up-to-date Pinebook Pro. Kmail config shows account info and previous setup (connected account password etc. still showing). Issue appears sporadically after aprox. 5-6 launches of KMail and I assume it's a in-app render or display issue as it causes a complete crash of KMail after closing and restarting one time further, -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 425786] akonadi_archivemail_agent (akonadi_archivemail_agent), signal: Segmentation fault - Akonadi::EntityTreeModel::modelIndexForCollection (model=, collection=...)
https://bugs.kde.org/show_bug.cgi?id=425786
--- Comment #6 from Ahmad Samir ---
What I found out so far, the stack trace in comment #1 is a different issue
than the other ones, that one is caused by deleting mInfo in the ArchiveJob
dtor, it looks like a race issue caused by that objected (allocated with new)
having already been deleted in the dtor of ArchiveMailManager, I think this can
be fixed by using shared_ptr to manage ArchiveMailInfo objects which are passed
from ArchiveMailManager too ArchiveJob.
The other stacktraces, are a crash in QObject::metaObject(); proxiesAndModel
from EntityTreeModel, calls qobject_cast which calls QMetaObject::cast:
const QObject *QMetaObject::cast(const QObject *obj) const
{
return (obj && obj->metaObject()->inherits(this)) ? obj : nullptr;
}
the crash happens in obj->metaObject(), I haven't been able to figure out why
exactly that happens.
Steps to reproduce that crash:
- KMail -> Settings -> Configure automatic archiving
- Attach gdb to the running akonadi_archivemail_agent
- Create a new archiving job, OK/Apply
- Wait a while for the scheduled job to fire
- Crash
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 426361] New: Kmail hangs when clicking on mail
https://bugs.kde.org/show_bug.cgi?id=426361 Bug ID: 426361 Summary: Kmail hangs when clicking on mail Product: kmail2 Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ssky...@web.de Target Milestone: --- Application: kmail (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 5.4.0-42-generic x86_64 Distribution: Ubuntu 18.04.5 LTS -- Information about the crash: - What I was doing when the application crashed: Clicked on mail in inbox. Around one to two times a day this leads to a haning kmail. If I close kmail the application crashes. See the attachted stacktrace. I need to run "akonadictl stop" and then start kmail again to get access to the mails again. Normally kmail then works fine until the next Linux reboot. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f585ca5cbc0 (LWP 4050))] Thread 27 (Thread 0x7f5705513700 (LWP 4368)): #0 0x7f584f43d9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5590e0a75c98) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f584f43d9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5590e0a75c48, cond=0x5590e0a75c70) at pthread_cond_wait.c:502 #2 0x7f584f43d9f3 in __pthread_cond_wait (cond=0x5590e0a75c70, mutex=0x5590e0a75c48) at pthread_cond_wait.c:655 #3 0x7f584421cc95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f584421d177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f584421df11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f584421a5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f584f4376db in start_thread (arg=0x7f5705513700) at pthread_create.c:463 #8 0x7f5859b47a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f5705d14700 (LWP 4367)): #0 0x7f584f43d9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5590e0a75c98) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f584f43d9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5590e0a75c48, cond=0x5590e0a75c70) at pthread_cond_wait.c:502 #2 0x7f584f43d9f3 in __pthread_cond_wait (cond=0x5590e0a75c70, mutex=0x5590e0a75c48) at pthread_cond_wait.c:655 #3 0x7f584421cc95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f584421d177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f584421df11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f584421a5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f584f4376db in start_thread (arg=0x7f5705d14700) at pthread_create.c:463 #8 0x7f5859b47a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f5786f49700 (LWP 4366)): #0 0x7f584f43d9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f5840ae5fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f584f43d9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f5840ae5f68, cond=0x7f5840ae5f90) at pthread_cond_wait.c:502 #2 0x7f584f43d9f3 in __pthread_cond_wait (cond=0x7f5840ae5f90, mutex=0x7f5840ae5f68) at pthread_cond_wait.c:655 #3 0x7f58407ef5f4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f58407ef639 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f584f4376db in start_thread (arg=0x7f5786f49700) at pthread_create.c:463 #6 0x7f5859b47a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f578d204700 (LWP 4362)): #0 0x7f5859b3acf9 in __GI___poll (fds=0x7f5788001cb0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f584d7205c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f584d7206dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f585a48388f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f585a42890a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f585a24723a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f585a24c17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f584f4376db in start_thread (arg=0x7f578d204700) at pthread_create.c:463 #8 0x7f5859b47a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f57beffd700 (LWP 4090)): #0 0x7f5859b47d67 in epoll_wait (epfd=69, events=0x7f57a00020f0, maxevents=32, timeout=-1) at
[kleopatra] [Bug 426030] Kleopatra crashes when sign / encrypt a folder
https://bugs.kde.org/show_bug.cgi?id=426030 Christoph Feck changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Christoph Feck --- The backtrace lacks debug symbol information. Please install debug packages for kleopatra and its dependencies and add the updated backtrace. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports If you need help, please ask in a forum of your distribution. -- You are receiving this mail because: You are on the CC list for the bug.
