26th December 2016, 4:42
(19th December 2016, 2:48)kdemeoz Wrote: This surprises me. I use it all the time; it's great, & seems to work as well for me in Maui as it did in Mint 17.3 KDE4.
Hmmm, well, my previous post certainly does not tell the full story. It IS entirely accurate for my Tower, whose kalarm really does continue to work as well in Maui as it used to do in Mint KDE4. However, as per several older posts of mine elsewhere in these fora, my Tower's Maui was NOT a clean installation; whilst / was formatted & Maui installed therein, my separate encrypted /home partition was deliberately NOT formatted, ie, Tower's Maui's /home now has a mixture of Maui user config files, but also legacy Mint 17.3 KDE4 user config files. I now suspect that the latter is the only reason that Tower's kalarm still works for me in Maui.
Conversely, over recent weeks i have been rebuilding my Lappy [also used to have Mint 17.3 KDE4]. As per another thread i [briefly] dabbled with it as dual-boot Mint 18 Xfce + Maui, but in the past couple of days i gave up on that & began again; it is now completely Maui 2.1, & was a clean installation -- it has no remnants of anything from Mint KDE4. Sadly, in this build, whilst i was still able to install kalarm, it is simply unusable. I cannot create any alarms. Each time i do, a frustrating dialog pops up; "Sorry - KAlarm. You must select a calendar to save the alarm in". I've not found a way to solve this.
This is so disappointing, not only for my Lappy, but because i am now very close to deciding to rebuild my Tower again with this time a completely clean installation of Maui [to hopefully eliminate a number of weird unpleasant Maui behaviour faults that no other users here seem to have, & which i thus suspect might be caused by some legacy KDE4 files] -- I like kalarm a lot & use it a lot, so knowing that if i do rebuild Tower i will lose kalarm there too just like Lappy, is a bit upsetting.