[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #7 from Éric Brunet --- Created attachment 105670 --> https://bugs.kde.org/attachment.cgi?id=105670&action=edit patch to reenable numbers patch against kmail 16.12.3 to re-enable showing number of unread emails in systray -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #8 from Éric Brunet --- This is the patch I have been using for two weeks to re-enable nulbers in systray. It works fine. It is against kmail 16.12.3, which is the version shipped by fedora 25. It is not a simple revert of the feature removal: the displayed was small and ugly. The reason is that kmail sends a pixmap of size 32x32 which is scaled down by systray to 22x22 (in standard theme). I am not sure how to ask the theme what the correct icon size should be. I think the problem is also present in the unpatched kmail. Please? You could put me in the loop and I would answer bug reports about this? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 128454] if copies of sent messages cannot be uploaded to the IMAP server they should be moved there from the local folder later
https://bugs.kde.org/show_bug.cgi?id=128454 Hans-Peter Jansen changed: What|Removed |Added CC||h...@urpla.net --- Comment #5 from Hans-Peter Jansen --- I'm admin of a couple of kmail users, which ALL suffer from this problem on a regular base. Forcing the user to move the content of the local sent folder to the right IMAP sent folders manually in order to reach a consistent state is more than a nuisance. From my POV, this is a plain bug and I would like to raise the Importance of this long standing issue accordingly. Sure, it might happen, that the IMAP server cannot be accessed, while the mail was sent. Given the number of times this happens, this is most probably, because akonadi is already active on this server. kmail2/akonadi should always add a custom header, when it stores mails in local sent folder temporarily. The header value should point to the correct destination of this mail. Akonadi should retry to move the mail, until it's done (or the mailbox vanished, than it's okay to remove the header, and give up). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 379155] Imap resources crash when trying to open settings
https://bugs.kde.org/show_bug.cgi?id=379155 Christophe Giboudeaux changed: What|Removed |Added Latest Commit|https://commits.kde.org/kde |https://commits.kde.org/kde |pim-runtime/e8b131fe179f474 |pim-runtime/611510d0a005bc9 |af9de12f1289ea70cd99e90e4 |3102aa4b9f1a5b5f9905c4179 --- Comment #7 from Christophe Giboudeaux --- Git commit 611510d0a005bc93102aa4b9f1a5b5f9905c4179 by Christophe Giboudeaux, on behalf of Montel Laurent. Committed on 22/05/2017 at 10:37. Pushed by cgiboudeaux into branch 'Applications/17.04'. Fix Bug 379155 - Imap resources crash when trying to open settings M +2-2resources/imap/setupserver.cpp https://commits.kde.org/kdepim-runtime/611510d0a005bc93102aa4b9f1a5b5f9905c4179 -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 380087] New: KMail crash on quit
https://bugs.kde.org/show_bug.cgi?id=380087 Bug ID: 380087 Summary: KMail crash on quit Product: kmail2 Version: 5.5.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jonathan.ver...@gmail.com Target Milestone: --- Application: kmail (5.5.1) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.4.0-78-generic x86_64 Distribution: KDE neon User Edition 5.9 -- Information about the crash: - What I was doing when the application crashed: After a time, Kmail stops displaying mail (the message pane just shows "Retrieving folder contents. Please wait".) Restarting kmail sometimes helps. So I quit kmail using Ctrl-Q and the crash happend. 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 0x7f97c993ca00 (LWP 29733))] Thread 26 (Thread 0x7f969bb7d700 (LWP 4408)): #0 0x7f97ea9a0a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f97ea95b929 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f97ea95c2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f97ea95c49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f97f69a275b in QEventDispatcherGlib::processEvents (this=0x7f96ac01c420, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f97f694d0ba in QEventLoop::exec (this=this@entry=0x7f969bb7cbc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f97f677cf64 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f97f6781b48 in QThreadPrivate::start (arg=0x6ccacd0) at thread/qthread_unix.cpp:368 #8 0x7f97ec6b56ba in start_thread (arg=0x7f969bb7d700) at pthread_create.c:333 #9 0x7f97f608e82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 25 (Thread 0x7f973e337700 (LWP 31510)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f97e41215af in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f97e4121bc9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f97e4121d80 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f97e411e747 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f97ec6b56ba in start_thread (arg=0x7f973e337700) at pthread_create.c:333 #6 0x7f97f608e82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 24 (Thread 0x7f973fdf6700 (LWP 30283)): #0 QTimerInfoList::timerWait (this=0x7f96b4002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:387 #1 0x7f97f69a1d0e in timerSourcePrepareHelper (timeout=0x7f973fdf59f4, src=) at kernel/qeventdispatcher_glib.cpp:132 #2 timerSourcePrepare (source=, timeout=0x7f973fdf59f4) at kernel/qeventdispatcher_glib.cpp:165 #3 0x7f97ea95b91d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f97ea95c2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f97ea95c49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f97f69a275b in QEventDispatcherGlib::processEvents (this=0x7f96b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f97f694d0ba in QEventLoop::exec (this=this@entry=0x7f973fdf5bc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #8 0x7f97f677cf64 in QThread::exec (this=) at thread/qthread.cpp:507 #9 0x7f97f6781b48 in QThreadPrivate::start (arg=0x5053400) at thread/qthread_unix.cpp:368 #10 0x7f97ec6b56ba in start_thread (arg=0x7f973fdf6700) at pthread_create.c:333 #11 0x7f97f608e82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 23 (Thread 0x7f9744d61700 (LWP 30267)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f97e41215af in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f97e4121bc9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f97e4121d80 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f97e411e747 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f97ec6b56ba in start_thread (arg=0x7f9744d61700) at pthread_create.c:333 #6 0x7f97f608e82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 22 (Thread 0x7f9745ff3700 (LWP 30266)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f97dfe496f4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f97dfe49739 in ?? ()
[kmail2] [Bug 380091] New: can not open
https://bugs.kde.org/show_bug.cgi?id=380091 Bug ID: 380091 Summary: can not open Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kep...@gmail.com Target Milestone: --- it closes by itself, can not be loaded can not use it https://pastebin.com/H3swtHM1 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 379548] IMAP resource crashes on configure operation
https://bugs.kde.org/show_bug.cgi?id=379548 Gioacchino Mazzurco changed: What|Removed |Added CC||gmazzurc...@gmail.com Ever confirmed|0 |1 Severity|normal |critical Status|UNCONFIRMED |CONFIRMED Version|unspecified |5.5.1 --- Comment #10 from Gioacchino Mazzurco --- I experience similar crash on Gentoo with kmail 5.5.1, on dmesg i have found this. [Mon May 22 15:05:39 2017] akonadi_imap_re[6140]: segfault at 10 ip 7ff60959a8d1 sp 7ffd231df2a0 error 4 in libKF5MailTransport.so.5.5.1[7ff60957+4d000] [Mon May 22 15:05:41 2017] akonadi_imap_re[6152]: segfault at 10 ip 7f831c6a18d1 sp 7fff978704a0 error 4 in libKF5MailTransport.so.5.5.1[7f831c677000+4d000] [Mon May 22 15:05:47 2017] akonadi_imap_re[6158]: segfault at 10 ip 7f48003218d1 sp 7ffc4c519300 error 4 in libKF5MailTransport.so.5.5.1[7f48002f7000+4d000] [Mon May 22 15:06:15 2017] akonadi_imap_re[6181]: segfault at 10 ip 7efbfa20f8d1 sp 7fff63019490 error 4 in libKF5MailTransport.so.5.5.1[7efbfa1e5000+4d000] [Mon May 22 15:06:17 2017] akonadi_imap_re[6187]: segfault at 10 ip 7fbfa8d5e8d1 sp 7ffe384652e0 error 4 in libKF5MailTransport.so.5.5.1[7fbfa8d34000+4d000] [Mon May 22 15:06:18 2017] akonadi_imap_re[6193]: segfault at 10 ip 7f941be818d1 sp 7ffce89f3370 error 4 in libKF5MailTransport.so.5.5.1[7f941be57000+4d000] -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 379548] IMAP resource crashes on configure operation
https://bugs.kde.org/show_bug.cgi?id=379548 --- Comment #11 from Gioacchino Mazzurco --- Trying to configure it from akonadiconsole i get this message in the terminal org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_imap_resource" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed! 0 restarts left. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 380100] New: Akonadi Console crashes at launch
https://bugs.kde.org/show_bug.cgi?id=380100 Bug ID: 380100 Summary: Akonadi Console crashes at launch Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: akonadiconsole Assignee: kdepim-bugs@kde.org Reporter: hmcilva...@cox.net Target Milestone: --- Created attachment 105681 --> https://bugs.kde.org/attachment.cgi?id=105681&action=edit Dump report When selecting the "Akonadi Console" application from the neon application menu, the system responds like it's trying to execute, then presents a notification that the application has crashed and closes out. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 380101] New: Question: CalDavSync
https://bugs.kde.org/show_bug.cgi?id=380101 Bug ID: 380101 Summary: Question: CalDavSync Product: korganizer Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: html export Assignee: kdepim-bugs@kde.org Reporter: alex...@web.de Target Milestone: --- My question: Is it possible to syncronize the calendar by CALDAVSYNC with my ANDROID-Smartphone (Huawei P10 PLUS) and/or other accounts ? -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 380107] New: Kontact crashed, while "Mark as read"
https://bugs.kde.org/show_bug.cgi?id=380107 Bug ID: 380107 Summary: Kontact crashed, while "Mark as read" Product: kontact Version: 5.2.3 Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: shado...@gmx.net Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.7.1 Frameworks Version: 5.28.0 Operating System: Linux 4.9.0-2-amd64 x86_64 Distribution: Debian GNU/Linux 9.0 (stretch) -- Information about the crash: - What I was doing when the application crashed: i want to mark all messages as read, then it crashed maybe related to: 368252 The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6deb7a3dc0 (LWP 3085))] Thread 29 (Thread 0x7f6d0e0bb700 (LWP 6138)): #0 0x7f6de0cfc9d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6de0cfee7b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6de0cff91b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6de0cffb0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6de969106b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6de963a9ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6de94680f3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6de946cda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6de2ac8494 in start_thread (arg=0x7f6d0e0bb700) at pthread_create.c:333 #9 0x7f6de8b6f93f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 28 (Thread 0x7f6ce3503700 (LWP 9011)): #0 0x7f6dcdb87078 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #1 0x7f6dcdb87b30 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f6dcdb87bf0 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f6dcdb95bd9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f6dcd7302c8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #5 0x7f6de2ac8494 in start_thread (arg=0x7f6ce3503700) at pthread_create.c:333 #6 0x7f6de8b6f93f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 27 (Thread 0x7f6d24f5c700 (LWP 8913)): #0 0x7f6de0cff5a6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6de0cffa60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6de0cffb0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6de969106b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6de963a9ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6de94680f3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6de946cda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6de2ac8494 in start_thread (arg=0x7f6d24f5c700) at pthread_create.c:333 #8 0x7f6de8b6f93f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 26 (Thread 0x7f6d25f9c700 (LWP 8911)): #0 0x7f6de0d45104 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6de0cff3f1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6de0cff994 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6de0cffb0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6de969106b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6de963a9ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6de94680f3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6de946cda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6de2ac8494 in start_thread (arg=0x7f6d25f9c700) at pthread_create.c:333 #9 0x7f6de8b6f93f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 25 (Thread 0x7f6d2577c700 (LWP 8909)): #0 0x7f6de8b664ed in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6de0cff9f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6de0cffb0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6de969106b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6de963a9ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-
