https://bugs.kde.org/show_bug.cgi?id=409605
Bug ID: 409605
Summary: KAlarm: Failed to insert new part into database,
Memory Leak probably related
Product: kalarm
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: Akonadi
Assignee: djar...@kde.org
Reporter: samuel.s.shan...@hotmail.com
Target Milestone: ---
Created attachment 121376
--> https://bugs.kde.org/attachment.cgi?id=121376&action=edit
kalarmfilter=KSystemLog filtered on 'kalarm', wholeLogForError=KSysLog
unfiltered on error pop-up.
SUMMARY
When trying to add or edit a KAlarm, a foreign key constraint fails and the
alarm is not added/edited, in fact existing alarms disappear from the list.
Also observed is a gradual memory leak in both KAlarm and akonadi_kalarm that
probably wasn't happening before the database error, but I can't say for sure.
STEPS TO REPRODUCE
1. Open Kalarm
2. Add or Edit an Alarm
3. Click OK
1. Open Kalarm
2. Open resource monitor
OBSERVED RESULT
Add/Edit Alarm causes pop-up saying "Failed to Create Alarm"
Details: "Failed to insert new part into database"
Also, neither alarm appears in the list afterward, even if it was only being
edited, though they do seem to return to the list after restarting Kalarm if
they were created before the issue and only edited. The edit does not take
effect.
Open Resource Monitor
Memory Usage increasing by ~1,000K/s for kalarm process
Memory Usage increasing by ~400K/s for akonadi_kalarm process
EXPECTED RESULT
Alarms are Created/Edited with no error pop-up and appear in the list if
created, and stay in the list if edited.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
