[kleopatra] [Bug 458325] cannot import .p12 certificate
https://bugs.kde.org/show_bug.cgi?id=458325 Soyasi changed: What|Removed |Added CC||orla...@robledano.es --- Comment #1 from Soyasi --- I have the same problem with the free certificates in pfx or p12 format issued by actalis. For kleopatra to read them, I import them with the Windows 11 certificate manager and export them again with the private key, so if it reads them without problems. The only difference I see between the original and the one issued by Windows 11. openssl pkcs12 -info -in certificado.pfx *Original* MAC: sha1, Iteration 102400 MAC length: 20, salt length: 20 PKCS7 Data Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 51200 Bag Attributes localKeyID: XX XX XX XX friendlyName: xx...@gmail.com Key Attributes: Enter PEM pass phrase: -windows 11- MAC: sha1, Iteration 2000 MAC length: 20, salt length: 20 PKCS7 Data Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2000 Bag Attributes localKeyID: XX XX XX XX friendlyName: x...@gmail.com Microsoft CSP Name: Microsoft Enhanced Cryptographic Provider v1.0 Key Attributes X509v3 Key Usage: 10 Enter PEM pass phrase: You can get a free testing certificate on the next page: https://extrassl.actalis.it/portal/uapub/freemail?lang=en -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 478734] Main window is not closable after first close to tray
https://bugs.kde.org/show_bug.cgi?id=478734 Vincenc Elias changed: What|Removed |Added Version|5.240.81|unspecified Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||vinca.ostrav...@gmail.com Keywords||reproducible --- Comment #1 from Vincenc Elias --- Thank you for your report! I can replicate the bug on the latest unstable kde neon with kmail version 5.240.85 beta 2. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 478734] Main window is not closable after first close to tray
https://bugs.kde.org/show_bug.cgi?id=478734 Andrew Shark changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 478734] New: Main window is not closable after first close to tray
https://bugs.kde.org/show_bug.cgi?id=478734 Bug ID: 478734 Summary: Main window is not closable after first close to tray Classification: Applications Product: kmail2 Version: 5.240.81 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: ash...@linuxcomp.ru Target Milestone: --- It is impossible to close the KMail window second time. My setup is that kmail starts minimized to tray. And when I close window, it normally is still working in tray. However, after upgrade to kde-unstable (I am on Arch, kmail package is 24.01.80-3), it behaves wrong. STEPS TO REPRODUCE 0. Configure KMail so it can be closed to tray. 1. Start Kmail (may be autostarted at login) 2. Click the tray icon to show main window. 3. Close the window. The window closes and the tray icon still shown (as expected). 4. Click the tray icon again to show main window. 5. Try to close window now. OBSERVED RESULT There is no reaction on close button. You can press Ctrl Q or just kill the window with Ctrl + Meta + Esc, but then the application terminates (no more tray icon). EXPECTED RESULT The window should be closed normally, and the app should continue working in tray. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.7-arch1-1 (64-bit) Graphics Platform: Wayland Additional info: After killing the window, relaunching kmail shows the message that it failed to start. Second start however normally start the kmail. And then the bug of unclosable window can be reproduced. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 475412] akonadi_mail_dispatcher_agent closed unexcpectedly
https://bugs.kde.org/show_bug.cgi?id=475412 --- Comment #10 from tprotopope...@gmail.com --- (In reply to Laurent Montel from comment #9) > Do you use smtp mailtransport ? Yes, for one account (gmail), and exchange for two others. I have had to switch back to the standard opensuse 15.5 packages for the time being (busy time at work, can't afford not to have email working right now). -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 478727] New: Crash when I select an encrypted email
https://bugs.kde.org/show_bug.cgi?id=478727 Bug ID: 478727 Summary: Crash when I select an encrypted email Classification: Applications Product: kontact Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tabaccat...@yahoo.it Target Milestone: --- Application: kontact (5.24.1 (23.08.1)) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.0-14-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 23.10 DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Open Kmail, click on an encreypted email (PEC, italia Posta Elettronica Certificata) et voilà, it crashes. Only whit some email, especially from the tax office (not jocking) The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f99fc2b6d56 in KMime::Content::headerByType(char const*) const () from /lib/x86_64-linux-gnu/libKPim5Mime.so.5 #5 0x7f99fc2b7c4e in KMime::Content::contentTransferEncoding(bool) () from /lib/x86_64-linux-gnu/libKPim5Mime.so.5 #6 0x7f99fc2b8caf in ?? () from /lib/x86_64-linux-gnu/libKPim5Mime.so.5 #7 0x7f99fc2b8dfb in KMime::Content::decodedText(bool, bool) () from /lib/x86_64-linux-gnu/libKPim5Mime.so.5 #8 0x7f99f4300a35 in MimeTreeParser::ObjectTreeParser::extractNodeInfos(KMime::Content*, bool) () from /lib/x86_64-linux-gnu/libKPim5MimeTreeParser.so.5 #9 0x7f99f43015ec in MimeTreeParser::ObjectTreeParser::parseObjectTree(KMime::Content*, bool) () from /lib/x86_64-linux-gnu/libKPim5MimeTreeParser.so.5 #10 0x7f99f4485adc in MessageViewer::ViewerPrivate::parseContent(KMime::Content*) () from /lib/x86_64-linux-gnu/libKPim5MessageViewer.so.5 #11 0x7f99f4488334 in MessageViewer::ViewerPrivate::displayMessage() () from /lib/x86_64-linux-gnu/libKPim5MessageViewer.so.5 #12 0x7f99f4488a89 in MessageViewer::ViewerPrivate::updateReaderWin() () from /lib/x86_64-linux-gnu/libKPim5MessageViewer.so.5 #13 0x7f9a63d06312 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f99f42e0d62 in MimeTreeParser::NodeHelper::update(MimeTreeParser::UpdateMode) () from /lib/x86_64-linux-gnu/libKPim5MimeTreeParser.so.5 #15 0x7f9a63d06312 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f99f42e0d02 in ?? () from /lib/x86_64-linux-gnu/libKPim5MimeTreeParser.so.5 #17 0x7f9a63d06312 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f99f498075b in ?? () from /lib/x86_64-linux-gnu/libqgpgme.so.15 #19 0x7f9a63cf99a0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f9a6496bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f9a63ccc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f9a63ccfeb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f9a63d286f7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f9a5a25cb2c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f9a5a2b846f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f9a5a25ad20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f9a63d27daa in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f9a63ccb15b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f9a63cd3904 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x55823c0d4587 in ?? () #31 0x7f9a632280d0 in __libc_start_call_main (main=main@entry=0x55823c0d3bd0, argc=argc@entry=1, argv=argv@entry=0x775a89b8) at ../sysdeps/nptl/libc_start_call_main.h:58 #32 0x7f9a63228189 in __libc_start_main_impl (main=0x55823c0d3bd0, argc=1, argv=0x775a89b8, init=, fini=, rtld_fini=, stack_end=0x775a89a8) at ../csu/libc-start.c:360 #33 0x55823c0d4b35 in ?? () [Inferior 1 (process 4344) detached] The reporter indicates this bug may be a duplicate of or related to bug 426432, bug 470858, bug 467921, bug 474477. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 Fri13 changed: What|Removed |Added CC||frii...@gmail.com --- Comment #73 from Fri13 --- I have not used KMail for few years now. Just returned back to use it after using Gmail web interface for so long, and solely because after decade the wished features had been finally implemented (Ctrl+M to hide menus for new and message windows). I spent just over an hour to seek that where was the setting to hide that HTML bar. I knew that there is a setting to hide it, all I could find was all the new nice features like exceptions to download external data etc. IMHO email should be just about text. Any HTML email is nothing else than trouble and insult to every email user, same way as idea of top posting. After an hour I gave up and decided to just search for where the setting was. And I found this thread... So after few years, I decided to log-in to my old bugzilla account just to write this comment. I read almost all comments in this thread, and I am stunned that maintainer just say "As-Is" and "Closed Interntional". Those are not valid reasoning at all for closing this bug report. KDE was known for long time to be the most configurable and customizable by the user, to get it look as wanted. KMail had for long time the annoying forced way to require menubar be visible everywhere, denying to make a functional, easy and nice looking interface for email users. And now one step forward, one step backward... Gain something, lose something. This time it is just all the time on-your-face that there is some mystical HTML message or NO-HTML etc. Just confusing normal users and causing fear and worry. Not that there would be one time information or until user clicks "Don't show anymore", but it is forced to stay there all the time... -- You are receiving this mail because: You are the assignee for the bug.
