Open Bug 1757263 Opened 3 years ago Updated 2 years ago

Thunderbird calendar subscription has no effect with nextcloud caldav server

Categories

(Calendar :: General, defect)

Thunderbird 99
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: wf, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:97.0) Gecko/20100101 Firefox/97.0

Steps to reproduce:

create new calendar using "+" button in calendar view
select "im Netzwerk"
add username and nextcloud addess and click "Kalender Suchen"
enter password
calendar search is successful
select one or more calendars (tried both options)
click "Abonnieren"

Actual results:

nothing visible. There seems to be no effect what so ever

Expected results:

The calendar entries should show or an error message appear that explains the failure.

Component: Untriaged → General
Product: Thunderbird → Calendar
Summary: Thunderbird calender abbonement has no effect with nextcloud caldav server → Thunderbird calendar abandonment has no effect with nextcloud caldav server
Summary: Thunderbird calendar abandonment has no effect with nextcloud caldav server → Thunderbird calendar abonment has no effect with nextcloud caldav server
Summary: Thunderbird calendar abonment has no effect with nextcloud caldav server → Thunderbird calendar ahas no effect with nextcloud caldav server
Summary: Thunderbird calendar ahas no effect with nextcloud caldav server → Thunderbird calendar subscription has no effect with nextcloud caldav server

Abonnieren -> Subscription (i am not sure whether the english Thunderbird uses that wording since i am using a german locale)

Wolfgang, are you still seeing this when using the latest beta?

Flags: needinfo?(wf)
Whiteboard: [closeme 2023-01-20]

@Wayne Mercy - thank you for working on this. My current Thunderbird is 102.6.1 and i never retried and i a not too motivated to try out a beta as frustrated as i am with how bug reports in Thunderbird have been handled in the past. See bug 1791358 for an over 4 year old problem that is essential and giving us trouble almost daily but it not fixed.

Flags: needinfo?(wf)

I suggested testing beta because your bug report cites version 99, which is a beta-only version.

But were you actually using version 91? If you were using version 91, we only need to know whether version 102 still fails.

Flags: needinfo?(wf)

https://bugzilla.mozilla.org/show_bug.cgi?id=1638262 has the description of the current behavior yes 102 still fails

Flags: needinfo?(wf)
Whiteboard: [closeme 2023-01-20]

102.12.0 still has the problem

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