[kmail2] [Bug 487029] kmail uses media type literal packet in OpenPGP
https://bugs.kde.org/show_bug.cgi?id=487029 theodor-andreas.boer...@gmx.de changed: What|Removed |Added Component|folders |crypto -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 487029] New: kmail uses media type literal packet in OpenPGP
https://bugs.kde.org/show_bug.cgi?id=487029 Bug ID: 487029 Summary: kmail uses media type literal packet in OpenPGP Classification: Applications Product: kmail2 Version: 6.0.2 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: theodor-andreas.boer...@gmx.de Target Milestone: --- SUMMARY When encrypting messages in OpenPGP/MIME format, kmail uses the format tag 'm' in the literal data packet inside the OpenPGP Message, while in RFC 4880, only are 'b', 't' and 'u' are defined. Because of that, some MUAs do not display the decrypted message. kmail changed from using 'b' to using 'm' between 5.24.5 and 6.0.2. STEPS TO REPRODUCE 1. Compose an encrypted message. 2. Export the message, save it into an imap folder, or send it to another mailbox. 3. Try to view the message in Mozilla Thunderbird. OBSERVED RESULT Thunderbird shows obscure error message. EXPECTED RESULT The message should be displayable by Thunderbird (and other MUAs). ADDITIONAL INFORMATION Relevant section in RFC 4880: https://datatracker.ietf.org/doc/html/rfc4880#section-5.9 Draft for the 'm' format tag: https://www.ietf.org/archive/id/draft-moscaritolo-openpgp-literal-01.html You can use `gpg --list-packets` to find out which format tag was used in an OpenPGP Message. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 287540] Webkit based mail composer
https://bugs.kde.org/show_bug.cgi?id=287540 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #8 from Robert Riemann --- Blogilo is unmaintained for 6 years according to https://invent.kde.org/unmaintained/blogilo . I suggest to close this feature request. Personally, I also think that html editing is not on par yet with other mail composers, but I wonder if this report is well suited to track this. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 355342] composer mangles mail text on forwarding or edit as new
https://bugs.kde.org/show_bug.cgi?id=355342 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc --- Comment #4 from Robert Riemann --- I suggest to close this as no info was provided and nobody complaint since 2017! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 484706] IMAP-folders stay offline
https://bugs.kde.org/show_bug.cgi?id=484706 Silvan Calarco changed: What|Removed |Added CC||silvan.cala...@mambasoft.it -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 486160] All akonadi network resources are offline
https://bugs.kde.org/show_bug.cgi?id=486160 Silvan Calarco changed: What|Removed |Added CC||silvan.cala...@mambasoft.it -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 487025] New: kmail systray click is broken in 6.* if opened through kontact instead of kmail
https://bugs.kde.org/show_bug.cgi?id=487025 Bug ID: 487025 Summary: kmail systray click is broken in 6.* if opened through kontact instead of kmail Classification: Applications Product: kontact Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: k...@fuchsnet.ch Target Milestone: --- SUMMARY Kmail has an option to show a systray icon for unread mails. Clicking on this icon used to (and is supposed to, I guess, see below) toggle showing kmail if clicked. This no longer works in Plasma 6 / with KDEPim 6 if and only if kmail was started through kontact. It does work when starting kmail directly. It also occasionally starts working again after closing kontact, opening kmail, closing kmail, opening kontact. STEPS TO REPRODUCE 1. Configure kmail to show a systray icon 2. Start kontact 3. Click the icon OBSERVED RESULT The kmail (or kontact) window should toggle (minimize and un-minimize) EXPECTED RESULT Nothing happens on click Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 20NQS30W00 System Version: ThinkPad X390 Yoga -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 486119] Replying to a particular HTML message hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=486119 --- Comment #3 from Peter --- (In reply to Peter from comment #0) > SUMMARY > I have one HTML email chain, in particular, for which replying causes Kmail > to hang. > > STEPS TO REPRODUCE > 1. Start Kmail > 2. Select HTML email. > 3. Select Reply to. > > OBSERVED RESULT > Kmail hangs. Sometimes it opens the composer after a number of minutes. > However, if I try to compose a reply, the window hangs, with title bar > showing it as 'not responding', after entering a couple of lines. > > Strangely, there is one more kmail task listed in Task Managerthan in > System Monitor. (See screenshot.) > > Even if I kill the kmail process, or reboot, the kmail process is still > there, in the same hung state. > > EXPECTED RESULT > > > SOFTWARE/OS VERSIONS > Operating System: KDE neon 6.0 > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.1.0 > Qt Version: 6.7.0 > Kernel Version: 6.5.0-28-generic (64-bit) > Graphics Platform: Wayland > Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz > Memory: 7.5 GiB of RAM > Graphics Processor: Mesa Intel® Xe Graphics > Manufacturer: Dell Inc. > Product Name: XPS 13 9305 > > ADDITIONAL INFORMATION > I realise this isn't much information to go on, but I can attempt to provide > more if someone lets me know what to provide. (Would a copy of the message > be any help?) > > This seems similar to #484729, but this bug is reported as fixed. What makes the problem worse is that, on terminating and restarting the Kmail process, both a main Kmail window and a composer window for the reply try to open, resulting in Kmail hanging again. This can happen again and again. Eventually, I will manage to restart Kmail properly, but I haven't managed to identify what allows this to happen. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 487013] New: Calendar crashes when trying to create an event
https://bugs.kde.org/show_bug.cgi?id=487013 Bug ID: 487013 Summary: Calendar crashes when trying to create an event Classification: Applications Product: korganizer Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rui...@gmail.com Target Milestone: --- Application: korganizer (5.22.3 (22.12.3)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.14.21-150500.55.59-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.5" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: The calendar app crashes when trying to add an event to some specifically chosen day. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault [KCrash Handler] #4 KJob::setError (this=this@entry=0x4545454545454514, errorCode=errorCode@entry=100) at /usr/src/debug/kcoreaddons-5.103.0-150500.1.3.x86_64/src/lib/jobs/kjob.cpp:254 #5 0x7fc9c0be8544 in Akonadi::SessionPrivate::serverStateChanged (this=, state=) at /usr/src/debug/akonadi-server-22.12.3-bp155.1.7.x86_64/src/core/session.cpp:297 #6 0x7fc9bf5dda0b in QtPrivate::QSlotObjectBase::call (a=0x7fff0ef5e500, r=0x564e4cc99970, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate (sender=0x564e4cb4f5c0, signal_index=5, argv=0x7fff0ef5e500) at kernel/qobject.cpp:3923 #8 0x7fc9bf5d6e82 in QMetaObject::activate (sender=, m=m@entry=0x7fc9c0d05bc0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff0ef5e500) at kernel/qobject.cpp:3983 #9 0x7fc9c0be1e51 in Akonadi::ServerManager::stateChanged (this=, _t1=, _t1@entry=Akonadi::ServerManager::Broken) at /usr/src/debug/akonadi-server-22.12.3-bp155.1.7.x86_64/build/src/core/KF5AkonadiCore_autogen/include/moc_servermanager.cpp:180 #10 0x7fc9c0be4856 in Akonadi::ServerManagerPrivate::setState (state=Akonadi::ServerManager::Broken, this=) at /usr/src/debug/akonadi-server-22.12.3-bp155.1.7.x86_64/src/core/servermanager.cpp:73 #11 ::operator() (name=..., __closure=) at /usr/src/debug/akonadi-server-22.12.3-bp155.1.7.x86_64/src/core/servermanager.cpp:154 #12 QtPrivate::FunctorCall, QtPrivate::List, void, Akonadi::ServerManager::ServerManager(Akonadi::ServerManagerPrivate*):: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #13 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #14 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #15 0x7fc9bf5d44ab in QObject::event (this=0x564e4cb4f5c0, e=0x564e4d1c1620) at kernel/qobject.cpp:1347 #16 0x7fc9c015553c in QApplicationPrivate::notify_helper (this=this@entry=0x564e4c9580b0, receiver=receiver@entry=0x564e4cb4f5c0, e=e@entry=0x564e4d1c1620) at kernel/qapplication.cpp:3640 #17 0x7fc9c015c2ff in QApplication::notify (this=, receiver=0x564e4cb4f5c0, e=0x564e4d1c1620) at kernel/qapplication.cpp:3164 #18 0x7fc9bf5a0013 in QCoreApplication::notifyInternal2 (receiver=0x564e4cb4f5c0, event=0x564e4d1c1620) at kernel/qcoreapplication.cpp:1064 #19 0x7fc9bf5a01ee in QCoreApplication::sendEvent (receiver=receiver@entry=0x564e4cb4f5c0, event=event@entry=0x564e4d1c1620) at kernel/qcoreapplication.cpp:1462 #20 0x7fc9bf5a2a31 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x564e4c9540e0) at kernel/qcoreapplication.cpp:1821 #21 0x7fc9bf5a2fb8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1680 #22 0x7fc9bf6032b3 in postEventSourceDispatch (s=0x564e4cae1b10) at kernel/qeventdispatcher_glib.cpp:277 #23 0x7fc9bc4c182b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #24 0x7fc9bc4c1bd0 in ?? () from /usr/lib64/libglib-2.0.so.0 #25 0x7fc9bc4c1c5c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #26 0x7fc9bf60295c in QEventDispatcherGlib::processEvents (this=0x564e4cae11b0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #27 0x7fc9bf59e87a in QEventLoop::exec (this=this@entry=0x7fff0ef5eac0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:235 #28 0x7fc9bf5a80b7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1375 #29 0x564e4c751218 in main (argc=, argv=) at /usr/src/debug/korganizer-22.12.3-bp155.1.6.x86_64/src/main.cpp:72 [Inferior 1 (process 329) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 487003] New: kontact crashes if i put a "contact group" in the partecipant dialog
https://bugs.kde.org/show_bug.cgi?id=487003 Bug ID: 487003 Summary: kontact crashes if i put a "contact group" in the partecipant dialog Classification: Applications Product: kontact Version: 5.22.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: calendar Assignee: kdepim-bugs@kde.org Reporter: diego.ercol...@gmail.com Target Milestone: --- The issue came if you put a group (while you are writing it it autocomplete as it should) in the contact list, when you click "apply" a dialog appears telling that "it's not a correct address... would you like to add"? And if you click yest, kontact crashes -- You are receiving this mail because: You are the assignee for the bug.
