Bug 2325952 - Crash without recovery when trying to sync calendar events from a Nextcloud server that is in maintenance mode
Summary: Crash without recovery when trying to sync calendar events from a Nextcloud s...
Keywords:
Status: CLOSED DUPLICATE of bug 2321107
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 41
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Milan Crha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-13 16:35 UTC by Matti Pulkkinen
Modified: 2024-11-15 11:38 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-15 11:38:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Crash backtrace (20.27 KB, application/gzip)
2024-11-14 19:11 UTC, Matti Pulkkinen
no flags Details

Description Matti Pulkkinen 2024-11-13 16:35:45 UTC
I have added my Nextcloud account as an "online account" in GNOME Settings, and I use that to sync up my calendar events. When the Nextcloud server goes into maintenance mode (which is every night in my case), before too long I will get a crash report about evolution-data-server on my PC. My calendar events vanish, and they don't get restored even after the Nextcloud server comes back up. I have to check and uncheck calendar syncing through GNOME Settings to get my calendar events to show up again.

Reproducible: Always

Steps to Reproduce:
1. Add a Nextcloud account through GNOME Settings and enable calendar syncing
2. Set the Nextcloud server to maintenance mode, and then wait
Actual Results:  
Evolution-data-server crashes and doesn't start syncing calendar events again until its manually toggled off and back on again.

Expected Results:  
No crash, and successful recovery of operations once the Nextcloud server comes back up.

Evolution-data-server version: 3.54.1-1.fc41

Comment 1 Milan Crha 2024-11-14 07:14:34 UTC
Thanks for a bug report. It's very hard to guess what went wrong without a backtrace of the crash. As you receive d crash notice, thus I suppose the ABRT caught the crash, could you get the backtrace from there, please?

A blind guess is that this is crashing due to a libsoup3 bug:
https://gitlab.gnome.org/GNOME/libsoup/-/issues/386

Comment 2 Matti Pulkkinen 2024-11-14 19:11:32 UTC
Created attachment 2057792 [details]
Crash backtrace

Crash backtrace from last night, as requested.

Comment 3 Milan Crha 2024-11-15 11:38:26 UTC
Thanks for the update. I can confirm the crash is the upstream bug I guessed. It's also filled here as bug #2321107, thus I mark this as a duplicate of it.

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


Note You need to log in before you can comment on or make changes to this bug.