[kmail2] [Bug 417471] New: Add a new column with a new tag "check back later"
https://bugs.kde.org/show_bug.cgi?id=417471 Bug ID: 417471 Summary: Add a new column with a new tag "check back later" Product: kmail2 Version: 5.12.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: alexandre.bonn...@linuxfr.eu Target Milestone: --- In kmail there are two great features ; you can configure the columns shown to display an icon for important messages, as well as an icon for the TODO tag. Also, when you click those icons, you simply toggle the important/not important state, or the TODO/DONE one. When the important state is used, the mail text color is shown in red. When the TODO tag is used, the mail text color is shown in green. This is great, and allow an efficient workflow. But that workflow could be improved with a small addition : When you receive some mails, you often have a choice to make : - The mail is basic information -> Read it directly and be done with it - The mail contains information you need to act on -> Read it and set the TODO tag (so you get a nice color you can identify easily while browsing your previous mails to search for unfinished todos) - The mail contains information that you worked on, then replied to with a question of your own. -> Now, since some people are unreliable and may miss your email, you WILL need to check later if you got an answer. To do that you need to mark that initial email as "Check back later" (which could color the text in pink for instance). This way you know you _already have done the work_, but only need to ping again the person you answered to. This "Check back later" tag (name to be defined) is different than the "TODO" one since a todo means some amount of work have to be done (and that take time), while "Check back later" only needs you to resend a quick message like "Hey, I haven't heard about you on this subject. Could you please get back to me whenever you're available? xoxoxo". This would go a long way to improve a mail management workflow, and be sure to not miss anything (this is loosely based on the Get Things Done methodology). Bonus : Even better, when adding a 'check back later' tag to an email, it could automatically create a task (like you can already do) and just asks for the date and hour, the default calendar being configured somewhere else. Right now once you created a task from kmail, you have no indication if a particular email has tasks attached to it, or even if those tasks are done. So the main purpose of this wish is to have a way to color an email with a one click toggle like the TODO one. Regards -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #114 from Wolfgang Bauer --- (In reply to Said Bakr from comment #113) > The issue is also found for me at Kubuntu 18.04 when using Kio Gdrive from > Dolphin. That's fixed already (in kaccounts-providers 19.12.2): https://cgit.kde.org/kaccounts-providers.git/commit/?id=0a71da4e3caae0defe200a85954fc7e2012010c1 But that has nothing to do with Akonadi or its IMAP resource. -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 417389] security/kleopatra: Right click entries are greyed out
https://bugs.kde.org/show_bug.cgi?id=417389 gr...@kde.org changed: What|Removed |Added CC||gr...@kde.org --- Comment #3 from gr...@kde.org --- Downstream bug is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242670 ; I never did get around to checking the RMB behavior. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Said Bakr changed: What|Removed |Added CC||said@gmail.com --- Comment #113 from Said Bakr --- The issue is also found for me at Kubuntu 18.04 when using Kio Gdrive from Dolphin. -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 417389] security/kleopatra: Right click entries are greyed out
https://bugs.kde.org/show_bug.cgi?id=417389 Gerard Seibert changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- Ever confirmed|0 |1 --- Comment #2 from Gerard Seibert --- (In reply to Andre Heinecke from comment #1) Every item is greyed out. Even my own key elicits a greyed out response when right-clicked on. Interestingly enough, I have Kleopatra installed on a Win 10 machine, and it is working perfectly. The problem is specific, in most likelihood, to FreeBSD. I doubt that reporting it to the Windows community will help, but I'll give it a try. -- You are receiving this mail because: You are on the CC list for the bug.
[kontact] [Bug 417396] Kontact crashes opening settings.
https://bugs.kde.org/show_bug.cgi?id=417396 Stefano changed: What|Removed |Added CC||erist...@cryptolab.net -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 416403] During account wizard using @protonmail.com, get "Kmail could not convert value of setting 'Authentication' to required type"
https://bugs.kde.org/show_bug.cgi?id=416403 kde.sebac...@simplelogin.co changed: What|Removed |Added CC||kde.sebac...@simplelogin.co --- Comment #10 from kde.sebac...@simplelogin.co --- Arch Linux Plasma 5.17.5 Framework 5.67.0 Qt 5.14.1 Kmail 5.13.2 Account Assistant 0.2 Bug confirmed. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 417418] Kontact crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=417418 --- Comment #1 from t...@tuor.org --- I tried it again. And Kontact crashes again. Can't use it. Will have to figure out how to fix it :( -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 417418] New: Kontact crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=417418 Bug ID: 417418 Summary: Kontact crash on opening settings Product: kontact Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: t...@tuor.org Target Milestone: --- Application: kontact (5.13.2 (19.12.2)) Qt Version: 5.13.2 Frameworks Version: 5.67.0 Operating System: Linux 5.3.0-28-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I clicked on the settings -> Confugure Kontact... - Custom settings of the application: I did beginn to setup an email account, but didn't finish and closed the application. Later I wanted to end my job, but Kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8438621340 (LWP 23704))] Thread 25 (Thread 0x7f83c700 (LWP 24112)): #0 0x7f8430a5bed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f83cfffe6f0, expected=0, futex_word=0x7f83cfffe8c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f83cfffe790, mutex=0x7f83cfffe878, cond=0x7f83cfffe8a0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f83cfffe8a0, mutex=0x7f83cfffe878, abstime=0x7f83cfffe790) at pthread_cond_wait.c:667 #3 0x7f842551a146 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f842551aaed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f842551ac82 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f84254d37a1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f84254d66e2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f84254d6fd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f842551cb2a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8430a556db in start_thread (arg=0x7f83c700) at pthread_create.c:463 #11 0x7f8434f2b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f8361dc5700 (LWP 23795)): #0 0x7f8430a5b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f8361dc48d8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f8361dc4888, cond=0x7f8361dc48b0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f8361dc48b0, mutex=0x7f8361dc4888) at pthread_cond_wait.c:655 #3 0x7f842551a04a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f842551aafc in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f842551ac3f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f84254d3775 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f84254d6a7a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f84254d7014 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f842551cb2a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8430a556db in start_thread (arg=0x7f8361dc5700) at pthread_create.c:463 #11 0x7f8434f2b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f8362dee700 (LWP 23777)): #0 0x7f8434f1ebf9 in __GI___poll (fds=0x7f83500049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f842eb885c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f842eb886dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8435a89acb in QEventDispatcherGlib::processEvents (this=0x7f835b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8435a29f9a in QEventLoop::exec (this=this@entry=0x7f8362ded9e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f84358453aa in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f8435846b52 in QThreadPrivate::start (arg=0x5609990e9240) at thread/qthread_unix.cpp:360 #7 0x7f8430a556db in start_thread (arg=0x7f8362dee700) at pthread_create.c:463 #8 0x7f8434f2b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f8363fff700 (LWP 23774)): #0 0x7f8434f1a0b4 in __GI___libc_read (fd=104, buf=0x7f8363ffe7d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f842ebcd2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f842eb880b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f842eb88570 in ?? () from
[Akonadi] [Bug 410935] akonadi _ews_ressource crashes when setting office365 account
https://bugs.kde.org/show_bug.cgi?id=410935 --- Comment #2 from julien_palmi...@hotmail.fr --- Created attachment 125842 --> https://bugs.kde.org/attachment.cgi?id=125842=edit New crash information added by DrKonqi akonadi_ews_resource (5.13.2 (19.12.2)) using Qt 5.13.2 - What I was doing when the application crashed: just set an akonadi_EWS mail account. all seems OK, i even got my work organization page to log onto, what should be the final step to set the account up. But once my work organization information validated, akonadi_EWS crashes, and does crash everytime i restart the app, or try to check out my mails. Also, it seems somethings are working as i can see all my webmail account folders are visible on kmail. visible but all empty. -- Backtrace (Reduced): #6 0x7f09a7132012 in qstrnlen (maxlen=19, str=0x7f0a7002bacf ) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbytearray.h:80 #7 QString::fromUtf8 (str=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:581 #8 Akonadi::TagAttribute::deserialize (this=0x55abf0878f30, data=...) at ./src/core/tagattribute.cpp:155 #9 0x55abeea537ce in EwsTagStore::unserializeTag (this=this@entry=0x55abf06c7180, data=..., tag=...) at ./resources/ews/tags/ewstagstore.cpp:95 #10 0x55abeea53d92 in EwsTagStore::tags (this=0x55abf06c7180) at ./resources/ews/tags/ewstagstore.cpp:172 -- You are receiving this mail because: You are the assignee for the bug.
