[kmail2] [Bug 378702] Rename favourite folder: ENTER key triggers "Default name" button instead of "OK" (save changes) button
https://bugs.kde.org/show_bug.cgi?id=378702 Laurent Montelchanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Did you still have it in last version ? it seems to work here. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388573] Draft message is confused about mail transport
https://bugs.kde.org/show_bug.cgi?id=388573 --- Comment #2 from Laurent Montel--- I think it's a draft which was created with another mailtransport id. I think that you have create this email with another instance of kmail or you reinstall it etc. This warning is displaying when "X-KMail-Transport: " in unknown. it's normal that it will send correctly as it will fallback to new mailtransport id. -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 388478] Could not create key pair: No agent running
https://bugs.kde.org/show_bug.cgi?id=388478 Andre Heineckechanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Andre Heinecke --- Kleopatra's self test should have shown errors in that case. Can you please confirm that Settings -> Run Self-Test shows errors? I can only imagine that this problem occurs if GnuPG was not installed properly as part off the gpg4win installation. An error there was not handled in 3.0.0. You could try to reinstall GnuPG using the "Simple installer for the current GnuPG" from: https://gnupg.org/download/index.html -- You are receiving this mail because: You are on the CC list for the bug.
[kleopatra] [Bug 381910] New user: Starting kleopatra shows 'loading certificate cache ...' forever
https://bugs.kde.org/show_bug.cgi?id=381910 Andre Heineckechanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #13 from Andre Heinecke --- Thanks for your test. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 360313] akonadi_davgroupware_resource doesn't respond on return
https://bugs.kde.org/show_bug.cgi?id=360313 --- Comment #2 from David Faure--- The reason I'm asking is that there is the dialog to configure the resource (initially, at least, but I don't know if it reappears later on), there's the kwallet dialog, there's maybe a password dialog that appears when kwallet is disabled... and in my case I use kwallet so there is in fact no password dialog popping up at all. Hence the request for clarification. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 360313] akonadi_davgroupware_resource doesn't respond on return
https://bugs.kde.org/show_bug.cgi?id=360313 David Faurechanged: What|Removed |Added CC||fa...@kde.org --- Comment #1 from David Faure --- Can you post a screenshot so we can be sure which dialog this is about? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 385770] openSUSE TW (+nvidia) kmail crash when searching To: contact
https://bugs.kde.org/show_bug.cgi?id=385770 Bruno Friedmannchanged: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #3 from Bruno Friedmann --- Closed will be reopen if after resetting completely the setup it will be again produced -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 388648] New: Kontact crash
https://bugs.kde.org/show_bug.cgi?id=388648 Bug ID: 388648 Summary: Kontact crash Product: kontact Version: 5.7.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: benmaybe...@live.com Target Milestone: --- Application: kontact (5.7.0) Qt Version: 5.9.3 Frameworks Version: 5.41.0 Operating System: Linux 4.10.0-42-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: - What I was doing when the application crashed: I was looking at my emails, I clicked on the "sent items" tab, and a few seconds later, Kontact crashes. This happens every time. The crash can be reproduced every time. -- 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 0x7f3b01c3d900 (LWP 18383))] Thread 27 (Thread 0x7f39c15d2700 (LWP 18452)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f3aef28635f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f3aef286af7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f3aef2878c0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f3aef283f2d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f3afa3fc6ba in start_thread (arg=0x7f39c15d2700) at pthread_create.c:333 #6 0x7f3afe68a3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 26 (Thread 0x7f39c41bd700 (LWP 18437)): #0 0x7f3af84f4a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3af84af464 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3af84b0346 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3af84b049c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3aff1bb6cb in QEventDispatcherGlib::processEvents (this=0x7f39bc0008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f3aff163e2a in QEventLoop::exec (this=this@entry=0x7f39c41bccc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f3afef8c8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f3afef91709 in QThreadPrivate::start (arg=0x61713a0) at thread/qthread_unix.cpp:368 #8 0x7f3afa3fc6ba in start_thread (arg=0x7f39c41bd700) at pthread_create.c:333 #9 0x7f3afe68a3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 25 (Thread 0x7f39ce627700 (LWP 18418)): #0 QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:243 #1 0x7f3aff1bbad1 in postEventSourcePrepare (timeout=0x0, s=0x7f39c80012d0) at kernel/qeventdispatcher_glib.cpp:252 #2 postEventSourceCheck (source=0x7f39c80012d0) at kernel/qeventdispatcher_glib.cpp:269 #3 0x7f3af84afdc1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3af84b0330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3af84b049c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f3aff1bb6cb in QEventDispatcherGlib::processEvents (this=0x7f39c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f3aff163e2a in QEventLoop::exec (this=this@entry=0x7f39ce626cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #8 0x7f3afef8c8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #9 0x7f3afef91709 in QThreadPrivate::start (arg=0x2e11dd0) at thread/qthread_unix.cpp:368 #10 0x7f3afa3fc6ba in start_thread (arg=0x7f39ce627700) at pthread_create.c:333 #11 0x7f3afe68a3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 24 (Thread 0x7f39df0c9700 (LWP 18415)): #0 0x7f3af84f4a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3af84b0290 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3af84b049c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3aff1bb6cb in QEventDispatcherGlib::processEvents (this=0x7f39d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f3aff163e2a in QEventLoop::exec (this=this@entry=0x7f39df0c8cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f3afef8c8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f3afef91709 in QThreadPrivate::start (arg=0x2c788c0) at thread/qthread_unix.cpp:368 #7 0x7f3afa3fc6ba in start_thread (arg=0x7f39df0c9700) at pthread_create.c:333 #8 0x7f3afe68a3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 23 (Thread 0x7f39df8ca700 (LWP 18414)): #0 0x7f3af84f4a79 in
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #11 from Éric Brunet--- Created attachment 109722 --> https://bugs.kde.org/attachment.cgi?id=109722=edit patch to reenable numbers, v17.12.0 Hi Kamil, I am happy this is useful to someone. I'll post updated patches in a more timely way. Here is the patch to re-enable numbers for kmail 5.7.0, as found in kde 17.12.0, as shipped by the latest fedora 27 updates -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388645] New: Can't send larger attachments
https://bugs.kde.org/show_bug.cgi?id=388645 Bug ID: 388645 Summary: Can't send larger attachments Product: kmail2 Version: 5.7.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: fgro...@onlinehome.de Target Milestone: --- I can send short e-mails without attachment without problems since Bug 388068 is solved. But always if I try to send an bigger attachment I get the following error message: Jan 07 11:38:44 franks akonadi_maildispatcher_agent[1112]: QIODevice::write (QTcpSocket): device not open Jan 07 11:38:44 franks akonadi_maildispatcher_agent[1112]: org.kde.pim.ksmtp: Socket error: 0 Jan 07 11:38:44 franks plasmashell[903]: Currrent active notifications: QHash() Jan 07 11:38:44 franks plasmashell[903]: Guessing partOf as: 0 Jan 07 11:38:44 franks plasmashell[903]: New Notification: "Das Senden der E-Mail ist fehlgeschlagen" "Fehler beim Übertragen der Nachricht. Die Verbindung zum Server ist abgebrochen." -1 & Part of: 0 Kmail and components are 17.12.0. Even if I get this error, the message including attachments is send in the background. -- You are receiving this mail because: You are the assignee for the bug.