[kalarm] [Bug 296703] Can't save/edit alarms

https://bugs.kde.org/show_bug.cgi?id=296703 David Jarvie changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because

[kalarm] [Bug 368532] Failed to create default calendar (New configuration timed out)

https://bugs.kde.org/show_bug.cgi?id=368532 David Jarvie changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because

[kalarm] [Bug 295926] Kalarm not allowing editing or deleting of alarms

https://bugs.kde.org/show_bug.cgi?id=295926 David Jarvie changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because

[kalarm] [Bug 290050] cannot add alarms after upgrading to 4.8 beta

https://bugs.kde.org/show_bug.cgi?id=290050 David Jarvie changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because

[kalarm] [Bug 322331] Creating alarm fails with "Failed to create alarm. (Append failed)"

https://bugs.kde.org/show_bug.cgi?id=322331 David Jarvie changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because

[kalarm] [Bug 340618] KAlarm fails to save sound file setting

https://bugs.kde.org/show_bug.cgi?id=340618 David Jarvie changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because

[kalarm] [Bug 313614] Should be possible to set a simple alarm using kalarm without having akonadi running

https://bugs.kde.org/show_bug.cgi?id=313614 David Jarvie changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because

[kalarm] [Bug 357186] “ fatal error: phonon/backendcapabilities.h: No such file or directory” when building kdepim

https://bugs.kde.org/show_bug.cgi?id=357186 David Jarvie changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because

[kalarm] [Bug 425383] One time alarm activates more than once if you restart your computer

https://bugs.kde.org/show_bug.cgi?id=425383 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Component|kalarmd

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 David Jarvie changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution

[kalarm] [Bug 424563] Can't press enter to dismiss alarm

https://bugs.kde.org/show_bug.cgi?id=424563 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kalarm] [Bug 315401] Add option to ignore errors when executing command alarms

https://bugs.kde.org/show_bug.cgi?id=315401 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Latest Commit

[Breeze] [Bug 423971] KAlarm App/Tray icon is too similar with the notification icon

https://bugs.kde.org/show_bug.cgi?id=423971 David Jarvie changed: What|Removed |Added Summary|App/Tray icon is too|KAlarm App/Tray icon is too

[Breeze] [Bug 423971] App/Tray icon is too similar with the notification icon

https://bugs.kde.org/show_bug.cgi?id=423971 David Jarvie changed: What|Removed |Added Component|general |Icons Version|2.13.4

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #19 from David Jarvie --- I've now updated my Neon system to Plasma 5.19.2, KDE Frameworks 5.72.0, Qt 5.14.2, Linux kernel 5.3.0-62, and rebuilt kalarm and other KDE PIM packages. It still works for me. -- You are receiving this mail

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #18 from David Jarvie --- The latest KAlarm (not yet released) works on my current system, which is Neon with Plasma 5.18.4, KDE Frameworks 5.70.0, Qt 5.14.2. I'm now updating my system, and will check once that is complete. -- You

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #16 from David Jarvie --- What version of KAlarm are you running? -- You are receiving this mail because: You are watching all bug changes.

[Akonadi] [Bug 423406] /usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_X put my cpu at 100%

https://bugs.kde.org/show_bug.cgi?id=423406 --- Comment #3 from David Jarvie --- This doesn't happen on my system, so without more information on exactly where in akonadi_kalarm_resource CPU is being used, I can't investigate. This issue will go away in KAlarm version 3.0, which will no longer

[Akonadi] [Bug 423406] /usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_X put my cpu at 100%

https://bugs.kde.org/show_bug.cgi?id=423406 --- Comment #1 from David Jarvie --- Did a single akonadi_kalarm_resource process use 100% CPU? If so, the stack trace doesn't help to find out why, since it gives no indication of where in the KAlarmResource it is hogging the CPU. -- You

[kalarm] [Bug 423043] kalarm doesn't show alarms until restarting kalarm

https://bugs.kde.org/show_bug.cgi?id=423043 David Jarvie changed: What|Removed |Added Version Fixed In||20.08 Status|REPORTED

