[korganizer] [Bug 336490] new journal is not created due to lack of the calendar, although events and to-do's are ok and calendar (google) exist
https://bugs.kde.org/show_bug.cgi?id=336490 gjditchfi...@acm.org changed: What|Removed |Added Severity|critical|wishlist CC||gjditchfi...@acm.org --- Comment #11 from gjditchfi...@acm.org --- Currently KDE's Google API library does not support journal entries. It also seems that many DAV servers do not support VJOURNAL objects. For now I can only suggest storing them, in a local ics file. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452306] Day picker in KOrganizer's edit event dialog does not respect "weekly start day" option
https://bugs.kde.org/show_bug.cgi?id=452306 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Severity|normal |wishlist --- Comment #4 from gjditchfi...@acm.org --- The week number is a different can of worms: it is the ISO week number, https://en.wikipedia.org/wiki/Week#The_ISO_week_date_system and by definition those weeks start on Monday. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452306] Day picker in KOrganizer's edit event dialog does not respect "weekly start day" option
https://bugs.kde.org/show_bug.cgi?id=452306
Tusooa Zhu changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #3 from Tusooa Zhu ---
In other words, the behaviour in the agenda view (agrees with KOrganizer
configuration) and the day picker ("agrees with LC_TIME") should be consistent
with each other.
Specially, the "week number" in the day picker is not consistent with the
layout itself. If I pick Apr 10, 2022 (Sunday), it shows Week 14; if I pick Apr
11, 2022 (the following Monday), it shows Week 15! But the two days are on the
same row. This is totally unexpected from a user's point of view.
As I provided the information requested, I changed the status back to REPORTED.
--
You are receiving this mail because:
You are the assignee for the bug.
[korganizer] [Bug 452306] Day picker in KOrganizer's edit event dialog does not respect "weekly start day" option
https://bugs.kde.org/show_bug.cgi?id=452306 --- Comment #2 from Tusooa Zhu --- (In reply to gjditchfield from comment #1) > The week's starting day seems to be controlled by the user's locale. > When I switch between Canadian English and français (France), > KOrganizer switches between Sunday and Monday. > The setting is shared by all KDE apps. It is set in System Settings, > Regional Settings > Formats > Time. > What locale are you using? > > (Another way to check is to run "locale LC_TIME -k" in a terminal. > "first_weekday=2" in the output means the first weekday is Monday.) I am on `LC_TIME="en_CA.UTF-8"`. However, as this is KOrganizer, and KOrganizer has its own setting entry for "start day of week," I as a user expect it should be used instead. In addition, I am not willing to change my current date format just to get the expected "start day of week" behaviour. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452306] Day picker in KOrganizer's edit event dialog does not respect "weekly start day" option
https://bugs.kde.org/show_bug.cgi?id=452306 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||gjditchfi...@acm.org Resolution|--- |WAITINGFORINFO --- Comment #1 from gjditchfi...@acm.org --- The week's starting day seems to be controlled by the user's locale. When I switch between Canadian English and français (France), KOrganizer switches between Sunday and Monday. The setting is shared by all KDE apps. It is set in System Settings, Regional Settings > Formats > Time. What locale are you using? (Another way to check is to run "locale LC_TIME -k" in a terminal. "first_weekday=2" in the output means the first weekday is Monday.) -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452306] New: Day picker in KOrganizer's edit event dialog does not respect "weekly start day" option
https://bugs.kde.org/show_bug.cgi?id=452306 Bug ID: 452306 Summary: Day picker in KOrganizer's edit event dialog does not respect "weekly start day" option Product: korganizer Version: 5.19.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: incidence editors Assignee: kdepim-bugs@kde.org Reporter: tus...@kazv.moe Target Milestone: --- 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 *** Weekly start day in KOrganizer is set to Monday. Day picker still show a calendar with weeks starting at Sunday. STEPS TO REPRODUCE 1. Settings -> Time and Date -> Weekly start day: Monday (this has always been my setting.) 2. In agenda view, add an event. 3. Trigger the day picker by clicking the text box after "Start" or "End" OBSERVED RESULT The pop-up calendar should have Monday at the beginning of each row. EXPECTED RESULT The pop-up calendar has Sunday at the beginning of each row. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.16.12-gentoo-x86_64 / 5.24.4 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [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 Volker Krause changed: What|Removed |Added CC||vkra...@kde.org --- Comment #1 from Volker Krause --- In which desktop shell are you running this? In Plasma here the notification body contains the event start time, the icon in the notification is interactive, and the notification panel allows group dismissal. https://invent.kde.org/pim/akonadi-calendar/-/merge_requests/15 has a proposal for making past reminders easier to distinguish. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 452296] New: Email won't be encrypted automatically
https://bugs.kde.org/show_bug.cgi?id=452296 Bug ID: 452296 Summary: Email won't be encrypted automatically Product: kmail2 Version: 5.19.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: christoph.klas...@intevation.de Target Milestone: --- SUMMARY In the settings I enabled automatic encryption but encryption isn't activated when I write a new email. STEPS TO REPRODUCE 1. Open settings for account and go to "Cryptography" 2. Enable the option "Automatically encrypt messages when possible". 3. Close the settings and click on "New" to write an email. OBSERVED RESULT The button "Encrypt" isn't activated. EXPECTED RESULT I would expect that the button "Encrypt" would be activated. SOFTWARE VERSIONS KDE neon 5.24 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 452295] New: Possibility to retrieve key where signature is
https://bugs.kde.org/show_bug.cgi?id=452295 Bug ID: 452295 Summary: Possibility to retrieve key where signature is Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: christoph.klas...@intevation.de Target Milestone: --- Created attachment 147981 --> https://bugs.kde.org/attachment.cgi?id=147981=edit Signature in KMail To increase the usability of KMail it would be positive if there would be a possibility to retrieve a missing key right in the area where the information of the signature is shown. Otherwise users have to open the terminal and search for a key there but that's an uncomfortable way of retrieving a key for "normal" users. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 452285] New: Cannot disable or enable plugin conponents, such as KJots or Zanshin, anymore
https://bugs.kde.org/show_bug.cgi?id=452285 Bug ID: 452285 Summary: Cannot disable or enable plugin conponents, such as KJots or Zanshin, anymore Product: kontact Version: 5.19.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- In previous versions of Kontact, I was able to disable and enable components (e.g., KJots, Calendar, Zanshin) by enableing or disabling a checkbox in front of the component in the settings window. Now I cannot find any such option anymore, which is a problem in two ways: 1. I cannot re-enable previously disabled views 2. The components sidebar is cluttered with irrelevant components and this sidebar is different on different computers regarding the components installed there. For example, if Zanshin is not installed the component is not show. This also changes short cut assignments, since Ctrl+Number is associated with the ordered view in that sidebar. This in turn makes them hard to use when working in different environments. Current workaround is to enable/disable plugins manually via kontactrc (see my example below). Thus, I would like to see an option again to enable / disable components. [Plugins] kontact_akregatorpluginEnabled=false kontact_journalpluginEnabled=false kontact_kaddressbookpluginEnabled=true kontact_kjotspluginEnabled=false kontact_kmailpluginEnabled=true kontact_knodepluginEnabled=false kontact_knotespluginEnabled=false kontact_korganizerpluginEnabled=true kontact_ktimetrackerpluginEnabled=true kontact_plannerpluginEnabled=true kontact_specialdatespluginEnabled=true kontact_summarypluginEnabled=false kontact_todopluginEnabled=true kontact_zanshinpluginEnabled=false Operating System: Gentoo Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.26-gentoo (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are the assignee for the bug.
