[kontact] [Bug 443037] New: Kontact Crashed When Starting
https://bugs.kde.org/show_bug.cgi?id=443037 Bug ID: 443037 Summary: Kontact Crashed When Starting Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: john4deidre2...@xtra.co.nz Target Milestone: --- Application: kontact (5.18.1 (21.08.1)) Qt Version: 5.15.2 Frameworks Version: 5.86.0 Operating System: Linux 5.14.6-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Tried to start kontact from menu and it crashed with this crash report The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fdee58075c0 (LWP 5982))] [KCrash Handler] #6 0x7fdeef2c1a75 in QScopedPointer >::operator-> (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 #7 qGetPtrHelper > > (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1143 #8 QAction::d_func (this=this@entry=0x0) at kernel/qaction.h:63 #9 QAction::setText (this=this@entry=0x0, text=...) at kernel/qaction.cpp:714 #10 0x7fde87158f8a in KMMainWidget::updateFolderMenu (this=0x563bf6b0f0f0) at /usr/src/debug/kmail-21.08.1-1.2.x86_64/src/kmmainwidget.cpp:3996 #11 0x7fde87150746 in KMMainWidget::setupActions (this=0x563bf6b0f0f0) at /usr/src/debug/kmail-21.08.1-1.2.x86_64/src/kmmainwidget.cpp:3384 #12 0x7fde8713ac14 in KMMainWidget::KMMainWidget (this=, parent=, aGUIClient=, actionCollection=, config=..., this=, parent=, aGUIClient=, actionCollection=, config=...) at /usr/src/debug/kmail-21.08.1-1.2.x86_64/src/kmmainwidget.cpp:249 #13 0x7fde87a2e26a in KMailPart::KMailPart (parent=, parentWidget=0x7fff69317ef0, this=0x563bf2f3db90, __in_chrg=, __vtt_parm=) at /usr/src/debug/kmail-21.08.1-1.2.x86_64/src/kmail_part.cpp:71 #14 KPluginFactory::createPartInstance (parentWidget=0x7fff69317ef0, parent=, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:812 #15 0x7fdeef90a5b2 in KPluginFactory::create (this=this@entry=0x563bf31c46b0, iface=0x7fdeede95068 <_ZL31qt_meta_stringdata_KParts__Part.lto_priv.0+168> "KParts::Part", parentWidget=parentWidget@entry=0x563bf3eea9c0, parent=parent@entry=0x563bf3eea9c0, args=..., keyword=...) at /usr/src/debug/kcoreaddons-5.86.0-1.2.x86_64/src/lib/plugin/kpluginfactory.cpp:212 #16 0x7fdeefa94e03 in KPluginFactory::create (args=..., parent=0x563bf3eea9c0, this=0x563bf31c46b0) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:853 #17 KontactInterface::Core::createPart (this=0x563bf3eea9c0, libname=0x563bf3142328 "kmailpart") at /usr/src/debug/kontactinterface-21.08.1-1.3.x86_64/src/core.cpp:79 #18 0x7fdeefa952ee in KontactInterface::Plugin::loadPart (this=this@entry=0x563bf515ea70) at /usr/src/debug/kontactinterface-21.08.1-1.3.x86_64/src/plugin.cpp:130 #19 0x7fde8727de06 in KMailPlugin::createPart (this=0x563bf515ea70) at /usr/src/debug/kmail-21.08.1-1.2.x86_64/src/kontactplugin/kmail/kmail_plugin.cpp:151 #20 0x7fdeefa95cd4 in KontactInterface::Plugin::part (this=this@entry=0x563bf515ea70) at /usr/src/debug/kontactinterface-21.08.1-1.3.x86_64/src/plugin.cpp:141 #21 0x7fdeefac20bb in Kontact::MainWindow::selectPlugin (this=0x563bf3eea9c0, plugin=0x563bf515ea70) at /usr/src/debug/kontact-21.08.1-1.2.x86_64/src/mainwindow.cpp:561 #22 0x7fdeefac34ec in Kontact::MainWindow::loadSettings (this=this@entry=0x563bf3eea9c0) at /usr/src/debug/kontact-21.08.1-1.2.x86_64/src/mainwindow.cpp:690 #23 0x7fdeefac77f5 in Kontact::MainWindow::initObject (this=0x563bf3eea9c0) at /usr/src/debug/kontact-21.08.1-1.2.x86_64/src/mainwindow.cpp:159 #24 0x7fdeefac84f7 in Kontact::MainWindow::MainWindow (this=, this=) at /usr/src/debug/kontact-21.08.1-1.2.x86_64/src/mainwindow.cpp:88 #25 0x563bf19d8035 in KontactApp::activate (this=0x7fff69318cf0, args=..., workingDir=...) at /usr/src/debug/kontact-21.08.1-1.2.x86_64/src/main.cpp:119 #26 0x7fdeefa9234e in KontactInterface::PimUniqueApplication::newInstance (this=0x7fff69318cf0, startupId=..., arguments=..., workingDirectory=...) at /usr/src/debug/kontactinterface-21.08.1-1.3.x86_64/src/pimuniqueapplication.cpp:177 #27 0x7fdeefa94703 in KontactInterface::PimUniqueApplication::qt_static_metacall (_c=, _id=, _a=0x7fff69318600, _o=0x7fff69318cf0) at /usr/src/debug/kontactinterface-21.08.1-1.3.x86_64/build/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:87 #28 KontactInterface::PimUniqueApplication::qt_static_metacall (_o=_o@entry=0x7fff69318cf0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=1, _a=_a@entry=0x7fff69318600) at
[korganizer] [Bug 443029] New: Opening KOrganizer Settings > Configure KOrganizer crashes the app
https://bugs.kde.org/show_bug.cgi?id=443029 Bug ID: 443029 Summary: Opening KOrganizer Settings > Configure KOrganizer crashes the app Product: korganizer Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: nyo...@outlook.com Target Milestone: --- Application: korganizer (5.18.1 (21.08.1)) Qt Version: 5.15.3 Frameworks Version: 5.86.0 Operating System: Linux 5.11.0-36-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: Opening KOrganizer's Configure window. I have one .ics file imported and I've been having issues updating the event from within KOrganizer. I wanted to go and troubleshoot the group settings but i obviously couldnt get into that menu. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Aborted [New LWP 36108] [New LWP 36109] [New LWP 36110] [New LWP 36112] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f0999a48aff in __GI___poll (fds=0x7ffe84a2f0f8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f09929e1bc0 (LWP 36105))] Thread 5 (Thread 0x7f098b5ef700 (LWP 36112)): #0 0x7f0999a48aff in __GI___poll (fds=0x7f0978004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f099740336e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f09974034a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f099a0315eb in QEventDispatcherGlib::processEvents (this=0x7f0978000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0999fd587b in QEventLoop::exec (this=this@entry=0x7f098b5ee9e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f0999def292 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f0999df042c in QThreadPrivate::start (arg=0x55886c22b8d0) at thread/qthread_unix.cpp:329 #7 0x7f0997f5a609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f0999a55293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f0990940700 (LWP 36110)): #0 0x7f0999a48aff in __GI___poll (fds=0x7f098002d990, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f099740336e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f09974034a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f099a0315eb in QEventDispatcherGlib::processEvents (this=0x7f098b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0999fd587b in QEventLoop::exec (this=this@entry=0x7f099093f9e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f0999def292 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f0999df042c in QThreadPrivate::start (arg=0x55886c2207a0) at thread/qthread_unix.cpp:329 #7 0x7f0997f5a609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f0999a55293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f0991151700 (LWP 36109)): #0 0x7f0999a48aff in __GI___poll (fds=0x7f0984004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f099740336e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f09974034a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f099a0315eb in QEventDispatcherGlib::processEvents (this=0x7f0984000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0999fd587b in QEventLoop::exec (this=this@entry=0x7f09911509b0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f0999def292 in QThread::exec (this=this@entry=0x7f099b090d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f099b00cf4b in QDBusConnectionManager::run (this=0x7f099b090d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #7 0x7f0999df042c in QThreadPrivate::start (arg=0x7f099b090d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:329 #8 0x7f0997f5a609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f0999a55293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f0991e76700 (LWP 36108)): #0 0x7f0999a48aff in __GI___poll
[kmail2] [Bug 443021] New: Message Marked Unread Again When New Mail Received
https://bugs.kde.org/show_bug.cgi?id=443021 Bug ID: 443021 Summary: Message Marked Unread Again When New Mail Received Product: kmail2 Version: 5.15.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: gtwilli...@gmail.com Target Milestone: --- SUMMARY Messages are often marked as unread after reading when new mail is received. This happens with Gmail account. STEPS TO REPRODUCE 1. Read mail just before scanning for new mail 2. 3. OBSERVED RESULT Already-read mail gets marked as unread until selected again EXPECTED RESULT Read mail stays marked read while new messages show up. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 KDE Plasma Version: 5.20.5-1.fc33.x86_64 KDE Frameworks Version: 5.79.0-2.fc33.x86_64 Qt Version: 5.15.2-2.fc33.x86_64 ADDITIONAL INFORMATION This is a long-standing problem that has been here for many years. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 443019] New: Some Mails are displayed as HTML by default even though it is not set as preferred
https://bugs.kde.org/show_bug.cgi?id=443019 Bug ID: 443019 Summary: Some Mails are displayed as HTML by default even though it is not set as preferred Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY In KMail's settings under "security" I have NOT checked "Prefer HTML view over plain text". I even went into the folder preferences for my inbox and specifically set it to prefer plain text over HTML, yet many e-mails are displayed as HTML by default. After opening the mail I can manually (and only temporarily) switch to plain text view, but I'd like to force that as the default for all mails. STEPS TO REPRODUCE 1. Make sure that HTML view is NOT preferred in the global security setings 2. Optionally, also set the inbox to prefer plain text view. 3. Open some mails from various sources, some of them will still open in HTML view OBSERVED RESULT Some mails open in HTML view even though plain text view is preferred EXPECTED RESULT When HTML view is not preferred (when plain text is preferred), ALL mails should be forced into plain text view by default when opening them. Also, it might be less confusing if in KMail's security settings there were radio buttons for selecting either "prefer plain text" or "prefer HTML" like in the folder settings, instead of just a check box for "prefer HTML view" SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 439958] X-Face can break cryptographic signatures
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #16 from Sandro Knauß --- (In reply to David C. Bryant from comment #14) > (In reply to Sandro Knauß from comment #13) > > I can confirm it [snip ...] > > > > @David: can you check, if you get proper signatures, if you disable the > > picture (X-Face)? (Picture tab of the Identity). > > Yes, Sandro, signatures work fine with X-Face disabled. See the screenshot > I'm adding as an attachment to this bug report today. I am using the same > picture as was in the X-Face header as my gravatar (see discussion below). > So the message appears the same (to me) both with and without embedded > X-Face headers (except that X-Face breaks the crypto signature). Okay, than I have to look into why X-Face header sometimes breaks the signature. It needs to be any modification after the signature is done. The X-Face header have multiple lines in autosave files. So I expect, that somehow the newlines gets stripped out after the signature is created. > A friend referred me to this web page: > https://datatracker.ietf.org/doc/html/draft-autocrypt-lamps-protected- > headers-02 and raised the question "should the X-Face header be a protected > header?" I'm not real sure of the answer. Personally, I don't care if > somebody views the wrong picture in a signed message I send. Integrity of > the text message is all I really care about. Others might feel differently, > though. Well the X-Face header is for sure a non-structural header and the RFC tells us to copy ALL non-structural headers, that are known when composing the mail. https://datatracker.ietf.org/doc/html/draft-autocrypt-lamps-protected-headers-02#section-4.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 439958] X-Face can break cryptographic signatures
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #14 from David C. Bryant --- (In reply to Sandro Knauß from comment #13) > I can confirm it [snip ...] > > @David: can you check, if you get proper signatures, if you disable the > picture (X-Face)? (Picture tab of the Identity). Yes, Sandro, signatures work fine with X-Face disabled. See the screenshot I'm adding as an attachment to this bug report today. I am using the same picture as was in the X-Face header as my gravatar (see discussion below). So the message appears the same (to me) both with and without embedded X-Face headers (except that X-Face breaks the crypto signature). A friend referred me to this web page: https://datatracker.ietf.org/doc/html/draft-autocrypt-lamps-protected-headers-02 and raised the question "should the X-Face header be a protected header?" I'm not real sure of the answer. Personally, I don't care if somebody views the wrong picture in a signed message I send. Integrity of the text message is all I really care about. Others might feel differently, though. One other thing. The field used to display the "X-Face" picture is also used to display "gravatars" kept on file in KAddressbook. So people can (in effect) attach pictures to their messages without using "X-Face" (with the recipient's assistance). One can even configure KMail itself to search for gravatars on the internet (Configure KMail --> Plugins --> Gravatar Config). So "X-Face" is becoming redundant. Just a thought. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 439958] X-Face can break cryptographic signatures
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #15 from David C. Bryant --- Created attachment 141949 --> https://bugs.kde.org/attachment.cgi?id=141949=edit Screenshot -- signature works OK with X-Face disabled -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 443009] New: Replying email breaks text encoding
https://bugs.kde.org/show_bug.cgi?id=443009
Bug ID: 443009
Summary: Replying email breaks text encoding
Product: kontact
Version: 5.18.1
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: mail
Assignee: kdepim-bugs@kde.org
Reporter: boite.pour.s...@gmail.com
Target Milestone: ---
SUMMARY
On some email (not all), replying breaks the text encoding and all "special"
characters are replaced by unreadable code.
The text is displayed correctly in the initial message view (which is HTML)
like this:
Je suis en train de créer une
But if I hit reply, I get this instead:
> Je suis en train de créer
STEPS TO REPRODUCE
1. The initial message was written with Apple mail and is using
quoted-printable for the content transfer encoding, and the content type is
specifying utf-8, like this:
--Apple-Mail-B6D63D2D-099E-44BF-9EDA-531641451B38
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
Merci Vincent.=20
Salut Cyril j=E2=80=99esp=C3=A8re que tu vas bien ?=20
Je suis en train de cr=C3=A9er...
[...content removed here for privacy...]
--Apple-Mail-B6D63D2D-099E-44BF-9EDA-531641451B38
Content-Type: multipart/mixed;
boundary=Apple-Mail-ACFFAAD7-7608-4761-8991-19B6D013FB0C
Content-Transfer-Encoding: 7bit
--Apple-Mail-ACFFAAD7-7608-4761-8991-19B6D013FB0C
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
Merci Vincent.=
Salut Cyril j=E2=80=99esp=C3=A8re que tu vas bien ?Je suis en train de cr=C3=A9er
[...content removed here for privacy...]
2. If you hit reply on such message, you'll get this:
Le lundi 27 septembre 2021 07:53:13 CEST, vous avez écrit :
> Merci Vincent.
>
> Salut Cyril jâespère que tu vas bien ?
> Je suis en train de créer
3. Please notice that if I select some text and hit reply, the text is
correctly encoded (but I loose the unselected text obviously)
4. Also, switching HTML or plain text does not work either to restore the
correct encoding of the text
5. Also, the part that KMail is writing by itself ("vous avez écrit :") is also
wrong.
It's not a duplicate of bug 441136 since I don't have the option "Keep original
charset when replying" selected.
OBSERVED RESULT
See above
EXPECTED RESULT
See above
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85
Qt Version: 5.15.2
KMail: Version 5.18.1 (21.08.1)
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are the assignee for the bug.
[korganizer] [Bug 436445] KOrganizer fails to delete events and tasks from google calendar
https://bugs.kde.org/show_bug.cgi?id=436445 dreamndi changed: What|Removed |Added CC||shosta...@gmail.com --- Comment #2 from dreamndi --- I have the same bug. Occasionally Plasma Akonadi opens a page with Google Login. KDE neon UE 5.22 KDE Plasma 5.22.5 KDE Frameworks 5.86 Qt Version 5.15.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 439958] X-Face can break cryptographic signatures
https://bugs.kde.org/show_bug.cgi?id=439958 Sandro Knauß changed: What|Removed |Added Status|REPORTED|CONFIRMED Component|composer|crypto Summary|Error in cryptographic |X-Face can break |signatures affixed by KMail |cryptographic signatures Ever confirmed|0 |1 --- Comment #13 from Sandro Knauß --- I can confirm it, but it is not reproducible with every gpg key, what is quite strange. What I checked is to create a draft with X-Face enabled. For one gnupg key the signatures keep fine. When I select another key, the signature is broken with the same X-Face. (I actually modified the identity and change the gnupg key and the matching email address). At least, if those mails get send, the signautre would get broken in any case, as the X-Face line is too long for most mail servers, so they would break the line and this will break the signature in always. @David: can you check, if you get proper signatures, if you disable the picture (X-Face)? (Picture tab of the Identity). -- You are receiving this mail because: You are the assignee for the bug.