[kalarm] [Bug 423043] kalarm doesn't show alarms until restarting kalarm

https://bugs.kde.org/show_bug.cgi?id=423043 --- Comment #1 from David Jarvie --- Perhaps step 42 will provide the answer after all (I hope) ;) What might fix this is to delete all KAlarm's Akonadi active alarm resources, and then recreate them. To do this, first quit kalarm. Then run

[kalarm] [Bug 370708] alarms disappeared after disk full

https://bugs.kde.org/show_bug.cgi?id=370708 David Jarvie changed: What|Removed |Added Version Fixed In|KCalendarCore 5.71 |KCalendarCore 5.72 -- You are receiving

[kalarm] [Bug 370708] alarms disappeared after disk full

https://bugs.kde.org/show_bug.cgi?id=370708 David Jarvie changed: What|Removed |Added Latest Commit|536b15fd6b2c14276fc90fd3665 |https://invent.kde.org/fram

[kalarm] [Bug 370708] alarms disappeared after disk full

https://bugs.kde.org/show_bug.cgi?id=370708 David Jarvie changed: What|Removed |Added Version Fixed In||KCalendarCore 5.71 Latest Commit

[kalarm] [Bug 370708] alarms disappeared after disk full

https://bugs.kde.org/show_bug.cgi?id=370708 --- Comment #6 from David Jarvie --- It turns out that QSaveFile (which is supposed to preserve the original file if a write error occurs) *is* actually used by the library code which saves calendar files. However, when the disk is full, QSaveFile

[kalarm] [Bug 409538] Display alarms don't work, but command alarms do work

https://bugs.kde.org/show_bug.cgi?id=409538 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kalarm] [Bug 326396] KAlarm crash on adding existing KAlarm calendar to Kontact

https://bugs.kde.org/show_bug.cgi?id=326396 David Jarvie changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution

[kalarm] [Bug 412181] Crash while editing alarm item and updating packages on Debian Buster

https://bugs.kde.org/show_bug.cgi?id=412181 David Jarvie changed: What|Removed |Added Version Fixed In||20.04.2 Resolution

[kalarm] [Bug 390501] disappearing alarms

https://bugs.kde.org/show_bug.cgi?id=390501 David Jarvie changed: What|Removed |Added Version Fixed In||20.08 Resolution

[kalarm] [Bug 398404] Imported alarms from a old kalarm

https://bugs.kde.org/show_bug.cgi?id=398404 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kalarm] [Bug 419639] Playing audio alarms with set volumes causes sporadic crashes

https://bugs.kde.org/show_bug.cgi?id=419639 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kalarm] [Bug 417733] Sound doesn't work in KAlarm

https://bugs.kde.org/show_bug.cgi?id=417733 --- Comment #4 from David Jarvie --- Sound alarms work on my Neon system (which is an Ubuntu derivative, as is Kubuntu). I have the following phonon packages installed: libphonon4qt5-4 libphonon4qt5-bin libphonon4qt5experimental4 phonon4qt5 phonon4qt5

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 David Jarvie changed: What|Removed |Added Version Fixed In|19.12.3 |20.04.2 Resolution

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 David Jarvie changed: What|Removed |Added Status|REOPENED|CONFIRMED --- Comment #13 from David Jarvie

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 David Jarvie changed: What|Removed |Added Component|Akonadi |general -- You are receiving this mail because

[frameworks-knotifications] [Bug 419857] KAlarm crashes when opening from the systray in Sway WM

