[kmail2] [Bug 485661] Kmail popup windows closes when trying to copy or move message to folder
https://bugs.kde.org/show_bug.cgi?id=485661 Thomas Fischer changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #11 from Thomas Fischer --- Can confirm the problem with Fedora Linux 40: KMail 24.08.2 Qt 6.7.2 KDE Frameworks 6.7.0 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 445351] Akregator always wants to recover the session on boot
https://bugs.kde.org/show_bug.cgi?id=445351 --- Comment #12 from Thomas Dickson --- As of Akregator 6.1.1 (at least for me): The recover session screen is still showing up every time it's launched, but it does seem to remember all the actions from the past session correctly (read articles, etc) -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 445351] Akregator always wants to recover the session on boot
https://bugs.kde.org/show_bug.cgi?id=445351 --- Comment #10 from Thomas Dickson --- It's definitely an issue with how akregator uses KIO (or maybe a bug in KIO itself?), as the error message is from KIO::SlaveBase::send (src/core/slavebase.cpp:1470). May have to look around and see what part of akregator calls the KIO stuff. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 445351] Akregator always wants to recover the session on boot
https://bugs.kde.org/show_bug.cgi?id=445351 --- Comment #8 from Thomas Dickson --- There's a whole lot of write errors as akregator exits: ^C kf.kio.core: An error occurred during write. The worker terminates now. kf.kio.core: An error occurred during write. The worker terminates now. user@comp2: ~ $ kf.kio.core: An error occurred during write. The worker terminates now. kf.kio.core: An error occurred during write. The worker terminates now. kf.kio.core: An error occurred during write. The worker terminates now. kf.kio.core: An error occurred during write. The worker terminates now. kf.kio.core: An error occurred during write. The worker terminates now. kf.kio.core: An error occurred during write. The worker terminates now. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 445351] Akregator always wants to recover the session on boot
https://bugs.kde.org/show_bug.cgi?id=445351 Thomas Dickson changed: What|Removed |Added CC||thom-dick...@proton.me --- Comment #7 from Thomas Dickson --- It seems to be an issue with how Akregator exits primarily, maybe it's a problem with how wayland signals applications to exit? I will endeavour to run a debug build and see what it spits out and put it here later if I can. This seems to be a very impactful bug on the user's experience, could we change the importance of this bug? -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 464247] Article images too large to fit in viewport
https://bugs.kde.org/show_bug.cgi?id=464247 Thomas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||thom-dick...@proton.me Latest Commit||170f2fa0c5427102bed7367cf03 ||f7cc8a207b646 --- Comment #3 from Thomas --- Fixed as of commit 170f2fa0c5427102bed7367cf03f7cc8a207b646 - https://invent.kde.org/pim/akregator/-/commit/170f2fa0c5427102bed7367cf03f7cc8a207b646?merge_request_iid=48 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 483987] New: "Reply all" protection: ask for confirmation before replying to a potentially large number of recipients
https://bugs.kde.org/show_bug.cgi?id=483987 Bug ID: 483987 Summary: "Reply all" protection: ask for confirmation before replying to a potentially large number of recipients Classification: Applications Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- Similar to the existing "Check Before Send Mail" plugin, Kmail should warn and ask for an extra confirmation if an email is about to be sent to a potentially large number of recipients. Criteria to test for: - Number of recipients in To, CC, and BCC fields is about a certain threshold - A mail address previously configured by the user as a "distribution address" is used. A "distribution address" would be a mail address like "every...@example.com", where the mail server then takes are to distribute the mail to a large number of recipients. Those check should not be limited to cases when the user chooses "reply all". Even a 'normal' reply to a distribution address should trigger a warning. Implementation detail/suggestion: Before sending, KMail or Akonadi counts the number of mail addresses (To, CC, BBC). Every mail address which is in the list of known distribution addresses counts 1000 (or any sufficiently large number). The threshold for a warning is 10. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476572] New: Display the colour of an email when selected
https://bugs.kde.org/show_bug.cgi?id=476572 Bug ID: 476572 Summary: Display the colour of an email when selected Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: pitho...@free.fr Target Milestone: --- Bonjour, Example : in the list of emails, if the text of one email is displayed in red (= important), it becomes white on a blue line background when selected. The color selected for an email must be visible when the email is selected, whichever is this color. When changing the color, this must be acknowledged / visible on the display. Pierre STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476497] New: Checking words spelling
https://bugs.kde.org/show_bug.cgi?id=476497 Bug ID: 476497 Summary: Checking words spelling Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: pitho...@free.fr Target Milestone: --- Kmail must not check the text which is not part of the answer typed !!! The text of the original email must not be checked. Pierre STEPS TO REPRODUCE 1. Answer an email with spell mistakes 2. 3. OBSERVED RESULT EXPECTED RESULT Only the text typed for the answer must be checked, nothing else. SOFTWARE/OS VERSIONS Mageia 9/KDE Plasma: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476321] Answering an email to which a file is attached
https://bugs.kde.org/show_bug.cgi?id=476321 --- Comment #5 from Pierre THOMAS --- (In reply to Laurent Montel from comment #3) > I understand french :) (I am french :) ) > > I tested your text by when I reply it's quoted => it will not show warning. > > Could you paste a screenshot from your composer when you reply and you see > warning. > > For me I have ">" at the beginning of each line > => code will not check this text. > > so it's ok for me. > > thanks Bonjour, For the email in the screenshot, the warning is displayed after having just clicked "Répondre", nothing else. The problem is similar for spell checking: the spell checking must absolutely be limited to the text typed for the answer ... Pierre -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476321] Answering an email to which a file is attached
https://bugs.kde.org/show_bug.cgi?id=476321 --- Comment #4 from Pierre THOMAS --- Created attachment 162835 --> https://bugs.kde.org/attachment.cgi?id=162835&action=edit Screenshot -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476321] Answering an email to which a file is attached
https://bugs.kde.org/show_bug.cgi?id=476321 --- Comment #2 from Pierre THOMAS --- (In reply to Laurent Montel from comment #1) > I don't understand how to reproduce it. > We check if text has "attachment" words. > but we mustn't check when text is quoted > > => please provide a test email please. > > Thanks I thank you Laurent for considering my request. Example Email received : Bonjour à tous, Je vous laisse découvrir le programme qui vous a été concocté par la commission animation pour le week-end avec hébergement des 4 et 5 mai 2024. Vous trouverez en pièce jointe la fiche d'inscription et le descriptif du séjour. Le nombre de places étant limité, priorité est donnée aux adhérents. Toutefois, il vous sera possible d'inscrire un invité non adhérent sur votre bulletin d'inscription, sachant que son inscription ne pourra être validée que sous réserve de places disponibles. Amicalement Catherine When I click to locate the mouse cursor at the beginning of the text of my answer to type, and then I type Enter, without having typed anything else, I get the warning : Le message que vous avez composé fait référence à un fichier joint, mais vous n'avez rien joint. Voulez-vous joindre un fichier à votre message ? (I hope you understang French !) I didn’t type any word concerning a file to attach !!! This warning must not be displayed !!! I guess the warning comes from the fact that the text of the the original email contains « en pièce jointe » (???). The text of the original email must not be analyzed by KMail !!! Pierre -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476321] New: Answering an email to which a file is attached
https://bugs.kde.org/show_bug.cgi?id=476321 Bug ID: 476321 Summary: Answering an email to which a file is attached Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: pitho...@free.fr Target Milestone: --- Kmail must not propose to join a file if nothing in the answer to an original email suggests a file to be joined. If the original email has a file joined (and perhaps words saying a file is joined), Kmail proposes to join a file to the answer !!! Pierre STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Mageia 9 / Plasma 5.27.5 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476185] New: Editing an email saved as a draft
https://bugs.kde.org/show_bug.cgi?id=476185 Bug ID: 476185 Summary: Editing an email saved as a draft Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: pitho...@free.fr Target Milestone: --- Bonjour, First of all, saving an email as a draft must not close the compose window : saving an email as a draft does not mean that the composition of the email is finished ! And, after having saved an email as a draft, when using the menu "Modify as new", the logo image used as a signature is lost ! Pierre STEPS TO REPRODUCE: see above EXPECTED RESULT - The compose window must not be closed when saving as a draft. - When editing again a draft, it must be presented as it was previously composed with the signature. Linux/KDE Plasma: Mageia 9 / Plasma KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476050] Sender of a new email
https://bugs.kde.org/show_bug.cgi?id=476050 --- Comment #1 from Pierre THOMAS --- And it is risky: a sent email to an association (3 association) may be sent by the default account which my private account and which is not the account I must use for this association !! I consider this as a severe bug ! Pierre -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 461233] Default time unit for suspending
https://bugs.kde.org/show_bug.cgi?id=461233 --- Comment #2 from Pierre THOMAS --- Bonjour, What does that mean ? The regression in KOrganizer will not be corrected ? Pierre -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476050] Sender of a new email
https://bugs.kde.org/show_bug.cgi?id=476050 Pierre THOMAS changed: What|Removed |Added CC||pitho...@free.fr -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476049] Allow the distant content in an email
https://bugs.kde.org/show_bug.cgi?id=476049 Pierre THOMAS changed: What|Removed |Added CC||pitho...@free.fr -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 461233] Default time unit for suspending
https://bugs.kde.org/show_bug.cgi?id=461233 Pierre THOMAS changed: What|Removed |Added CC||pitho...@free.fr -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476075] Sending a link to a web page from Firefox
https://bugs.kde.org/show_bug.cgi?id=476075 Pierre THOMAS changed: What|Removed |Added CC||pitho...@free.fr -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476075] New: Sending a link to a web page from Firefox
https://bugs.kde.org/show_bug.cgi?id=476075 Bug ID: 476075 Summary: Sending a link to a web page from Firefox Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: pitho...@free.fr Target Milestone: --- I use Mageia Linux. I defined KMail as the default mail client. When clicking on the button "Envoyer par e-mail un lien vers la page" (Send by email a link to the page), this opens a compose windows of KMail, it is OK. But the sending account is not the account of the default identity : it must be the account of the default identity ! Or what else ??!! What is the account chosen by KMail ? (if there is a choice ??) Pierre -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476050] New: Sender of a new email
https://bugs.kde.org/show_bug.cgi?id=476050 Bug ID: 476050 Summary: Sender of a new email Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: pitho...@free.fr Target Milestone: --- When creating a new email to send, the sender of this new email must be the account / identity corresponding to the folder selected (main folder, subfolders: Received, Sent, Draft). If the main folder is selected : OK If a subfolder is selected : the account by default is the sender !!! This is not correct Pierre -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 476049] New: Allow the distant content in an email
https://bugs.kde.org/show_bug.cgi?id=476049 Bug ID: 476049 Summary: Allow the distant content in an email Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: pitho...@free.fr Target Milestone: --- After having tested the possibilities, I guess there is a bug somewhere … For one email, by a right click on the sender address : ◦ I marked both cases Afficher le format HTML (Display HTML format), ◦ In the contact details, I marked the case Autoriser les contenus distants dans les messages HTML reçus (Allow distant contents in received HTML emails). But when the same email or another email of the same sender is selected and displayed, the warning is displayed again (Ce message HTML peut contenir des références externes à des images ...) !!! This is very annoying. Allowing the distant content in an email must be possible with 2 mouse clicks once for all. Pierre -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 475916] Line spacing in quoted text
https://bugs.kde.org/show_bug.cgi?id=475916 Pierre THOMAS changed: What|Removed |Added CC||pitho...@free.fr -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 475916] New: Line spacing in quoted text
https://bugs.kde.org/show_bug.cgi?id=475916 Bug ID: 475916 Summary: Line spacing in quoted text Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: pitho...@free.fr Target Milestone: --- When answering to an email, even this received email is displayed correctly, the text of the original email quoted is displayed with very very large spacing between the lines : this is a bug which must be corrected ! I can’t send such emails. Pierre STEPS TO REPRODUCE 1. Click on Answer button 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 474144] Korganizer crashes when forwarding an event
https://bugs.kde.org/show_bug.cgi?id=474144 --- Comment #2 from Thomas Monjalon --- In Korganizer, I do a right-clik on an event and choose "send as iCalendar". Then I choose the recipient, click OK, and it crashes. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 475362] New: Crash after updating Debian Bookworm to testing
https://bugs.kde.org/show_bug.cgi?id=475362 Bug ID: 475362 Summary: Crash after updating Debian Bookworm to testing Classification: Applications Product: korganizer Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: thack...@nexgo.de Target Milestone: --- Application: korganizer (5.22.3 (22.12.3)) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.5.0-1-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Hello @ll, after updating Debian Bookworm AMD64 to testing AMD64, korganizer is crashing after starting it. Sorry for the inconvenience Thomas. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault [KCrash Handler] #4 0x7fd3051dc020 in KJob::setError(int) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #5 0x7fd305516dc4 in Akonadi::SessionPrivate::serverStateChanged(Akonadi::ServerManager::State) () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 #6 0x7fd303efba32 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd305511d01 in Akonadi::ServerManager::stateChanged(Akonadi::ServerManager::State) () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 #8 0x7fd305513c54 in ?? () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 #9 0x7fd303eef400 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fd304b62d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7fd303ec30d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fd303ec66d1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fd303f1d1e3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fd3015b81b4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd3015bb2d7 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd3015bb8f0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7fd303f1c8d6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fd303ec1b7b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fd303eca020 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x564af86cc6da in ?? () #21 0x7fd3036406ca in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #22 0x7fd303640785 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #23 0x564af86cc971 in ?? () [Inferior 1 (process 72771) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 474144] New: Korganizer crashes when forwarding an event
https://bugs.kde.org/show_bug.cgi?id=474144
Bug ID: 474144
Summary: Korganizer crashes when forwarding an event
Classification: Applications
Product: korganizer
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: tho...@monjalon.net
Target Milestone: ---
Application: korganizer (5.24.0 (23.08.0))
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.4.12-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
Since a recent update, I am not able to forward a calendar event.
The crash can be reproduced every time.
-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f2629aef0b8 in
Akonadi::MailClient::queueMessage(MailTransport::Transport const*,
MessageComposer::Composer const*, QSharedPointer
const&, KIdentityManagement::Identity const&, Akonadi::MailClient::MessageData
const&, QSharedPointer const&) (message=..., msg=...,
identity=, incidence=..., composer=,
transport=0x561d04ed36f0, this=0x561d03ffcbf0) at
/usr/src/debug/akonadi-calendar/akonadi-calendar-23.08.0/src/mailclient_p.cpp:323
#7 operator() (__closure=0x561d04eb5680) at
/usr/src/debug/akonadi-calendar/akonadi-calendar-23.08.0/src/mailclient_p.cpp:641
#8 QtPrivate::FunctorCall, QtPrivate::List<>, void,
Akonadi::MailClient::send(const KCalendarCore::IncidenceBase::Ptr&, const
KIdentityManagement::Identity&, const MessageData&, const QString&)::
>::call (arg=, f=...) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#9 QtPrivate::Functor, 0>::call, void>
(arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256
#10 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>,
void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=0x561d04eb5670, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443
#11 0x7f262a2d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff5abc71f0, r=, this=0x561d04eb5670, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#12 doActivate(QObject*, int, void**) (sender=0x561d04ede3f0,
signal_index=6, argv=0x7fff5abc71f0) at kernel/qobject.cpp:3925
#13 0x7f262b7c30aa in KJob::result(KJob*, KJob::QPrivateSignal)
(this=this@entry=0x561d04ede3f0, _t1=, _t1@entry=0x561d04ede3f0,
_t2=...) at
/usr/src/debug/kcoreaddons/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#14 0x7f262b7c907c in KJob::finishJob(bool) (this=0x561d04ede3f0,
emitResult=) at
/usr/src/debug/kcoreaddons/kcoreaddons-5.109.0/src/lib/jobs/kjob.cpp:98
#15 0x7f262a2d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff5abc7320, r=, this=0x561d04f1cbd0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x561d04ec9270,
signal_index=6, argv=0x7fff5abc7320) at kernel/qobject.cpp:3925
#17 0x7f262b7c30aa in KJob::result(KJob*, KJob::QPrivateSignal)
(this=this@entry=0x561d04ec9270, _t1=, _t1@entry=0x561d04ec9270,
_t2=...) at
/usr/src/debug/kcoreaddons/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#18 0x7f262b7c907c in KJob::finishJob(bool) (this=0x561d04ec9270,
emitResult=) at
/usr/src/debug/kcoreaddons/kcoreaddons-5.109.0/src/lib/jobs/kjob.cpp:98
#19 0x7f262b7c9cd2 in KJob::emitResult() (this=) at
/usr/src/debug/kcoreaddons/kcoreaddons-5.109.0/src/lib/jobs/kjob.cpp:338
#20 0x7f2627a3a67a in operator() (auditLogAsHtml=,
auditLogError=, signature=..., result=,
__closure=0x561d04efe8e0) at
/usr/src/debug/messagelib/messagelib-23.08.0/messagecomposer/src/job/signjob.cpp:277
#21 QtPrivate::FunctorCall,
QtPrivate::List, void, MessageComposer::SignJob::process()::
>::call (arg=, f=...) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#22 QtPrivate::Functor, 4>::call, void> (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256
#23
QtPrivate::QFunctorSlotObject, 4, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x561d04efe8d0, r=, a=,
ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443
#24 0x7f262a2d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff5abc74b0, r=, this=0x561d04efe8d0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#25 doActivate(QObject*, int, void**) (sender=0x561d04ec7660,
signal_index=7, argv=0x7fff5abc74b0) at kernel/qobject.cpp:3925
#26 0x7f2626d55806 in QGpgME::SignJob::result(GpgME::SigningResult const&,
QByteArray const&, QString const&, GpgME::Error const&) (this=,
_t1=, _t2=, _t3=, _t4=) at /usr/s
[Akonadi] [Bug 473593] New: Ability to mark calendars as read-only independent of backend
https://bugs.kde.org/show_bug.cgi?id=473593 Bug ID: 473593 Summary: Ability to mark calendars as read-only independent of backend Classification: Frameworks and Libraries Product: Akonadi Version: 5.23.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de CC: c...@carlschwan.eu Target Milestone: --- Currently, the UI (e.g. Akonadi Console, "Folder Properties" on a calendar) offers no option to mark a calendar as read-only, i.e. to disallow changes or removal of events or adding new events. This should be implemented independent of the backend, irrespective of whether it is a local calendar or a DAV resource. Background: in my groupware server account, I have several calendars: one for events I maintain (add/edit events) and several that are subscriptions to external calendar feeds which are read-only. Either the groupware server does not relay the information which calendars are read-only, or Akonadi does not interpret this information correctly. At least in KOrganizer, changes can be made to calendars that are technically read-only. To block those changes, the user should have the choice to mark a calendar read-only even if changes are technically possible, e.g. to avoid accidental changes to calendars. The Folder Properties dialog has a "ACL" tab, but it warns to make changes here. Even if my request can be "solved" by making changes here, it sounds like a dangerous path and it deters users from making the changes. Instead, there should be a simple checkbox in the "General" tab next to the "custom icon" setting that allows the user to make the calendar read-only (or not). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472335] New: Slow startup to desktop at login
https://bugs.kde.org/show_bug.cgi?id=472335 Bug ID: 472335 Summary: Slow startup to desktop at login Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tho...@mitterfellner.at CC: c...@carlschwan.eu Target Milestone: --- It seems that there has been a regression with desktop startup after login at some point. This has been really fast, almost immediate, maybe 2-4 s after entering my credentials but now it takes ~15 s for the desktop to show. The version I'm using is 5.27.4 on openSUSE Leap 15.5. This duration is not shorter when I just log out and log in again. Caveat: I am not sure this is due to akonadi but in my journalctl -b output I get many akonadi messages over the course of 10 s (I pressed Enter on the login screen at 19:40:01): Jul 17 19:40:05 x akonadi_control[4223]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Jul 17 19:40:05 x akonadiserver[4238]: org.kde.pim.akonadiserver: Starting up the Akonadi Server... Jul 17 19:40:06 x kalendarac[4276]: akonadi.collectionattributetable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.collectionmimetyperelation OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.collectionpimitemrelation OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.collectiontable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.flagtable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.mimetypetable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.parttable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.parttypetable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.pimitemflagrelation OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.pimitemtable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.pimitemtagrelation OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.relationtable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.relationtypetable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.resourcetable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.schemaversiontable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.tagattributetable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.tagremoteidresourcerelationtable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.tagtable OK Jul 17 19:40:06 x kalendarac[4276]: akonadi.tagtypetable OK Jul 17 19:40:06 x akonadiserver[4238]: org.kde.pim.akonadiserver: Running DB initializer Jul 17 19:40:06 x akonadiserver[4238]: org.kde.pim.akonadiserver: DB initializer done Jul 17 19:40:06 x akonadiserver[4238]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Jul 17 19:40:06 x akonadi_control[4223]: org.kde.pim.akonadicontrol: Akonadi server is now operational. Jul 17 19:40:06 x akonadiserver[4238]: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fbcb4003f20) ) Jul 17 19:40:06 x akonadiserver[4238]: org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fbcb4003f20) identified as "ETMCalendarMonitor - 94885386041040" Jul 17 19:40:07 x akonadiserver[4238]: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fbcb40555b0) ) Jul 17 19:40:07 x akonadiserver[4238]: org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fbcb40555b0) identified as "AgentBaseChangeRecorder - 94373361138464" Jul 17 19:40:08 x akonadiserver[4238]: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fbcb4015440) ) Jul 17 19:40:08 x akonadiserver[4238]: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fbcb405a4b0) ) Jul 17 19:40:08 x akonadiserver[4238]: org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fbcb4015440) identified as "AgentBaseChangeRecorder - 94813301524080" Jul 17 19:40:08 x akonadiserver[4238]: org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fbcb405a4b0) identified as "AgentBaseChangeRecorder - 94820412118752" Jul 17 19:40:08 x akonadiserver[4238]: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::Notifica
[kontact] [Bug 471509] New: KDE Address book crashes
https://bugs.kde.org/show_bug.cgi?id=471509 Bug ID: 471509 Summary: KDE Address book crashes Classification: Applications Product: kontact Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: li...@tux-home.eu Target Milestone: --- Application: kontact (5.22.3 (22.12.3)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.14.21-150500.53-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.5" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Hello dear KDE developers, my KDE address book keeps crashing. Can you help me? Bye Tom The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted [KCrash Handler] #4 0x7fa6d8a1fc6b in raise () from /lib64/libc.so.6 #5 0x7fa6d8a21305 in abort () from /lib64/libc.so.6 #6 0x7fa6d8c6f735 in ?? () from /usr/lib64/libstdc++.so.6 #7 0x7fa6d8c7adbc in ?? () from /usr/lib64/libstdc++.so.6 #8 0x7fa6d8c7ae27 in std::terminate() () from /usr/lib64/libstdc++.so.6 #9 0x7fa6d8c7b088 in __cxa_throw () from /usr/lib64/libstdc++.so.6 #10 0x7fa6880bf996 in Akonadi::Item::throwPayloadException(int, int) const () from /usr/lib64/libKF5AkonadiCore.so.5 #11 0x7fa64859bb63 in std::enable_if::isPolymorphic, KContacts::Addressee>::type Akonadi::Item::payloadImpl() const () from /usr/lib64/libkaddressbookprivate.so.5 #12 0x7fa6485a48a2 in KContacts::Addressee Akonadi::Item::payload() const () from /usr/lib64/libkaddressbookprivate.so.5 #13 0x7fa6485a00c3 in ?? () from /usr/lib64/libkaddressbookprivate.so.5 #14 0x7fa6485a1e95 in ?? () from /usr/lib64/libkaddressbookprivate.so.5 #15 0x7fa6d9305a3b in ?? () from /usr/lib64/libQt5Core.so.5 #16 0x7fa6da4e648c in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib64/libKF5CoreAddons.so.5 #17 0x7fa6da4e79a1 in KJob::finishJob(bool) () from /usr/lib64/libKF5CoreAddons.so.5 #18 0x7fa6d92fc4db in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #19 0x7fa6d9ecc53c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #20 0x7fa6d9ed32ff in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #21 0x7fa6d92c8043 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #22 0x7fa6d92caa61 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #23 0x7fa6d932b2e3 in ?? () from /usr/lib64/libQt5Core.so.5 #24 0x7fa6ce3e682b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #25 0x7fa6ce3e6bd0 in ?? () from /usr/lib64/libglib-2.0.so.0 #26 0x7fa6ce3e6c5c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #27 0x7fa6d932a98c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #28 0x7fa6d92c68aa in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #29 0x7fa6d92d00e7 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #30 0x55776596752d in ?? () #31 0x7fa6d8a0a24d in __libc_start_main () from /lib64/libc.so.6 #32 0x557765967b6a in ?? () [Inferior 1 (process 6106) detached] The reporter indicates this bug may be a duplicate of or related to bug 437409, bug 468185. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 471164] New: Kadressbook crashes
https://bugs.kde.org/show_bug.cgi?id=471164 Bug ID: 471164 Summary: Kadressbook crashes Classification: Applications Product: kontact Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: li...@tux-home.eu Target Milestone: --- Application: kontact (5.23.2 (23.04.2)) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.3.7-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Kadressbook crashes after I set up a new contact group. However, I can set up new contacts without crashing. I hope you can fix the problem. Goodbye Tom The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kontact (kontact), signal: Aborted [KCrash Handler] #4 0x7f1446692a7c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7f1446641226 in raise () from /lib64/libc.so.6 #6 0x7f1446629897 in abort () from /lib64/libc.so.6 #7 0x7f14468acbf7 in ?? () from /lib64/libstdc++.so.6 #8 0x7f14468bc22c in ?? () from /lib64/libstdc++.so.6 #9 0x7f14468bc297 in std::terminate() () from /lib64/libstdc++.so.6 #10 0x7f14468bc4f8 in __cxa_throw () from /lib64/libstdc++.so.6 #11 0x7f13b8246582 in ?? () from /lib64/libKPim5AkonadiCore.so.5 #12 0x7f13b829bae7 in ?? () from /lib64/libKPim5AkonadiCore.so.5 #13 0x7f13b829bff8 in ?? () from /lib64/libKPim5AkonadiCore.so.5 #14 0x7f13b82e561d in Akonadi::ItemCreateJob::doHandleResponse(long long, QSharedPointer const&) () from /lib64/libKPim5AkonadiCore.so.5 #15 0x7f13b82c69d4 in Akonadi::SessionPrivate::handleCommands() () from /lib64/libKPim5AkonadiCore.so.5 #16 0x7f13b82c7c30 in ?? () from /lib64/libKPim5AkonadiCore.so.5 #17 0x7f1446f192b0 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f1447ba519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7f1446eed4f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #20 0x7f1446ef0af1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #21 0x7f1446f46c83 in ?? () from /lib64/libQt5Core.so.5 #22 0x7f143da698d8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #23 0x7f143da69ce8 in ?? () from /lib64/libglib-2.0.so.0 #24 0x7f143da69d7c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #25 0x7f1446f46496 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #26 0x7f1446eebf8b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f1446ef4420 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #28 0x55763271bfe3 in ?? () #29 0x7f144662abb0 in __libc_start_call_main () from /lib64/libc.so.6 #30 0x7f144662ac79 in __libc_start_main_impl () from /lib64/libc.so.6 #31 0x55763271c625 in ?? () [Inferior 1 (process 7266) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 347045] Sunday is always automatically selected once weekly recurrence drop down is clicked
https://bugs.kde.org/show_bug.cgi?id=347045
Thomas Karpiniec changed:
What|Removed |Added
CC||t...@1.21jiggawatts.net
--- Comment #8 from Thomas Karpiniec ---
I've tracked this down to this connection in `KCheckComboBox`:
https://invent.kde.org/pim/libkdepim/-/blob/master/src/widgets/kcheckcombobox.cpp#L122
connect(this, &QComboBox::activated, this, [this]() {
d->toggleCheckState();
});
The idea is that the `activated` signal will fire when the user clicks on an
item in the list, so its check state should be toggled. The problem is that
this signal is _also_ firing when you first click the drop-down. I tested a
hack that swallows the first `activated` event after `showPopup()` and this
made it work correctly.
This doesn't appear to be normal behaviour for QComboBox which makes me wonder
if we have the signal connected somewhere else and causing problems. I captured
the following backtrace but haven't quite figured out where this is coming from
yet:
#0 KPIM::KCheckComboBox::KCheckComboBoxPrivate::toggleCheckState
(this=0x12ccc90) at
/home/tk/kde/src/libkdepim/src/widgets/kcheckcombobox.cpp:113
#1 0x74f25232 in QtPrivate::QSlotObjectBase::call (a=0x7fffc170,
r=0x12cc800, this=0x12cccf0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#2 doActivate (sender=0x12cc800, signal_index=8, argv=0x7fffc170)
at kernel/qobject.cpp:3923
#3 0x74f1de2f in QMetaObject::activate (sender=sender@entry=0x12cc800,
m=m@entry=0x760c25c0 ,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fffc170)
at kernel/qobject.cpp:3983
#4 0x75ca8a91 in QComboBox::activated (this=this@entry=0x12cc800,
_t1=) at .moc/moc_qcombobox.cpp:510
#5 0x75caa23e in QComboBoxPrivate::emitActivated
(this=this@entry=0x12cc840, index=...) at
../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:62
#6 0x75caf322 in QComboBoxPrivate::_q_editingFinished (this=0x12cc840)
at widgets/qcombobox.cpp:1358
#7 0x74f251d3 in doActivate (sender=0x12cd930, signal_index=11,
argv=0x7fffc2d0) at kernel/qobject.cpp:3935
#8 0x74f1de2f in QMetaObject::activate (sender=sender@entry=0x12cd930,
m=m@entry=0x760c5b20 ,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at
kernel/qobject.cpp:3983
#9 0x75ceafd3 in QLineEdit::editingFinished
(this=this@entry=0x12cd930) at .moc/moc_qlineedit.cpp:473
#10 0x75cf1d61 in QLineEdit::focusOutEvent (this=0x12cd930,
e=0x7fffc530) at widgets/qlineedit.cpp:1959
#11 0x75be6ee0 in QWidget::event (this=0x12cd930, event=0x7fffc530)
at kernel/qwidget.cpp:8793
#12 0x75be6ee0 in QWidget::event (this=0x12cc800, event=0x7fffc530)
at kernel/qwidget.cpp:8793
#13 0x75ba51ae in QApplicationPrivate::notify_helper (this=, receiver=0x12cc800, e=0x7fffc530) at kernel/qapplication.cpp:3640
#14 0x74eec978 in QCoreApplication::notifyInternal2
(receiver=0x12cc800, event=0x7fffc530) at kernel/qcoreapplication.cpp:1064
#15 0x75baa160 in QApplicationPrivate::openPopup (this=,
popup=, popup@entry=0x12cf790) at kernel/qapplication.cpp:3767
#16 0x75be3ab0 in QWidgetPrivate::show_helper
(this=this@entry=0x12d4aa0) at kernel/qwidget.cpp:7844
#17 0x75be6823 in QWidgetPrivate::setVisible (this=0x12d4aa0,
visible=) at kernel/qwidget.cpp:8137
#18 0x75cb034e in QComboBox::showPopup (this=0x12cc800) at
widgets/qcombobox.cpp:2953
#19 0x75cb10de in QComboBoxPrivate::showPopupFromMouseEvent
(this=0x12cc840, e=) at widgets/qcombobox.cpp:3303
#20 0x75be6d78 in QWidget::event (this=0x12cc800, event=0x7fffcd50)
at kernel/qwidget.cpp:9045
#21 0x75ba51ae in QApplicationPrivate::notify_helper
(this=this@entry=0x435230, receiver=receiver@entry=0x12cc800,
e=e@entry=0x7fffcd50) at kernel/qapplication.cpp:3640
#22 0x75bad5df in QApplication::notify (this=,
receiver=, e=0x7fffcd50) at kernel/qapplication.cpp:3084
#23 0x74eec978 in QCoreApplication::notifyInternal2
(receiver=0x12cc800, event=0x7fffcd50) at kernel/qcoreapplication.cpp:1064
#24 0x75bab93e in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x12cc800, event=event@entry=0x7fffcd50,
alienWidget=, nativeWidget=0x7fffe0003430,
buttonDown=buttonDown@entry=0x760f2330 ,
lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at
kernel/qapplication.cpp:2622
#25 0x75bff80d in QWidgetWindow::handleMouseEvent (this=0x18dd660,
event=0x7fffd000) at kernel/qwidgetwindow.cpp:684
#26 0x75c02d2f in QWidgetWindow::event (this=0x18dd660,
event=0x7fffd000) at kernel/qwidgetwindow.cpp:300
#27 0x75ba51ae in QApplicationPrivate::notify_helper (this=, receiver=0x18d
[korganizer] [Bug 458254] Cannot hide completed todo
https://bugs.kde.org/show_bug.cgi?id=458254 Thomas Karpiniec changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||eventviews/-/commit/db4009f ||65c84be6a364a9f7b405c64520c ||f57f58 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Thomas Karpiniec --- Git commit db4009f65c84be6a364a9f7b405c64520cf57f58 by Thomas Karpiniec. Committed on 08/06/2023 at 04:34. Pushed by vkrause into branch 'master'. Invalidate model to apply sortCompletedTodosSeparately pref M +4-0src/todo/todoview.cpp https://invent.kde.org/pim/eventviews/-/commit/db4009f65c84be6a364a9f7b405c64520cf57f58 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 458254] Cannot hide completed todo
https://bugs.kde.org/show_bug.cgi?id=458254 Thomas Karpiniec changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||t...@1.21jiggawatts.net --- Comment #1 from Thomas Karpiniec --- I can confirm but I think OP has misunderstood the preference. It's intended to control whether to-dos should be sorted differently rather than whether they are visible. Hiding is currently supported via filters (which works correctly). The real bug here IMO is that changing the preference doesn't actually update the view until you either restart KOrganizer or toggle the flat/tree view, so it seems broken. If this was working correctly the reporter probably would have understood its intent. KOrganizer: Version 5.23.1 (23.04.1) -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 470584] New: KOrganizer crash while changing filter in ToDo List
https://bugs.kde.org/show_bug.cgi?id=470584 Bug ID: 470584 Summary: KOrganizer crash while changing filter in ToDo List 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: t...@1.21jiggawatts.net Target Milestone: --- Application: korganizer (5.23.1 (23.04.1)) Qt Version: 5.15.9 Frameworks Version: 5.106.0 Operating System: Linux 6.3.4-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: I was looking at my list of ToDos. I have the filter buttons shown on the toolbar. I used the filter dropdown to switch from one of my filters to no filter and the program crashed immediately. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault [KCrash Handler] #4 0x7fac4e8a56b3 in EventViews::AgendaView::calendar2 (this=, incidence=...) at /usr/src/debug/eventviews-23.04.1/src/agenda/agendaview.cpp:1227 #5 0x7fac4e8afe4e in EventViews::AgendaView::displayIncidence (this=0x5579281928e0, incidence=..., createSelected=false) at /usr/src/debug/eventviews-23.04.1/src/agenda/agendaview.cpp:1981 #6 0x7fac4e8b16d5 in EventViews::AgendaView::fillAgenda (this=0x5579281928e0) at /usr/src/debug/eventviews-23.04.1/src/agenda/agendaview.cpp:1947 #7 0x7fac4f318c50 in QObject::event (this=0x5579281928e0, e=0x55792893f620) at kernel/qobject.cpp:1347 #8 0x7fac4ffa51ae in QApplicationPrivate::notify_helper (this=, receiver=0x5579281928e0, e=0x55792893f620) at kernel/qapplication.cpp:3640 #9 0x7fac4f2ec978 in QCoreApplication::notifyInternal2 (receiver=0x5579281928e0, event=0x55792893f620) at kernel/qcoreapplication.cpp:1064 #10 0x7fac4f2eff71 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55792733c090) at kernel/qcoreapplication.cpp:1821 #11 0x7fac4f346713 in postEventSourceDispatch (s=0x55792740b930) at kernel/qeventdispatcher_glib.cpp:277 #12 0x7fac4cd168d8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #13 0x7fac4cd16ce8 in ?? () from /lib64/libglib-2.0.so.0 #14 0x7fac4cd16d7c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #15 0x7fac4f345f26 in QEventDispatcherGlib::processEvents (this=0x55792741bb80, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #16 0x7fac4f2eb40b in QEventLoop::exec (this=this@entry=0x7ffe017fad10, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #17 0x7fac4f2f38a0 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #18 0x557926b296e2 in main (argc=, argv=) at /usr/src/debug/korganizer-23.04.1/src/main.cpp:72 [Inferior 1 (process 25611) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 440831] Segmentation Fault on syncing MeContact
https://bugs.kde.org/show_bug.cgi?id=440831 Thomas Karpiniec changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||kdepim-runtime/commit/e6007 ||c7e81d8987fa402f70084675f7a ||d3e33eac Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Thomas Karpiniec --- Git commit e6007c7e81d8987fa402f70084675f7ad3e33eac by Thomas Karpiniec. Committed on 25/04/2023 at 11:06. Pushed by carlschwan into branch 'master'. Skip EWS items where there is no registered handler Prevents nullptr dereference when handling an unexpected item type EwsItemTypeItem, such as can be found in "MeContact" on outlook.com. M +6-1resources/ews/ewsfetchitemsjob.cpp https://invent.kde.org/pim/kdepim-runtime/commit/e6007c7e81d8987fa402f70084675f7ad3e33eac -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467439] New: Crash when selecting multiple mails while pressing Ctrl
https://bugs.kde.org/show_bug.cgi?id=467439 Bug ID: 467439 Summary: Crash when selecting multiple mails while pressing Ctrl Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- After first filtering mails in the list of mails for a keyword and while selecting (mouse cursor) several of the found mails while pressing Ctrl, KMail crashed: Using Fedora 37, the following program/library versions were used: KMail 22.12.3 KF5 KMime 22.12.3 Q5 5.15.8 Frameworks 5.103.0 Output on command line up to crash: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP [New Thread 0x7fff36ffd6c0 (LWP 12933)] [New Thread 0x7fff367fc6c0 (LWP 12934)] [New Thread 0x7fff35ffb6c0 (LWP 12935)] [New Thread 0x7fff357fa6c0 (LWP 12936)] qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [New Thread 0x7fff1e1bd6c0 (LWP 12942)] [New Thread 0x7fff1d9bc6c0 (LWP 12943)] [Detaching after fork from child process 12947] [Detaching after fork from child process 12949] [Detaching after fork from child process 12951] [New Thread 0x7fff0bbff6c0 (LWP 12953)] [New Thread 0x7fff0abbe6c0 (LWP 12956)] [New Thread 0x7fff09f2d6c0 (LWP 12957)] [New Thread 0x7fff0970c6c0 (LWP 12958)] [New Thread 0x7fff08f0b6c0 (LWP 12959)] [New Thread 0x7ffef3fff6c0 (LWP 12960)] [Thread 0x7fff57fff6c0 (LWP 12908) exited] [Thread 0x7fff767fc6c0 (LWP 12904) exited] [Thread 0x7fff777fe6c0 (LWP 12902) exited] [New Thread 0x7fff767fc6c0 (LWP 13009)] [New Thread 0x7fff777fe6c0 (LWP 13010)] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56efca90) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56efca90) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5702e190) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56e4b8b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [New Thread 0x7fff57fff6c0 (LWP 13019)] [Detaching after fork from child process 13095] Recognized the following URL or filename: "https://fortimail.his.se/releasecontrol?release=1%3Athomas.fischer%40his.se%3AMTY3ODk1OTc0Mi4zNTIwXzU4NTkxMF8xMDkxNDAuMTcwNTczI1EjMzJHOUIyVDQwMjk0MTQwMDAwLCNGI1MjNTY2Njc2I0U%3D%3Aver%3A2%3A01%3A01%3A59cbce3b04f7780ddb461e6fdf6f90f3f0f58606"; Using Firefox executable "/usr/bin/firefox" [Thread 0x7fff57fff6c0 (LWP 13019) exited] [New Thread 0x7fff57fff6c0 (LWP 13197)] [Detaching after fork from child process 13210] Recognized the following URL or filename: "https://fortimail.his.se/releasecontrol?release=1%3Athomas.fischer%40his.se%3AMTY3ODk1OTc0Mi4zNTIwXzU4NTkxMF8xMDkxNDAuMTcwNTczI1EjMzJHOUIyVDQwMjk0MTQwMDAwLCNGI1MjNTY2Njc2I0U%3D%3Aver%3A2%3A01%3A01%3A59cbce3b04f7780ddb461e6fdf6f90f3f0f58606"; Using Firefox executable "/usr/bin/firefox" qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup,
[kmail2] [Bug 467436] New: Crash when moving mails between folders
https://bugs.kde.org/show_bug.cgi?id=467436 Bug ID: 467436 Summary: Crash when moving mails between folders Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- After observing regular crashes in KMail when moving mails between folders (via context menu, then "Move to", on mail in list of mails), I ran kmail via gdb with debuginfod enabled. Akonadi is no affected by crash, I still get popups on incoming mails even after KMail had crashed. Version numbers of concerned programs/libraries: KMail 22.12.3, Fedora release 1.fc37 QWayand 5.15.8, Fedora release 1.fc37 KF5 KXmlGui 5.103.0, Fedora release 1.fc37 Most recent output in terminal before crash: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/6”" "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/5”" [Thread 0x7fff75bfb6c0 (LWP 9496) exited] kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP [Thread 0x7fff773fe6c0 (LWP 9633) exited] [Thread 0x7fff753fa6c0 (LWP 8215) exited] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6c0678b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6c0678b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e7000) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [New Thread 0x7fff753fa6c0 (LWP 11224)] [New Thread 0x7fff773fe6c0 (LWP 11225)] [New Thread 0x7fff75bfb6c0 (LWP 11226)] [New Thread 0x7ffeecbfc6c0 (LWP 11326)] [New Thread 0x7ffeebbfa6c0 (LWP 11328)] [New Thread 0x7ffeec3fb6c0 (LWP 11327)] [New Thread 0x7ffeeb3f96c0 (LWP 11329)] [New Th
[kontact] [Bug 463450] Application: Kontact (kontact), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=463450 Thomas Fischer changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #1 from Thomas Fischer --- I may have encountered the same or a very similar problem. I have kmail crashing several times a day when moving mails between folders (via context menu in mail list) on a Fedora Linux KDE spin system that is not even one week old. I ran the kmail binary via gdb with debuginfod enabled to get the following output. The first few lines may be older and not directly related to the crash: qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5737bdf0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56bbb930) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [Thread 0x7ffee9bff6c0 (LWP 32407) exited] [Thread 0x7fff66c0 (LWP 32406) exited] [Thread 0x7fff75ffb6c0 (LWP 29371) exited] Downloading separate debug info for /usr/lib64/qt5/plugins/kf5/FrameworkIntegrationPlugin.so Downloading separate debug info for /usr/lib64/libcanberra-0.30/libcanberra-pulse.so [New Thread 0x7fff75ffb6c0 (LWP 32420)] [Detaching after fork from child process 32421] [Detaching after fork from child process 32423] [New Thread 0x7fff66c0 (LWP 32426)] [Detaching after fork from child process 32427] [Thread 0x7fff66c0 (LWP 32426) exited] org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history [New Thread 0x7fff66c0 (LWP 32471)] [New Thread 0x7ffee9bff6c0 (LWP 32472)] [New Thread 0x7ffeea7ff6c0 (LWP 32473)] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6003f460) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5729bca0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents malloc(): unaligned fastbin chunk detected Thread 1 "kmail" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 Downloading source file /usr/src/debug/glibc-2.36-9.fc37.x86_64/nptl/pthread_kill.c 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7fffee2afec3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7fffee25fa76 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7fffee2497fc in __GI_abort () at abort.c:79 #4 0x7fffee2a408e in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fffee3bd465 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #5 0x7fffee2b9b9c in malloc_printerr (str=str@entry=0x7fffee3c0400 "malloc(): unaligned fastbin chunk detected") at malloc.c:
[korganizer] [Bug 464894] New: Non-optimal display of items in week view
https://bugs.kde.org/show_bug.cgi?id=464894 Bug ID: 464894 Summary: Non-optimal display of items in week view Classification: Applications Product: korganizer Version: 5.22.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: agendaview (weekview) Assignee: kdepim-bugs@kde.org Reporter: asiasuppenes...@gmx.de Target Milestone: --- Created attachment 155698 --> https://bugs.kde.org/attachment.cgi?id=155698&action=edit The item highlighted by the hand-drawn red arrow is very small and could be displayed much wider SUMMARY When using korganizer's week view, sometimes calendar entries are displayed too small, i.e. smaller than they could be. I believe that maximising the use of the available space in a given column is a generally desirable goal. The attached picture should say it all - the item highlighted by the arrow could actually span three quarters of the column width, but instead only covers one quarter. STEPS TO REPRODUCE 1. Create a set of partially conflicting calendar entries, similar to those in the attached image 2. Observe how korganizer arranges the items OBSERVED RESULT Usually space is wasted and calendar entries are too small for their titles to be visible EXPECTED RESULT Maximise use of available space, yielding a higher fraction of titles to be readable / identifiable SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 395683] Entry for security-aware messengers
https://bugs.kde.org/show_bug.cgi?id=395683 Thomas Rother changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Thomas Rother --- Status on kaddressbook 5.21.3 Telegram can be added, Threema and Signal still missing A number of messenger seem to be obsolete, pretty obscure or proprietary (AIM, Gadu-Gadu, GroupWise, Meanwhile, MSN Messenger, QQ) -- You are receiving this mail because: You are the assignee for the bug.
[kmailtransport] [Bug 392138] First SMTP authentication fails for almost every emails
https://bugs.kde.org/show_bug.cgi?id=392138 Thomas Monjalon changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #3 from Thomas Monjalon --- I use STARTTLS, so cannot say if the bug is still there without it. As nobody tried to reproduce after 4 years, closing it. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461810] New: Crash with malloc(): mismatching next->prev_size (unsorted)
https://bugs.kde.org/show_bug.cgi?id=461810
Bug ID: 461810
Summary: Crash with malloc(): mismatching next->prev_size
(unsorted)
Classification: Applications
Product: kmail2
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: fisc...@unix-ag.uni-kl.de
Target Milestone: ---
Since an update on ArchLinux in late October, KMail crashes quite often when
moving mails between folders, e.g. when sorting mails form Inbox to some other
folder. According to the package manager, both kmail and Akonadi have the
version number 22.08.3-1.
To collect information, I stopped Akonadi (akonadictl stop) and restarted it in
a console to see any relevant debug output during a crash. Same with kmail. No
special settings for extra debug output e.g. via kdebugsettings were made.
Akonadi made only some initial output but nothing later or during a crash.
kmail, however, gave the following output. I think but are not sure that the
output up to the last "DispatchModeAttribute" was before the crash.
Error loading text-to-speech plug-in "speechd"
org.kde.pim.mailtransportakonadi: Item doesn't have DispatchModeAttribute.
d->folderTreeWidget->selectedCollection() Collection ID: 199remote ID:
"AAMkADdjYzdhYjJkLTBjNGItNDRhZS05NjZjLWIxNzY5OTI2MTllNwAuAAA5OWMvCOhAR7niCe/yxRIKAQCzEcl00IXvRLelEuHv21iGxUoQAAA="
name: "Personal"
url: QUrl("akonadi:?collection=199")
parent: 38
"AAMkADdjYzdhYjJkLTBjNGItNDRhZS05NjZjLWIxNzY5OTI2MTllNwAuAAA5OWMvCOhAR7niCe/yxRIKAQCzEcl00IXvRLelEuHv21iGxTaMAAA="
resource: "akonadi_ews_resource_0"
rights: QFlags(AllRights)
contents mime type: ("message/rfc822", "inode/directory")
isVirtual: false
CachePolicy:
inherit: true
interval: -1
timeout: -1
sync on demand: false
local parts: ()
CollectionStatistics:
count: 3620
unread count: 1
size: 561984064
org.kde.pim.mailtransportakonadi: Item doesn't have DispatchModeAttribute.
malloc(): mismatching next->prev_size (unsorted)
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
malloc(): unaligned fastbin chunk detected
Let me know if I should try to re-create the crash with some additional debug
settings enabled.
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 461810] Crash with malloc(): mismatching next->prev_size (unsorted)
https://bugs.kde.org/show_bug.cgi?id=461810 --- Comment #1 from Thomas Fischer --- Just restarted kmail. It crashed again when moving a mail (context menu to move mail to another folder). This time, the output was different: malloc(): unaligned tcache chunk detected *** KMail got signal 6 (Exiting) *** Dead letters dumped. malloc(): unaligned tcache chunk detected malloc(): unaligned tcache chunk detected Unable to start Dr. Konqi Re-raising signal for core dump handling. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 384255] Idea to suggest latest contacts in recipient picker
https://bugs.kde.org/show_bug.cgi?id=384255 Thomas Monjalon changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 461233] New: Default time unit for suspending
https://bugs.kde.org/show_bug.cgi?id=461233 Bug ID: 461233 Summary: Default time unit for suspending Classification: Applications Product: korganizer Version: 5.16.0 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-bugs@kde.org Reporter: pitho...@free.fr Target Milestone: --- Bonjour, I use KOrganizer as my only calendar. The default time unit for suspending warning is minutes. I wish the default time unit for suspending warnings is a parameter in the preferences of KOrganizer, for being able to set it to hours. My best regards. Pierre -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 461131] New: Korganizer sometimes crashes on startup
https://bugs.kde.org/show_bug.cgi?id=461131
Bug ID: 461131
Summary: Korganizer sometimes crashes on startup
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: asiasuppenes...@gmx.de
Target Milestone: ---
Application: korganizer (5.21.2 (22.08.2))
Qt Version: 5.15.6
Frameworks Version: 5.99.0
Operating System: Linux 6.0.3-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.26.1 [KCrashBackend]
-- Information about the crash:
When booting my desktop machine and starting KDE, sometimes I'm greeted with
DrKonqi telling me that Korganizer has crashed. Zero user interaction has
happened until this point. Simply restarting the app has worked fine in all
cases so far.
The crash can be reproduced sometimes.
-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
[KCrash Handler]
#4 KJob::setError (this=this@entry=0x0, errorCode=errorCode@entry=100) at
/usr/src/debug/kcoreaddons-5.99.0-1.1.x86_64/src/lib/jobs/kjob.cpp:254
#5 0x7f9316bc6734 in Akonadi::SessionPrivate::serverStateChanged
(this=, state=) at
/usr/src/debug/akonadi-22.08.2/src/core/session.cpp:298
#6 0x7f931531305d in QtPrivate::QSlotObjectBase::call (a=0x7ffeed012800,
r=0x557b96de6d60, this=0x557b96dffc70) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#7 doActivate (sender=0x557b96e074b0, signal_index=5,
argv=0x7ffeed012800) at kernel/qobject.cpp:3919
#8 0x7f931530c4df in QMetaObject::activate (sender=,
m=, local_signal_index=local_signal_index@entry=2,
argv=argv@entry=0x7ffeed012800) at kernel/qobject.cpp:3979
#9 0x7f9316bbdb31 in Akonadi::ServerManager::stateChanged (this=, _t1=, _t1@entry=Akonadi::ServerManager::Broken) at
/usr/src/debug/akonadi-22.08.2/build/src/core/KF5AkonadiCore_autogen/include/moc_servermanager.cpp:180
#10 0x7f9316bbdd9c in Akonadi::ServerManagerPrivate::setState
(state=Akonadi::ServerManager::Broken, this=0x7f9316ca7300
<_ZZN12_GLOBAL__N_115Q_QGS_sInstance13innerFunctionEvE6holder.lto_priv.0>) at
/usr/src/debug/akonadi-22.08.2/src/core/servermanager.cpp:73
#11 Akonadi::ServerManagerPrivate::timeout (this=0x7f9316ca7300
<_ZZN12_GLOBAL__N_115Q_QGS_sInstance13innerFunctionEvE6holder.lto_priv.0>) at
/usr/src/debug/akonadi-22.08.2/src/core/servermanager.cpp:93
#12
Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}::operator()()
const (__closure=) at
/usr/src/debug/akonadi-22.08.2/src/core/servermanager.cpp:52
#13 QtPrivate::FunctorCall, QtPrivate::List<>, void,
Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}>::call(Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}&,
void**) (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#14
QtPrivate::Functor::call,
void>(Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}&,
void*, void**) (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#15
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) (which=, this_=, r=, a=, ret=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#16 0x7f931531305d in QtPrivate::QSlotObjectBase::call (a=0x7ffeed012910,
r=0x557b96e074b0, this=0x557b96de0980) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#17 doActivate (sender=0x7f93080150e0, signal_index=3,
argv=0x7ffeed012910) at kernel/qobject.cpp:3919
#18 0x7f931530c4df in QMetaObject::activate (sender=,
m=m@entry=0x7f93155b39c0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffeed012910)
at kernel/qobject.cpp:3979
#19 0x7f9315316e9a in QTimer::timeout (this=, _t1=...) at
.moc/moc_qtimer.cpp:205
#20 0x7f93153077ed in QObject::event (this=0x7f93080150e0,
e=0x7ffeed012a60) at kernel/qobject.cpp:1369
#21 0x7f9315fa53fe in QApplicationPrivate::notify_helper (this=, receiver=0x7f93080150e0, e=0x7ffeed012a60) at
kernel/qapplication.cpp:3637
#22 0x7f93152dc178 in QCoreApplication::notifyInternal2
(receiver=0x7f93080150e0, event=0x7ffeed012a60) at
kernel/qcoreapplication.cpp:1064
#23 0x7f9315332c01 in QTimerInfoList::activateTimers (this=0x557b96cd08c0)
at kernel/qtimerinfo_unix.cpp:643
#24 0x7f9315333494 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:183
#25 0x7f9312d20a50 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#26 0x7f9312d20e08 in ?? () from /lib64/libglib-2.0.so.0
#27 0x7f9312d20e9c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#28 0x7f9315333806 in QEventDispatcherGlib::processEvents
(this=0x557b96cd05a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#29 0x7f93152dabeb in QEventLoop::exec (t
[kaddressbook] [Bug 349166] When moving multiple entries, only one of them gets synced
https://bugs.kde.org/show_bug.cgi?id=349166 Thomas Bleher changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #8 from Thomas Bleher --- (In reply to Justin Zobel from comment #7) > Thank you for reporting this bug in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! Thanks for asking :) I don't use KAddressbook anymore (mostly just using the webfrontend of NextCloud now). But kram...@web.de reported that it works for him now, so I guess this bug can be closed. -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453805] Text of event reminders does not use local timezone
https://bugs.kde.org/show_bug.cgi?id=453805 Thomas Fischer changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #2 from Thomas Fischer --- (In reply to David E. Narvaez from comment #1) > Forget about the timezone: it does not even say what day the event is. I have not tested it myself yet, but it looks like commit 2b832b9d08e4eaca0825 added the date if the event is on another day. https://invent.kde.org/pim/akonadi-calendar/-/commit/2b832b9d08e4eaca08258e4f372e92a18fed035e The missing time zone information is not fixed, as the time is formatted as "QLocale::NarrowFormat" which is supposed to format a time in the shortest possible way, basically guaranteeing that no time zone will be shown. https://doc.qt.io/qt-5/qlocale.html#FormatType-enum Maybe the code can be refactored to format time differently (longer) if the event's time zone differs from the current time zone? -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 449182] New: Enhancement request: Enable write-access for Office 365 Calendars
https://bugs.kde.org/show_bug.cgi?id=449182 Bug ID: 449182 Summary: Enhancement request: Enable write-access for Office 365 Calendars Product: korganizer Version: 5.18.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: exchangeplugin Assignee: kdepim-bugs@kde.org Reporter: thomas@reuss.rocks Target Milestone: --- SUMMARY Currently, Kontact/Korganizer does only provide read-access to Office 365 accounts (EWS) STEPS TO REPRODUCE 1. Attach Microsoft Office 365 account in Korganizer 2. Create a new task/appointment 3. The Office 365 account is not available as target OBSERVED RESULT EXPECTED RESULT Having write-access to Office 365 account SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian GNU/Linux / KDE Plasma 5.23.5 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 420515] Breeze Dark: Color of "today" does not differ from background
https://bugs.kde.org/show_bug.cgi?id=420515 --- Comment #10 from Thomas Tanghus --- (In reply to gjditchfield from comment #9) > I like that idea -- visible, but not gaudy. Thomas, please look at the > screenshots in https://invent.kde.org/pim/eventviews/-/merge_requests/43 Something like that. Maybe not red as it's often used to indicate errors. Isn't there some color constants for each theme you can use for highlight? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 --- Comment #56 from Thomas Monjalon --- With recent versions, it works fine for me: syncing with fastmail caldav. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 420515] Breeze Dark: Color of "today" does not differ from background
https://bugs.kde.org/show_bug.cgi?id=420515 --- Comment #6 from Thomas Tanghus --- (In reply to gjditchfield from comment #5) > Do you still have this problem? On my computer using current versions of > Breeze Dark and KOrganizer, today's tile is quite a bit lighter than the > others (see attachment). Akonadi has - again - crapped out, resulting in a non-functioning kdepim, so I can't test it myself. It does look a bit sharper, but my old eyes would prefer some more distinction. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 411373] Nextcloud calendar disappears
https://bugs.kde.org/show_bug.cgi?id=411373 --- Comment #8 from Thomas Tanghus --- It still happens once in a while here, but it's so rarely that I would say it works for me. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 116482] metakit: akregator crashes at startup
https://bugs.kde.org/show_bug.cgi?id=116482 Thomas Tanghus changed: What|Removed |Added CC|tho...@tanghus.net | -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 244204] Address editing dialog should be localized per address convention of the country selected
https://bugs.kde.org/show_bug.cgi?id=244204 Thomas Bleher changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Thomas Bleher --- Seems to work now with kaddressbook 4:20.08.1-0ubuntu1 on Ubuntu 20.10. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 244199] Add geocoding support
https://bugs.kde.org/show_bug.cgi?id=244199 Thomas Bleher changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |LATER --- Comment #2 from Thomas Bleher --- It seems like there is no map anymore below the address. I don't use KAddressbook anymore, so I cannot really judge this. Since I seem to be the only one requesting this, I'm closing this bug. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 432820] New: Missing German translation in reminder popup
https://bugs.kde.org/show_bug.cgi?id=432820 Bug ID: 432820 Summary: Missing German translation in reminder popup Product: korganizer Version: 5.16.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-bugs@kde.org Reporter: asiasuppenes...@gmx.de Target Milestone: --- Created attachment 135604 --> https://bugs.kde.org/attachment.cgi?id=135604&action=edit Screenshot showing the missing translation SUMMARY When the reminder popup hosts several entries, the "Dismiss All" button is not translated to German. It's a small issue, but since I see it almost every day I decided to eventually open this ticket. Not really knowing what I'm talking about, I think it's due to the translation in https://websvn.kde.org/trunk/l10n-kf5/de/messages/korganizer/korgac.po?revision=1583435&view=markup, line 53ff, being marked as fuzzy, which it actually is not. The German translation is a proper translation of the original phrase. Instead, the original English wording is slightly fuzzy, but acceptable in my opinion. STEPS TO REPRODUCE 1. Set your desktop environment language to German 2. Create several calendar entries set for the same date+time, all with reminders activated 3. Let the date+time arrive, so that a reminder popup window is shown 4. Observe the "Dismiss All" button at the bottom of the popup window Last but not least: Thanks for the great work, everyone! OBSERVED RESULT The button shows English text EXPECTED RESULT The button shows German text SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 258145] Context menu should offer all external browsers
https://bugs.kde.org/show_bug.cgi?id=258145 Thomas Tanghus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Thomas Tanghus --- I haven't used Konqueror for years, and don't even remember what the issue was. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 411036] Unable to select Categories
https://bugs.kde.org/show_bug.cgi?id=411036 Thomas Tanghus changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Thomas Tanghus --- It seems to be working fine now on 5.15.1. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 392980] KOrganizer crashes all times when closing
https://bugs.kde.org/show_bug.cgi?id=392980 Thomas Rother changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Thomas Rother --- worksforme on current releases -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 429393] HTML email "leaks" styles into headers
https://bugs.kde.org/show_bug.cgi?id=429393 --- Comment #5 from Thomas Tanghus --- (In reply to Laurent Montel from comment #4) > could you send me it your email in private ? > Thanks I have tried to send it to you, but I'm not sure it actually got sent as KMail didn't give any notifications. Let me know if it hasn't arrived. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 429393] HTML email "leaks" styles into headers
https://bugs.kde.org/show_bug.cgi?id=429393 --- Comment #2 from Thomas Tanghus --- Created attachment 133498 --> https://bugs.kde.org/attachment.cgi?id=133498&action=edit HTML -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 429393] HTML email "leaks" styles into headers
https://bugs.kde.org/show_bug.cgi?id=429393 --- Comment #1 from Thomas Tanghus --- Created attachment 133497 --> https://bugs.kde.org/attachment.cgi?id=133497&action=edit Plain -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 429393] New: HTML email "leaks" styles into headers
https://bugs.kde.org/show_bug.cgi?id=429393 Bug ID: 429393 Summary: HTML email "leaks" styles into headers Product: kmail2 Version: 5.15.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tho...@tanghus.net Target Milestone: --- SUMMARY When you view an HTML email sometimes the styles - CSS? - is also changing the header STEPS TO REPRODUCE 1. Set KMail to use standard headers (Fancy headers also fails) 2. Add Toggle HTML Mode to toolbar (can't find other ways to do it?) 3. View an (some) HTML emails, toggle to HTML mode on each. 4. Watch & Judge OBSERVED RESULT The headers changes style EXPECTED RESULT The headers should remain the same. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-30-generic OS Type: 64-bit ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 429329] New: kleopatra does not export private keys. Instead exporting public key only.
https://bugs.kde.org/show_bug.cgi?id=429329 Bug ID: 429329 Summary: kleopatra does not export private keys. Instead exporting public key only. Product: kleopatra Version: 3.1.11 Platform: Other OS: All Status: REPORTED Severity: major Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: tschwei...@gmail.com CC: kdepim-bugs@kde.org, m...@kde.org Target Milestone: --- SUMMARY kleopatra does not export private keys. Instead exporting public key only. STEPS TO REPRODUCE 1. Install kleopatra 2. create new private/public key pair 3. export private key OBSERVED RESULT finding public key only within exported file EXPECTED RESULT finding public/private key within exported file SOFTWARE/OS VERSIONS Windows: 10 Linux/KDE Plasma: as found in Ubuntu 20.04 KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 414100] Text not visible when using dark theme
https://bugs.kde.org/show_bug.cgi?id=414100 --- Comment #9 from Thomas Tanghus --- (In reply to Christophe Giboudeaux from comment #7) > We already received a report from a visually impaired user for whom a light > background is an issue. In what context is a light background an issue? I fail to see the relevanse here. > In the KMail version I use, there's a "Do not change color from original > HTML mail" option on the Appearance / Colors tab. Did you already try it? This doesn't make any difference for most HTML emails, but for plain text it has the unwanted effect of reversing the dark theme. See attachment. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414100] Text not visible when using dark theme
https://bugs.kde.org/show_bug.cgi?id=414100 --- Comment #8 from Thomas Tanghus --- Created attachment 133142 --> https://bugs.kde.org/attachment.cgi?id=133142&action=edit Inverse background -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414100] Text not visible when using dark theme
https://bugs.kde.org/show_bug.cgi?id=414100 --- Comment #6 from Thomas Tanghus --- Looking at #365315 it looks like an Akregator issue as it sounds like doesn't honour any HTML/CSS defined colours. In KMail there is a difference between the text view and the HTML view. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414100] Text not visible when using dark theme
https://bugs.kde.org/show_bug.cgi?id=414100 --- Comment #5 from Thomas Tanghus --- As I wrote in #428500 Many if not all HTML mail composers assumes that the background is light, and thus doesn't specify a background colour. If you use e.g. Breeze dark it often leads to black letters on dark grey background. Here it could possibly be solved by having a light background in HTML emails per default, perhaps with an option in Settings/Appearance/Colors. If the HTML email has a background defined it will be automatically rendered instead, and if it has a background defined there's a high probability that it also sets the font colour(s). It would - as far as I can see - solve both #317803 and #317198 and it would leave a very small (theoretical) subset where the text is difficult to read, as opposed to now when it is a very small subset that is easily readable. Thanks for catching my duplicate btw. I'm pretty sure I searched for "dark theme" but didn't get any results - but I could be wrong ;) -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 428500] New: HTML mail background
https://bugs.kde.org/show_bug.cgi?id=428500 Bug ID: 428500 Summary: HTML mail background Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: tho...@tanghus.net Target Milestone: --- Created attachment 132909 --> https://bugs.kde.org/attachment.cgi?id=132909&action=edit HTML mail with breeze Dark SUMMARY Many if not all HTML mail composers assumes that the background is light, and thus doesn't specify a background colour. If you use e.g. Breeze dark it often leads to black letters on dark grey background. STEPS TO REPRODUCE 1. Use Breeze Dark theme. 2. Go through your HTML emails 3. I betcha at least some shows the issue as shown in the attachment. OBSERVED RESULT Almost unreadable emails EXPECTED RESULT Readable emails ;) SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-64-generic OS Type: 64-bit Processors: 2 × Intel® Pentium® CPU B960 @ 2.20GHz Memory: 7,7 GiB of RAM ADDITIONAL INFORMATION Nextcloud mail had the same problem, but apparently it has been solved by somehow changing the theme. Here it could possibly be solved by having a light background in HTML emails perhaps with an option in Settings/Appearance/Colors. https://github.com/nextcloud/mail/issues/1742#issuecomment-530347369 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426238] Reply quote is not always pre-filled
https://bugs.kde.org/show_bug.cgi?id=426238
--- Comment #7 from Thomas Monjalon ---
Created attachment 131686
--> https://bugs.kde.org/attachment.cgi?id=131686&action=edit
proposed fix
I think I have a fix in kmime Content::parse()
+if (ct->isEmpty())
+ct->setMimeType("text/plain");
Please check the attachment, thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 426238] Reply quote is not always pre-filled
https://bugs.kde.org/show_bug.cgi?id=426238 --- Comment #6 from Thomas Monjalon --- The bug is not present with emails having a Content-Type field. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426238] Reply quote is not always pre-filled
https://bugs.kde.org/show_bug.cgi?id=426238 --- Comment #5 from Thomas Monjalon --- After testing above URLs, they work fine for me as well. The problem is with emails as they are locally. Please check with the attachment. Note: I do not compose as HTML, all emails are in the same folder, and there is no special template. I started seeing this regression recently (5.15 I believe). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426238] Reply quote is not always pre-filled
https://bugs.kde.org/show_bug.cgi?id=426238 --- Comment #4 from Thomas Monjalon --- Created attachment 131460 --> https://bugs.kde.org/attachment.cgi?id=131460&action=edit email which is not quoted on reply -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426238] Reply quote is not always pre-filled
https://bugs.kde.org/show_bug.cgi?id=426238 --- Comment #2 from Thomas Monjalon --- This email is not quoted on reply: https://patches.dpdk.org/patch/76484/mbox/ This email is quoted well when replying: https://patches.dpdk.org/patch/76166/mbox/ It seems it depends on the sender (probably its MTA). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 384249] midnight shuffle
https://bugs.kde.org/show_bug.cgi?id=384249 Thomas Monjalon changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Thomas Monjalon --- I've disabled grouping to avoid re-sorting mails every days, but it is still restarting sorting after midnight. Any tip? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426239] New: Mailing-list address is Cc'ed 2 times
https://bugs.kde.org/show_bug.cgi?id=426239 Bug ID: 426239 Summary: Mailing-list address is Cc'ed 2 times Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: tho...@monjalon.net Target Milestone: --- When replying to a mailing list message, the mailing list address is added as Cc even if it is already part of the original recipients. The consequence is to have to mailing list added 2 times. Given a mailing-list address does not need to have a name, I would prefer removing the original one (which may have a name added by the original sender) and keep the one added by kmail in Cc. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426238] New: Reply quote is not always pre-filled
https://bugs.kde.org/show_bug.cgi?id=426238 Bug ID: 426238 Summary: Reply quote is not always pre-filled Product: kmail2 Version: 5.15.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: tho...@monjalon.net Target Milestone: --- SUMMARY When replying a mail, the quote is sometimes missing. STEPS TO REPRODUCE 1. Click on "Reply" OBSERVED RESULT Sometimes the text area is blank, sometimes it is correctly pre-filled with quoted message. It depends on which email is replied. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 411373] Nextcloud calendar disappears
https://bugs.kde.org/show_bug.cgi?id=411373 --- Comment #3 from Thomas Tanghus --- Since then the situation has; improved may be to strong a word, but changed ;) Now the calendars get deselected every once in a while. Akonadi/KOrganizer doesn't seem to try to reconnect to the server. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 420515] Breeze Dark: Color of "today" does not differ from background
https://bugs.kde.org/show_bug.cgi?id=420515 --- Comment #3 from Thomas Tanghus --- Created attachment 128443 --> https://bugs.kde.org/attachment.cgi?id=128443&action=edit Visualization of the issue -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 420515] Breeze Dark: Color of "today" does not differ from background
https://bugs.kde.org/show_bug.cgi?id=420515 Thomas Tanghus changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Thomas Tanghus --- I managed to make a dupe #421500 before finding this. Confirmed! ;) -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 420515] Breeze Dark: Color of "today" does not differ from background
https://bugs.kde.org/show_bug.cgi?id=420515 Thomas Tanghus changed: What|Removed |Added CC||tho...@tanghus.net --- Comment #1 from Thomas Tanghus --- *** Bug 421500 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 421500] Current day background in Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=421500 Thomas Tanghus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Thomas Tanghus --- Aaaand closing as dupe of #420515 *** This bug has been marked as a duplicate of bug 420515 *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 421500] New: Current day background in Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=421500 Bug ID: 421500 Summary: Current day background in Breeze Dark Product: korganizer Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: monthview Assignee: kdepim-bugs@kde.org Reporter: tho...@tanghus.net Target Milestone: --- Created attachment 128442 --> https://bugs.kde.org/attachment.cgi?id=128442&action=edit Korganizer screen shot SUMMARY When using Breeze Dark the background color of the current day in month view is only a bit darker than the rest of the days. STEPS TO REPRODUCE 1. Change to the Breeze Dark theme. 2. Open KOrganizer or Kontact OBSERVED RESULT It's very hard to differentiate current day, at least with my weary eyes. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411728] Messageid is leaking hostname
https://bugs.kde.org/show_bug.cgi?id=411728 Thomas Monjalon changed: What|Removed |Added Status|REPORTED|RESOLVED CC||tho...@monjalon.net Resolution|--- |NOT A BUG --- Comment #2 from Thomas Monjalon --- The Message-ID can be tuned: Settings / Configure KMail / Composer / Headers "Use custom Message-ID suffix" -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 412327] Plugin library 'kde_grantlee_plugin' not found
https://bugs.kde.org/show_bug.cgi?id=412327 --- Comment #10 from Thomas McNicholas --- (In reply to Antonio Rojas from comment #9) > The ArchLinux issue was a packaging problem which has nothing to do with > this. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 412327] Plugin library 'kde_grantlee_plugin' not found
https://bugs.kde.org/show_bug.cgi?id=412327 --- Comment #7 from Thomas McNicholas --- Now works correctly after new Grantlee update. Thanks KDE community OS: Arch Linux KDE Plasma 5.17.4 Frameworks 5.65.0 Qt 5.13.2 -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 412327] Plugin library 'kde_grantlee_plugin' not found
https://bugs.kde.org/show_bug.cgi?id=412327 Thomas McNicholas changed: What|Removed |Added Platform|Neon Packages |Archlinux Packages CC||temcnicho...@dismail.de Version|5.12.3 |5.13.0 --- Comment #6 from Thomas McNicholas --- The 'grantlee' notification came with today's update and appears in akregator and kaddressbook and it may also be the cause of why I now can't read my email. OS: Arch Linux KDE Plasma 5.17.4 Frameworks 5.65.0 Qt 5.13.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414825] saving dialog does not propose a file name
https://bugs.kde.org/show_bug.cgi?id=414825 --- Comment #2 from Thomas Monjalon --- Thanks a lot Laurent -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414825] New: saving dialog does not propose a file name
https://bugs.kde.org/show_bug.cgi?id=414825 Bug ID: 414825 Summary: saving dialog does not propose a file name Product: kmail2 Version: 5.12.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: tho...@monjalon.net Target Milestone: --- SUMMARY When saving a message to a file, a file name computed from the title was proposed. When saving a lot of emails (especially for applying patches) we just had to do ctrl+s and enter. Now no filename is proposed, we must type each one. Please, this is really breaking my workflow :) STEPS TO REPRODUCE 1. save a message OBSERVED RESULT no filename in the dialog field EXPECTED RESULT filename pre-filled based on message title SOFTWARE/OS VERSIONS ArchLinux KDE Plasma Version: 5.17.3 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 414395] akregator refuses to import some feeds
https://bugs.kde.org/show_bug.cgi?id=414395 Thomas Capricelli changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from Thomas Capricelli --- Ok, I can confirm it is definitely a bug of the package, not from akregator itself. Close this one. Thx Laurent :-) -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 414395] akregator refuses to import some feeds
https://bugs.kde.org/show_bug.cgi?id=414395 --- Comment #4 from Thomas Capricelli --- Concerning akregator version, i'm not sure, but the last one i think. The About box says '5.12.3', but gentoo package is called kde-apps/akregator-19.08.3 Anyway, the problem was there with previous version, at least since 19.04.3 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 414395] akregator refuses to import some feeds
https://bugs.kde.org/show_bug.cgi?id=414395 --- Comment #3 from Thomas Capricelli --- Created attachment 124086 --> https://bugs.kde.org/attachment.cgi?id=124086&action=edit screenshot showing the error i get -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 414395] akregator refuses to import some feeds
https://bugs.kde.org/show_bug.cgi?id=414395 --- Comment #2 from Thomas Capricelli --- It works for you ? Then it might be a problem with my distribution (gentoo). Here's a screen shot. The "add Feed" is the dialog you get when right clicking on some feeds directory on the left and choose "Add feed...". The error dialog is what i get when clicking on ok in the first dialog. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 414395] New: akregator refuses to import some feeds
https://bugs.kde.org/show_bug.cgi?id=414395 Bug ID: 414395 Summary: akregator refuses to import some feeds Product: akregator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kdebugs.20.orz...@spamgourmet.com Target Milestone: --- SUMMARY I can't import some feeds. For exemple https://www.lowrisc.org/index.xml, but it happends every once a while. STEPS TO REPRODUCE 1. add a feed 2. paste https://www.lowrisc.org/index.xml in url OBSERVED RESULT Error window "Fonte non trovata in https://www.lowrisc.org/index.xml"; EXPECTED RESULT imported feed SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux, gentoo KDE Plasma Version: 5.15 -> 5.17, at least KDE Frameworks Version: 5.59 -> 5.64, at least Qt Version: 5.12 -> 5.14, at least ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 412771] New: Akregator crashes when clicking a link in a web page
https://bugs.kde.org/show_bug.cgi?id=412771 Bug ID: 412771 Summary: Akregator crashes when clicking a link in a web page Product: akregator Version: 5.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: t...@nobu-games.com Target Milestone: --- Application: akregator (5.12.1) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Links in web pages cause Akregator to crash. In this case I tried to open a link on a Reddit page. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4c6fb82bc0 (LWP 12051))] Thread 22 (Thread 0x7f4b2e7be700 (LWP 12179)): #0 0x7f4c5de6bed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4b2e7bd6f0, expected=0, futex_word=0x7f4b2e7bd8c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f4c5de6bed9 in __pthread_cond_wait_common (abstime=0x7f4b2e7bd790, mutex=0x7f4b2e7bd878, cond=0x7f4b2e7bd8a0) at pthread_cond_wait.c:533 #2 0x7f4c5de6bed9 in __pthread_cond_timedwait (cond=0x7f4b2e7bd8a0, mutex=0x7f4b2e7bd878, abstime=0x7f4b2e7bd790) at pthread_cond_wait.c:667 #3 0x7f4c64c480c6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4c64c48a5d in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4c64c48bf2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4c64c01ca1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4c64c04bad in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4c64c052d4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4c64c4aa65 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4c5de656db in start_thread (arg=0x7f4b2e7be700) at pthread_create.c:463 #11 0x7f4c6b91388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f4b2f93f700 (LWP 12177)): #0 0x7f4c5de6b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f4b2f93e8d8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f4c5de6b9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f4b2f93e888, cond=0x7f4b2f93e8b0) at pthread_cond_wait.c:502 #2 0x7f4c5de6b9f3 in __pthread_cond_wait (cond=0x7f4b2f93e8b0, mutex=0x7f4b2f93e888) at pthread_cond_wait.c:655 #3 0x7f4c64c47fca in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4c64c48a6c in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4c64c48baf in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4c64c01c75 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4c64c04bad in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4c64c05314 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4c64c4aa65 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4c5de656db in start_thread (arg=0x7f4b2f93f700) at pthread_create.c:463 #11 0x7f4c6b91388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f4b3ebeb700 (LWP 12097)): #0 0x7f4c5de6bed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4b3ebea6f0, expected=0, futex_word=0x7f4b3ebea8c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f4c5de6bed9 in __pthread_cond_wait_common (abstime=0x7f4b3ebea790, mutex=0x7f4b3ebea878, cond=0x7f4b3ebea8a0) at pthread_cond_wait.c:533 #2 0x7f4c5de6bed9 in __pthread_cond_timedwait (cond=0x7f4b3ebea8a0, mutex=0x7f4b3ebea878, abstime=0x7f4b3ebea790) at pthread_cond_wait.c:667 #3 0x7f4c64c480c6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4c64c48a5d in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4c64c48bf2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4c64c01ca1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4c64c04f0b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4c64c052d4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4c64c4aa65 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4c5de656db in start_thread (arg=0x7f4b3ebeb700) at pthread_create.c:463 #11 0x7f4c6b91388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f4b3f56c700 (LWP 12096)): #0 0x7f4c5de6b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x
[korganizer] [Bug 411408] To-do view doesn't remember column width
https://bugs.kde.org/show_bug.cgi?id=411408 --- Comment #2 from Thomas Tanghus --- It doesn't remember which column to sort by either. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 411373] Nextcloud calendar disappears
https://bugs.kde.org/show_bug.cgi?id=411373 --- Comment #1 from Thomas Tanghus --- Now the calendar has decided to reappear. That's all good, maybe my Nextcloud instance was unavailable, but since the To-do view was able to deal with just the cached values, so should the month view be able to do that as well. Maybe sending a notification, that the backend is unavailable. -- You are receiving this mail because: You are the assignee for the bug.
