[ksmtp] [Bug 488405] Kontact/Kmail can no longer send email org.kde.pim.ksmtp: SMTP Socket error
https://bugs.kde.org/show_bug.cgi?id=488405 --- Comment #2 from Jeffrey Bouter --- Nevermind, I can no longer reproduce this issue on OpenSUSE Tumbleweed (ksmtp-24.05.0-1.1.x86_64) -- You are receiving this mail because: You are the assignee for the bug.
[ksmtp] [Bug 488405] Kontact/Kmail can no longer send email org.kde.pim.ksmtp: SMTP Socket error
https://bugs.kde.org/show_bug.cgi?id=488405 Jeffrey Bouter changed: What|Removed |Added CC||k...@kn0x.org --- Comment #1 from Jeffrey Bouter --- Can confirm, emails remain stuck in outbox. Happens on OpenSUSE Tumbleweed, ksmtp-24.05.0-1.1.x86_64 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482445] New: kmail font rendering broken on plasma 6 and HiDPI (scaled) display
https://bugs.kde.org/show_bug.cgi?id=482445 Bug ID: 482445 Summary: kmail font rendering broken on plasma 6 and HiDPI (scaled) display Classification: Applications Product: kmail2 Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: k...@kn0x.org Target Milestone: --- Created attachment 166415 --> https://bugs.kde.org/attachment.cgi?id=166415=edit screenshot of a test email in kmail SUMMARY On Plasma 6, font rendering is broken when reading emails using kmail on a scaled (hidpi) display. Please see attached screenshot for a beautiful preview. All other components of kmail scale and render fine. STEPS TO REPRODUCE 1. Use wayland (not tested on X11) 2. Configure display scaling (only tested on 125% and 150%) 3. Open an email in kmail. Both HTML and text format are affected OBSERVED RESULT Blurred, unhinted fonts EXPECTED RESULT Clean, well rendered and hinted fonts. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 22.04 (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Graphics platform: Wayland kmail version: 6.0.0 (24.02.0) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 472461] Emails sent from EWS accounts are not properly encrypted by GPG
https://bugs.kde.org/show_bug.cgi?id=472461 --- Comment #1 from Jeffrey Bouter --- Created attachment 160421 --> https://bugs.kde.org/attachment.cgi?id=160421=edit working result -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 472461] New: Emails sent from EWS accounts are not properly encrypted by GPG
https://bugs.kde.org/show_bug.cgi?id=472461 Bug ID: 472461 Summary: Emails sent from EWS accounts are not properly encrypted by GPG Classification: Applications Product: kmail2 Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: k...@kn0x.org Target Milestone: --- Created attachment 160420 --> https://bugs.kde.org/attachment.cgi?id=160420=edit broken result SUMMARY When sending emails originating from an EWS account, emails are not properly encrypted using GPG. Encryption happens, but the other end is not able to decrypt the messages. The other way around, however, works fine. I've connected two email accounts to my kmail. One is personal and using IMAP, the other is my work account using EWS. STEPS TO REPRODUCE 1. Add an EWS account to kmail 2. Set up a GPG key for said account (if not present already) 3. Send an encrypted email to a different account OBSERVED RESULT Receiving side is unable to decrypt the email EXPECTED RESULT Receiving side is able to decrypt the email SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Please see attached screenshots -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 459341] Kmail crash when trying to write recipent address in the new mail window
https://bugs.kde.org/show_bug.cgi?id=459341 Jeffrey Bouter changed: What|Removed |Added CC||k...@kn0x.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 444108] New: kmail dragging mail to sidebar starts scrolling fast in wayland sessions
https://bugs.kde.org/show_bug.cgi?id=444108 Bug ID: 444108 Summary: kmail dragging mail to sidebar starts scrolling fast in wayland sessions Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: k...@kn0x.org Target Milestone: --- SUMMARY Affects kmail 5.18.2 and earlier versions. STEPS TO REPRODUCE 1. Use wayland session 2. Start kmail 3. Try to drag and drop an email into a different folder OBSERVED RESULT The window with folders starts scrolling through the list like crazy (either up or down) EXPECTED RESULT The sidebar stays still so emails can be moved to other folders SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Only affects kmail on wayland -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 438292] Can't move email in wayland
https://bugs.kde.org/show_bug.cgi?id=438292 Jeffrey Bouter changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 438292] Can't move email in wayland
https://bugs.kde.org/show_bug.cgi?id=438292 --- Comment #1 from Jeffrey Bouter --- Seems to be resolved in 5.17.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 438292] New: Can't move email in wayland
https://bugs.kde.org/show_bug.cgi?id=438292 Bug ID: 438292 Summary: Can't move email in wayland Product: kmail2 Version: Git (master) Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: k...@kn0x.org Target Milestone: --- SUMMARY When trying to move emails to folders on wayland, the sidebar start scrolling in an upwards direction, making it virtually impossible to move emails to a different folder. Obviously this only affects dragging an email using your mouse. STEPS TO REPRODUCE 1. Use a wayland session 2. Open kmail 3. Try to move an email to a different folder (by dragging it) OBSERVED RESULT Sidebar starts scrolling in an upwards direction EXPECTED RESULT The ability to move email to a new folder SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 425334] New: Akonadi crashes upon login after switching from QMYSQL to QPSQL
https://bugs.kde.org/show_bug.cgi?id=425334 Bug ID: 425334 Summary: Akonadi crashes upon login after switching from QMYSQL to QPSQL Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: k...@kn0x.org Target Milestone: --- Application: akonadiserver (5.14.3 (20.04.3)) Qt Version: 5.14.2 Frameworks Version: 5.72.0 Operating System: Linux 5.8.0-050800-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: Logging in to my system - Custom settings of the application: akonadiserverrc: [Debug] Tracer=null [%General] Driver=QPSQL [QPSQL] Host=127.0.0.1 InitDbPath= Name=akonadi Options= Password=REDACTED ServerPath= StartServer=false User=akonadi ~ The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 _mm_crc32_u64 (__V=, __C=462873301) at /usr/lib/gcc/x86_64-linux-gnu/9/include/smmintrin.h:848 #5 crc32 (ptr=0xfe17f00a3cc0, len=, h=) at tools/qhash.cpp:112 #6 0x7f0cabaa6ab4 in hash (seed=, len=, p=) at tools/qhash.cpp:223 #7 qHash (key=..., seed=) at tools/qhash.cpp:239 #8 0x7f0bf8024330 in ?? () #9 0x7f0ca4f446a0 in ?? () #10 0x5650c253b3a8 in ?? () #11 0x5650c2346dea in QHash::remove (this=0x7f0bf8024338, this@entry=0x5650c253b3a8, akey=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:102 #12 0x5650c23444a0 in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x5650c253b370, request=0x7f0bf8024330, errorMsg=...) at ./src/server/storage/itemretrievalmanager.cpp:179 #13 0x7f0cabc7f51e in QtPrivate::QSlotObjectBase::call (a=0x7f0ca4f44810, r=0x5650c253b370, this=0x7f0c900080d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate (sender=0x7f0c90005120, signal_index=3, argv=0x7f0ca4f44810) at kernel/qobject.cpp:3870 #15 0x7f0cabc79af7 in QMetaObject::activate (sender=sender@entry=0x7f0c90005120, m=m@entry=0x5650c243b800 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f0ca4f44810) at kernel/qobject.cpp:3930 #16 0x5650c2392188 in Akonadi::Server::AbstractItemRetrievalJob::requestCompleted (this=this@entry=0x7f0c90005120, _t1=, _t2=...) at ./obj-x86_64-linux-gnu/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:136 #17 0x5650c23479ab in Akonadi::Server::ItemRetrievalJob::callFinished (this=0x7f0c90005120, watcher=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:257 #18 0x7f0cabc7f51e in QtPrivate::QSlotObjectBase::call (a=0x7f0ca4f449c0, r=0x7f0c90005120, this=0x7f0c900085b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate (sender=0x7f0c90006960, signal_index=3, argv=0x7f0ca4f449c0) at kernel/qobject.cpp:3870 #20 0x7f0cabc79af7 in QMetaObject::activate (sender=, m=m@entry=0x7f0cac00d5e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f0ca4f449c0) at kernel/qobject.cpp:3930 #21 0x7f0cabfee7e3 in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158 #22 0x7f0cabfee8e8 in QDBusPendingCallWatcherPrivate::_q_finished (this=) at qdbuspendingcall.cpp:494 #23 QDBusPendingCallWatcher::qt_static_metacall (_o=, _c=, _id=, _a=) at .moc/moc_qdbuspendingcall.cpp:86 #24 0x7f0cabc772a9 in QObject::event (this=0x7f0c90006960, e=0x7f0bf804d1e0) at kernel/qobject.cpp:1339 #25 0x7f0cabc49767 in doNotify (event=0x7f0bf804d1e0, receiver=0x7f0c90006960) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #26 QCoreApplication::notify (event=0x7f0bf804d1e0, receiver=0x7f0c90006960, this=) at kernel/qcoreapplication.cpp:1151 #27 QCoreApplication::notifyInternal2 (receiver=0x7f0c90006960, event=0x7f0bf804d1e0) at kernel/qcoreapplication.cpp:1075 #28 0x7f0cabc4bf74 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5650c253f2c0) at kernel/qcoreapplication.cpp:1815 #29 0x7f0cabca2b87 in postEventSourceDispatch (s=0x7f0c90004bb0) at kernel/qeventdispatcher_glib.cpp:277 #30 0x7f0caa463fbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f0caa464240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7f0caa4642e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7f0cabca21e2 in QEventDispatcherGlib::processEvents (this=0x7f0c9b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #34 0x7f0cabc4824b in QEventLoop::exec (this=this@entry=0x7f0ca4f44da0, flags=..., flags@entry=...) at
