[kmail2] [Bug 401687] kmail doesn't send queued messages
https://bugs.kde.org/show_bug.cgi?id=401687 Konstantin Kharlamov changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from Konstantin Kharlamov --- A few weeks ago I tried KMail again, and it worked for me. I used it for a few weeks for rare communication on mailing lists from two different mail accounts and as far as I can tell the bug was resolved. KMail version was 19.12.3. I encountered another problem though, which made me to remove KMail. Probably the last time now. This time an issue is that KMail sometimes (once a few days probably) suddenly starts redownloading all emails I have, thousands of them. It leads to freezes of the whole system for an hour-two. Unfortunately, I don't think I have motivation to report this one. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388036] Include support for autocrypt
https://bugs.kde.org/show_bug.cgi?id=388036 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 377485] regression: system tray icon no longer shows number of unread articles
https://bugs.kde.org/show_bug.cgi?id=377485 Yamashita Ren changed: What|Removed |Added CC||lemaitre.dulo...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420484] Entering a string in the search field of the message list crashes the application
https://bugs.kde.org/show_bug.cgi?id=420484 --- Comment #2 from Arcadie Cracan --- Backtrace attached. Changing get_error_string() to get_description() in emailquery.cpp, line 205 solves the issue. I have already committed a patch: https://phabricator.kde.org/D29164 Thank you for your help! Kind regards, Arcadie Cracan On Fri, Apr 24, 2020 at 7:55 AM Laurent Montel wrote: > https://bugs.kde.org/show_bug.cgi?id=420484 > > Laurent Montel changed: > >What|Removed |Added > > > CC||mon...@kde.org > > --- Comment #1 from Laurent Montel --- > Could you add a backtrace ? > Do you have a debug in console ? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 420520] Akregator indicator does not hide when all feeds are read
https://bugs.kde.org/show_bug.cgi?id=420520 --- Comment #1 from Yamashita Ren --- Related to https://bugs.kde.org/show_bug.cgi?id=377485 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 420520] New: Akregator indicator does not hide when all feeds are read
https://bugs.kde.org/show_bug.cgi?id=420520 Bug ID: 420520 Summary: Akregator indicator does not hide when all feeds are read Product: akregator Version: 5.13.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: lemaitre.dulo...@gmail.com Target Milestone: --- The Akregator indicator need a way to accurately show if there are items to read. Currently : When you start Akregator, whether are unread items or not, its indicator is always visible in the notification area (indicator parameter is "shown when relevant"). The indicator becomes hidden ONLY if there are some unread items in Akregator and you read them all. The indicator does NOT start hidden if there are no items to read when you start Akregator. Fix required : 1) Akregator needs to use another icon when there are no items to read. or 2) Akregator needs to have its indicator hidden in the notification area when it is started, if there are no items to read. System : Kubuntu 20.04 KDE Plasma 5.18.4 KDE Frameworks 5.68.0 Qt 5.12.8 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 --- Comment #32 from Parker --- "[...] that are maintained by a single developer 365 days each year." Did you realize you just agreed with what I said earlier? He works alone because the people who try to help him can't. If you want everything to be done your way, you don't have patience with those who are learning and you think you're right about everything, so there's no surprise if you work alone. This isn't just about lines of code, it's also about the person you are. Treating people who come here to make a suggestion or report a bug well is essential and necessary. KMail has a lot of bugs and a lot of things don't work, but that doesn't mean it's dead. It just needs to be more open to contributions. If that's done, other people will contribute. -- 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 Matt Scheirer changed: What|Removed |Added CC||matt.schei...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 420515] New: Breeze Dark: Color of "today" does not differ from background
https://bugs.kde.org/show_bug.cgi?id=420515 Bug ID: 420515 Summary: Breeze Dark: Color of "today" does not differ from background Product: korganizer Version: 5.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: monthview Assignee: kdepim-bugs@kde.org Reporter: p...@mail.de Target Milestone: --- SUMMARY If I choose "Breeze Dark" as global system theme, KOrganizer is also dark, which is fine. But in month view the tile of today's day is plain black and no (or only very little) different from the other tiles and almost not recognizable. STEPS TO REPRODUCE 1. Set Breeze Dark global theme 2. Look at month view at today's day. OBSERVED RESULT "today" is just as black as the other days. EXPECTED RESULT "today" is somehow highlighted. SOFTWARE/OS VERSIONS Linux: Debian Testing KDE Plasma Version: 5.17.5 KDE Frameworks 5.62.0 Qt 5.12.5 (kompiliert gegen 5.12.5) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 416377] kmail crash `saving as` an attachmnet
https://bugs.kde.org/show_bug.cgi?id=416377 --- Comment #2 from YangMame --- Created attachment 127821 --> https://bugs.kde.org/attachment.cgi?id=127821=edit New crash information added by DrKonqi kmail (5.13.3 (19.12.3)) using Qt 5.14.2 - What I was doing when the application crashed: trying to save or open files in email,then crashed everytime -- Backtrace (Reduced): #6 0x7fece9c53b7f in () at /usr/lib64/libKF5Mime.so.5 #7 0x7fece9c4ddae in KMime::Content::headerByType(char const*) const () at /usr/lib64/libKF5Mime.so.5 #8 0x7fece9c4f4a9 in KMime::Content::contentDisposition(bool) () at /usr/lib64/libKF5Mime.so.5 #9 0x7fecea12ef7c in MimeTreeParser::NodeHelper::fileName(KMime::Content const*) () at /usr/lib64/libKF5MimeTreeParser.so.5 #10 0x7fecea666b9d in () at /usr/lib64/libKF5MessageViewer.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 416377] kmail crash `saving as` an attachmnet
https://bugs.kde.org/show_bug.cgi?id=416377 YangMame changed: What|Removed |Added CC||yangm...@icloud.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 413071] [Wayland] Kmail crashes when resized or maximized
https://bugs.kde.org/show_bug.cgi?id=413071 Rainer Finke changed: What|Removed |Added Version|5.13.2 |5.14.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 389230] Account assistant shows Wayland generic icon
https://bugs.kde.org/show_bug.cgi?id=389230 Rainer Finke changed: What|Removed |Added Version|5.13.2 |5.14.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414955] KMail stops responding when preview pane active on Wayland-Plasma
https://bugs.kde.org/show_bug.cgi?id=414955 Rainer Finke changed: What|Removed |Added Version|5.13.2 |5.14.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 --- Comment #31 from Christoph Feck --- Give me a break. KMail is not just KMail. It consists of dozens of repositories that are maintained by a single developer 365 days each year. If you want it to evolve beyond that, find more developers who are not scared by the complexity of the codebase. Most bugs, by the way, are in the multi-process design dictated by Akonadi. It needs many developers and many years to fix that design. > KDE really needs an e-mail client. These types of statements usually come from users who don't like the available alternatives. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 420497] New: Korganizer crashed when trying to invite attendees to an existing recurring event
https://bugs.kde.org/show_bug.cgi?id=420497 Bug ID: 420497 Summary: Korganizer crashed when trying to invite attendees to an existing recurring event Product: korganizer Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: dkanunni...@gmail.com Target Milestone: --- Application: korganizer (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.67.0 Operating System: Linux 5.3.0-46-generic x86_64 Windowing system: X11 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: Tried to add attendees to an existing recurring event from CalDAV (Nextcloud) - Custom settings of the application: Nextcloud CalDAV calendar -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5b9c8dbf40 (LWP 1503))] Thread 10 (Thread 0x7f5b6bfff700 (LWP 1595)): #0 __GI___libc_read (nbytes=10, buf=0x7f5b6bffe95e, fd=38) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=38, buf=0x7f5b6bffe95e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f5b83306955 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.0.so #3 0x7f5b83388406 in pa_mainloop_prepare () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f5b83388ea4 in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f5b83388f60 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f5b8339710d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f5b8333537c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.0.so #8 0x7f5ba17bd669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f5ba3891323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f5b80cd5700 (LWP 1578)): #0 0x7f5ba0e5cb53 in g_source_ref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5ba0e5cc01 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5ba0e5df6b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5ba0e5e9db in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5ba0e5ebe3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5ba3e45653 in QEventDispatcherGlib::processEvents (this=0x7f5b6c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f5ba3dec5cb in QEventLoop::exec (this=this@entry=0x7f5b80cd4b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f5ba3c25a45 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f5ba3c26c92 in QThreadPrivate::start (arg=0x55b6301eae70) at thread/qthread_unix.cpp:361 #9 0x7f5ba17bd669 in start_thread (arg=) at pthread_create.c:479 #10 0x7f5ba3891323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f5b81553700 (LWP 1533)): #0 0x7f5ba3884c2f in __GI___poll (fds=0x7f5b780029e0, nfds=1, timeout=10194) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5ba0e5eaae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5ba0e5ebe3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5ba3e45653 in QEventDispatcherGlib::processEvents (this=0x7f5b78000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f5ba3dec5cb in QEventLoop::exec (this=this@entry=0x7f5b81552b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f5ba3c25a45 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f5ba3c26c92 in QThreadPrivate::start (arg=0x55b62f1474a0) at thread/qthread_unix.cpp:361 #7 0x7f5ba17bd669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f5ba3891323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f5b81eb4700 (LWP 1528)): #0 0x7f5ba3884c2f in __GI___poll (fds=0x7f5b740025e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5ba0e5eaae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5ba0e5ebe3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5ba3e45653 in QEventDispatcherGlib::processEvents (this=0x7f5b74000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f5ba3dec5cb in QEventLoop::exec (this=this@entry=0x7f5b81eb3b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f5ba3c25a45 in QThread::exec (this=) at
