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 "Akonadi
https://bugs.kde.org/show_bug.cgi?id=410834
--- Comment #9 from BryanFRitt ---
(In reply to David Jarvie from comment #7)
> That's the output I was looking for. It looks likely that you have a
> duplicate Akonadi resource for KAlarm. This bug has been fixed in the KDE
> Applications 19.08 release
https://bugs.kde.org/show_bug.cgi?id=410834
--- Comment #8 from BryanFRitt ---
Note:
"Mid-air collision detected!
Someone else has made changes to bug 410834 at the same time you were trying
to"
Here's what I typed during the collision period...
ps aux | grep akonadi | sed 's/ \+/ /g' | cut -
https://bugs.kde.org/show_bug.cgi?id=410834
David Jarvie changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=410834
--- Comment #6 from BryanFRitt ---
Is something like this what your looking for?
[ shortened the output for ps aux | grep akonadi ]
grep akonadi
/usr/bin/akonadi_control
/usr/bin/akonadiserver
/usr/sbin/mysqld --defaults-file=/home/bryan/.local/share/ak
https://bugs.kde.org/show_bug.cgi?id=410834
--- Comment #5 from BryanFRitt ---
"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?"
How I ca
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
https://bugs.kde.org/show_bug.cgi?id=410834
--- Comment #3 from BryanFRitt ---
I purged anything to do with akonadi, set
/home/bryan/.local/share/akonadi_ical_resource_3/ to read only then reinstalled
back kde-full,
Now it looks like /usr/bin/akonadi_control > /usr/bin/akonadi_kalarm_resource
--
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 are watchin
https://bugs.kde.org/show_bug.cgi?id=410834
--- Comment #1 from BryanFRitt ---
Ops... I meant /usr/bin/akonadi_control was the one using CPU... 'End Process'
this, and no more of those files will be created.
--
You are receiving this mail because:
You are watching all bug changes.
10 matches
Mail list logo