Bug 492415

Summary: Akonadi integration overrides akonadi config, writing broken colour values on each plasma restart
Product: [Plasma] plasmashell Reporter: Christian (Fuchs) <kde>
Component: Digital Clock widgetAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, nicolas.fella
Priority: NOR    
Version: 6.1.4   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: deskop recording showing the issue on each plasma restart

Description Christian (Fuchs) 2024-08-30 17:07:36 UTC
Created attachment 173131 [details]
deskop recording showing the issue on each plasma restart

SUMMARY
Since the last system update, on every restart of plasma shell it writes bad config values into akonadi configuration when the integration  ("display calendar events" of akonadi in plasma, e.g. in the clock popup calendar) is enabled

STEPS TO REPRODUCE
1.  Have plasma 6.1.4 /  akonadiserver 6.2.0 (24.08.0)
2.  Have the akonadi integration enabled  (show calendar events in the plasma calendar)
3.  Restart plasma (or the whole system, either works, really)

OBSERVED RESULT
Values in akonadi are overwritten with broken values

EXPECTED RESULT
A plasma start should never ever write any akonadi config values, most certainly not broken ones

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.6-200.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga
Comment 1 Christian (Fuchs) 2024-08-30 17:19:41 UTC
Marking as critical, because not only does that overwrite user config with broken values, but also potentially sync this broken config to other devices that have the same calendars configured
Comment 2 Nate Graham 2024-08-30 21:48:34 UTC

*** This bug has been marked as a duplicate of bug 492396 ***