https://bugs.kde.org/show_bug.cgi?id=419857 David Jarvie changed: What|Removed |Added Assignee|djar...@kde.org |kdelibs-b...@kde.org CC

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #12 from David Jarvie --- I suspect that the QObject::disconnect errors probably come from inside QCommandLineParser rather than KAlarm itself, although I can't be sure. Certainly, there isn't any obvious place in KAlarm where a set of four

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #11 from David Jarvie --- If you're running a plasma desktop, when an application crashes, the KDE crash dialog should normally appear prompting you to report the crash, and allowing the crash trace to be viewed and copied. I don't know

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #7 from David Jarvie --- Sorry, of course if KAlarm is already running before you enter those commands, they will all run without waiting. Anyway, when I do the same, all the commands run successfully. Did the crash occur when you ran

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #6 from David Jarvie --- If you pasted those lines into konsole, each line would wait until you quitted KAlarm, before continuing on to the next line. Did you actually quit KAlarm 6 times? If not, what exactly did you paste into konsole

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #4 from David Jarvie --- You say you ran the commands from a script, so I tried the following script: #!/bin/bash kalarm -c yellow -t 2020-07-01-15:00 --reminder 2D 'Do, 02.07.: some reminder' kalarm -c yellow -t 2020-07-29-15:00

[kalarm] [Bug 417108] Command line operation fails

https://bugs.kde.org/show_bug.cgi?id=417108 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed

[kalarm] [Bug 417733] Sound doesn't work in KAlarm

https://bugs.kde.org/show_bug.cgi?id=417733 --- Comment #3 from David Jarvie --- Thanks for that information. Note that package dependencies are the responsibility of distributions, so you should report any missing dependent packages to Kubuntu. The issue about the time column not being wide

[kalarm] [Bug 417733] Sound doesn't work in KAlarm

https://bugs.kde.org/show_bug.cgi?id=417733 --- Comment #1 from David Jarvie --- Did sound work after installing the extra packages? -- You are receiving this mail because: You are watching all bug changes.

[kalarm] [Bug 416060] Upgrade to qt5.14.0 broke non-anti-aliased fonts in kalarm

https://bugs.kde.org/show_bug.cgi?id=416060 David Jarvie changed: What|Removed |Added Resolution|FIXED |UPSTREAM --- Comment #3 from David Jarvie

[kalarm] [Bug 414383] Defer dialogue is hidden when another application is full screen

https://bugs.kde.org/show_bug.cgi?id=414383 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[kalarm] [Bug 414383] New: Defer dialogue is hidden when another application is full screen

https://bugs.kde.org/show_bug.cgi?id=414383 Bug ID: 414383 Summary: Defer dialogue is hidden when another application is full screen Product: kalarm Version: unspecified Platform: Debian stable OS: Linux

[kalarm] [Bug 414348] time remaining not shown in active display alarm

https://bugs.kde.org/show_bug.cgi?id=414348 David Jarvie changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED

[kalarm] [Bug 412181] Crash while editing alarm item and updating packages on Debian Buster

https://bugs.kde.org/show_bug.cgi?id=412181 --- Comment #1 from David Jarvie --- At what exact point did the crash occur? Did you already have the alarm edit dialog open when the crash occurred? If not, how did you try to open the alarm edit dialog - via the main window, or by clicking

[kalarm] [Bug 398404] Imported alarms from a old kalarm

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

[kalarm] [Bug 411296] Timezone must be specified in dbus scheduleMessage

https://bugs.kde.org/show_bug.cgi?id=411296 David Jarvie changed: What|Removed |Added Version Fixed In||19.08.1 Latest Commit

[kalarm] [Bug 410834] Excessive Akonadi CPU and storage use

https://bugs.kde.org/show_bug.cgi?id=410834 --- Comment #10 from David Jarvie --- Reassigning this bug report would be confusing, since much of it relates to KAlarm. If you want the akonadi_ical_resource CPU or file usage to be investigated, you should create a new bug report for Product

[kalarm] [Bug 403124] Two kalarm resources fighting each other

https://bugs.kde.org/show_bug.cgi?id=403124 David Jarvie changed: What|Removed |Added CC||bryanfr...@hotmail.com --- Comment #7 from

[kalarm] [Bug 410834] Excessive Akonadi CPU and storage use

https://bugs.kde.org/show_bug.cgi?id=410834 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kalarm] [Bug 410834] Excessive Akonadi CPU and storage use

https://bugs.kde.org/show_bug.cgi?id=410834 --- Comment #4 from David Jarvie --- Can you please list all the akonadi_kalarm_resource_... processes which are running, so that I can check if there are more than there should be. Which version of KAlarm or KDE Applications are you running? -- You

