[kalarm] [Bug 455377] Akonadi/Kalarm Constant Disk Access & High CPU Usage + Creates 700,000 Files
https://bugs.kde.org/show_bug.cgi?id=455377 --- Comment #5 from David Jarvie --- I have suspected in the past that sometimes KAlarm does not show up in the system tray when it should. I suspect that this may have been due to some glitch in Plasma, although I could never confirm this. In KDE 22.08, I haven't seen this issue, so it may have been fixed by now. I suggest that if KAlarm is running, i.e. if 'kalarm --tray' shows in the task list, that you kill it, and then start up KAlarm again. Then in its Preferences dialog (Settings -> Configure KAlarm), in the View tab, deselect Show in System Tray. It should then run normally but not in the system tray. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 455377] Akonadi/Kalarm Constant Disk Access & High CPU Usage + Creates 700,000 Files
https://bugs.kde.org/show_bug.cgi?id=455377 --- Comment #4 from Frank James --- (In reply to David Jarvie from comment #3) > I'm glad you've been able to solve your problems by using the workaround. > > Re-setting the bug status to fixed, since it's fixed in later versions. Hi again. OK, I bit the bullet, and have upgraded to 22.04 as suggested - however, now KAlarm fails to load at all! I first noticed there was no tray icon for it after the first boot, and when I've tried to launch it via Application Launcher, it's button shows up in the taskbar, with the moving circle indicating it is loading, but then the button disappears, and no KAlarm. When I try initiating it via the terminal, all I get is a frozen cursor beneath it, no output whatsoever. Looking at htop, I see *kalarm --tray* is apparently running. I downloaded the version for 22.04 - which I couldn't help but notice the page says it depends on the package akonadi-server, which I thought it no longer does - but when running the .deb I am told I already have the same version installed, and reinstalling it does not fix this. Any ideas on what is going on, and how I can fix this? I really (URGENTLY!) need KAlarm to be working. Many thanks in advance! -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 455377] Akonadi/Kalarm Constant Disk Access & High CPU Usage + Creates 700,000 Files
https://bugs.kde.org/show_bug.cgi?id=455377 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||20.08 Status|REPORTED|RESOLVED --- Comment #3 from David Jarvie --- I'm glad you've been able to solve your problems by using the workaround. Re-setting the bug status to fixed, since it's fixed in later versions. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 455377] Akonadi/Kalarm Constant Disk Access & High CPU Usage + Creates 700,000 Files
https://bugs.kde.org/show_bug.cgi?id=455377 Frank James changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- --- Comment #2 from Frank James --- (In reply to David Jarvie from comment #1) Hi David - many thanks, and sorry I didn't notice I'd gotten a reply 'til now! Thanks for all that info - while it's a pity there doesn't seem to be a way to upgrade Kalarm (which would be understandable if it needed a newer version of Akonadi, which it doesn't, so it's a bit perplexing), it's good to know that when I upgrade the system, this will be a thing of the past. And many thanks for your workaround - while it has been behaving ever since I fiddled around in Akonadi Console, so installing that app was definitely worth it, I'll keep your workaround in case I ever need it! Oh, and I actually put some wrong info in my summary, and apparently users can't edit their own comments on this site. I was incorrect when I said: *akonadi_kalarm_resource_1* is "kalarm" and that *akonadi_kalarm_resource_5* is "Archived Alarms" Both of those are actually "Archived Alarms" - "kalarm" is *akonadi_kalarm_dir_resource_1* - but it was only *akonadi_kalarm_resource_5* that was going back and forth from Ready to being busy. And I'm happy to note that after choosing to "Restart Agent", the problem hasn't restarted after multiple reboots! Cheers, and thanks for your input. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 455377] Akonadi/Kalarm Constant Disk Access & High CPU Usage + Creates 700,000 Files
https://bugs.kde.org/show_bug.cgi?id=455377 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from David Jarvie --- >From version 3.0 (KDE Apps 20.08), KAlarm no longer uses Akonadi, which fixes this issue. The decision to stop using Akonadi was due to the number of problems which kept arising with Akonadi - your issue is just one example of this, unfortunately. I'm not aware of any way of upgrading KAlarm by itself, so in order to KAlarm version 3 or later, you would probably have to upgrade KDE as a whole, which is likely to require a distro upgrade. You may be able to partially fix your problem with your current version as follows: 1) In the KAlarm main window, display the Calendars panel (using View -> Show Calendars) and select the calendar type of Archived Alarms. Hover over the listed resource (which will probably be called "Archived Alarms" to find out its file location, and note the location for later. 2) Ensure that no KAlarm alarm messages are currently displayed, and stop KAlarm by File -> Quit. (Or kill kalarm from the command line.) 3) Run akonadiconsole. In the Agents tab, select KAlarm's Archived Alarms, and remove it. 4) Run KAlarm again. It should recreate the archived alarms resource - check that it has done so by again looking at the archived alarms in the Calendars panel. A single calendar "Archived Alarms" should be listed (as before). If not, click Add and enter the noted file location, select alarm type Archived Alarms, and give it the display name "Archived Alarms". 5) Check whether this has improved the CPU consumption for the akaondi_kalarm_resource_* processes. I'm not sure whether creating a new KAlarm Directory resource works, so if you try to do the same for the Active Alarms calendar, you might possibly be unable to access your active alarms afterwards. You may just have to live with the problem until you are able to update to KAlarm version 3. -- You are receiving this mail because: You are watching all bug changes.
