[kmail2] [Bug 278046] KMail freezes when replying to long messages in HTML
https://bugs.kde.org/show_bug.cgi?id=278046 David Brůha changed: What|Removed |Added CC||sal...@albatani.cz -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 483976] KOrganizer forgets the enabled calendars
https://bugs.kde.org/show_bug.cgi?id=483976 --- Comment #6 from David Faure --- For some reason, Carl's fix only went to the 24.02 branch, not to master. But if I may say so, I prefer my fix. It reacts only on actual user interaction, while connecting to selectionChanged() worries me that it'll save partial state while loading the selection (by reacting at every step). -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 483976] KOrganizer forgets the enabled calendars
https://bugs.kde.org/show_bug.cgi?id=483976 David Faure changed: What|Removed |Added CC||fa...@kde.org --- Comment #5 from David Faure --- I fixed that last week: https://invent.kde.org/pim/akonadi-calendar/-/merge_requests/89 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 479951] Kmail sometimes deletes saved attachments when opened through KMail interface
https://bugs.kde.org/show_bug.cgi?id=479951 --- Comment #1 from David Passens --- This appears to be due to this[0] line in messagelib, where opened files are unconditionally deleted. [0] https://invent.kde.org/pim/messagelib/-/blob/master/messageviewer/src/widgets/opensavedfilefolderwidget.cpp?ref_type=heads#L75 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 479951] Kmail sometimes deletes saved attachments when opened through KMail interface
https://bugs.kde.org/show_bug.cgi?id=479951 David Passens changed: What|Removed |Added CC||da...@passens.org -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 484867] New: Account wizard crashes on imap setup
https://bugs.kde.org/show_bug.cgi?id=484867 Bug ID: 484867 Summary: Account wizard crashes on imap setup Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Account Wizard Assignee: kdepim-bugs@kde.org Reporter: da...@dmarec.fr CC: c...@carlschwan.eu Target Milestone: --- Application: accountwizard (0.2) Qt Version: 5.15.12 Frameworks Version: 5.112.0 Operating System: FreeBSD 14.0-RELEASE-p6 amd64 Windowing System: X11 Distribution (Platform): FreeBSD Ports DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: 1. Setting up account for the first time 2. imap selection. 3. type imap in server 4. crash ~ % freebsd-version -ku 14.0-RELEASE-p6 14.0-RELEASE-p6 The crash can be reproduced every time. -- Backtrace: Application: Assistant de création de compte (accountwizard), signal: Segmentation fault (lldb) process attach --pid 2545 Process 2545 stopped * thread #1, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x0008448fde88 libc.so.7`__sys_wait4 + 8 libc.so.7`__sys_wait4: -> 0x8448fde88 <+8>: syscall 0x8448fde8a <+10>: jb 0x8448fa9c8 0x8448fde90 <+16>: retq 0x8448fde91: int3 thread #2, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x0008448fdc2a libc.so.7`__sys_poll + 10 libc.so.7`__sys_poll: -> 0x8448fdc2a <+10>: jb 0x8448fa9c8 0x8448fdc30 <+16>: retq 0x8448fdc31: int3 0x8448fdc32: int3 thread #3, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x0008448fdc2a libc.so.7`__sys_poll + 10 libc.so.7`__sys_poll: -> 0x8448fdc2a <+10>: jb 0x8448fa9c8 0x8448fdc30 <+16>: retq 0x8448fdc31: int3 0x8448fdc32: int3 thread #4, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x0008448fdc2a libc.so.7`__sys_poll + 10 libc.so.7`__sys_poll: -> 0x8448fdc2a <+10>: jb 0x8448fa9c8 0x8448fdc30 <+16>: retq 0x8448fdc31: int3 0x8448fdc32: int3 thread #5, name = 'pool-spawner', stop reason = signal SIGSTOP frame #0: 0x000831909d2c libthr.so.3`___lldb_unnamed_symbol552 + 12 libthr.so.3`___lldb_unnamed_symbol552: -> 0x831909d2c <+12>: retq 0x831909d2d <+13>: int3 0x831909d2e <+14>: int3 0x831909d2f <+15>: int3 thread #6, name = 'gmain', stop reason = signal SIGSTOP frame #0: 0x0008448fdc2a libc.so.7`__sys_poll + 10 libc.so.7`__sys_poll: -> 0x8448fdc2a <+10>: jb 0x8448fa9c8 0x8448fdc30 <+16>: retq 0x8448fdc31: int3 0x8448fdc32: int3 thread #7, name = 'gdbus', stop reason = signal SIGSTOP frame #0: 0x0008448fdcaa libc.so.7`__sys_read + 10 libc.so.7`__sys_read: -> 0x8448fdcaa <+10>: jb 0x8448fa9c8 0x8448fdcb0 <+16>: retq 0x8448fdcb1: int3 0x8448fdcb2: int3 thread #8, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x0008448fdc2a libc.so.7`__sys_poll + 10 libc.so.7`__sys_poll: -> 0x8448fdc2a <+10>: jb 0x8448fa9c8 0x8448fdc30 <+16>: retq 0x8448fdc31: int3 0x8448fdc32: int3 thread #9, name = 'accountwizard', stop reason = signal SIGSTOP frame #0: 0x000831909d2c libthr.so.3`___lldb_unnamed_symbol552 + 12 libthr.so.3`___lldb_unnamed_symbol552: -> 0x831909d2c <+12>: retq 0x831909d2d <+13>: int3 0x831909d2e <+14>: int3 0x831909d2f <+15>: int3 Executable module set to "/usr/local/bin/accountwizard". Architecture set to: x86_64-unknown-freebsd14.0. (lldb) settings set term-width 200 (lldb) thread info thread #1: tid = 101296, 0x0008448fde88 libc.so.7`__sys_wait4 + 8, name = 'accountwizard', stop reason = signal SIGSTOP (lldb) bt all * thread #1, name = 'accountwizard', stop reason = signal SIGSTOP * frame #0: 0x0008448fde88 libc.so.7`__sys_wait4 + 8 frame #1: 0x000831918adc libthr.so.3`___lldb_unnamed_symbol727 + 60 frame #2: 0x00083a7bf29c libKF5Crash.so.5`___lldb_unnamed_symbol229 + 332 frame #3: 0x00083a7bed7b libKF5Crash.so.5`KCrash::defaultCrashHandler(int) + 1147 frame #4: 0x00083191653f libthr.so.3`___lldb_unnamed_symbol684 + 207 frame #5: 0x000831915afb libthr.so.3`___lldb_unnamed_symbol665 + 315 frame #6: 0x0008217782d3 frame #7: 0x00082b0b91ec libQt5Script.so.5`___lldb_unnamed_symbol1895 + 620 frame #8: 0x00082b0ee296 libQt5Script.so.5`___lldb_unnamed_symbol2501 + 150 frame #9: 0x00082b1746da libQt5Script.so.5`___lldb_unnamed_symbol3773 + 1210 frame #10: 0x00082b174949 libQt5Script.so.5`___lldb_unnamed_symbol3776 + 57 frame #11: 0x00082e8579b3
[kleopatra] [Bug 482897] New: Kleopatra does not support all GPG trust levels anymore
https://bugs.kde.org/show_bug.cgi?id=482897 Bug ID: 482897 Summary: Kleopatra does not support all GPG trust levels anymore Classification: Applications Product: kleopatra Version: 3.1.28.230805 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: kitt...@gmail.com CC: kdepim-bugs@kde.org, m...@kde.org Target Milestone: --- SUMMARY Kleopatra does not have anymore an option to set any of all 5 different trust levels from the GPG backend, which in turn implement the RFC-4880 specification. I have already brought up this topic in Gitlab, where Ingo Klöcker kindly suggested to move the issue here. I can see his point, and I can agree on making a UI which is simpler to use, but I don't find it particularly wise to make a step back to do so, especially for KDE software. Maybe the old menu could have been moved to an advanced section elsewhere, but that functionality cannot be entirely missing, in my opinion. Also, the way in which the new functionality has been implemented, basically transforms key trust management into a FSM with forced transitions (forced by which options you can click), which in my case required me to go and look into the actual code to get a clear understanding of what was going on. OBSERVED RESULT Kleopatra does not have an option to set key trust level anymore. EXPECTED RESULT Kleopatra should reflect GPG behavior, or at least allow for same functionality as GPG, even if layed out differently. A simplified way is welcome, but should reflect backend behavior. 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 on the CC list for the bug.
[Reminder Daemon] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 David Faure changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |akonadi-calendar/-/commit/2 |akonadi-calendar/-/commit/0 |2fbeb4e48646ab4fa9abce21c4e |dea82b7100a3f79a81bfdc2e627 |f1eab31475e5|ba8923131abe --- Comment #29 from David Faure --- Git commit 0dea82b7100a3f79a81bfdc2e627ba8923131abe by David Faure. Committed on 15/02/2024 at 19:40. Pushed by dfaure into branch 'release/24.02'. Implement a dialog for the user to choose the suspend duration The "Remind in 1h" action has been replaced with a "Remind later..." action which pops up that dialog. The UI is QWidget-based (reusing some code from korgac). On mobile we could just not show the "Remind later" action or implement a similar QML-based UI. Related: bug 481024, bug 457046, bug 453298, bug 457046 M +2-0reminder-daemon/CMakeLists.txt M +5-4reminder-daemon/alarmnotification.cpp M +2-2reminder-daemon/kalendaracmain.cpp M +21 -5reminder-daemon/kalendaralarmclient.cpp M +4-0reminder-daemon/kalendaralarmclient.h A +136 -0reminder-daemon/suspenddialog.cpp * A +33 -0reminder-daemon/suspenddialog.h * The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/pim/akonadi-calendar/-/commit/0dea82b7100a3f79a81bfdc2e627ba8923131abe -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 457046] Recent update removes the reminder popup window with a notification, snooze time adjustment is no longer available
https://bugs.kde.org/show_bug.cgi?id=457046 --- Comment #9 from David Faure --- Git commit 0dea82b7100a3f79a81bfdc2e627ba8923131abe by David Faure. Committed on 15/02/2024 at 19:40. Pushed by dfaure into branch 'release/24.02'. Implement a dialog for the user to choose the suspend duration The "Remind in 1h" action has been replaced with a "Remind later..." action which pops up that dialog. The UI is QWidget-based (reusing some code from korgac). On mobile we could just not show the "Remind later" action or implement a similar QML-based UI. Related: bug 481024, bug 452264, bug 453298 M +2-0reminder-daemon/CMakeLists.txt M +5-4reminder-daemon/alarmnotification.cpp M +2-2reminder-daemon/kalendaracmain.cpp M +21 -5reminder-daemon/kalendaralarmclient.cpp M +4-0reminder-daemon/kalendaralarmclient.h A +136 -0reminder-daemon/suspenddialog.cpp * A +33 -0reminder-daemon/suspenddialog.h * The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/pim/akonadi-calendar/-/commit/0dea82b7100a3f79a81bfdc2e627ba8923131abe -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 David Faure changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |akonadi-calendar/-/commit/2 |akonadi-calendar/-/commit/0 |2fbeb4e48646ab4fa9abce21c4e |dea82b7100a3f79a81bfdc2e627 |f1eab31475e5|ba8923131abe --- Comment #28 from David Faure --- Git commit 0dea82b7100a3f79a81bfdc2e627ba8923131abe by David Faure. Committed on 15/02/2024 at 19:40. Pushed by dfaure into branch 'release/24.02'. Implement a dialog for the user to choose the suspend duration The "Remind in 1h" action has been replaced with a "Remind later..." action which pops up that dialog. The UI is QWidget-based (reusing some code from korgac). On mobile we could just not show the "Remind later" action or implement a similar QML-based UI. Related: bug 457046, bug 452264, bug 453298, bug 457046 M +2-0reminder-daemon/CMakeLists.txt M +5-4reminder-daemon/alarmnotification.cpp M +2-2reminder-daemon/kalendaracmain.cpp M +21 -5reminder-daemon/kalendaralarmclient.cpp M +4-0reminder-daemon/kalendaralarmclient.h A +136 -0reminder-daemon/suspenddialog.cpp * A +33 -0reminder-daemon/suspenddialog.h * The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/pim/akonadi-calendar/-/commit/0dea82b7100a3f79a81bfdc2e627ba8923131abe -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 457046] Recent update removes the reminder popup window with a notification, snooze time adjustment is no longer available
https://bugs.kde.org/show_bug.cgi?id=457046 David Faure changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |akonadi-calendar/-/commit/2 |akonadi-calendar/-/commit/0 |2fbeb4e48646ab4fa9abce21c4e |dea82b7100a3f79a81bfdc2e627 |f1eab31475e5|ba8923131abe --- Comment #8 from David Faure --- Git commit 0dea82b7100a3f79a81bfdc2e627ba8923131abe by David Faure. Committed on 15/02/2024 at 19:40. Pushed by dfaure into branch 'release/24.02'. Implement a dialog for the user to choose the suspend duration The "Remind in 1h" action has been replaced with a "Remind later..." action which pops up that dialog. The UI is QWidget-based (reusing some code from korgac). On mobile we could just not show the "Remind later" action or implement a similar QML-based UI. Related: bug 481024, bug 452264, bug 453298 M +2-0reminder-daemon/CMakeLists.txt M +5-4reminder-daemon/alarmnotification.cpp M +2-2reminder-daemon/kalendaracmain.cpp M +21 -5reminder-daemon/kalendaralarmclient.cpp M +4-0reminder-daemon/kalendaralarmclient.h A +136 -0reminder-daemon/suspenddialog.cpp * A +33 -0reminder-daemon/suspenddialog.h * The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/pim/akonadi-calendar/-/commit/0dea82b7100a3f79a81bfdc2e627ba8923131abe -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453298] kalendarac: Notifications miss option to remind later with other time duration than 5 minutes
https://bugs.kde.org/show_bug.cgi?id=453298 David Faure changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |akonadi-calendar/-/commit/2 |akonadi-calendar/-/commit/0 |2fbeb4e48646ab4fa9abce21c4e |dea82b7100a3f79a81bfdc2e627 |f1eab31475e5|ba8923131abe --- Comment #11 from David Faure --- Git commit 0dea82b7100a3f79a81bfdc2e627ba8923131abe by David Faure. Committed on 15/02/2024 at 19:40. Pushed by dfaure into branch 'release/24.02'. Implement a dialog for the user to choose the suspend duration The "Remind in 1h" action has been replaced with a "Remind later..." action which pops up that dialog. The UI is QWidget-based (reusing some code from korgac). On mobile we could just not show the "Remind later" action or implement a similar QML-based UI. Related: bug 481024, bug 457046, bug 452264, bug 457046 M +2-0reminder-daemon/CMakeLists.txt M +5-4reminder-daemon/alarmnotification.cpp M +2-2reminder-daemon/kalendaracmain.cpp M +21 -5reminder-daemon/kalendaralarmclient.cpp M +4-0reminder-daemon/kalendaralarmclient.h A +136 -0reminder-daemon/suspenddialog.cpp * A +33 -0reminder-daemon/suspenddialog.h * The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/pim/akonadi-calendar/-/commit/0dea82b7100a3f79a81bfdc2e627ba8923131abe -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453298] kalendarac: Notifications miss option to remind later with other time duration than 5 minutes
https://bugs.kde.org/show_bug.cgi?id=453298 David Faure changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||akonadi-calendar/-/commit/2 ||2fbeb4e48646ab4fa9abce21c4e ||f1eab31475e5 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #9 from David Faure --- Git commit 22fbeb4e48646ab4fa9abce21c4ef1eab31475e5 by David Faure. Committed on 13/02/2024 at 15:57. Pushed by dfaure into branch 'master'. Implement a dialog for the user to choose the suspend duration The "Remind in 1h" action has been replaced with a "Remind later..." action which pops up that dialog. The UI is QWidget-based (reusing some code from korgac). On mobile we could just not show the "Remind later" action or implement a similar QML-based UI. Related: bug 481024, bug 457046, bug 452264, bug 457046 M +2-0reminder-daemon/CMakeLists.txt M +5-4reminder-daemon/alarmnotification.cpp M +2-2reminder-daemon/kalendaracmain.cpp M +21 -5reminder-daemon/kalendaralarmclient.cpp M +4-0reminder-daemon/kalendaralarmclient.h A +136 -0reminder-daemon/suspenddialog.cpp * A +33 -0reminder-daemon/suspenddialog.h * The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/pim/akonadi-calendar/-/commit/22fbeb4e48646ab4fa9abce21c4ef1eab31475e5 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 David Faure changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||akonadi-calendar/-/commit/2 ||2fbeb4e48646ab4fa9abce21c4e ||f1eab31475e5 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #28 from David Faure --- Git commit 22fbeb4e48646ab4fa9abce21c4ef1eab31475e5 by David Faure. Committed on 13/02/2024 at 15:57. Pushed by dfaure into branch 'master'. Implement a dialog for the user to choose the suspend duration The "Remind in 1h" action has been replaced with a "Remind later..." action which pops up that dialog. The UI is QWidget-based (reusing some code from korgac). On mobile we could just not show the "Remind later" action or implement a similar QML-based UI. Related: bug 481024, bug 457046, bug 453298, bug 457046 M +2-0reminder-daemon/CMakeLists.txt M +5-4reminder-daemon/alarmnotification.cpp M +2-2reminder-daemon/kalendaracmain.cpp M +21 -5reminder-daemon/kalendaralarmclient.cpp M +4-0reminder-daemon/kalendaralarmclient.h A +136 -0reminder-daemon/suspenddialog.cpp * A +33 -0reminder-daemon/suspenddialog.h * The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/pim/akonadi-calendar/-/commit/22fbeb4e48646ab4fa9abce21c4ef1eab31475e5 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 457046] Recent update removes the reminder popup window with a notification, snooze time adjustment is no longer available
https://bugs.kde.org/show_bug.cgi?id=457046 --- Comment #7 from David Faure --- Git commit 22fbeb4e48646ab4fa9abce21c4ef1eab31475e5 by David Faure. Committed on 13/02/2024 at 15:57. Pushed by dfaure into branch 'master'. Implement a dialog for the user to choose the suspend duration The "Remind in 1h" action has been replaced with a "Remind later..." action which pops up that dialog. The UI is QWidget-based (reusing some code from korgac). On mobile we could just not show the "Remind later" action or implement a similar QML-based UI. Related: bug 481024, bug 452264, bug 453298 M +2-0reminder-daemon/CMakeLists.txt M +5-4reminder-daemon/alarmnotification.cpp M +2-2reminder-daemon/kalendaracmain.cpp M +21 -5reminder-daemon/kalendaralarmclient.cpp M +4-0reminder-daemon/kalendaralarmclient.h A +136 -0reminder-daemon/suspenddialog.cpp * A +33 -0reminder-daemon/suspenddialog.h * The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/pim/akonadi-calendar/-/commit/22fbeb4e48646ab4fa9abce21c4ef1eab31475e5 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 457046] Recent update removes the reminder popup window with a notification, snooze time adjustment is no longer available
https://bugs.kde.org/show_bug.cgi?id=457046 David Faure changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||akonadi-calendar/-/commit/2 ||2fbeb4e48646ab4fa9abce21c4e ||f1eab31475e5 --- Comment #6 from David Faure --- Git commit 22fbeb4e48646ab4fa9abce21c4ef1eab31475e5 by David Faure. Committed on 13/02/2024 at 15:57. Pushed by dfaure into branch 'master'. Implement a dialog for the user to choose the suspend duration The "Remind in 1h" action has been replaced with a "Remind later..." action which pops up that dialog. The UI is QWidget-based (reusing some code from korgac). On mobile we could just not show the "Remind later" action or implement a similar QML-based UI. Related: bug 481024, bug 452264, bug 453298 M +2-0reminder-daemon/CMakeLists.txt M +5-4reminder-daemon/alarmnotification.cpp M +2-2reminder-daemon/kalendaracmain.cpp M +21 -5reminder-daemon/kalendaralarmclient.cpp M +4-0reminder-daemon/kalendaralarmclient.h A +136 -0reminder-daemon/suspenddialog.cpp * A +33 -0reminder-daemon/suspenddialog.h * The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/pim/akonadi-calendar/-/commit/22fbeb4e48646ab4fa9abce21c4ef1eab31475e5 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 David Faure changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||akonadi-calendar/-/commit/2 ||2fbeb4e48646ab4fa9abce21c4e ||f1eab31475e5 Resolution|--- |FIXED --- Comment #27 from David Faure --- Git commit 22fbeb4e48646ab4fa9abce21c4ef1eab31475e5 by David Faure. Committed on 13/02/2024 at 15:57. Pushed by dfaure into branch 'master'. Implement a dialog for the user to choose the suspend duration The "Remind in 1h" action has been replaced with a "Remind later..." action which pops up that dialog. The UI is QWidget-based (reusing some code from korgac). On mobile we could just not show the "Remind later" action or implement a similar QML-based UI. Related: bug 457046, bug 452264, bug 453298, bug 457046 M +2-0reminder-daemon/CMakeLists.txt M +5-4reminder-daemon/alarmnotification.cpp M +2-2reminder-daemon/kalendaracmain.cpp M +21 -5reminder-daemon/kalendaralarmclient.cpp M +4-0reminder-daemon/kalendaralarmclient.h A +136 -0reminder-daemon/suspenddialog.cpp * A +33 -0reminder-daemon/suspenddialog.h * The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/pim/akonadi-calendar/-/commit/22fbeb4e48646ab4fa9abce21c4ef1eab31475e5 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 --- Comment #22 from David Faure --- The change contains a new feature and lots of new texts to be translated, I have no idea if it can be accepted into 22.12.3. Let's see if it's approved before discussing backports, in any case. But you don't actually need it to be released in order to use it. You can easily rebuild a patch akonadi-calendar package even right now. You're on OpenSUSE so in your case it means downloading the src rpm (1), adding my change as a patch in the spec file (2), rebuilding the RPM (3), installing (4), done. Or doing that on the opensuse build service to install less development packages locally (but step 2 is the same). (1) sudo zypper source-install akonadi-calendar (2) adding the patch in /usr/src/packages/SOURCES, editing /usr/src/packages/SPECS/akonadi-calendar.spec to add it (3) rpmbuild -bb akonadi-calendar.spec (4) rpm -Uvh *.rpm Please don't ask me to guide you step by step, there are online resources for all this. Debian/ubuntu users can do something similar with apt-get source and debuild. -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 --- Comment #20 from David Faure --- Sorry for derailing the discussions about workarounds with a proper fix ;-) (see description in merge request) -- 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 #5 from David Faure --- I'm referring to https://invent.kde.org/pim/akonadi-calendar/-/merge_requests/82 -- 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 David Faure changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||fa...@kde.org --- Comment #4 from David Faure --- It should remember from one time to the next: if you select days and confirm "suspend", the next time it should offer days. The code for this was a bit convoluted in korgac (so it might have been buggy) but I re-worked that code in kalendarac and I can confirm, it will remember from one time to the next (even across process restarts). -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 David Faure changed: What|Removed |Added Component|calendar|general Product|kontact |Reminder Daemon --- Comment #16 from David Faure --- I'm working on a patch. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 --- Comment #11 from David Faure --- Hi Bernhard! Long time no "see" ;-) Yeah after my last comment I had a similar idea, one of the buttons in the notification could trigger a dialog box like the old korgac one, where we can have widgets to define a delay etc. KOrganizer might not be running, so it wouldn't be the right process for popping up that dialog. But kalendarac (the new daemon) could pop up the dialog like korgac did. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 --- Comment #9 from David Faure --- > Actually you should never have removed the original functionality "You"? Just because I have a @kde.org address does not mean I was part of that decision in any shape of form. On the contrary I was among the first ones to complain about it when I found out, as a user. And I'm writing here because I'm on the same side as you, trying to find possible solutions. I know you're frustrated but please refrain from attacking the first person you talk to. As for DBus, I'm sure the notification library sends a DBus signal that plasma reacts to, but I'm not sure how that would help as long as kalendarac only has code to postpone by 5 minutes and 1 hour. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 David Faure changed: What|Removed |Added CC||fa...@kde.org --- Comment #4 from David Faure --- I was told this was because freedesktop.org notifications don't support custom widgets, only a few action buttons, for interoperability with other desktop environments. I agree however this is really suboptimal, especially when not caring for other desktop environments. As for "workarounds", you can find the code in akonadi-calendar/reminder-daemon/alarmnotification.cpp line 135 and add more buttons like "remind tomorrow". Maybe we should implement an alternative notification solution in kalendarac that looks more like the old korgac dialog (minus its bugs...). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 David Faure changed: What|Removed |Added CC||fa...@kde.org --- Comment #11 from David Faure --- (In reply to Robby Engelmann from comment #5) > does this: > >qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to > >"stateChanged" : Type not registered with QtDBus in parameter list: > >QNetworkManagerInterface::NMState > >qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to > >"connectivityChanged" : Type not registered with QtDBus in parameter list: > >QNetworkManagerInterface::NMConnectivityState > >qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to > >"deviceTypeChanged" : Type not registered with QtDBus in parameter list: > >QNetworkManagerInterface::NMDeviceType > >qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to > >"meteredChanged" : Type not registered with QtDBus in parameter list: > >QNetworkManagerInterface::NMMetered > > hint, that kmail is not able to establish a network connection and this is > why no mails can be pop'ed and the sending fails. > And the failed sending triggers a crash? > And the ews ressource works because making use of another connection > protocol? > ...I am only wildly guessing... No these warnings were harmless and are now fixed in https://codereview.qt-project.org/c/qt/qtbase/+/527739. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 477214] Application: Google Mail (akonadi_imap_resource) crash in Akonadi::Collection::hasAttribute
https://bugs.kde.org/show_bug.cgi?id=477214 David Faure changed: What|Removed |Added Summary|Application: Google Mail|Application: Google Mail |(jshand2013)|(akonadi_imap_resource) |(akonadi_imap_resource) |crash in |crash in|Akonadi::Collection::hasAtt |Akonadi::Collection::hasAtt |ribute |ribute | -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 477214] Application: Google Mail (jshand2013) (akonadi_imap_resource) crash in Akonadi::Collection::hasAttribute
https://bugs.kde.org/show_bug.cgi?id=477214 --- Comment #3 from David Faure --- [KCrash Handler] #4 QHash::findNode(QByteArray const&, unsigned int*) const (ahp=, akey=, this=) at /usr/ src/debug/akonadi-23.08.3/src/core/attributestorage.cpp:69 #5 QHash::contains(QByteArray const&) const (akey=, this=) at /usr/include/qt5/QtCore/qhash.h:920 #6 Akonadi::AttributeStorage::hasAttribute(QByteArray const&) const (type=..., this=0x40) at /usr/src/debug/akonadi-23.08.3/src/core/attributestorage.cpp:69 #7 Akonadi::Collection::hasAttribute(QByteArray const&) const (this=this@entry=0x55e8e3c046e0, type=...) at /usr/src/debug/akonadi-23.08.3/src/core/collection.cpp:163 #8 0x7f90a30bd909 in Akonadi::Collection::hasAttribute() const (this=0x55e8e3c046e0) at /usr/src/debug/akonadi-23.08.3/src/co re/collection.h:595 #9 (anonymous namespace)::sortCollectionsForSync(Akonadi::Collection const&, Akonadi::Collection const&) (l=..., r=...) at /usr/src/debug/akonadi-23.08.3/src/agentbas e/resourcebase.cpp:855 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 477214] Application: Google Mail (jshand2013) (akonadi_imap_resource) crash in Akonadi::Collection::hasAttribute
https://bugs.kde.org/show_bug.cgi?id=477214 David Faure changed: What|Removed |Added Summary|Application: Google Mail|Application: Google Mail |(jshand2013)|(jshand2013) |(akonadi_imap_resource),|(akonadi_imap_resource) |signal: Segmentation fault |crash in ||Akonadi::Collection::hasAtt ||ribute CC||fa...@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 477606] New: Kmail crashes when archiving email account
https://bugs.kde.org/show_bug.cgi?id=477606 Bug ID: 477606 Summary: Kmail crashes when archiving email account Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kitt...@gmail.com Target Milestone: --- Application: kmail (5.24.3 (23.08.3)) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.5.10-200.fc38.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 39 (Thirty Nine) DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: Attempting to archive an Exchange account entirely, with all subfolders, results in kmail crashing. Chaning compression type does not change the outcome. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted [KCrash Handler] #4 0x7f82ae0ae834 in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x7f82ae05c8ee in raise () at /lib64/libc.so.6 #6 0x7f82ae0448ff in abort () at /lib64/libc.so.6 #7 0x7f82ae2a4d19 in __gnu_cxx::__verbose_terminate_handler() [clone .cold] () at /lib64/libstdc++.so.6 #8 0x7f82ae2b4f4c in __cxxabiv1::__terminate(void (*)()) () at /lib64/libstdc++.so.6 #9 0x7f82ae2b4fb7 in () at /lib64/libstdc++.so.6 #10 0x7f82ae2b5218 in () at /lib64/libstdc++.so.6 #11 0x7f82acb1a98f in Akonadi::Item::throwPayloadException(int, int) const [clone .cold] () at /lib64/libKPim5AkonadiCore.so.5 #12 0x7f82adf14422 in QSharedPointer Akonadi::Item::payload >() const () at /lib64/libKPim5MailCommon.so.5 #13 0x7f82adf74d67 in MailCommon::BackupJob::itemFetchJobResult(KJob*) () at /lib64/libKPim5MailCommon.so.5 #14 0x7f82ae8e8821 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #15 0x7f82afcf6706 in KJob::result(KJob*, KJob::QPrivateSignal) () at /lib64/libKF5CoreAddons.so.5 #16 0x7f82afcfc5bb in KJob::finishJob(bool) () at /lib64/libKF5CoreAddons.so.5 #17 0x7f82ae8df0cb in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #18 0x7f82af5aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #19 0x7f82ae8b4548 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #20 0x7f82ae8b79f5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #21 0x7f82ae906f9f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #22 0x7f82a8028e5c in g_main_context_dispatch_unlocked.lto_priv () at /lib64/libglib-2.0.so.0 #23 0x7f82a8083dd8 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0 #24 0x7f82a8026ad3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #25 0x7f82ae906a89 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #26 0x7f82ae8b2f0b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #27 0x7f82ae8bb19b in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #28 0x561c84bb5e5f in main () [Inferior 1 (process 11463) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 475679] Search shows no results
https://bugs.kde.org/show_bug.cgi?id=475679 --- Comment #3 from David Pérez --- I'm searching for some value that is in the description. Now I'm not using KDE Neon but Pop OS and cannot test latest version of KOrganizer. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 452322] KaddressBook does not let me add Google account
https://bugs.kde.org/show_bug.cgi?id=452322 --- Comment #5 from David --- I really appreciate your work, thank you very much. I don't know if it can be related, but after some time (some tens hours of system uptime) the account gets unlinked with some 10-12 errors popping up. Next time it happens I will take note of the exact message and in case open a new bug for that. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 475679] New: Search shows no results
https://bugs.kde.org/show_bug.cgi?id=475679 Bug ID: 475679 Summary: Search shows no results Classification: Applications Product: korganizer Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kdepim-bugs@kde.org Reporter: david.perez.ingeni...@gmail.com Target Milestone: --- Created attachment 162340 --> https://bugs.kde.org/attachment.cgi?id=162340=edit screenshot in italian language SUMMARY STEPS TO REPRODUCE 1. I have a calendar with lots of data, in a personal calendar stored in a local file. 2. I search for a string I know it is very frequent, by pressing Ctrl+F. 3. I select of the "search in" options and by type of event. 4. I select the right date range. OBSERVED RESULT No results. For some other keywords I get some results. EXPECTED RESULT Lots of results SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Plasma based on Ubuntu 22.04 (available in About System) KDE Plasma Version: 5.27 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 --- Comment #30 from David de Cos --- (In reply to caxilbund from comment #28) > I was able to set it up and configure it within korganizer. However, it came > up with "the configured account doesn't exist" error message after I had > supposedly configured it and the calendar did not appear. I hit the reset > button in the settings calendar dialog, the error message disappeared, the > ready message appeared, and lo and behold the calendar entries actually > appeared in the user interface. I have kdepim-runtime 23.08.1-3.1 in Opensuse Tumbleweed and this is the way I have managed to get my Google Calendar back. Thanks for the workaround! -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 David de Cos changed: What|Removed |Added CC||david.de...@ehu.eus -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 --- Comment #16 from David Korth --- Can verify that downgrading KDEPIM from 23.08 to 23.04.3 fixed this issue here. (Using Gentoo Linux.) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 David Korth changed: What|Removed |Added CC||gerbils...@gerbilsoft.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 444288] Akonadi "losing connection" to Google Calendars after some uptime / waking from sleep until either akonadictrl restart is used or Google Groupware is restarted in Korganizer.
https://bugs.kde.org/show_bug.cgi?id=444288 David Korth changed: What|Removed |Added CC||gerbils...@gerbilsoft.com -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 419929] kmail closes after setting trash folder
https://bugs.kde.org/show_bug.cgi?id=419929 David Larochette changed: What|Removed |Added CC||da...@larochette.me --- Comment #4 from David Larochette --- Created attachment 161156 --> https://bugs.kde.org/attachment.cgi?id=161156=edit strace log -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 469674] KMail crashes when trying to view certain e-mails
https://bugs.kde.org/show_bug.cgi?id=469674 David de Cos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from David de Cos --- The bug disappeared after a reinstall, there must have been something wrong with my previous system. Marking as resolved. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411640] Could not create collection trash, resourceId: 8
https://bugs.kde.org/show_bug.cgi?id=411640 David changed: What|Removed |Added Version|5.21.1 |5.22.3 Platform|openSUSE|Ubuntu Ever confirmed|0 |1 CC||davidan...@gmail.com Status|REPORTED|CONFIRMED --- Comment #5 from David --- I just experience this today on Kubuntu 23.04 and managed to fix it. Yesterday, I had been re-configuring my IMAP accounts to trash things into the remote trash bins instead of my local one. Today, when I started KMail I received this aforementioned error. I did some mucking around in Akonadi Console until I figured out which IMAP resource was failing. Then I went to the "Agents" tab and did a "Configure Natively", changing the trash bin to another location (back to my local mail trash). I was able to restart Akonadi and KMail and everything seemed to be working. Next I configured it back to using remote trash and it still seems to be okay, although akonadiconsole did crash once while restarting the server. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 469674] KMail crashes when trying to view certain e-mails
https://bugs.kde.org/show_bug.cgi?id=469674 --- Comment #3 from David de Cos --- Created attachment 158896 --> https://bugs.kde.org/attachment.cgi?id=158896=edit And a third one -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 469674] KMail crashes when trying to view certain e-mails
https://bugs.kde.org/show_bug.cgi?id=469674 --- Comment #2 from David de Cos --- Created attachment 158895 --> https://bugs.kde.org/attachment.cgi?id=158895=edit Another one -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 469674] KMail crashes when trying to view certain e-mails
https://bugs.kde.org/show_bug.cgi?id=469674 --- Comment #1 from David de Cos --- Created attachment 158892 --> https://bugs.kde.org/attachment.cgi?id=158892=edit One of the mails that crash my KMail -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 469674] New: KMail crashes when trying to view certain e-mails
https://bugs.kde.org/show_bug.cgi?id=469674 Bug ID: 469674 Summary: KMail crashes when trying to view certain e-mails Classification: Applications Product: kmail2 Version: 5.23.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: david.de...@ehu.eus Target Milestone: --- KMail crashes when I open certain e-mails. This has started today, after I upgraded my KDE Apps to version 23.04 and KDE Frameworks to 5.105. I haven't been able to figure out what those mails have in common, although most of them seem to be forwards, possibly with attached images. The same e-mails are viewed perfectly in another computer with KMail 5.22.3. This is the backtrace (identical in all the e-mails that produce the crash): ** Application: KMail (kmail), signal: Aborted [KCrash Handler] #4 0x7f54331a9c6b in raise () from /lib64/libc.so.6 #5 0x7f54331ab305 in abort () from /lib64/libc.so.6 #6 0x7f5433618675 in ?? () from /usr/lib64/libstdc++.so.6 #7 0x7f5433623d0c in ?? () from /usr/lib64/libstdc++.so.6 #8 0x7f5433622d79 in ?? () from /usr/lib64/libstdc++.so.6 #9 0x7f5433623496 in __gxx_personality_v0 () from /usr/lib64/libstdc++.so.6 #10 0x7f543336aa34 in _Unwind_RaiseException_Phase2 (exc=0x55ae89def080, context=0x7ffcd0fe8330, frames_p=0x7ffcd0fe8420) at ../../../libgcc/unwind.inc:64 #11 0x7f543336b0f1 in _Unwind_RaiseException (exc=0x55ae89def080) at ../../../libgcc/unwind.inc:136 #12 0x7f5433623fcb in __cxa_throw () from /usr/lib64/libstdc++.so.6 #13 0x7f543361827e in ?? () from /usr/lib64/libstdc++.so.6 #14 0x7f541ed4a4c6 in ZXing::QRCode::Reader::Reader(ZXing::DecodeHints const&) () from /usr/lib64/libZXing.so.1 #15 0x7f541ecd5a49 in ZXing::MultiFormatReader::MultiFormatReader(ZXing::DecodeHints const&) () from /usr/lib64/libZXing.so.1 #16 0x7f541ecd7cd7 in ?? () from /usr/lib64/libZXing.so.1 #17 0x7f541ecd8089 in ZXing::ReadBarcode(ZXing::ImageView const&, ZXing::DecodeHints const&) () from /usr/lib64/libZXing.so.1 #18 0x7f53cc1047b5 in zxingReadBarcode (img=..., hints=...) at /usr/src/debug/kitinerary-23.04.1-lp154.172.1.x86_64/src/lib/barcodedecoder.cpp:211 #19 0x7f53cc104dd5 in KItinerary::BarcodeDecoder::decodeZxing (this=, img=..., format=..., result=...) at /usr/src/debug/kitinerary-23.04.1-lp154.172.1.x86_64/src/lib/barcodedecoder.cpp:230 #20 0x7f53cc1051ae in KItinerary::BarcodeDecoder::decodeBinary (this=0x55ae895828e0, img=..., hint=...) at /usr/src/debug/kitinerary-23.04.1-lp154.172.1.x86_64/src/lib/barcodedecoder.cpp:54 #21 0x7f53cc0d39f6 in KItinerary::BarcodeDocumentProcessorHelper::expandNode (img=..., barcodeHints=..., parent=..., engine=0x7ffcd0fe8e40) at /usr/src/debug/kitinerary-23.04.1-lp154.172.1.x86_64/src/lib/processors/barcodedocumentprocessorhelper.cpp:20 #22 0x7f53cc0db2b0 in KItinerary::ImageDocumentProcessor::expandNode (this=, engine=0x7ffcd0fe8e40, node=...) at /usr/src/debug/kitinerary-23.04.1-lp154.172.1.x86_64/src/lib/processors/imagedocumentprocessor.cpp:46 #23 KItinerary::ImageDocumentProcessor::expandNode (this=, node=..., engine=0x7ffcd0fe8e40) at /usr/src/debug/kitinerary-23.04.1-lp154.172.1.x86_64/src/lib/processors/imagedocumentprocessor.cpp:30 #24 0x7f53cc07f65a in KItinerary::ExtractorEnginePrivate::processNode (this=this@entry=0x55ae89582890, node=...) at /usr/src/debug/kitinerary-23.04.1-lp154.172.1.x86_64/src/lib/engine/extractorengine.cpp:62 #25 0x7f53cc07f690 in KItinerary::ExtractorEnginePrivate::processNode (node=..., this=0x55ae89582890) at /usr/src/debug/kitinerary-23.04.1-lp154.172.1.x86_64/src/lib/engine/extractorengine.cpp:58 #26 KItinerary::ExtractorEnginePrivate::processNode (this=this@entry=0x55ae89582890, node=...) at /usr/src/debug/kitinerary-23.04.1-lp154.172.1.x86_64/src/lib/engine/extractorengine.cpp:64 #27 0x7f53cc07febe in KItinerary::ExtractorEnginePrivate::processNode (node=..., this=0x55ae89582890) at /usr/src/debug/kitinerary-23.04.1-lp154.172.1.x86_64/src/lib/engine/extractorengine.cpp:58 #28 KItinerary::ExtractorEngine::extract (this=this@entry=0x7ffcd0fe8e40) at /usr/src/debug/kitinerary-23.04.1-lp154.172.1.x86_64/src/lib/engine/extractorengine.cpp:154 #29 0x7f53e4148a8a in ItineraryProcessor::process (this=, part=...) at /usr/src/debug/kdepim-addons-23.04.1-lp154.254.1.x86_64/plugins/messageviewer/bodypartformatter/itinerary/itineraryprocessor.cpp:152 #30 0x7f54323200c5 in MimeTreeParser::ObjectTreeParser::processType (this=this@entry=0x7ffcd0fe9960, node=0x55ae89dea6c0, processResult=..., mimeType=...) at /usr/src/debug/messagelib-23.04.1-lp154.277.1.x86_64/mimetreeparser/src/objecttreeparser.cpp:146 #31 0x7f543232091d in MimeTreeParser::ObjectTreeParser::parseObjectTreeInternal (this=0x7ffcd0fe9960, node=,
[Akonadi] [Bug 450217] (SEGV) Crash in Akonadi::Server::AkonadiServer::connectionDisconnected
https://bugs.kde.org/show_bug.cgi?id=450217 --- Comment #21 from David Tonhofer --- Since postix has marked my report as duplicate, I will repost my way to reproduce reproducibly: 1) Start "Godot" 2) Have a "yellow tooltip" pop up about the window frame (not proper to Godot, but to the window manager) for example, go into the "minimize" button until "minimize" tooltip pops up 3) Move the mouse into the "minimize" tooltip 4) Kwin (not only Akonadi) crashes with segmentation fault. running: kwin-wayland-5.27.3-2.fc36 crash function: QTimer::timeout(QTimer::QPrivateSignal) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 467430] Akonadi crash when cursor moves into a tooltip popup window
https://bugs.kde.org/show_bug.cgi?id=467430 --- Comment #5 from David Tonhofer --- Created attachment 157928 --> https://bugs.kde.org/attachment.cgi?id=157928=edit core backtrace collected at kwin crash This may only be remotely related to the reported bug -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 467430] Akonadi crash when cursor moves into a tooltip popup window
https://bugs.kde.org/show_bug.cgi?id=467430 --- Comment #4 from David Tonhofer --- While trying to reproduce via: 1) Start Godot 2) Make a "yellow tooltip" pop up about the window frame (not proper to Godot but to the window manager) for example, go into the "minimize" button until "minimize" pops up 3) Move the mouse into the "minimize" tooltip 4) Kwin (not only Akonadi) crashes with segmentation fault (but I can't report bug because "kernel is tainted", cat /proc/sys/kernel/tainted says "512", i.e. "kernel issued warning"). running: kwin-wayland-5.27.3-2.fc36 crash function: QTimer::timeout(QTimer::QPrivateSignal) Attaching the "core_backtrace", for what it's worth -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 467565] Etesync crash
https://bugs.kde.org/show_bug.cgi?id=467565 David Redondo changed: What|Removed |Added Summary|Absturz von etesync |Etesync crash CC||k...@david-redondo.de --- Comment #1 from David Redondo --- > Absturz idR nach (vermuteten) Schreibzugriffen, Einträge können gelesen > werden und sind in der Anzeige, aberÄnderungen werden nicht >gespeichert und > regelmäßig (Syn-Intervalle?) kommen Absturzberichte. > >Dieser Absturz konkret erfolgte nach dem Systemstart. Bei Bedarf kann ich noch >einmal Abstürze provozieren und die Logs schicken. Crash after assumed write acesses. Entries can be read and are displayed but any changes are not saved and crash reports appear in regular interval. This crash happened on system start, if needed more crashes can be provoked. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 467430] Akonadi crash when cursor moves into a tooltip popup window
https://bugs.kde.org/show_bug.cgi?id=467430 David Tonhofer changed: What|Removed |Added Summary|Akonadi crash possibly due |Akonadi crash when cursor |to dolphin |moves into a tooltip popup ||window -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 467430] Akonadi crash possibly due to dolphin
https://bugs.kde.org/show_bug.cgi?id=467430 --- Comment #2 from David Tonhofer --- VERY reproducible. But I'm not sure whether it is KDE/Qt, GTK or Fedora related. For example, if you have the "abrt" tool open (report-gtk) and you activate the tooltip for the "minimize" button in the "abrt" window's decorations and you move the mouse into the tooltip ... kwin_wayland goes down with segmentation fault. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 467430] Akonadi crash possibly due to dolphin
https://bugs.kde.org/show_bug.cgi?id=467430 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 467430] Akonadi crash possibly due to dolphin
https://bugs.kde.org/show_bug.cgi?id=467430 --- Comment #1 from David Tonhofer --- Created attachment 157520 --> https://bugs.kde.org/attachment.cgi?id=157520=edit New crash information added by DrKonqi akonadiserver (5.22.0 (22.12.0)) using Qt 5.15.8 I happened again. The triggering event seems to be a yellow-colored tooltip that pops up near the mouse. If the mouse cursor is moved into the tooltip, akonadi crashes. -- Backtrace (Reduced): #4 std::default_delete::operator() (__ptr=0x111, this=) at /usr/include/c++/12/bits/unique_ptr.h:89 #5 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12/bits/unique_ptr.h:396 #6 std::__new_allocator > >::destroy > > (__p=, this=0x7fff5f24b0b8) at /usr/include/c++/12/bits/new_allocator.h:181 #7 std::allocator_traits > > >::destroy > > (__p=, __a=...) at /usr/include/c++/12/bits/alloc_traits.h:535 #8 std::vector >, std::allocator > > >::_M_erase (__position=..., this=0x7fff5f24b0b8) at /usr/include/c++/12/bits/vector.tcc:181 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467147] Falkon and KMail (qtwebengine-based(?)) segfault when DP screen is going to standby or powered off
https://bugs.kde.org/show_bug.cgi?id=467147 --- Comment #5 from David Edmundson --- given this is crashing in QtWayland, can you get a hash of the version used? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467147] Falkon and KMail (qtwebengine-based(?)) segfault when DP screen is going to standby or powered off
https://bugs.kde.org/show_bug.cgi?id=467147 David Edmundson changed: What|Removed |Added Keywords||wayland CC||k...@davidedmundson.co.uk Assignee|kwin-bugs-n...@kde.org |kdepim-bugs@kde.org Component|wayland-generic |general Product|kwin|kmail2 Version|5.27.3 |unspecified --- Comment #4 from David Edmundson --- Lets not put client-side issues in kwin. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 467430] New: Akonadi crash possibly due to dolphin
https://bugs.kde.org/show_bug.cgi?id=467430 Bug ID: 467430 Summary: Akonadi crash possibly due to dolphin Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: bugh...@gluino.name Target Milestone: --- Application: akonadiserver (5.22.0 (22.12.0)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.18-100.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: I feel this is at least the 3 time I have encountered this crash What happens: - I have a large-ish list of ODT LibreOffice Text docucment, the directory where they reside is open in DOLPHIN - Iteratively do: -- Click on document, opening it. -- Edit the name of the document in DOLPHIN by prepending a date (_MM_DD_) found inside the document. Hit RETURN. -- This rearranges the document list in DOLPHIN of course (as expected, but I know that renaming documents in DOLPHIN used to be fraught with some arbitrariness & danger) -- Do not bother to close thise LibreOffice Writer instance, which accumulates windows, but that's ok as I can close them all in one click once done. The crash seems to occur after hitting RETURN upon having renamed a document. Also, YouTube is playing lofi in the background. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 std::default_delete::operator() (__ptr=0x111, this=) at /usr/include/c++/12/bits/unique_ptr.h:89 #5 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12/bits/unique_ptr.h:396 #6 std::__new_allocator > >::destroy > > (__p=, this=0x7fff9bf42a28) at /usr/include/c++/12/bits/new_allocator.h:181 #7 std::allocator_traits > > >::destroy > > (__p=, __a=...) at /usr/include/c++/12/bits/alloc_traits.h:535 #8 std::vector >, std::allocator > > >::_M_erase (__position=..., this=0x7fff9bf42a28) at /usr/include/c++/12/bits/vector.tcc:181 #9 std::vector >, std::allocator > > >::erase (__position=..., this=0x7fff9bf42a28) at /usr/include/c++/12/bits/stl_vector.h:1530 #10 Akonadi::Server::AkonadiServer::connectionDisconnected (this=0x7fff9bf429a0) at /usr/src/debug/kf5-akonadi-server-22.12.0-2.fc36.x86_64/src/server/akonadi.cpp:234 #11 0x7f0e8aec8134 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7f0e8ae9d4cb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7f0e8aea0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #14 0x7f0e8aeeeb07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #15 0x7f0e89b18faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #16 0x7f0e89b6e2c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #17 0x7f0e89b16940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #18 0x7f0e8aeee5fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #19 0x7f0e8ae9bf3a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7f0e8aea4002 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #21 0x55fcbd308058 in AkApplicationBase::exec (this=0x7fff9bf42970) at /usr/src/debug/kf5-akonadi-server-22.12.0-2.fc36.x86_64/src/shared/akapplication.cpp:107 #22 main (argc=, argv=) at /usr/src/debug/kf5-akonadi-server-22.12.0-2.fc36.x86_64/src/server/main.cpp:65 [Inferior 1 (process 2555) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 455153] Cannot use XOAUTH2 authentication on POP3 resource (prevents checking gmail account with POP3 since 31/05/2022)
https://bugs.kde.org/show_bug.cgi?id=455153 David E. Narvaez changed: What|Removed |Added CC||david.narv...@computer.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 429010] KMAIL crashes when making a subfolder inside a Office 365 IMAP account
https://bugs.kde.org/show_bug.cgi?id=429010 David changed: What|Removed |Added Resolution|WAITINGFORINFO |LATER Status|NEEDSINFO |RESOLVED --- Comment #3 from David --- (In reply to Justin Zobel from comment #1) > Thank you for reporting this crash 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 crash with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! No, I cannot anymore. I'm closing this. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 426138] KAddressBook crash when sending SMS
https://bugs.kde.org/show_bug.cgi?id=426138 David changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 460756] New: Converting to sieve filters should use actual folder names instead of translated ones
https://bugs.kde.org/show_bug.cgi?id=460756 Bug ID: 460756 Summary: Converting to sieve filters should use actual folder names instead of translated ones Classification: Applications Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sieve Assignee: kdepim-bugs@kde.org Reporter: k...@david-redondo.de Target Milestone: --- SUMMARY The generated rules use translated folder names for example in German 'Posteingang' instead of INBOX STEPS TO REPRODUCE 1. Convert filter to sieve OBSERVED RESULT generated rule contains fileinto "Posteingang/..."; Server complains failed to store into mailbox 'Posteingang/...': Mailbox doesn't exist: Posteingang/... EXPECTED RESULT it should say fileinto "INBOX/..."; 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 460712] New: Segmentation fault when I advnced to next uread message
https://bugs.kde.org/show_bug.cgi?id=460712 Bug ID: 460712 Summary: Segmentation fault when I advnced to next uread message Classification: Applications Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- Application: kmail (5.20.3 (22.04.3)) (Compiled from sources) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.15.74-gentoo-x86_64 x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: I wasn't doing anything unusual. Clicked "Next" button, and it just died. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7f11d30a7410 in QWidget::style() const () at /usr/lib64/libQt5Widgets.so.5 #5 0x7f11d3084114 in QApplication::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #6 0x7f11d307e70f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #7 0x7f11d26c2338 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #8 0x7f11d271180b in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #9 0x7f11d27120b4 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f11cc4c2cfb in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #11 0x7f11cc4c2fa8 in () at /usr/lib64/libglib-2.0.so.0 #12 0x7f11cc4c305f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #13 0x7f11d27124a6 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #14 0x7f11d26c0dc3 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #15 0x7f11d26c90b0 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #16 0x55fa96bf6aa5 in () #17 0x7f11d205134a in () at /lib64/libc.so.6 #18 0x7f11d20513fc in __libc_start_main () at /lib64/libc.so.6 #19 0x55fa96bf7021 in () [Inferior 1 (process 4129) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #26 from David Jarvie --- Try the KDE kdepim-users mailing list for help on this. -- You are receiving this mail because: You are on the CC list for the bug.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #24 from David Jarvie --- It may be called kontact. You need to raise a new bug report for kontact (if that's the correct product name) about that issue. -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 460289] Opening the detailed progress window does nothing
https://bugs.kde.org/show_bug.cgi?id=460289 David Redondo changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||k...@david-redondo.de --- Comment #1 from David Redondo --- Same for me -- You are receiving this mail because: You are the assignee for the bug.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #21 from David Jarvie --- Unfortunately how to get a consistent working system again is a distro issue, not a KDE issue. If you can't sort it out, you need to ask for help on ArchLinux/Manjaro mailing lists. The KDE bug reporting system can't help with this. -- You are receiving this mail because: You are on the CC list for the bug.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #17 from David Jarvie --- The error message which you report in comment 14 shows that the libicu package either is not installed or is the wrong version. This shows that other packages than libical have been changed when you downgraded libical. You need to ensure that ONLY libical is changed when you downgrade it. -- You are receiving this mail because: You are on the CC list for the bug.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #15 from David Jarvie --- When you downgraded libical, no other packages should have been changed. There are evidently missing dependencies, which should not have happened when just libical was supposed to have been changed. I'm not familiar with the package system on Manjaro/ArchLinux, so I can't help with how to do it correctly, but it looks like you must have used a wrong command or something. -- You are receiving this mail because: You are on the CC list for the bug.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 --- Comment #13 from David Jarvie --- Just to be sure that I understand you correctly, please confirm that you downgraded the libical package to version 3.0.14, and that the faults still occurred. -- You are receiving this mail because: You are on the CC list for the bug.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #11 from David Jarvie --- This is due to a bug in libical version 3.0.15. This should be reported on the Manjaro bug reporting system. A downgrade to libical version 3.0.14 will fix the issue. *** This bug has been marked as a duplicate of bug 460442 *** -- You are receiving this mail because: You are on the CC list for the bug.
[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.
https://bugs.kde.org/show_bug.cgi?id=460389 David Jarvie changed: What|Removed |Added CC||kdepim-bugs@kde.org -- You are receiving this mail because: You are on the CC list for the bug.
[kaddressbook] [Bug 426138] KAddressBook crash when sending SMS
https://bugs.kde.org/show_bug.cgi?id=426138 --- Comment #2 from David --- (In reply to Justin Zobel from comment #1) > Thank you for reporting this crash 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 crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! Unfortunately it's been some months since I couldn't use Kaddressbook at all, my google account is not displayed and I have no contacts. I read somewhere that this is related to an API change by Google. Thus I am currently unable to test, sorry. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 459341] Kmail crash when trying to write recipent address in the new mail window
https://bugs.kde.org/show_bug.cgi?id=459341 David changed: What|Removed |Added CC||kitt...@gmail.com --- Comment #5 from David --- (In reply to Ingo Klöcker from comment #4) > qgpgme 1.17.0 was binary incompatible. Please file a bug with Fedora that > they need to skip 1.17.0 and use at least 1.17.1. See > https://dev.gnupg.org/T5872. yup, can confirm `sudo dnf downgrade qgpgme` solves the issue. -- 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 David E. Narvaez changed: What|Removed |Added CC||david.narv...@computer.org --- Comment #1 from David E. Narvaez --- Forget about the timezone: it does not even say what day the event is. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 457435] New: Krash after idling
https://bugs.kde.org/show_bug.cgi?id=457435 Bug ID: 457435 Summary: Krash after idling Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: deniswon...@cox.net Target Milestone: --- Application: kmail (5.20.1 (22.04.1)) (Compiled from sources) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.18.13-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: I opened the app and minimized before heading to work. Opened the app back up and got a crash report. I have a few apps running like Ktorrent and Nord products. But, nothing serious. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7f03ebfaac78 in QAction::setText(QString const&) () from /lib64/libQt5Widgets.so.5 #5 0x7f03f4601482 in KMMainWidget::updateFolderMenu() () from /lib64/libkmailprivate.so.5 #6 0x7f03f45f7ce5 in KMMainWidget::setupActions() () from /lib64/libkmailprivate.so.5 #7 0x7f03f45e0a91 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) () from /lib64/libkmailprivate.so.5 #8 0x7f03f45a61b5 in KMMainWin::KMMainWin(QWidget*) () from /lib64/libkmailprivate.so.5 #9 0x7f03f45b9457 in KMKernel::openReader(bool, bool) () from /lib64/libkmailprivate.so.5 #10 0x7f03f45be82f in KMKernel::action(bool, bool, bool, QString const&, QString const&, QString const&, QString const&, QString const&, QUrl const&, QList const&, QStringList const&, QString const&, QString const&, QString const&) () from /lib64/libkmailprivate.so.5 #11 0x7f03f45b7c80 in KMKernel::handleCommandLine(bool, QStringList const&, QString const&) () from /lib64/libkmailprivate.so.5 #12 0x56149a17a00c in KMailApplication::activate(QStringList const&, QString const&) () #13 0x7f03f48f2327 in KontactInterface::PimUniqueApplication::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libKF5KontactInterface.so.5 #14 0x7f03f48f2423 in KontactInterface::PimUniqueApplication::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/libKF5KontactInterface.so.5 #15 0x7f03ebd920bb in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5 #16 0x7f03ebd95cc0 in QDBusConnectionPrivate::activateCall(QObject*, int, QDBusMessage const&) [clone .part.0] () from /lib64/libQt5DBus.so.5 #17 0x7f03ebd9653e in QDBusConnectionPrivate::activateObject(QDBusConnectionPrivate::ObjectTreeNode&, QDBusMessage const&, int) () from /lib64/libQt5DBus.so.5 #18 0x7f03ebd98a0c in QDBusActivateObjectEvent::placeMetaCall(QObject*) () from /lib64/libQt5DBus.so.5 #19 0x7f03eb2d22c4 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #20 0x7f03ebfaed22 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #21 0x7f03eb2a8228 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #22 0x7f03eb2ab594 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #23 0x7f03eb2f9467 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #24 0x7f03e4e3ffaf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #25 0x7f03e4e952c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #26 0x7f03e4e3d940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #27 0x7f03eb2f8f5a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7f03eb2a6c7a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #29 0x7f03eb2aed42 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #30 0x56149a178c8f in main () [Inferior 1 (process 149591) detached] The reporter indicates this bug may be a duplicate of or related to bug 362085. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[frameworks-kholidays] [Bug 457176] New: No API documentation for HolidayRegion::rawHolidaysWithAstroSeasons()
https://bugs.kde.org/show_bug.cgi?id=457176 Bug ID: 457176 Summary: No API documentation for HolidayRegion::rawHolidaysWithAstroSeasons() Product: frameworks-kholidays Version: 5.96.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: djar...@kde.org Target Milestone: --- There is nothing in the API documentation to indicate what HolidayRegion::rawHolidaysWithAstroSeasons() is for, as compared to HolidayRegion::rawHolidays() - the API description for the two methods is identical. The name rawHolidaysWithAstroSeasons doesn't mean anything to me, so a description is necessary. Looking at the autotest/testholidayregion.cpp code, it seems, counter-intuitively, that rawHolidaysWithAstroSeasons() is functionally equivalent to the deprecated holidays() function. Rather, I would have expected that rawHolidays() would now be equivalent to holidays(). Please include descriptions for rawHolidaysWithAstroSeasons() and rawHolidays() which makes clear what each is actually for. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.97.0 -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 452322] KaddressBook does not let me add Google account
https://bugs.kde.org/show_bug.cgi?id=452322 --- Comment #2 from David --- (In reply to r.kunschke from comment #1) > The problem still remains since months or longer. > There are lot of duplicated bug reports which shows the importance. > > https://bugs.kde.org/show_bug.cgi?id=446580 > https://bugs.kde.org/show_bug.cgi?id=451621 > https://bugs.kde.org/show_bug.cgi?id=452322 > https://bugs.kde.org/show_bug.cgi?id=359178 > https://bugs.kde.org/show_bug.cgi?id=332224 Yup, can confirm, still present for me as well -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 456509] New: All applications suddenly ripped away while I do nothing special (since this morning's update: Fedora 36, updating
https://bugs.kde.org/show_bug.cgi?id=456509 Bug ID: 456509 Summary: All applications suddenly ripped away while I do nothing special (since this morning's update: Fedora 36, updating Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: bugh...@gluino.name Target Milestone: --- Application: akonadiserver (5.20.1 (22.04.1)) Qt Version: 5.15.3 Frameworks Version: 5.94.0 Operating System: Linux 5.18.10-200.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.25.2 [KCrashBackend] -- Information about the crash: So I was editing something in LibreOffice writer, sometimes changing names of files in dolphin while watching Jimmy Dore on Youtube via Firefox. Then all the applications got ripped away. This already happened a bit earlier today when I move the mouse to the top right corner of the screen. Wham! All the applications are gone. This never happened before a "dnf update" I did "this morning" of 2022-07-09, so it has probably something to do with that. Unfortunately I do not know which packages those were. The "dnf.log" in /var/log is not informative enough and my script to track package updates is currently out of commission. Just the right time. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 std::default_delete::operator() (__ptr=0x110, this=) at /usr/include/c++/12/bits/unique_ptr.h:89 #5 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12/bits/unique_ptr.h:396 #6 std::__new_allocator > >::destroy > > (__p=, this=0x7fff2040bbf8) at /usr/include/c++/12/bits/new_allocator.h:181 #7 std::allocator_traits > > >::destroy > > (__p=, __a=...) at /usr/include/c++/12/bits/alloc_traits.h:535 #8 std::vector >, std::allocator > > >::_M_erase (__position=..., this=0x7fff2040bbf8) at /usr/include/c++/12/bits/vector.tcc:181 #9 std::vector >, std::allocator > > >::erase (__position=..., this=0x7fff2040bbf8) at /usr/include/c++/12/bits/stl_vector.h:1530 #10 Akonadi::Server::AkonadiServer::connectionDisconnected (this=0x7fff2040bb70) at /usr/src/debug/kf5-akonadi-server-22.04.1-1.fc36.x86_64/src/server/akonadi.cpp:234 #11 0x7f9256087694 in QObject::event (this=0x7fff2040bb70, e=0x7f91f4005a20) at kernel/qobject.cpp:1314 #12 0x7f925605d63b in doNotify (event=0x7f91f4005a20, receiver=0x7fff2040bb70) at kernel/qcoreapplication.cpp:1154 #13 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1140 #14 QCoreApplication::notifyInternal2 (receiver=0x7fff2040bb70, event=0x7f91f4005a20) at kernel/qcoreapplication.cpp:1064 #15 0x7f92560609b4 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x559b07bee000) at kernel/qcoreapplication.cpp:1821 #16 0x7f92560ae807 in postEventSourceDispatch (s=0x559b07c0dee0) at kernel/qeventdispatcher_glib.cpp:277 #17 0x7f925437cfaf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7f92543d22c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #19 0x7f925437a940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7f92560ae2fa in QEventDispatcherGlib::processEvents (this=0x559b07c0b350, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7f925605c0ba in QEventLoop::exec (this=this@entry=0x7fff2040b9e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7f9256064162 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x559b05ea9fa8 in AkApplicationBase::exec (this=0x7fff2040bb40) at /usr/src/debug/kf5-akonadi-server-22.04.1-1.fc36.x86_64/src/shared/akapplication.cpp:107 #24 main (argc=, argv=) at /usr/src/debug/kf5-akonadi-server-22.04.1-1.fc36.x86_64/src/server/main.cpp:65 [Inferior 1 (process 5873) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 456403] Akonadi EWS module freezes PC when disconnected from the internet
https://bugs.kde.org/show_bug.cgi?id=456403 --- Comment #2 from David --- (In reply to David from comment #1) > Created attachment 150444 [details] > journal sample See towards the end of the log. Some ~50k entries were truncated because of attachments limitations, but they were all the same. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 456403] Akonadi EWS module freezes PC when disconnected from the internet
https://bugs.kde.org/show_bug.cgi?id=456403 --- Comment #1 from David --- Created attachment 150444 --> https://bugs.kde.org/attachment.cgi?id=150444=edit journal sample -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 456403] New: Akonadi EWS module freezes PC when disconnected from the internet
https://bugs.kde.org/show_bug.cgi?id=456403 Bug ID: 456403 Summary: Akonadi EWS module freezes PC when disconnected from the internet Product: Akonadi Version: 5.19.2 Platform: Fedora RPMs URL: https://bugzilla.redhat.com/show_bug.cgi?id=2104009 OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: EWS Resource Assignee: kdepim-bugs@kde.org Reporter: kitt...@gmail.com CC: kri...@op.pl Target Milestone: --- Description of problem: Sometimes, when PC is disconnected from the internet (WiFi firmware crash, network becomes out of reach, etc), akonadi's EWS component immediately start flooding system journal and making the system unresponsive. Version-Release number of selected component (if applicable): akonadictl 5.19.2 (21.12.2) How reproducible: Almost always Steps to Reproduce: 1. create an EWS account in KMail 2. connect to the internet 3. disconnect SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.18.6-100.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Additional info: See the attached log for a better insight. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 429220] KOrganizer uses time different than what's given
https://bugs.kde.org/show_bug.cgi?id=429220 David Chmelik changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|RESOLVED --- Comment #6 from David Chmelik --- I think fresh reinstall fixed this but something might cause it to reoccur, which I can't test because KOrganizer apparently can no longer use Google Calendar. -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 455369] Calendar event notifications lead to segfault if closed by notification button
https://bugs.kde.org/show_bug.cgi?id=455369 David Faure changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||akonadi-calendar/commit/266 ||94e8c82562eac2fdbdb6fa85f56 ||b27fca82a0 Status|ASSIGNED|RESOLVED --- Comment #4 from David Faure --- Git commit 26694e8c82562eac2fdbdb6fa85f56b27fca82a0 by David Faure. Committed on 30/06/2022 at 14:32. Pushed by dfaure into branch 'release/22.04'. Fix crash when clicking on dismiss, sometimes. client->dismiss(this) ends up setting client to nullptr, so the disconnect() warns about null receiver and doesn't actually disconnect. (This is similar to 24f3853f14ec in master) Related: bug 455472, bug 455886, bug 455258, bug 455583 M +1-1reminder-daemon/alarmnotification.cpp https://invent.kde.org/pim/akonadi-calendar/commit/26694e8c82562eac2fdbdb6fa85f56b27fca82a0 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 455583] kalendarc crashes when dismissing reminder notification
https://bugs.kde.org/show_bug.cgi?id=455583 David Faure changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||akonadi-calendar/commit/266 ||94e8c82562eac2fdbdb6fa85f56 ||b27fca82a0 Status|ASSIGNED|RESOLVED --- Comment #2 from David Faure --- Git commit 26694e8c82562eac2fdbdb6fa85f56b27fca82a0 by David Faure. Committed on 30/06/2022 at 14:32. Pushed by dfaure into branch 'release/22.04'. Fix crash when clicking on dismiss, sometimes. client->dismiss(this) ends up setting client to nullptr, so the disconnect() warns about null receiver and doesn't actually disconnect. (This is similar to 24f3853f14ec in master) Related: bug 455472, bug 455369, bug 455886, bug 455258 M +1-1reminder-daemon/alarmnotification.cpp https://invent.kde.org/pim/akonadi-calendar/commit/26694e8c82562eac2fdbdb6fa85f56b27fca82a0 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 455472] Reminders crashes on login
https://bugs.kde.org/show_bug.cgi?id=455472 David Faure changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||akonadi-calendar/commit/266 ||94e8c82562eac2fdbdb6fa85f56 ||b27fca82a0 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from David Faure --- Git commit 26694e8c82562eac2fdbdb6fa85f56b27fca82a0 by David Faure. Committed on 30/06/2022 at 14:32. Pushed by dfaure into branch 'release/22.04'. Fix crash when clicking on dismiss, sometimes. client->dismiss(this) ends up setting client to nullptr, so the disconnect() warns about null receiver and doesn't actually disconnect. (This is similar to 24f3853f14ec in master) Related: bug 455369, bug 455886, bug 455258, bug 455583 M +1-1reminder-daemon/alarmnotification.cpp https://invent.kde.org/pim/akonadi-calendar/commit/26694e8c82562eac2fdbdb6fa85f56b27fca82a0 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 455258] Reminders crashed while suspended
https://bugs.kde.org/show_bug.cgi?id=455258 David Faure changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||akonadi-calendar/commit/266 ||94e8c82562eac2fdbdb6fa85f56 ||b27fca82a0 --- Comment #2 from David Faure --- Git commit 26694e8c82562eac2fdbdb6fa85f56b27fca82a0 by David Faure. Committed on 30/06/2022 at 14:32. Pushed by dfaure into branch 'release/22.04'. Fix crash when clicking on dismiss, sometimes. client->dismiss(this) ends up setting client to nullptr, so the disconnect() warns about null receiver and doesn't actually disconnect. (This is similar to 24f3853f14ec in master) Related: bug 455472, bug 455369, bug 455886, bug 455583 M +1-1reminder-daemon/alarmnotification.cpp https://invent.kde.org/pim/akonadi-calendar/commit/26694e8c82562eac2fdbdb6fa85f56b27fca82a0 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453298] kalendarac: Notifications miss option to remind later with other time duration than 5 minutes
https://bugs.kde.org/show_bug.cgi?id=453298 David Faure changed: What|Removed |Added CC||fa...@kde.org --- Comment #2 from David Faure --- I added a "1 hour" option in master, but I agree that this is not yet optimal overall. https://invent.kde.org/pim/akonadi-calendar/-/merge_requests/26 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 455472] Reminders crashes on login
https://bugs.kde.org/show_bug.cgi?id=455472 David Faure changed: What|Removed |Added CC||fa...@kde.org --- Comment #2 from David Faure --- Should be fixed by https://invent.kde.org/pim/akonadi-calendar/-/merge_requests/28 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 455423] New: Forced to reboot on dbus error.
https://bugs.kde.org/show_bug.cgi?id=455423 Bug ID: 455423 Summary: Forced to reboot on dbus error. Product: kmail2 Version: 5.19.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- Created attachment 149815 --> https://bugs.kde.org/attachment.cgi?id=149815=edit Screenshot of error message. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Compose an email message 2. Choose "send" OBSERVED RESULT Message is moved to outbox folder, and hangs up there. Attempts to send using "send queued messages" always fail. The only way I know of to fix it is to reboot the system. When I do reboot, an error message is displayed: E-mail Sending Failed Failed to get D-Bus interface of mailfilteragent. This is an intermittent error. I suppose one in a thousand (0.1%) of the messages I send fail this way. A screenshot of the error message is attached. EXPECTED RESULT The KMail composer should be able to connect with mailfilteragent, and thence with my email provider via the internet. This happens about 99.9% of the time. And if there is an error with D-Bus, I should be able to see the notification without rebooting the whole system. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel version 5.15.41-gentoo (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Not a real big deal. But it happens often enough to be a nuisance. That's why I'm posting a bug report. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 454029] KOrganizer disappeared from system-tray options
https://bugs.kde.org/show_bug.cgi?id=454029 --- Comment #2 from David Chmelik --- korganizer-22.04.1-x86_64-1 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 429220] KOrganizer uses time different than what's given
https://bugs.kde.org/show_bug.cgi?id=429220 --- Comment #5 from David Chmelik --- korganizer-22.04.1-x86_64-1 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 454029] New: KOrganizer disappeared from system-tray options
https://bugs.kde.org/show_bug.cgi?id=454029 Bug ID: 454029 Summary: KOrganizer disappeared from system-tray options Product: korganizer Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY KOrganizer disappeared from system-tray options (which at same time had added a bunch of stuff I don't need or know what it is.) STEPS TO REPRODUCE 1. Set KOrganizer to show in system-tray (on older KDEP5.) 2. Upgrade KDE. 3. Look for KOrganizer in system-tray. OBSERVED RESULT Can't see/use KOrganizer to get organized. EXPECTED RESULT Have KOrganizer in system tray as reminder to get organized, and continue using it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64 15.1-current KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453343] New: KMail unable to send encrypted emails when using X.509 certificate and self encryption
https://bugs.kde.org/show_bug.cgi?id=453343 Bug ID: 453343 Summary: KMail unable to send encrypted emails when using X.509 certificate and self encryption Product: kmail2 Version: 5.19.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: kitt...@gmail.com Target Milestone: --- SUMMARY If self encryption is activated for sent messages, when selecting a X.509 certificate to encrypt emails Kmail refuses to proceed. STEPS TO REPRODUCE 1. Set an X.509 certificate to sign/encrypt in current identity 2. Create a new email to a recipient there exist a valid key for, and activate encryption 3. Click send OBSERVED RESULT KMail says "no valid encryption keys are found" to encrypt for myself, even though the key is set and works perfectly (tested in Kleopatra) EXPECTED RESULT It should of course work. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453342] New: KMail bad signature when using S/MIME
https://bugs.kde.org/show_bug.cgi?id=453342 Bug ID: 453342 Summary: KMail bad signature when using S/MIME Product: kmail2 Version: 5.19.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: kitt...@gmail.com Target Milestone: --- SUMMARY When sending a signed email in the S/MIME format, the email is marked to have "invalid signature" when read. If instead S/MIME opaque is selected, the signature is recognized valid by the sender account, invisible by others. STEPS TO REPRODUCE 1. Select S/MIME signing mode from settings 2. Set an X.509 certificate for signing 3. Send signed email OBSERVED RESULT When sending a signed email in the S/MIME format, the email is marked to have "invalid signature" when read. If instead S/MIME opaque is selected, the signature is recognized valid by the sender account, invisible by others. EXPECTED RESULT Of course signature should always be visible no matter the recipient, and valid no matter the signing format. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 452322] New: KaddressBook does not let me add Google account
https://bugs.kde.org/show_bug.cgi?id=452322 Bug ID: 452322 Summary: KaddressBook does not let me add Google account Product: kaddressbook Version: 5.19.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kitt...@gmail.com CC: to...@kde.org Target Milestone: --- SUMMARY Adding a google account from KaddressBook results in nothing. STEPS TO REPRODUCE 1. File → new → add address book 2. choose google 3. authenticate OBSERVED RESULT Nothing happens after closing the config dialog EXPECTED RESULT When it worked, google calendar and contacts were regularly updated and shown. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.15.17-200.fc35.x86_64 (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Issue also affects Korganizer. It feels like it started once I had configured a EWS account, but I don't know for sure. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 451029] New: Header colors wrong with dark breeze
https://bugs.kde.org/show_bug.cgi?id=451029 Bug ID: 451029 Summary: Header colors wrong with dark breeze Product: kmail2 Version: 5.19.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: usability Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: kitt...@gmail.com Target Milestone: --- SUMMARY kmail fails to render header characters correctly when using a dark theme. Even using the standard dark breeze, characters are black. STEPS TO REPRODUCE 1. select a dark system theme 2. open kmail OBSERVED RESULT email header is rendered incorrectly. EXPECTED RESULT Either include settings for header colors in kmail settings or make it adapt to dark themes as well SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.17 (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 448665] Blinking view
https://bugs.kde.org/show_bug.cgi?id=448665 David Redondo changed: What|Removed |Added CC||k...@david-redondo.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from David Redondo --- *** This bug has been marked as a duplicate of bug 436555 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 447210] New: KMail crashed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=447210 Bug ID: 447210 Summary: KMail crashed unexpectedly Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- Application: kmail (5.18.3 (21.08.3)) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.88.0 Operating System: Linux 5.10.76-gentoo-r1-x86_64 x86_64 Windowing System: X11 Distribution: Gentoo/Linux DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Not much. I had just moved a message to the "trash" folder when it died. I did just install version 21.8.3 a few weeks ago (Gentoo). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7fcd0cf27ef0 in QWidget::style() const () at /usr/lib64/libQt5Widgets.so.5 #5 0x7fcd0cf05014 in QApplication::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #6 0x7fcd0ceff63f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #7 0x7fcd0c5497d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #8 0x7fcd0c598afb in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #9 0x7fcd0c5993c4 in () at /usr/lib64/libQt5Core.so.5 #10 0x7fcd06451acb in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #11 0x7fcd06451d78 in () at /usr/lib64/libglib-2.0.so.0 #12 0x7fcd06451e2f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #13 0x7fcd0c5997b6 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #14 0x7fcd0c548263 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #15 0x7fcd0c550580 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #16 0x560e6b97c4d5 in () #17 0x7fcd0bf297fd in __libc_start_main () at /lib64/libc.so.6 #18 0x560e6b97c6da in () [Inferior 1 (process 17295) detached] Possible duplicates by query: bug 446679, bug 446675, bug 445967, bug 445525, bug 445028. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 446837] Add recursive option to "Hide this folder in the folder selection dialog"
https://bugs.kde.org/show_bug.cgi?id=446837 --- Comment #8 from David de Cos --- Hi Laurent, You're right, I didn't report it correctly. I've been testing it more thoroughly, and I think I have a clearer picture now. In order to reproduce it, you need to: 1) Find an empty folder. If you don't have one, create it. 2) Close KMail. 3) Open KMail and go straight to right click on the empty folder. The entry "Folder properties" isn't in the menu! 4) Right click on any other folder that isn't empty. "Folder properties" is there, as normal. 5) Go back to right click on the empty folder. "Folder properties" reappears. So it only happens right after starting KMail, and before clicking on any non-empty folder. That's exactly what I was doing when testing the folder plugin yesterday, so I interpreted it wrongly. One more thing: actually, the folder doesn't have to be empty. In reality, step number 1 should be "find a folder in which no message is selected". I actually don't know how to do that on purpose, but the fact is that I have some old folders in which I hadn't entered in a while, which do not have any message selected. So if I right click on those folders after starting KMail, the menu entry isn't there. Maybe you know how to unselect all messages in a folder, otherwise just use an empty one. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 446837] Add recursive option to "Hide this folder in the folder selection dialog"
https://bugs.kde.org/show_bug.cgi?id=446837 --- Comment #6 from David de Cos --- That's great, Laurent! Thank you very much for the fast response. I just noticed something curious, a very minor bug: 1) Use the plugin to mark some folders as hidden in the folder selection dialog. 2) Accept and close KMail right away, without clicking on any folder. 3) Restart KMail and right-click on one of the folders that you just configured via the plugin. 4) The "Folder Properties" option is not there. If you click on any other folder, the menu entry comes back again (so as I said, it's a very minor bug). Did you notice that too? If you want, I can create a new bug report for that. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 446837] Add recursive option to "Hide this folder in the folder selection dialog"
https://bugs.kde.org/show_bug.cgi?id=446837 --- Comment #2 from David de Cos --- Thank you very much for the info, Laurent. I didn't know this plugin, this should certainly speed the process. However, I don't think it's working well for me. I select a few folders at once -> Mark "Hide this folder in the folder selection dialog" -> Accept -> Restart KMail -> Check the properties of those folders (not via the plugin, but right click -> Folder properties), and the option is unmarked. I've done a few attempts, and sometimes only 1 of the folders has the option marked, but all the others don't. Can you please check if it works for you? Maybe I'm doing something wrong? Thanks a lot! -- You are receiving this mail because: You are the assignee for the bug.