[kalarm] [Bug 410596] Crash when importing alarms

https://bugs.kde.org/show_bug.cgi?id=410596 David Jarvie changed: What|Removed |Added Version Fixed In||19.08.1 Status|CONFIRMED

[kalarm] [Bug 410834] Excessive Akonadi CPU and storage use

https://bugs.kde.org/show_bug.cgi?id=410834 --- Comment #2 from David Jarvie --- This bug report seems to relate to KOrganizer, since akonadi_ical_resource is nothing to do with KAlarm. KAlarm uses processes called akonadi_kalarm_resource. -- You are receiving this mail because: You

[kalarm] [Bug 410596] Crash when importing alarms

https://bugs.kde.org/show_bug.cgi?id=410596 --- Comment #12 from David Jarvie --- Can you please commit your Phabricator patch so that this bug report can be closed? Thanks. -- You are receiving this mail because: You are watching all bug changes.

[kalarm] [Bug 410596] Crash when importing alarms

https://bugs.kde.org/show_bug.cgi?id=410596 --- Comment #11 from David Jarvie --- Ok, that makes sense. Thanks for your Phabricator patch, which I have accepted. -- You are receiving this mail because: You are watching all bug changes.

[kalarm] [Bug 410596] Crash when importing alarms

https://bugs.kde.org/show_bug.cgi?id=410596 David Jarvie changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[kalarm] [Bug 410596] Crash when importing alarms

https://bugs.kde.org/show_bug.cgi?id=410596 --- Comment #4 from David Jarvie --- The valgrind crash is in fact different from the original crash. The valgrind crash shows that multiple calendar status changes are being received in AlarmCalendar, before the processing of the previous one has

[kalarm] [Bug 410596] Crash when importing alarms

https://bugs.kde.org/show_bug.cgi?id=410596 --- Comment #3 from David Jarvie --- Oops, the command should be grep ^UID: file1 file2 ... | sort | uniq -c | grep -v "^ *1 " -- You are receiving this mail because: You are watching all bug changes.

[kalarm] [Bug 410596] Crash when importing alarms

https://bugs.kde.org/show_bug.cgi?id=410596 --- Comment #2 from David Jarvie --- Thank you for the good quality bug report. Even with the information you provided, it isn't clear what went wrong. It's possible (but not certain) that if any events have UIDs which are duplicated between different

[kalarm] [Bug 374337] Alarm export / import doesn't work properly

https://bugs.kde.org/show_bug.cgi?id=374337 David Jarvie changed: What|Removed |Added CC||rfernan...@cbm.sc.gov.br --- Comment #6 from

[kalarm] [Bug 384883] Issues to Export / Import Calendars

https://bugs.kde.org/show_bug.cgi?id=384883 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kalarm] [Bug 403124] Two kalarm resources fighting each other

https://bugs.kde.org/show_bug.cgi?id=403124 David Jarvie changed: What|Removed |Added CC||stepnj...@gmail.com --- Comment #6 from David

[kalarm] [Bug 405313] kalarm freezes in gnome

https://bugs.kde.org/show_bug.cgi?id=405313 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kalarm] [Bug 403124] Two kalarm resources fighting each other

https://bugs.kde.org/show_bug.cgi?id=403124 David Jarvie changed: What|Removed |Added CC||cyp...@gmail.com --- Comment #5 from David

[kalarm] [Bug 392357] kalarm thrashes hard drive forever

https://bugs.kde.org/show_bug.cgi?id=392357 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kalarm] [Bug 403124] Two kalarm resources fighting each other

https://bugs.kde.org/show_bug.cgi?id=403124 David Jarvie changed: What|Removed |Added Component|KAlarm resource |Akonadi Version Fixed

[Akonadi] [Bug 403124] Two kalarm resources fighting each other

https://bugs.kde.org/show_bug.cgi?id=403124 David Jarvie changed: What|Removed |Added Latest Commit||fa92abbb60ac6b3518d07da5c50

[kalarm] [Bug 409538] New: Display alarms don't work, but command alarms do work

