Description of problem: Version-Release number of selected component (if applicable): kalarm-19.04.0-1.mga7.src.rpm How reproducible: Steps to Reproduce: 1. On currently-displayed alarm list, do Select All and delete whole list. 2. Select 'Import Alarms', and point to kalarm-export.ics file containing up-to-ate set of alarms. 3. Instead of pouring into the now-empty list display the list of entries in that .ics file (as it does on Mageia7), the display stays empty! N.B. The new contents are needed when preparing laptop for trip away from base, so that the 'current' system's alarms are processed, chronologically. P.S. The name Kalarm is somewhat misleading in my opinion, as 'alarm' suggests a problem is being reported, whereas in my usage it might better have been called 'Remind', as it does offer all the options needed (e.g. daily, weekly, monthly, quarterly, annual).
Source RPM: kalarm-19.04.0-1.mga7.src.rpm => kalarm-20.08.3-1.mga8.src.rpm
Hi, thanks report8kg this. What version does affect you?
CC: (none) => ouaurelien
Hi, thanks reporting this. What version does affect you?
Problem is in M7 or in M8 Cauldron?
(In reply to Aurelien Oudelet from comment #3) > Problem is in M7 or in M8 Cauldron? Already corrected: M8. Apologies...
(In reply to Maurice Batey from comment #4) > (In reply to Aurelien Oudelet from comment #3) > > Problem is in M7 or in M8 Cauldron? > > Already corrected: M8. Apologies... If latest version does not function as it must act, this should be reported upstream. Please report at bugs.kde.org and copy/past here the opened ticket.
Keywords: (none) => UPSTREAM
On 09/12/2020 13:02, Aurelien wrote: > Please report at bugs.kde.org and copy/past here the opened ticket. There I'm puzzled to see: "Bug 27788 - Run command confused by spaces in filenames (edit)" Uh? Doesn't seem logical... Unclear how to proceed wth your request there!
(In reply to Maurice Batey from comment #6) > On 09/12/2020 13:02, Aurelien wrote: > > > Please report at bugs.kde.org and copy/past here the opened ticket. > > There I'm puzzled to see: > > "Bug 27788 - Run command confused by spaces in filenames (edit)" > > Uh? > > Doesn't seem logical... > > Unclear how to proceed wth your request there! Two different things. KDE Bugzilla system has same features as our at Mageia. In facts I wanted you to report this bug upstream, because you are affected by a dysfunction, because you want a functionality that you rely upon. But, I will do it for you. Can you provide me "kalarm-export.ics" by attaching this here in a zip file?
Well I was all set to do it, but I was flummoxed by seeing the same bug report number there for a different subject. Is that typical? Do I just ignore that duplication and continue? Also, you suggest I should append the "kalarm-export.ics" file, but that contains personal information not for public view, so I shall have to make an artificial equivalent. Will do that tomorrow, as am on tight schedule at the moment.
(In reply to Maurice Batey from comment #8) > Well I was all set to do it, but I was flummoxed by seeing the same bug > report number there for a different subject. Is that typical? In KDE Bugzilla (bugs.kde.org), Bug 27788 is for an other issue. You don't have to use same number as us. > Do I just ignore that duplication and continue? > > Also, you suggest I should append the "kalarm-export.ics" file, but that > contains personal information not for public view, so I shall have to make > an artificial equivalent. Will do that tomorrow, as am on tight schedule at > the moment. I would prefer an untouched at minimum "kalarm-export.ics" file as if there is an issue in it, we will catch it. Feel free to remove personal datas and at least write there some basic one. "A la limite", send me this file in a .tgz file archive and I will check it.
@Maurice Is this a question of exporting alarms from say M7 to import into M8? Or within the same release? I can try the latter anyway, and can try both releases if it is easy & necessary. Do you know that it worked in Mageia 7? Are you using Plasma? (Yawn)
CC: (none) => lewyssmith
(In reply to Lewis Smith from comment #10) > @Maurice > Is this a question of exporting alarms from say M7 to import into M8? Or > within the same release? M7-->M8 > I can try the latter anyway, and can try both > releases if it is easy & necessary. > Do you know that it worked in Mageia 7? As I said earlier, Import Alarms worked perfectly under M7, but is a NO-OP under M8. > Are you using Plasma? (Yawn) Yes.
(In reply to Aurelien Oudelet from comment #9) > I would prefer an untouched at minimum "kalarm-export.ics" file as if there > is an issue in it, we will catch it. Feel free to remove personal datas and > at least write there some basic one. > "A la limite", send me this file in a .tgz file archive and I will check it. No problem; just need to change some text in some of the DESCRIPTION tags. N.B. Nearly 100 alarms in the file.
(In reply to Maurice Batey from comment #12) > (In reply to Aurelien Oudelet from comment #9) > > "A la limite", send me this file in a .tgz file archive and I will check it. Using gzip, have now got 'adjusted' kmail-export.ics.gz, and have send it to your gmail address. (If prefer .tgz rather than .gz do let me know...)
@Maurice, I do checked your kalarm-export.ics file and successfully imported into KAlarm 20.08.3. File => Import Alarms This opened more that 98 windows in which there is a comment and date to check if they are correct. This can be confusing when you don't expect such behaviour. No errors in system journal. kalarm-export.ics comes from KAlarm 2.12.2 (Plasma Applications 19.04) Successfully imported in KAlarm 3.0.3 (Plasma Applications 20.08.3). So, I wonder where is the problem...
Keywords: UPSTREAM => (none)
(In reply to Aurelien Oudelet from comment #14) > @Maurice, > > I do checked your kalarm-export.ics file and successfully imported into > KAlarm 20.08.3. > > File => Import Alarms > > This opened more that 98 windows in which there is a comment and date to > check if they are correct. This can be confusing when you don't expect such > behaviour. That is not what happens on M7, and is worse than useless! > So, I wonder where is the problem... The problem remains that the following does NOT happen on M8: The crucial updating of the current alarm list that happened on M7 and all earlier versions was obtained as follows: 1. On currently-displayed alarm list, do Select All and delete whole list. 2. Select 'Import Alarms', and point to kalarm-export.ics file containing up-to-ate set of alarms (e.g. exported from PC). 3. The up-to-date alarm list pours into the now-empty list. Bingo! Kalarm now shows up-to-date alarm list cloned from PC. That is not happening on M8.
Perhaps there is some misunderstanding about "The crucial updating of the current alarm list that happened on M7 and all earlier versions". If we are talking release 'upgrade', I would hope that it left current alarms alone. Well, I have just done a test as follows, which worked throughout: On Mageia 7, Plasma, I created 4 different immediate alarms, which all worked. I re-created the same again a bit in the future, and exported them to a mounted partition. Re-booted into Mageia 8 (but forgot about Plasma, am in Xfce), and, with the Kalarm list starting empty (I never use it), imported the test alarms file with no problem; and no dialogue. They all showed, and subsequently worked. Must I do all this again remembering Plasma when logging into M8? I wonder whether there is anything special about the filename 'kmail-export.ics', or whether that was arbitrary. I used something different.
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
(In reply to Lewis Smith from comment #16) > ... with the Kalarm list starting empty (I never use it), > imported the test alarms file with no problem; and no dialogue. They all > showed, and subsequently worked. Good, but that's not the sequence I described! Copied/pastied from earlier: (What has been successful for many versions of Mageia, incl M7:) 1. On currently-displayed alarm list, do Select All and delete whole list. 2. Select 'Import Alarms', and point to kalarm-export.ics file containing up-to-ate set of alarms (e.g. exported from PC). 3. The up-to-date alarm list pours into the now-empty list. Bingo! Kalarm now shows up-to-date alarm list cloned from PC. That is not happening on M8. > I wonder whether there is anything special about the filename > 'kmail-export.ics', or whether that was arbitrary. I used something > different. I suspect you can use any variation of "kmail-export".ics
> that's not the sequence I described! I beg your pardon, but I followed it closely. Exporting the alarms file from M7 then importing it into M8 was doing it between different machines. Spot the differences: - different filename (you agree that should not matter) - the list I imported into was already empty, not deleted to be empty - For the import bit, I was not in Plasma. Aurélien in comment 14 tested your actual data (with a pop-up per alarm). Look, you are having trouble with a particular Kalarms file. Please attach that file to this bug - the same one you sent to A ? *Make sure that the variant you attach exhibits your problem*. Be explicit about its provenance: Magea 7 Kalarm x.y.z and the precise step-by-step you used to create it (in case there is more than one way to do so). Under M7/Plasma : I will import it into Kalarm, export it from there to a new file 'kalarm-export.ics'; for curiosity, clear all the Kalarms, and try importing the new file. Under M8/Plasma : create a few alarms in Kalarm, delete them all, and try importing the file into it. Does *that* satisfy you for exactness? Have you probed around your problem, for example tried a simpler equivalent test like mine in comment 16 to explore whether it is tied to your explicit file, or more generally re-producable? Also, what happens if you import the list into M8/Kalarm without first deleting the existing alarms.
(In reply to Lewis Smith from comment #18) > > that's not the sequence I described! > I beg your pardon, but I followed it closely. > - the list I imported into was already empty, not deleted to be empty But that's different from what I did, which was - by necessity - to remove an existing list, then Import an up-to-date copy to replace it. That always worked on all previous versions of Mageia. So the $64 question is: What has been changed in Kalarm -->M8? (And why) > Look, you are having trouble with a particular Kalarms file. Please attach > that file to this bug - the same one you sent to A ? Will do (I had assumed A had done that). > Also, what happens if you import the list into M8/Kalarm without first > deleting the existing alarms? Done that on M7; it APPENDS the new version to the existing one, which is why the earlier copy has to be deleted first. But I shall try it on M8. By the way, Lewis, have you been using Kalarm for long? Regards, Maurice
Created attachment 12069 [details] Sample kalarm-export-ics file Sample list of nearly 100 kalarms
Thank you for the attachment; proceeding with. Part 1/2 : export alarms list from Mageia 7/Plasma, kalarm-19.04.0-1.mga7 To have a list to export, I started by importing the attached one (whose name I had changed). It gave rise to a lot of pop-ups because the alarm time had passed, so it did them. This is OK, and explains comment 14. I clicked them all away. There were a few 'unable to delete...' complaints. Then I selected the whole lot, File-Export Selected Alarms to: kalarm-export.ics in shareable filestore. Back soon.
Part 2/2 : Import the exported alarms into Mageia 8/Plasma kalarm-20.08.3-1.mga8 with some alarms previously in the list, then deleted. Start by saying (should be in the previous comment) that the file as provided, after unzipping, was not the same size as that from re-creating it by exportation from M7; MB is the given one, the other as M7 Kalarm exported the same list: 57417 Rha 12 19:35 kalarm-export.ics [re-created ex M7 Kalarm] 59166 Rha 12 19:18 kalarm-export-MB.ics [the attachment] I will try importing the two to see if there is any difference. First create a few silly alarms to have an existing list. Then select all, delete (it asked whether I really wanted to). List empty. File-Import Alarms, choose M7 exported file kalarm-export.ics They apparently all appeared, this time with no alarm pop-ups... Deleted them all (98), it asked for confirmation; -> empty list. Then imported MB's attached file [renamed] kalarm-export-MB.ics They apparently all appeared, this time with a lot of alarm pop-ups, legitimate. There were 98 (checked by selecting all, Delete). Bingo! as we say. So, Maurice, you need to do some homework. The brute allegation is not reproduceable, neither by Aurélien comment 14, nor me here, with your own data. You do not seem to have tried even slightly alternate scenarios like starting with an empty alarm list (which should surely be the case after a new installation); or re-exporting it from its origin. Most users play around such problems a bit to try & pin it down - and often do. > > Also, what happens if you import the list into M8/Kalarm without > > first deleting the existing alarms? > Done that on M7; it APPENDS the new version to the existing one Seems sensible. Passed ones seem to get actioned and *not* appended. For M8, it does indeed append the additions. > By the way, Lewis, have you been using Kalarm for long? Never before. My life is not based on having my computer always on, and could not be further removed from relying on it for reminders! In your court.
Just taken another look on M8. This time - before deleting all alarms displayed in list - I renamed the intended Import file to the unique "kalarm-export-new.ics", and asked to Import that - which it DID. Great! BUT - having done that - the M8 Kalarm then immediately proceeded to spatter the screen with a display of all the 96 or entries in the list - completely useless and messy - as I see happened and reported by others above. What on earth was the point in doing that? How was that an 'improvement? So there is an incompatibility with the M7 version, which was happy to use a file with same name as before, and just show the entries pouring into the vacated list... Any way of enquiring what other changes were made M7-->M8?
As for alarm windows popping up, I myself (but Aurélien apparently saw the whole lot) only got about half the number, not the whole set. I think they were alarms that needed showing. Would that not be legitimate? I have just raise Kalarm to find its upstream version, and it popped a lot of reminders for recent dates. Quite correct. At present, this looks more like an application issue. Can you raise it on a KDE forum? The Mageia 8 version describes itself (Help-About Kalarm) as: Kalarm Version 3.0.3 (KDE Apps 20.08.03) > Any way of enquiring what other changes were made M7-->M8? I cannot here cite the Mageia 7 equivalent, but you would need to do so in a forum - an ideal starting point. CC'ing the KDE team for info.
Keywords: (none) => UPSTREAMCC: (none) => kde
Well, yes, Import does work, but in a very messy and inconvenient way, especially when Importing a large alarm list. Unlike most M8 versions of applications, which (unlike e.g. Windows apps) do make the effort to pick up a cloned M7 application's settings in $HOME, Kalarm does not, apparently having adopted some new policy w.r.t. the naming of kalarm-export.ics files. Presumably this was supposed to be an M8 'improvement', but the effect - particularly when circumstances require the alarm list in an e.g. laptop to be replaced by the latest version Exported by a PC for Import on laptop - causes a lot of inconvenience - worse than useless - when alarms from the imported list are splattered all over the screen (instead of just listed in the kalarm screen (as happens in M7 kalarm). I suspect that what happened during the update of kalarm from M7 to M8 version was that the immediate displayed mess in kalarm's Import of a new list was simply reflecting a minimal alarm list as an immediate check that the Import had worked, and that removal of that temporary immediate display was forgotten when finalising the M8 version. With the M7 version the Import simply shows the list in the Kalarm window, and alarms are only executed after exit and restart of Kalarm. As M8 kalarm is at the moment, I can continue to achieve my goal with Import, but will try forcing an immediate closedown & restart of Kalarm to avoid having to clear up the Import mess on screen.
Created attachment 12095 [details] Arbitrry Kalarms Exported file to test Import As per the attachment title.
Attachment 12069 is obsolete: 0 => 1
Back to Mageia 7, Kalarm (Help-About) Version 2.12.2, kalarm-19.04.0-1.mga7 I started it, already charged with your alarms list (it popped a few reminders), cleared the entire list, then Imported again your actual alarms list file. Well, well, well: it popped 50 reminder windows (what I reported earlier for M8), + a couple of 'failure to delete alarm' alerts which I had also seen before. No. of alarms down to 97. The behaviour was similar but with fewer popups when I deleted the alarms imported from your actual file, then imported the same list previously exported by this Kalarm instance. So M7/M8 differences are unconfirmed; different exact behaviour in different circumstances, clearly. Not warranting a bug.
Resolution: (none) => INVALIDStatus: UNCONFIRMED => RESOLVEDKeywords: UPSTREAM => (none)
(In reply to Lewis Smith from comment #27) > Back to Mageia 7, Kalarm (Help-About) Version 2.12.2, kalarm-19.04.0-1.mga7 > > I started it, already charged with your alarms list (it popped a few > reminders), cleared the entire list, then Imported again your actual alarms > list file. Well, well, well: it popped 50 reminder windows (what I reported > earlier for M8), + a couple of 'failure to delete alarm' alerts which I had > also seen before. > No. of alarms down to 97. Do you really believe that reflects some *improvement* M7->M8??? What was the justification for change M7-->M8, causing this incompatible and ugly worse-than-useless result? > The behaviour was similar but with fewer popups when I deleted the alarms > imported from your actual file, then imported the same list previously > exported by this Kalarm instance. You did *what*?! Trimmed the real list to minimise the mess?! > So M7/M8 differences are unconfirmed; different exact behaviour in different > circumstances, clearly. Not warranting a bug. Beg strongly to disagree, I'm afraid... I believe I have done the right thing here; I've waved a red flag to warn of an ugly upward compatibility. If the Powers That Be disagree, then so bit it. I do not propose to post here again. Merry Xmas to you all.
This should 1sked in upstream bugzilla.
(In reply to Maurice Batey from comment #28) > (In reply to Lewis Smith from comment #27) > > Back to Mageia 7, Kalarm (Help-About) Version 2.12.2, kalarm-19.04.0-1.mga7 > > > > I started it, already charged with your alarms list (it popped a few > > reminders), cleared the entire list, then Imported again your actual alarms > > list file. Well, well, well: it popped 50 reminder windows (what I reported > > earlier for M8), + a couple of 'failure to delete alarm' alerts which I had > > also seen before. > > No. of alarms down to 97. > Do you really believe that reflects some *improvement* M7->M8??? > What was the justification for change M7-->M8, causing this incompatible and > ugly worse-than-useless result? You did not seem to understand: I imported *your* data into *M7* Kalarm, and it behaved more or less as per your complaint re M8. So there is not the massive difference you pretend. Try it yourself. > > The behaviour was similar but with fewer popups when I deleted the alarms > > imported from your actual file, then imported the same list previously > > exported by this Kalarm instance. > You did *what*?! Trimmed the real list to minimise the mess?! I trimmed nothing. I repeat: 1. I imported your data into M7 Kalarm (forget how many alarms, perhaps 50). 2. I exported that data into a 'clone' export/import file. Conceptually the same, but clearly subtly different because the file sizes were not identical. See comments 21 22. 3. After having imported your actual file into M8 Kalarm, with I think around 50 alarms, I tried importing its clone produced via M7 Kalarm to see whether that made a difference. It did - I noted no popus. > I believe I have done the right thing here; I've waved a red flag to warn of > an ugly upward compatibility. Which is not demonstrable; beyond different behaviour in different circumstances. Try importing *your* file into Mageia 7 (rather than M8) Kalarm. As for all those popups, are they not legitimate reminders that need showing after (on) import? And in an upgrade situation, I suspect existing alarms would be left intact. > Merry Xmas to you all. At least thank you for that. Reciprocated.