[Akonadi] [Bug 485426] New: Google Groupware agent stops syncing after a while
https://bugs.kde.org/show_bug.cgi?id=485426 Bug ID: 485426 Summary: Google Groupware agent stops syncing after a while Classification: Frameworks and Libraries Product: Akonadi Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Google Resource Assignee: kdepim-bugs@kde.org Reporter: materem...@gmail.com CC: c...@carlschwan.eu, dvra...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When I add a Google account to Akonadi it syncs properly, calendar events turn up in KOrganizer and Merkuro calendar as well. Sync can be initiated from Merkuro or from Akonadi Console. After a while if there is a sync it gets stuck at 0% forever. Recreating the agent or reconfiguring it (reauth) solves the issue. My guess is that refreshing the access token is not working. I had the same issue with 6.0.1 as well. I have tried clearing up akonadi config and starting from scratch, I have tried switching backends, tried stopping and restarting akonadi. I also tried to install latest KDE neon in VirtualBox and set up the same account, it had the same results (6.0.1). STEPS TO REPRODUCE 1. add a google account 2. confirm it syncs properly in Akonadi Console, manual resync is also possible with Sync all 3. wait a few hours (6-8) and try to resync, it gets stuck at 0% OBSERVED RESULT not Syncing EXPECTED RESULT Syncing SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch with Kde 6.0.2 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 485427] New: wish: Allow to only show specific calenders in the Upcomming Events Summary
https://bugs.kde.org/show_bug.cgi?id=485427 Bug ID: 485427 Summary: wish: Allow to only show specific calenders in the Upcomming Events Summary Classification: Applications Product: kontact Version: 6.0.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: summary Assignee: kdepim-bugs@kde.org Reporter: n...@rumpeltin.de Target Milestone: --- Currently the Upcoming Events Summary shows events from all available calendars. Since I also imported the SoGO calendars from my colleges, the overview shows over 100 events per day that are not relevant for me. This makes the whole Upcoming Events Summary unusable. There is an option called "Show my events only" in the settings, but it has no effect. It would be nice to be able to show only events from specific calendars. Like it is already possible for the calendar in the Plasma clock widget. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 485426] Google Groupware agent stops syncing after a while
https://bugs.kde.org/show_bug.cgi?id=485426 materem...@gmail.com changed: What|Removed |Added CC||materem...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 485470] New: Kontact as a Flatpak clashes with Debian installation
https://bugs.kde.org/show_bug.cgi?id=485470 Bug ID: 485470 Summary: Kontact as a Flatpak clashes with Debian installation Classification: Applications Product: kontact Version: 5.24.4 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: lionsshark...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I was messing around with Kontact in Flatpak to compare feature parity with the older version shipped in Debian 12. The Flatpak tends to take in accounts from Akonadi already in the Debian installation instead of being a completely isolated instance separate from Debian. STEPS TO REPRODUCE 1. Have Kontact installed from apt on Debian with accounts already set up 2. Install Kontact as a Flatpak 3. Flatpak version recognizes the accounts from the Debian/Apt version and somehow interacts with the Debian Akonadi database 4. Sync, but unsuccessfully. All account info (even from accounts freshly created in the flatpak version) does not sync in the flatpak version and no data populates. OBSERVED RESULT Flatpak version of the app is devoid of data for all recognized accounts. All changes and syncing is visible on the Debian version. The Flatpak version is functionally useless when the Debian database exists. EXPECTED RESULT The Flatpak should be completely independent of the Debian installation. When installed for the first time, the Flatpak should have no accounts set up and when an account is set up, it should populate accordingly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian 12 with Kernel 6.1.0-18-amd64 (64-bit) (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION On Debian version, I set up my Akonadi database to use SQLite instead of MySQL. -- You are receiving this mail because: You are the assignee for the bug.
[libkgapi] [Bug 485390] 0 % sync korganizer -> G calendar
https://bugs.kde.org/show_bug.cgi?id=485390 Philippe ROUBACH changed: What|Removed |Added Summary|25 % sync korganizer -> G |0 % sync korganizer -> G |calendar|calendar -- You are receiving this mail because: You are on the CC list for the bug.
[libkgapi] [Bug 485390] 0 % sync korganizer -> G calendar
https://bugs.kde.org/show_bug.cgi?id=485390 --- Comment #1 from Philippe ROUBACH --- also, this problem blocks the sync G calendar -> korganizer. You must delete the G Groupware engine, then add it again to get a running sync G calendar -> korganizer. -- You are receiving this mail because: You are on the CC list for the bug.
