[akregator] [Bug 407036] New: Akregator close tab crash
https://bugs.kde.org/show_bug.cgi?id=407036 Bug ID: 407036 Summary: Akregator close tab crash Product: akregator Version: 5.11.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jdhayes.li...@gmail.com Target Milestone: --- Application: akregator (5.11.0) Qt Version: 5.12.0 Frameworks Version: 5.57.0 Operating System: Linux 4.15.0-48-generic x86_64 Distribution: KDE neon Plasma LTS Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: I was closing a tab and it crashed, I restarted and tried again and it crashed again. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Illegal instruction Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff75b521bc0 (LWP 7069))] Thread 34 (Thread 0x7ff5fcbf1700 (LWP 7162)): #0 0x7ff757290187 in __GI___libc_write (fd=2, buf=0x7ff5fcbedc40, nbytes=39) at ../sysdeps/unix/sysv/linux/write.c:27 #1 0x7ff75720b1bd in _IO_new_file_write (f=0x7ff75756c680 <_IO_2_1_stderr_>, data=0x7ff5fcbedc40, n=39) at fileops.c:1203 #2 0x7ff75720bb2f in new_do_write (to_do=, data=0x7ff5fcbedc40 "[warn] epoll_wait: Bad file descriptor\n", fp=0x7ff75756c680 <_IO_2_1_stderr_>) at fileops.c:457 #3 0x7ff75720bb2f in _IO_new_file_xsputn (f=0x7ff75756c680 <_IO_2_1_stderr_>, data=, n=39) at fileops.c:1277 #4 0x7ff7571de707 in buffered_vfprintf (s=s@entry=0x7ff75756c680 <_IO_2_1_stderr_>, format=format@entry=0x7ff742eb76a8 "[%s] %s\n", args=args@entry=0x7ff5fcbf0200) at vfprintf.c:2350 #5 0x7ff7571db726 in _IO_vfprintf_internal (s=s@entry=0x7ff75756c680 <_IO_2_1_stderr_>, format=0x7ff742eb76a8 "[%s] %s\n", ap=ap@entry=0x7ff5fcbf0200) at vfprintf.c:1301 #6 0x7ff7572b24c6 in ___fprintf_chk (fp=0x7ff75756c680 <_IO_2_1_stderr_>, flag=1, format=) at fprintf_chk.c:35 #7 0x7ff742e9f9ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #8 0x7ff742e9fb44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #9 0x7ff742ea146c in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #10 0x7ff742e97114 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #11 0x7ff750ca07dd in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7ff750c3749b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7ff750c69d21 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #14 0x7ff750c9ccd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #15 0x7ff74a91f6db in start_thread (arg=0x7ff5fcbf1700) at pthread_create.c:463 #16 0x7ff7572a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 33 (Thread 0x7ff5fd3f2700 (LWP 7161)): #0 0x7ff74a9259f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7ff5fd3f1908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff74a9259f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7ff5fd3f18b8, cond=0x7ff5fd3f18e0) at pthread_cond_wait.c:502 #2 0x7ff74a9259f3 in __pthread_cond_wait (cond=0x7ff5fd3f18e0, mutex=0x7ff5fd3f18b8) at pthread_cond_wait.c:655 #3 0x7ff750c9a0a9 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7ff750c9aae8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7ff750c9ab7f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7ff750c58868 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7ff750c5b387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7ff750c5b9b4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7ff750c9ccd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7ff74a91f6db in start_thread (arg=0x7ff5fd3f2700) at pthread_create.c:463 #11 0x7ff7572a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7ff5fe4f4700 (LWP 7157)): #0 0x7ff74a925ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7ff5fe4f3710, expected=0, futex_word=0x7ff5fe4f38f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7ff74a925ed9 in __pthread_cond_wait_common (abstime=0x7ff5fe4f37b0, mutex=0x7ff5fe4f38a8, cond=0x7ff5fe4f38d0) at pthread_cond_wait.c:533 #2 0x7ff74a925ed9 in __pthread_cond_timedwait (cond=0x7ff5fe4f38d0, mutex=0x7ff5fe4f38a8, abstime=0x7ff5fe4f37b0) at pthread_cond_wait.c:667 #3 0x7ff750c9a177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7ff750c9aada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7ff750c9abc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7ff750c58851 in () at
[korgac] [Bug 407031] korgac immediate crash segfault Disco Dingo
https://bugs.kde.org/show_bug.cgi?id=407031 David Oldford changed: What|Removed |Added Attachment #119699|0 |1 is obsolete|| --- Comment #1 from David Oldford --- Created attachment 119701 --> https://bugs.kde.org/attachment.cgi?id=119701=edit better kcrash info When I purged and reinstalled korganizer I forgot to reinstall the korganizer debug info. This kcrash info is with the debug info. -- You are receiving this mail because: You are the assignee for the bug.
[korgac] [Bug 407031] New: korgac immediate crash segfault Disco Dingo
https://bugs.kde.org/show_bug.cgi?id=407031 Bug ID: 407031 Summary: korgac immediate crash segfault Disco Dingo Product: korgac Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: david_oldf...@hotmail.com Target Milestone: --- Created attachment 119699 --> https://bugs.kde.org/attachment.cgi?id=119699=edit kcrash info SUMMARY STEPS TO REPRODUCE 1. login to plasma or start korganizer or run korgac from commandline OBSERVED RESULT korgac crashes with a segmentation fault and drkonqi starts EXPECTED RESULT korgac would run in the background and provide calendar notifications SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.0.0-13-generic / 5.15.4 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION This system is up to date with kubuntu packages for disco dingo and was upgraded from cosmic cuttlefish. The issue has been present since the upgrade. I've tried uninstalling and reinstalling korganizer with no effect, including using apt purge to remove it. console output: korgac KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = korgac path = /usr/bin pid = 24842 KCrash: Arguments: /usr/bin/korgac KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Stopped korgac -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 344874] username/password not being sent in header
https://bugs.kde.org/show_bug.cgi?id=344874 --- Comment #19 from Thaodan --- Is there a way to always send auth headers? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 344874] username/password not being sent in header
https://bugs.kde.org/show_bug.cgi?id=344874 Lukasz changed: What|Removed |Added CC|dolo...@outlook.com | -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 406946] Akonadi crashes when sending a large attachment
https://bugs.kde.org/show_bug.cgi?id=406946 --- Comment #2 from Aaron Williams --- Unfortunately, I have been unable to get a backtrace. It is very repeatable. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 406154] kmail closes too early
https://bugs.kde.org/show_bug.cgi?id=406154 kwanza.p...@virginmedia.com changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from kwanza.p...@virginmedia.com --- I updated QT to 5.12.3 and KDE apps to 19.04.0 which seems to have fixed the problem. I am not sure which of the two applications was the original culprit. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 407026] Kmail crashes whenever creating a new mail
https://bugs.kde.org/show_bug.cgi?id=407026 --- Comment #2 from Andreas --- I should have mentioned that, in order to exclude inconsistent settings as cause of the crashes, I deleted all kmail/kmail2 relevant settings I have been able to identify in my home directory, except for the akonadi account settings. This does not change the observed result in any way. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 407026] Kmail crashes whenever creating a new mail
https://bugs.kde.org/show_bug.cgi?id=407026 Andreas changed: What|Removed |Added CC||hoheneg...@web.de --- Comment #1 from Andreas --- Created attachment 119698 --> https://bugs.kde.org/attachment.cgi?id=119698=edit Debug trace of kmail for crash during startup (observed when not deleting autosave folder) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 407026] New: Kmail crashes whenever creating a new mail
https://bugs.kde.org/show_bug.cgi?id=407026 Bug ID: 407026 Summary: Kmail crashes whenever creating a new mail Product: kmail2 Version: 5.11.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: hoheneg...@web.de Target Milestone: --- Created attachment 119697 --> https://bugs.kde.org/attachment.cgi?id=119697=edit The command line output observed during new mail crash. SUMMARY Kmail crashes when creating a new mail. STEPS TO REPRODUCE Not sure how to reproduce, but I see the issues on two similar KDE neon installations, so I am wondering why nobody else seems to have reported it. The history of the crash is as follows. I experienced a crash of kmail (for whatever reason; In one case I modified the plugin settings trying to enable language tool grammar check). After the crash kmail did not start anymore (crashing each time at start). I figured that I could fix that with rm -r /home/andreas/.local/share/kmail2/autosave After that kmail can be started again without immediate crash. However, clicking the new mail icon (or pressing a shortcut that would also bring up a new composer window) crashes kmail with the trace below. In the second attachment I provide the trace that I get if I do not remove the autosave directory, in which case kmail crashes right at the start. OBSERVED RESULT Kmail crashes leaving the attached output on the command line. The consequence is that it cannot be used anymore to write and send mail. EXPECTED RESULT Kmail shows a new composer window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.15 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION 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 0x7fef2a5b0bc0 (LWP 20620))] Thread 25 (Thread 0x7fee634e9700 (LWP 20674)): #0 0x7fef1cd89ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fee634e8710, expected=0, futex_word=0x7fee634e88f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fef1cd89ed9 in __pthread_cond_wait_common (abstime=0x7fee634e87b0, mutex=0x7fee634e88a8, cond=0x7fee634e88d0) at pthread_cond_wait.c:533 #2 0x7fef1cd89ed9 in __pthread_cond_timedwait (cond=0x7fee634e88d0, mutex=0x7fee634e88a8, abstime=0x7fee634e87b0) at pthread_cond_wait.c:667 #3 0x7fef11ce9177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fef11ce9ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fef11ce9bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fef11ca7851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fef11caa387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fef11caa974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fef11cebcd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fef1cd836db in start_thread (arg=0x7fee634e9700) at pthread_create.c:463 #11 0x7fef2760688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fee69ac0700 (LWP 20671)): #0 0x7fef1cd899f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fef0d29efb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fef1cd899f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fef0d29ef68, cond=0x7fef0d29ef90) at pthread_cond_wait.c:502 #2 0x7fef1cd899f3 in __pthread_cond_wait (cond=0x7fef0d29ef90, mutex=0x7fef0d29ef68) at pthread_cond_wait.c:655 #3 0x7fef0cfa8844 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fef0cfa8889 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fef1cd836db in start_thread (arg=0x7fee69ac0700) at pthread_create.c:463 #6 0x7fef2760688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fee6a2c1700 (LWP 20666)): #0 0x7fef1cd89ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fee6a2c0710, expected=0, futex_word=0x7fee6a2c08f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fef1cd89ed9 in __pthread_cond_wait_common (abstime=0x7fee6a2c07b0, mutex=0x7fee6a2c08a8, cond=0x7fee6a2c08d0) at pthread_cond_wait.c:533 #2 0x7fef1cd89ed9 in __pthread_cond_timedwait (cond=0x7fee6a2c08d0, mutex=0x7fee6a2c08a8, abstime=0x7fee6a2c07b0) at pthread_cond_wait.c:667 #3 0x7fef11ce9177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fef11ce9ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fef11ce9bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fef11ca7851 in () at
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #7 from Nick --- Created attachment 119696 --> https://bugs.kde.org/attachment.cgi?id=119696=edit akonadictl_fsck_vacuum_after_NULL-RID_cleanup.txt -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #5 from Nick --- Martin, akonadictl version is 5.7.3 kdepim is at level 17.12.3 The levels of all akonadi/kmail/etc installed software and the reports od akonadictl fsck| vacuum are provided as attachments. After the "remoteId is NULL" cleanup I noticed that all those annoyng messages "wait until ..." are gone . I checked my email at the interner provider server and there are no emails there . The IP tech support told me that with IMAP after an email is received by the client[laptop] it is deleted from the server . So I did not understand why the kmail client was checking remote server . Now it appears that kmail/akonadi tries to solve that NULL remoteId . akonadictl fsck's message ' Item "28761" has no RID.' is wrong . That item with id=28761 HAS an RID but its value is set to NULL . It is very strange/misleading message and the culprit seems to be akonadictl and/or kmail because they do not interpret correctly database/table/record's contents . Thanks, Nick -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #6 from Nick --- Created attachment 119695 --> https://bugs.kde.org/attachment.cgi?id=119695=edit akonadi_kmail_kontact_mariadb_installed_software_levels.txt -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 359191] aKregator does not honor LC_TIME / date and time in wrong format
https://bugs.kde.org/show_bug.cgi?id=359191 p...@gmx.com changed: What|Removed |Added CC||p...@gmx.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406958] Unreferenced files in file_db_data
https://bugs.kde.org/show_bug.cgi?id=406958 --- Comment #5 from Christophe Giboudeaux --- I fixed the versions after reading your comment. 18.08 is maybe not a year old but it's 3 releases behind. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 344874] username/password not being sent in header
https://bugs.kde.org/show_bug.cgi?id=344874 --- Comment #18 from Thaodan --- I tried the demo instance and this one works. But still some requests are send without login parameters and return 401 (as expected). Should I set nextcloud to ignore unauthiated requests or something? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406856] Found 3734 items without RID.; Item "30024" has RID and is dirty.
https://bugs.kde.org/show_bug.cgi?id=406856 --- Comment #4 from Martin Steigerwald --- Nick, which version are you testing on? Do you use KDEPIM 18.12 or later by chance? If so could you please update the version number to the output of 'akonadictl --version'? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 Achim Bohnet changed: What|Removed |Added CC||a...@mpe.mpg.de --- Comment #10 from Achim Bohnet --- I've experienced the bug, but with mysql not postgres, on an almost daily basis with all 18.12.* release aka 5.10.* . (I use KDE Neon User) With 18.12.* I've seen again after a long time the multiple merge candidate bugs and suddenly had duzends of items with "no RID". (5.10 almost drive me crazy.) I always assumed that those problems trigger the "mysql server not stopped by 'akonadictl stop'". So I'm not astonished that the bug is to reproducable for everyone. IMHO you should bump the "version" of this bug from 5.6.1 to 5.10.3. Achim -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 Martin Steigerwald changed: What|Removed |Added Version|5.6.1 |5.10.3 --- Comment #11 from Martin Steigerwald --- Achim, thanks. Updated version number. So you see mysqld process around even five minutes after "akonadictl stop"? Please report your findings regarding "items without RID" on: Bug 406856 Found 3734 items without RID.; Item "30024" has RID and is dirty. (Please always put new information on the relevant bug report, to help to keep each bug report concise and to one topic.) I update version number there as well then. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 407017] New: akonadi_maildir_resource crash
https://bugs.kde.org/show_bug.cgi?id=407017 Bug ID: 407017 Summary: akonadi_maildir_resource crash Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Maildir Resource Assignee: kdepim-bugs@kde.org Reporter: a...@laxu.de Target Milestone: --- I had a akonadi_maildir_resource crash in Ubuntu disco. I do not see what version number is correct, as the different libakonadi-packages seem to have different version numbers, but none with 5.x Application: akonadi_maildir_resource (akonadi_maildir_resource), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8e88e39800 (LWP 2778))] Thread 4 (Thread 0x7f8e7f7fe700 (LWP 2814)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7f8e8cb57535 in __GI_abort () at abort.c:79 #8 0x7f8e8cdd0642 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7f8e8cddc186 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f8e8cddc1d1 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f8e8cf9cdd3 in qTerminate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f8e8cf9e7c0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f8e8cb14182 in start_thread (arg=) at pthread_create.c:486 #14 0x7f8e8cc4fb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f8e7700 (LWP 2805)): #0 0x7f8e8cc43729 in __GI___poll (fds=0x7f8e78026410, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8e8b48bcb6 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8e8b48bddc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8e8d1de063 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8e8d1895bb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8e8cfd42c6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8e8e06a565 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f8e8cfd5612 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8e8cb14182 in start_thread (arg=) at pthread_create.c:486 #9 0x7f8e8cc4fb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f8e87b2f700 (LWP 2785)): #0 0x7f8e8cc43729 in __GI___poll (fds=0x7f8e87b2eca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8e8bf5f917 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f8e8bf6153a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f8e8871f6a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f8e8cfd5612 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8e8cb14182 in start_thread (arg=) at pthread_create.c:486 #6 0x7f8e8cc4fb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f8e88e39800 (LWP 2778)): #0 0x7f8e8b48b1d4 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f8e8b48bbeb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8e8b48bddc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8e8d1de063 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8e8d1895bb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8e8d1915e2 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8e8e5bc31e in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5 #7 0x55eb81799f11 in ?? () #8 0x7f8e8cb58b6b in __libc_start_main (main=0x55eb81799d80, argc=3, argv=0x7ffc99443a28, init=, fini=, rtld_fini=, stack_end=0x7ffc99443a18) at ../csu/libc-start.c:308 #9 0x55eb81799dba in _start () [Inferior 1 (process 2778) detached] -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 134277] multiweek view as in sunbird would be !
https://bugs.kde.org/show_bug.cgi?id=134277 ar...@sanusi.de changed: What|Removed |Added CC||ar...@sanusi.de --- Comment #5 from ar...@sanusi.de --- this still does not exist, correct? Would be awesome to have -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 --- Comment #9 from Axel Braun --- (In reply to Martin Steigerwald from comment #8) > Thank you Axel for confirming on recent version. I forgot: ocb@T520:~> rpm -qa | grep akonadi akonadi-calendar-lang-18.12.3-1.2.noarch akonadi-server-18.12.3-2.1.x86_64 akonadi-plugin-mime-18.12.3-1.2.x86_64 akonadi-calendar-tools-lang-18.12.3-1.2.noarch akonadi-plugin-kalarmcal-18.12.3-1.2.x86_64 akonadi-import-wizard-lang-18.12.3-1.2.noarch akonadi-search-18.12.3-1.2.x86_64 akonadi-notes-lang-18.12.3-1.2.noarch akonadi-mime-18.12.3-1.2.x86_64 akonadi-server-lang-18.12.3-2.1.noarch akonadi-calendar-tools-18.12.3-1.2.x86_64 akonadiconsole-18.12.3-1.2.x86_64 akonadi-contact-18.12.3-1.2.x86_64 akonadi-plugin-contacts-18.12.3-1.2.x86_64 akonadi-plugin-calendar-18.12.3-1.2.x86_64 akonadi-import-wizard-18.12.3-1.2.x86_64 akonadi-contact-lang-18.12.3-1.2.noarch akonadi-search-lang-18.12.3-1.2.noarch akonadi-mime-lang-18.12.3-1.2.noarch -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 --- Comment #8 from Martin Steigerwald --- Thank you Axel for confirming on recent version. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 Axel Braun changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- --- Comment #7 from Axel Braun --- I'm running latest KDE on openSUSE Tumbleweed: Plasma 5.15.4 Framework 5.57.0 QT: 5.12.2 and can confirm that the issue persists: docb@T520:~> akonadictl status Akonadi Control: stopped Akonadi Server: stopped Akonadi Server Search Support: available (Remote Search, Akonadi Search Plugin) Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent, akonadi_birthdays_resource, akonadi_contacts_resource, akonadi_davgroupware_resource, akonadi_ews_resource, akonadi_ewsmta_resource, akonadi_facebook_resource, akonadi_followupreminder_agent, akonadi_googlecalendar_resource, akonadi_googlecontacts_resource, akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource, akonadi_indexing_agent, akonadi_invitations_agent, akonadi_kalarm_dir_resource, akonadi_kalarm_resource, akonadi_knut_resource, akonadi_kolab_resource, akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mailfilter_agent, akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent, akonadi_notes_agent, akonadi_notes_resource, akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_sendlater_agent, akonadi_tomboynotes_resource, akonadi_unifiedmailbox_agent, akonadi_vcard_resource, akonadi_vcarddir_resource docb@T520:~> ps ax | grep postgres 2893 ?S 0:00 /usr/lib/postgresql96/bin/postgres -D /home/docb/.local/share/akonadi/db_data -k/tmp/akonadi-docb.N9ni6K -h 2896 ?Ss 0:00 postgres: logger process 2900 ?Ss 0:06 postgres: checkpointer process 2901 ?Ss 0:01 postgres: writer process 2902 ?Ss 0:01 postgres: wal writer process 2903 ?Ss 0:00 postgres: autovacuum launcher process 2904 ?Ss 0:04 postgres: stats collector process 14412 pts/1S+ 0:00 grep --color=auto postgres -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406958] Unreferenced files in file_db_data
https://bugs.kde.org/show_bug.cgi?id=406958 --- Comment #4 from Martin Steigerwald --- Christophe, come on now: 5.9.2 is also available. Okay, I bring this up on kdepim-devel mailing list. 18.08 is not even a year old. You are basically telling Linux distro users to get lost by closing bugs from not even one year old versions like this. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 --- Comment #6 from Martin Steigerwald --- Thing is: yes, I understand that it would be tedious to receive bug reports of long fixed bugs with versions that are 2 or more years old. But 18.08 is not even a year. If you are implying that you are not interested in bug reports regarding versions that are not even a year old, you are basically telling Linux distro users to get lost. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 --- Comment #5 from Martin Steigerwald --- 18.08 unmaintained already? Well, FWIW Dan asked me whether Akonadi crashes which may prevent a proper database shutdown¹. Now I did and even used an existing bug report and you just closed it. That basically means that as long as I choose to use the Debian Sid aka Unstable release (not even the one in current Debian Stretch aka Stable) and report any bugs about it, my bugs would be outdated to begin with. My short comment on this: I disagree. [1] https://mail.kde.org/pipermail/kdepim-users/2019-April/001827.html -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 406946] Akonadi crashes when sending a large attachment
https://bugs.kde.org/show_bug.cgi?id=406946 Christophe Giboudeaux changed: What|Removed |Added Component|akregator |mail --- Comment #1 from Christophe Giboudeaux --- Do you have a backtrace? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 344874] username/password not being sent in header
https://bugs.kde.org/show_bug.cgi?id=344874 --- Comment #17 from Christophe Giboudeaux --- also no issue on demo.nextcloud.com, I see the test event I just created on the recent activities tab -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 344874] username/password not being sent in header
https://bugs.kde.org/show_bug.cgi?id=344874 --- Comment #16 from Christophe Giboudeaux --- > I'm having the same issue with my nextcloud server. I tried adding a dav resource pointing to demo.owncloud.com a couple days ago without seeing any issue. I could create an event and a contact without anything complaining. -- You are receiving this mail because: You are the assignee for the bug.