https://bugs.kde.org/show_bug.cgi?id=409538 Bug ID: 409538 Summary: Display alarms don't work, but command alarms do work Product: kalarm Version: 2.11.16 Platform: Mint (Debian based) URL:

[kalarm] [Bug 405313] kalarm freezes in gnome

https://bugs.kde.org/show_bug.cgi?id=405313 --- Comment #22 from David Jarvie --- If you kill kalarm first, does it freeze again after restarting it and trying to do step 1? One thing which might possibly help to stop KAlarm freezing would be to delete its Akonadi data (which is separate from

[kalarm] [Bug 397093] please make the following kalarm columns hide-able: repeat, type-icon, color

https://bugs.kde.org/show_bug.cgi?id=397093 David Jarvie changed: What|Removed |Added Latest Commit||b186cbe4816f0d1b1392585ede0

[kalarm] [Bug 408625] Kalarm unable to resume properly after suspend to ram

https://bugs.kde.org/show_bug.cgi?id=408625 --- Comment #1 from David Jarvie --- To narrow down the cause of this bug, could you please try entering the following command in a terminal window when KAlarm has stopped working after suspension, and report whether KAlarm starts working after

[kalarm] [Bug 407328] KAlarm crashed on first trigger of reoucurring alarm

https://bugs.kde.org/show_bug.cgi?id=407328 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kalarm] [Bug 407882] After adding a new resource in KAlarm, it is not seen by KAlarm

https://bugs.kde.org/show_bug.cgi?id=407882 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Version Fixed

[kalarm] [Bug 407882] After adding a new resource in KAlarm, it is not seen by KAlarm

https://bugs.kde.org/show_bug.cgi?id=407882 David Jarvie changed: What|Removed |Added Latest Commit|4db8a94f7e94555607312d35e02 |6b47cbcbb8f57dd6c2b9b3a9fe5

[kalarm] [Bug 407882] After adding a new resource in KAlarm, it is not seen by KAlarm

https://bugs.kde.org/show_bug.cgi?id=407882 David Jarvie changed: What|Removed |Added Latest Commit|5453e43e9af511b25e2f9bee93b |4db8a94f7e94555607312d35e02

[kalarm] [Bug 407882] After adding a new resource in KAlarm, it is not seen by KAlarm

https://bugs.kde.org/show_bug.cgi?id=407882 David Jarvie changed: What|Removed |Added Status|REPORTED|CONFIRMED Latest Commit

[kalarm] [Bug 408006] Errors at startup

https://bugs.kde.org/show_bug.cgi?id=408006 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Summary|please read

[kalarm] [Bug 407544] KAlarm 19.04 doesn't work at all

https://bugs.kde.org/show_bug.cgi?id=407544 David Jarvie changed: What|Removed |Added CC||anticorporatedemocrat@zoho

[kalarm] [Bug 407882] New: After adding a new resource in KAlarm, it is not seen by KAlarm

https://bugs.kde.org/show_bug.cgi?id=407882 Bug ID: 407882 Summary: After adding a new resource in KAlarm, it is not seen by KAlarm Product: kalarm Version: unspecified Platform: Neon Packages OS: Linux

[kalarm] [Bug 407544] KAlarm 19.04 doesn't work at all

https://bugs.kde.org/show_bug.cgi?id=407544 David Jarvie changed: What|Removed |Added Latest Commit||fe40ba8aa6e61beb9e3bf89742d

[kalarm] [Bug 407544] KAlarm 19.04 doesn't work at all

https://bugs.kde.org/show_bug.cgi?id=407544 David Jarvie changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[kalarm] [Bug 407328] KAlarm crashed on first trigger of reoucurring alarm

https://bugs.kde.org/show_bug.cgi?id=407328 --- Comment #2 from David Jarvie --- What type of recurrence did you specify (Daily / Weekly / etc)? What holiday region is configured in KAlarm? To check this, look at the "Holiday region" selection in Settings -> Configure KAlarm -&g

[neon] [Bug 407827] New: Neon developer live image doesn't contain development packages

https://bugs.kde.org/show_bug.cgi?id=407827 Bug ID: 407827 Summary: Neon developer live image doesn't contain development packages Product: neon Version: unspecified Platform: Other OS: Linux

