[kalarm] [Bug 398404] Imported alarms from a old kalarm
https://bugs.kde.org/show_bug.cgi?id=398404 --- Comment #6 from turcovadio --- I imported the alarms to the default alarm calendar (the default directory). My best wishes Luis Duarte David Jarvie escreveu no dia sábado, 31/08/2019 à(s) 11:52: > https://bugs.kde.org/show_bug.cgi?id=398404 > > --- Comment #5 from David Jarvie --- > I'm sorry this bug report has been left for a long time now. > > Can you tell me whether you imported the alarms into the default alarm > calendar, or did you import them into a new calendar? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 398404] Imported alarms from a old kalarm
https://bugs.kde.org/show_bug.cgi?id=398404 --- Comment #4 from turcovadio --- Yes, it happens every time I log in. I just discovered the bug - usually I configure an alarm starting at 05:00 and repeating every hour. I have a lot of alarms repeating every day and every hour (I am a procrastinator). Suppose I create an alarm configured to start 10:41 and repeating every hour. So, when I open my computer the day after, at some time, only the alarm 10:41 fires. After, I close the kalarm demon, and restart again, all the other alarms 05:00 fire. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 398404] Imported alarms from a old kalarm
https://bugs.kde.org/show_bug.cgi?id=398404 --- Comment #2 from turcovadio --- Created attachment 115290 --> https://bugs.kde.org/attachment.cgi?id=115290=edit The present kalarm calendar -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 398404] New: Imported alarms from a old kalarm
https://bugs.kde.org/show_bug.cgi?id=398404 Bug ID: 398404 Summary: Imported alarms from a old kalarm Product: kalarm Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: turcova...@gmail.com Target Milestone: --- Created attachment 114849 --> https://bugs.kde.org/attachment.cgi?id=114849=edit My exported alarms I am using Kalarm 2.10-11-ak with Debian Jessie (8.10.0) with Xfce 4.10. Earlier I used Kalarm in Debian Wheezy (7.10.0), from where I export the alarms and I created a file. In the new OS (Jessie) I imported the alarms from the above mentioned file, and I added a few new alarms. The Kalarm is configured to start automatically at the start-up of the SO. A lot of times, the displayed alarms are the new ones. The old ones, only appear when I close the Kalarm daemon and start it again. The old alarms must appear at same time the new ones. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 374337] Alarm export / import doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=374337 --- Comment #5 from turcovadio <turcova...@gmail.com> --- You should close the report of the bug, due to the kalarm programmers changed the way as was saved (exported) the alarms. The other reason was I couldn't replicate the bug. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 374434] New: Inconsistency in the fulfillment of time
https://bugs.kde.org/show_bug.cgi?id=374434 Bug ID: 374434 Summary: Inconsistency in the fulfillment of time Product: kalarm Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: turcova...@gmail.com Target Milestone: --- When I define a new alarm, or change a old one, I can notice some inconsistencies. In the Alarm tab I can fill directly "At date / time" -> "in the time" field something like this 0500 that translates in 05:00. For me is Ok. When I try to do the same in the Recurrence tab -> "Recur every" field it fails (example: 0200 (it should translate in 02:00)) -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 370708] alarms disappeared after disk full
https://bugs.kde.org/show_bug.cgi?id=370708 --- Comment #4 from turcovadio <turcova...@gmail.com> --- For an unknown reason, the disk of my computer became repeatedly full. At that time, I exported selected alarms as a way to restore Kalarm, in case of the alarms being wiped out. But last time I imported the saved alarms, there was inconsistencies that prevented the import. I needed to delete all the files related to my alarms in order to import the saved ones. The operation of import of saved alarms should be improved. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 370708] alarms disappeared after disk full
https://bugs.kde.org/show_bug.cgi?id=370708 --- Comment #2 from turcovadio <turcova...@gmail.com> --- Hi, again As you know, it is possible to prevent the complete losing of information in a case of full disk. It is logical to lose some information in the case of creating new alarms (in a full disk scenario), but now what remains in a full disk scenario is the deleted alarms. All the active alarms disappear. I think it is a good policy, when updating new alarms, keep the old file, create a new one, and after being successful, change the old file to the new one. In a case of a crash or full disk, create the possibility to recover the old file. Of course this is not new to you. What you surely didn't remember is that the disks can become full. Anyway, Kalarm is a great program. Thank you for your reply. Luis Duarte 2016-10-16 17:41 GMT+01:00 David Jarvie via KDE Bugzilla < bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=370708 > > --- Comment #1 from David Jarvie <djar...@kde.org> --- > KAlarm is probably not the only application which can potentially lose data > when the disk becomes full. This is due to the way that files on disk are > updated - unless it's just a case of appending data to the end of a file, > when > a file is updated it is completely rewritten in an empty part of the disk > and > then the old data is marked as free. This handled by the file system > itself, > and it may not be possible to prevent data loss in such cases other than by > creating a new file with the new data, checking whether that succeeded, and > then deleting the old file only if it did succeed. This may not be > compatible > with the way that Akonadi (which handles file updates) works. This needs > investigation. > > In the meantime, the best advice it to always keep backups of important > data, > and don't let your disk fill up completely. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 370708] New: alarms disappeared after disk full
https://bugs.kde.org/show_bug.cgi?id=370708 Bug ID: 370708 Summary: alarms disappeared after disk full Product: kalarm Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: turcova...@gmail.com My disk became totally full. After that I lost every alarm after Kalarm trying to display the messages (alarms). I will be good having a way to have a permanent file with the alarms. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
