https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #24 from Flossy Cat <flossy-...@online.de> --- (In reply to Bernhard E. Reiter from comment #23) > … > It also maybe an option on OpenSuse to use one of the > https://en.opensuse.org/SDB:KDE_repositories > that is providing newer KDE Application revision to stable Opensuse Leap. That I did before reporting the bug – alas then the repositories failed on their internal requirements, perhaps a momentary glitch. But it provides applications only in version 23.08.04, and the patch probably will take some time to shine up, if I not have to wait to 23.08.05 … I will first have to catch up with my work delay caused by this nasty surprise before trying again or following David's suggestion … My workaround via KAlarm from 2024-02-09 (see https://bugs.kde.org/show_bug.cgi?id=481024#c13) works very well and actually brings several benefits and solves the problem of reminder storms you mentioned when switching machines. (Benefits: * (optional) list of recent reminders triggered – very valuable when you lose track on a stressy day * lookeahead of upcoming reminders – very valuable to e.g. shift them proactively if you need some undisturbed time or to preemptively do tasks if a meeting is cancelled * color-coding of reminders * command execution reminders * waking machine from suspend for reminders (not my cup of tea but maybe valuable for some) ) It is really great David restored the eliminated snoozing functionality – thanks – but KAlarm as general reminder handler is worth considering, IMHO. Looking at the further crippling of KDE (see e.g. https://bugs.kde.org/show_bug.cgi?id=481069) after a quarter of a century of choosing KDE I have to consider on which desktop and tool set I will bet for my old age, when I will not be able anymore to workaround, patch, juggle numerous repository and weather dependency messes … (I'm relatively relaxed concerning the desktop having a well-tuned XFCE as fall-back since KDE 4, but the use-breaking regression in KDE PIM hit my hard, unsuspected and with very bad timing …) I consider the change culture in KDE fundamentally broken: Since the KDE3/4 transition I regularly see breaking changes all over the place, "discussed" and "announced" in some very small circles with minimal reach into the end-users. (And IMHO the discussions show these persons do not have a sophisticated usage of the components they are crippling …) The end-users are then hit by nasty surprises a dozen month or more later which then leads to numerous complains, bug reports etc. which are handled quite lukewarm judging from the handling of the duplicate bugs I collected in my bug report. Only when I "threatened" to quickly draft up a working workaround to show the urgency, David took pity and kindly patched and restored the lost functionality. And the patch is – no offense meant, David! – a relatively minor one (still, of course, hours of work I appreciate!). All the while KDE is losing user base – many of the participants of the duplicated bug reports did not partake in this discussion, despite me inviting them in every duplicated report thread. I consider those potentially lost users … Any idea where this fundamental discussion about the change culture of KDE should be started? (bug reports is the wrong place, IMHO) -- You are receiving this mail because: You are watching all bug changes.