[kalarm] [Bug 407544] KAlarm 19.04 doesn't work at all

https://bugs.kde.org/show_bug.cgi?id=407544 --- Comment #1 from David Jarvie --- Did you get crash handler dialogs? Without a crash trace, it is unlikely to be possible to fix this. -- You are receiving this mail because: You are watching all bug changes.

[kalarm] [Bug 405313] kalarm freezes in gnome

https://bugs.kde.org/show_bug.cgi?id=405313 --- Comment #18 from David Jarvie --- It looks as if more Akonadi resources are running than there should be. To fix this: 1. In KAlarm, use the View -> Show Calendars menu option to display the alarm calendars in use. 2. Right click on each calen

[kalarm] [Bug 405313] kalarm freezes in gnome

https://bugs.kde.org/show_bug.cgi?id=405313 --- Comment #12 from David Jarvie --- Sorry for the delay in replying, but I've been away. I don't think that the fault is likely to be due to your system update. A possible reason for the problem could be that there are multiple Akonadi resources

[kalarm] [Bug 405313] kalarm freezes in gnome

https://bugs.kde.org/show_bug.cgi?id=405313 --- Comment #2 from David Jarvie --- This looks similar to bug 392357. The culprit is likely to be Akonadi. There is a goal to replace the use of Akonadi for KAlarm, but this will take some time yet. -- You are receiving this mail because: You

[kalarm] [Bug 405323] Suggestion & question: Backups

https://bugs.kde.org/show_bug.cgi?id=405323 --- Comment #1 from David Jarvie --- You should check the location of KAlarm's calendar files as follows. In the menu, use View -> Show Calendars. Hover the mouse over each calendar shown there, and it will display the location of the file u

[kalarm] [Bug 345922] Option to avoid kalarm windows over fullscreen applications

https://bugs.kde.org/show_bug.cgi?id=345922 --- Comment #3 from David Jarvie --- Some people definitely require alarms to show on top of full screen windows. The best solution, I think, is to add an option when creating an alarm to show it as a notification instead of as a window. This could

[Akonadi] [Bug 403124] Two kalarm resources fighting each other

https://bugs.kde.org/show_bug.cgi?id=403124 --- Comment #1 from David Jarvie --- It looks as if the two resources are set up to use the same calendar file, /home/v13/.kde/share/apps/kalarm/template.ics. This shouldn't happen by default. Do you have any idea why this might have happened - have

[kalarm] [Bug 392357] kalarm thrashes hard drive forever

https://bugs.kde.org/show_bug.cgi?id=392357 --- Comment #5 from David Jarvie --- I think that the following procedure should prevent kalarm akonadi resources from running, although I can't guarantee that it will work. 1) Stop akonadi using the command 'akonadictl stop' in a terminal window. 2

[kalarm] [Bug 399840] Doesn't make sound in Kalarm

https://bugs.kde.org/show_bug.cgi?id=399840 David Jarvie changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution

[kalarm] [Bug 399840] Doesn't make sound in Kalarm

https://bugs.kde.org/show_bug.cgi?id=399840 --- Comment #1 from David Jarvie --- Can you please supply information on your distribution and version, and on the KAlarm version. -- 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 #3 from David Jarvie --- Does the fault happen every time you log in, or did it only happen the first time after importing the alarms? -- You are receiving this mail because: You are watching all bug changes.

[kalarm] [Bug 398658] Kalarm Version 2.12.1 "Defer" button is grayed (disabled) if any recurrence is selected

https://bugs.kde.org/show_bug.cgi?id=398658 David Jarvie changed: What|Removed |Added Version Fixed In||18.08.2 Latest Commit

[kalarm] [Bug 398404] Imported alarms from a old kalarm

https://bugs.kde.org/show_bug.cgi?id=398404 --- Comment #1 from David Jarvie --- Did you import the alarms into a new calendar file, or into the default file? Could you please attach your default calendar file (probably ~/.local/share/kalarm/calendar.ics). -- You are receiving this mail

<    1   2   3   4   5   6   7   >