[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 Bernhard E. Reiter changed: What|Removed |Added CC||bernh...@intevation.de -- 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.
[Akonadi] [Bug 480770] Regression: EWS Server might require HTTP 1.1
https://bugs.kde.org/show_bug.cgi?id=480770 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #6 from Antonio Rojas --- Thanks, this fixes the resource not working at all for me since beta2. I still get disconnected after a couple of hours and need to relogin constantly, any ideas? https://bugs.kde.org/show_bug.cgi?id=478033 -- 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 #8 from Flossy Cat --- (In reply to David Faure from comment #4) > 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 know – but this only demonstrates the choice to move to "freedesktop.org notifications" as sole solution was ill-advided. > I agree however this is really suboptimal, especially when not caring for > other desktop environments. "really suboptimal" is runner-up for the euphemism of the week … IMHO it is a fundamental lack of respect and rude to long-term KDE users to fundamentally break existing functionality (and their workflows) without proper announcement and transition provisions. The fatal decision happened around 2 years ago, complaints exist since more than 18 month – without solution. I was confronted with this breaking changes when non-suspecting upgrading my distribution – and the heart-ripping decision to give up a quarter of a century KDE PIM usage, if I do not find a working workaround within 2–3 weeks. (And that is not the first incident of this time – but so far definitely the worst and potentially final one.) IMHO the proper way would have been to keep the old behavior as an option and wait for the reaction for at least 2 years before cutting of the old functionality. > As for "workarounds", you can find the code in > akonadi-calendar/reminder-daemon/alarmnotification.cpp line 135 and add more > buttons like "remind tomorrow". The number of buttons is limited and cannot provide for my variable needs, lest the needs of the numerous others having raised similar complaints. This is *not a viable workaround*. Are there any D-Bus-events I could hook on? > Maybe we should implement an alternative notification solution in kalendarac > that looks more like the old korgac dialog (minus its bugs...). Definitely. And very soon. Actually you should never have removed the original functionality without a substitute or a transition strategy as lined out above. -- 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 #7 from Flossy Cat --- Comment on attachment 165676 --> https://bugs.kde.org/attachment.cgi?id=165676 Screenshot of a notifier popup This screenshots serves as comparison to the information actually provided via the "execute command" hook – see comment #5 -- 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 #6 from Flossy Cat --- Created attachment 165676 --> https://bugs.kde.org/attachment.cgi?id=165676&action=edit Screenshot of a notifier popup This screenshot of a notifier popup serves for comparison with the information provided to "execute command" hooks in comment #5 -- 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 #5 from Flossy Cat --- VIA KNOTIFIER (In reply to Flossy Cat from comment #2) > Possible Workaround: »kalarm« > == > … > The burning question remains, how to call »kalarm« or create »kalarm« > reminders from »korganizer« reminder events. The notification demon (at least »knotifier«) allows (still – see below) to trigger a command with a notification. To usefully trigger a »kalarm« workaround we'd need sufficient information to construct a new reminder. I tested for * arguments – the command triggered receives no data via arguments added to the call * enviroment – the command triggered receives no data via environment variables * STDIN – the command triggered receives no data via its STDIN file descriptor Finally I tested for %-escaped variables and found the following: (https://invent.kde.org/frameworks/knotifications/-/blob/kf5/src/notifybyexecute.cpp?ref_type=heads) %e – Event ID %a – Application Name %s – text of the notification %w – WinID %t – window title %i – notification ID %d – Application display name For the event in the attached screenshot this yields EventID(%e)=»alarm« AppName(%a)=»kalendarac« Text(%t)=»Aufgabe hat um 16:32 begonnen« NotificationID(%i)=»10« DisplayName(%d)=»Erinnerungen« WindowTitle(%t)=»%t« – obviously this variable is not expanded? WinID(%w)=»0« – effectively no windowID returned As can be seen from the screenshot – essential information is not provided. :-( There is much room for improvement to make the option of programmatic notifications useful – if you share this sentiment you might care to comment on https://bugs.kde.org/show_bug.cgi?id=481068 Further, judging from the code, the option of executing commands as part of a notification will be removed in KF6: »notifybyexecute« is missing in https://invent.kde.org/frameworks/knotifications/-/tree/master/src?ref_type=heads I strongly object to this further usability-degradation – you might want to join that cause: https://bugs.kde.org/show_bug.cgi?id=481069 Further I tested the option to write notification data to a file (which could of course be a suitably hooked-up socket): This just yields »- KNotify Mi. Feb. 7 16:54:01 2024: Aufgabe hat um 16:32 begonnen« for the event above – again not useful as essential information is missing and even less useful than the %-escapes! Because of this short-comings this approach is alas not viable (as isn't "via »korganizer«") … -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 481063] A reminder option to run a command would enable valuable use-cases
https://bugs.kde.org/show_bug.cgi?id=481063 --- Comment #1 from Flossy Cat --- I forgot to mention: as a seasoned computer engineer I might help with changes if brought up to speed … -- 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.
[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 #3 from Flossy Cat --- VIA KORGANIZER (In reply to Flossy Cat from comment #2) > Possible Workaround: »kalarm« > == > … > The burning question remains, how to call »kalarm« or create »kalarm« > reminders from »korganizer« reminder events. AFAIR there once was an option within »korganizer« – even if not I see valuable use-cases besides this workaround topic. You might care to support and comment on the feature request: https://bugs.kde.org/show_bug.cgi?id=481063 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 481063] New: A reminder option to run a command would enable valuable use-cases
https://bugs.kde.org/show_bug.cgi?id=481063 Bug ID: 481063 Summary: A reminder option to run a command would enable valuable use-cases Classification: Applications Product: korganizer Version: 5.22.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: incidence editors Assignee: kdepim-bugs@kde.org Reporter: flossy-...@online.de Target Milestone: --- SUMMARY A few examples of IMHO valuable use-cases: * start a video-conferencing client a few minutes before a meeting * start more complex set-ups like a VPN and a collaboration platform before a meeting * change the desktop activity suiting to the event or todo at hand I consider the availability of such "user exits" to implement new and sophisticated functionality (especially as a proof of new concept) generally as an important advantage of the unixoid eco-system and characteristic for a sophisticated usage of computers. SECURITY CONSIDERATIONS Obviously when importing calendar or todo events from any source, "run command" reminders MUST be ignored. (As RFC 5545 does not provide for this kind of reminders the risk is theoretical anyhow.) -- 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 Flossy Cat changed: What|Removed |Added CC||flossy-...@online.de --- Comment #3 from Flossy Cat --- I experienced the same issue when upgrading within my distribution. As neither here nor in the many duplicates I see any progress to a solution, I've set up a discussion about possible workarounds to which I invite anybody interested: https://bugs.kde.org/show_bug.cgi?id=481024#c1 -- 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 #3 from Flossy Cat --- (In reply to geekiehiway from comment #0) I experienced the same issue when upgrading within my distribution. As neither here nor in the many duplicates I see any progress to a solution, I've set up a discussion about possible workarounds to which I invite anybody interested: https://bugs.kde.org/show_bug.cgi?id=481024#c1 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453299] kalendarac: Notifications miss option to edit event directly
https://bugs.kde.org/show_bug.cgi?id=453299 Flossy Cat changed: What|Removed |Added CC||flossy-...@online.de --- Comment #5 from Flossy Cat --- (In reply to Till Schäfer from comment #0) I experienced the same issue when upgrading within my distribution. As neither here nor in the many duplicates I see any progress to a solution, I've set up a discussion about possible workarounds to which I invite anybody interested: https://bugs.kde.org/show_bug.cgi?id=481024#c1 -- 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 Flossy Cat changed: What|Removed |Added CC||flossy-...@online.de --- Comment #7 from Flossy Cat --- (In reply to Till Schäfer from comment #0) I experienced the same issue when upgrading within my distribution. As neither here nor in the many duplicates I see any progress to a solution, I've set up a discussion about possible workarounds to which I invite anybody interested: https://bugs.kde.org/show_bug.cgi?id=481024#c1 -- 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 Flossy Cat changed: What|Removed |Added CC||flossy-...@online.de --- Comment #26 from Flossy Cat --- (In reply to Bernhard E. Reiter from comment #0) I experienced the same issue when upgrading within my distribution. As neither here nor in the many duplicates I see any progress to a solution, I've set up a discussion about possible workarounds to which I invite anybody interested: https://bugs.kde.org/show_bug.cgi?id=481024#c1 -- 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 Flossy Cat changed: What|Removed |Added CC||flossy-...@online.de --- Comment #2 from Flossy Cat --- I experienced the same issue when upgrading within my distribution. As neither here nor in the many duplicates I see any progress to a solution, I've set up a discussion about possible workarounds to which I invite anybody interested: https://bugs.kde.org/show_bug.cgi?id=481024#c1 -- 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 #2 from Flossy Cat --- Possible Workaround: »kalarm« == »kalarm« provides all the necessary functionality to set and postpone alarms (and even some useful additional functionality). The burning question remains, how to call »kalarm« or create »kalarm« reminders from »korganizer« reminder events. Usage of »kalarm« is quite simple – 3 useful variants exist (a matter of personal preference): »kalarm -b --edit-new-display -n "Test kalarm" -t 14:50 "Test notification via kalarm"« Opens a window to edit the alarm and change various details, the time, etc. »kalarm -b -n "Test kalarm" -t 14:50 "Test notification via kalarm"« This will immediately set and trigger an alarm at the given time (which has to be slightly in the future). The alarm is presented in a separate window, providing a button, opening a window for flexible snooze options. »kalarm -N -b -n "Test kalarm" -t 14:50 "Test notification via kalarm"« This will immediately set and trigger an alarm as above, but because of »-N« the alarm is presented as notification, providing a button, opening a window for flexible snooze options. (»-N« can be used in the »--edit-new-display« too, to preselect notification as method). (In all variants there is a annoying bug in handling the parameters: https://bugs.kde.org/show_bug.cgi?id=481053) -- 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 #1 from Flossy Cat --- SEARCH FOR A WORKAROUND Within this comment thread I suggest to collect the discussion about workarounds. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 480543] Akonadis sqlite backend does not honor sql limits
https://bugs.kde.org/show_bug.cgi?id=480543 --- Comment #4 from Carl Schwan --- Git commit c5a3d64c8a1a643277f35c19e2a43b40186e1efa by Carl Schwan. Committed on 08/02/2024 at 12:18. Pushed by carlschwan into branch 'master'. Ensure query size in search manager remains less than 1000 With sqlite we have a limit on how many parameters we can add to a IN query. M +23 -6src/server/search/searchmanager.cpp https://invent.kde.org/pim/akonadi/-/commit/c5a3d64c8a1a643277f35c19e2a43b40186e1efa -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 480543] Akonadis sqlite backend does not honor sql limits
https://bugs.kde.org/show_bug.cgi?id=480543 --- Comment #3 from Carl Schwan --- Git commit b403d43764b4482e4c63f32a72b319e68d164bf9 by Carl Schwan. Committed on 08/02/2024 at 12:25. Pushed by carlschwan into branch 'release/24.02'. Ensure query size in search manager remains less than 1000 With sqlite we have a limit on how many parameters we can add to a IN query. (cherry picked from commit c5a3d64c8a1a643277f35c19e2a43b40186e1efa) M +23 -6src/server/search/searchmanager.cpp https://invent.kde.org/pim/akonadi/-/commit/b403d43764b4482e4c63f32a72b319e68d164bf9 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 480543] Akonadis sqlite backend does not honor sql limits
https://bugs.kde.org/show_bug.cgi?id=480543 --- Comment #2 from Carl Schwan --- Another bug fixes just got merged for this https://invent.kde.org/pim/akonadi/-/merge_requests/182 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 480543] Akonadis sqlite backend does not honor sql limits
https://bugs.kde.org/show_bug.cgi?id=480543 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
