SUMMARY The command line parameters of »kalarm« invocations are not correctly transferred into the edit window (and the alarm itself if the edit window is skipped). STEPS TO REPRODUCE 1. call »kalarm --edit-new-display -n "Name" "Message"« 2. call »kalarm -n "Name" "Message"« OBSERVED RESULT The "Name" is put into the message text field, the name field remains empty and the "Message" is dropped completely. EXPECTED RESULT "Name" should show in the name field, "Message" in the message field. SOFTWARE/OS VERSIONS [copied from System Information] Operating System: openSUSE Leap 15.5 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.14.21-150500.55.44-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-10210U CPU @ 1.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics
I forgot to mention: as a seasoned computer engineer I might help with changes if brought up to speed …
Now fixed for KAlarm version 3.6.4 in KDE Gear 23.08.5 (commit a05422923b625f9cf5f1d6f167e6a6d0b3e60b7f) and KAlarm version 3.7.0 in KDE Gear 24.02 (commit f3dd19a8e2b900a36ca2433e59f6ae9c93ae42da). Thanks for reporting this. There was a slip-up when originally implementing the --name option.
(In reply to David Jarvie from comment #2) > Now fixed for KAlarm version 3.6.4 in KDE Gear 23.08.5 (commit > a05422923b625f9cf5f1d6f167e6a6d0b3e60b7f) and KAlarm version 3.7.0 in KDE > Gear 24.02 (commit f3dd19a8e2b900a36ca2433e59f6ae9c93ae42da). Thank you very much for your quick solution. Would it be possible to apply the fix also to the reported version 3.5.4.2 in KDE Gear 22.12.3? Because that is the version available in OpenSuSE 15.5 without non-standard repositories. Even when resorting to https://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_15.5/ I only get 23.08.4 – thus missing out on your fix. (Worse: at the moment this repository seems not to be consistent within itself and produces a wealth of dependency problems within the KDE components … :( > Thanks for reporting this. There was a slip-up when originally implementing > the --name option. Be my guest – thank you for fixing so fast!
Versions already released by KDE cannot be modified other than by patching the source and rebuilding yourself (or by persuading OpenSUSE to issue a patched version, which I assume they are unlikely to do). If you can't patch and build yourself, you'll have to wait for KDE Gear release 23.08.5 (based on Qt5, due on 15 February) or 24.02 (based on Qt6, due on 28 February), although I don't know when or if OpenSUSE will issue these releases.
(In reply to David Jarvie from comment #4) > Versions already released by KDE cannot be modified other than by patching > the source and rebuilding yourself (or by persuading OpenSUSE to issue a > patched version, which I assume they are unlikely to do). As OpenSuSE is not only providing regularly security update but also bug fixes to all components in the release repository it would be worth a try. (The reason I use this distro as productive base …) I expect to see an automatic update suggested by SW monitoring, if you kindly apply the fix to version 3.5.4.2 in KDE Gear 22.12.3 (if possible at all). It would be an interesting experiment and I would report back. > If you can't patch and build yourself, I could, but it is quite an effort and leaves my productive systems in a non-automatic patch state (at least partially) – last resort, IMHO. > you'll have to wait for KDE Gear release 23.08.5 < (based > on Qt5, due on 15 February) or 24.02 (based on Qt6, due on 28 February), > although I don't know when or if OpenSUSE will issue these releases. I'll wait – perhaps the dependency mess in the KDE 23.08.4 is an indicator of this upcoming change … Thank you for quickly providing the fix.
The KDE 22.12 branch was effectively closed when 23.04 was created, so I wouldn't be willing to apply the fix to it. I'm afraid the options are to apply a patch to the OpenSUSE repository or to wait for 23.08.5.
(In reply to David Jarvie from comment #6) > The KDE 22.12 branch was effectively closed when 23.04 was created, so I > wouldn't be willing to apply the fix to it. When it is closed it is closed … > I'm afraid the options are to > apply a patch to the OpenSUSE repository or to wait for 23.08.5. For this specific bug fix I can wait. (I'm just wondering from which source OpenSUSE is pulling all the bug fixes I regularly receive alongside the security patches …) Thank you, again.