[Akonadi] [Bug 421614] akonadiserver segfaults everytime it is stopped
https://bugs.kde.org/show_bug.cgi?id=421614 Tamer Hassan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Tamer Hassan --- obviously a problem with current libmysqlclient21 (8.0.20) in (k)ubuntu not problem with Akonadi See: https://bugs.launchpad.net/bugs/1877504 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 421726] New: kmail crashes when open message with QR code attached
https://bugs.kde.org/show_bug.cgi?id=421726 Bug ID: 421726 Summary: kmail crashes when open message with QR code attached Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mat...@fh-aachen.de Target Milestone: --- Application: kmail (5.14.1 (20.04.0)) (Compiled from sources) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.6.13-gentoo_lorbeer x86_64 Windowing system: X11 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: Clicking on a message with an attached QR code in a png file. Message never gets displayed or marked as read. Happens in akonadiconsole as well. Note the this == 0x0 in Grantlee::TemplateImpl::render The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff72dade040 (LWP 214996))] Thread 50 (Thread 0x7ff63aeaa700 (LWP 215095)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5584ce08b444) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5584ce08b3f0, cond=0x5584ce08b418) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5584ce08b418, mutex=0x5584ce08b3f0) at pthread_cond_wait.c:638 #3 0x7ff7275c4d1b in () at /usr/lib64/dri/radeonsi_dri.so #4 0x7ff7275c4927 in () at /usr/lib64/dri/radeonsi_dri.so #5 0x7ff73ea0a000 in start_thread (arg=) at pthread_create.c:477 #6 0x7ff741211a6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 49 (Thread 0x7ff651207700 (LWP 215094)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5584cde22d60) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5584cde22d10, cond=0x5584cde22d38) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5584cde22d38, mutex=0x5584cde22d10) at pthread_cond_wait.c:638 #3 0x7ff7275c4d1b in () at /usr/lib64/dri/radeonsi_dri.so #4 0x7ff7275c4927 in () at /usr/lib64/dri/radeonsi_dri.so #5 0x7ff73ea0a000 in start_thread (arg=) at pthread_create.c:477 #6 0x7ff741211a6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 48 (Thread 0x7ff651e08700 (LWP 215093)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5584cdda95e0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5584cdda9590, cond=0x5584cdda95b8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5584cdda95b8, mutex=0x5584cdda9590) at pthread_cond_wait.c:638 #3 0x7ff7275c4d1b in () at /usr/lib64/dri/radeonsi_dri.so #4 0x7ff7275c4927 in () at /usr/lib64/dri/radeonsi_dri.so #5 0x7ff73ea0a000 in start_thread (arg=) at pthread_create.c:477 #6 0x7ff741211a6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 47 (Thread 0x7ff652ffd700 (LWP 215089)): #0 0x7ff741206d8f in __GI___poll (fds=0x7ff648004a30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff73dfc700e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff73dfc712f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff741887c6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff74183044b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff74167b09e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ff74167c0ef in () at /usr/lib64/libQt5Core.so.5 #7 0x7ff73ea0a000 in start_thread (arg=) at pthread_create.c:477 #8 0x7ff741211a6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 46 (Thread 0x7ff6537fe700 (LWP 215075)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7ff6537fd978) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7ff6537fd928, cond=0x7ff6537fd950) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7ff6537fd950, mutex=0x7ff6537fd928) at pthread_cond_wait.c:638 #3 0x7ff738346d2c in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x in () Thread 45 (Thread 0x7ff653fff700 (LWP 215058)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7ff653ffe978) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7ff653ffe928, cond=0x7ff653ffe950) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7ff653ffe950, mutex=0x7ff653ffe928) at pthread_cond_wait.c:638 #3 0x7ff738346d2c in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x in () Th
[kmail2] [Bug 421726] kmail crashes opening message with QR code attached
https://bugs.kde.org/show_bug.cgi?id=421726 Victor Mataré changed: What|Removed |Added Summary|kmail crashes when open |kmail crashes opening |message with QR code|message with QR code |attached|attached -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 421726] kmail crashes opening message with QR code attached
https://bugs.kde.org/show_bug.cgi?id=421726 --- Comment #1 from Victor Mataré --- On a second look at the backtrace, it's probably not the QR code, but the attached APPLE_WALLET.pkpass file. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 421726] kmail crashes opening message with QR code attached
https://bugs.kde.org/show_bug.cgi?id=421726 Victor Mataré changed: What|Removed |Added Version|unspecified |5.14.1 Platform|Compiled Sources|Gentoo Packages -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 388726] kmail crashes for addresses containing unusual characters
https://bugs.kde.org/show_bug.cgi?id=388726 stefan.schwar...@gmx.net changed: What|Removed |Added Platform|Debian unstable |Debian testing Version|5.7.2 |5.12.3 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Akonadi] [Bug 421664] Sending email does not work with XOAUTH2
https://bugs.kde.org/show_bug.cgi?id=421664 Arne Spiegelhauer changed: What|Removed |Added CC||gm2@gmail.com --- Comment #1 from Arne Spiegelhauer --- Same history for me. Sending stops working exactly when the access token acquired at startup or restart expires. Apparently the software responsible for transferring the message from the Outbox to the smtp server does not handle access token expiry correctly. akonadi and kmail version 19.04.0 -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 413349] akonadi_imap_resource segmentation fault when trying to modify receiving account on sqlite3 backend
https://bugs.kde.org/show_bug.cgi?id=413349 Christoph Feck changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 406240] Hour for TODO won't change on KDE NEON
https://bugs.kde.org/show_bug.cgi?id=406240 --- Comment #3 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.
[korganizer] [Bug 412506] Adding new events always takes the whole day
https://bugs.kde.org/show_bug.cgi?id=412506 --- Comment #4 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.
[korganizer] [Bug 405857] KOrganizer Calendar event time not saved
https://bugs.kde.org/show_bug.cgi?id=405857 --- 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.
