Bug 1940186 - Nextcloud Calendar and Contacts can no longer accept self signed cert for
Summary: Nextcloud Calendar and Contacts can no longer accept self signed cert for
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-calendar
Version: 34
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Igor Raits
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-17 18:42 UTC by Andrew Thurman
Modified: 2022-06-07 22:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-07 22:00:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Andrew Thurman 2021-03-17 18:42:57 UTC
Description of problem:
My Nextcloud instance has a self-signed cert, and in the past it has simply given me a dialog when adding, and a dialog in the various applications. Now I get a dialog when adding that works, a dialog when mounting that works, a dialog in using the Calendar (flatpak) that when accepted just keeps reappearing, and can only be removed by "cancelling" (not "rejecting"). Contacts simply doesn't work at all or crashes when starting.

Version-Release number of selected component (if applicable):
gnome-online-accounts

How reproducible:
Always on 34-testing
Never on 33

Steps to Reproduce:
See Above

Actual results:
See Above

Expected results:
Accept Self-Signed cert with ease

Additional info:
● ostree://fedora:fedora/34/x86_64/testing/silverblue
                   Version: 34.20210317.0 (2021-03-17T03:08:53Z)
                BaseCommit: 1d282a1c0c6594b7a3b9edc0fc61f3e3f70d08aab3cc22afbaa8c7337c914a7a
              GPGSignature: Valid signature by 8C5BA6990BDB26E19F2A1A801161AE6945719A39
           LayeredPackages: abrt-desktop

Comment 1 Debarshi Ray 2021-03-17 23:47:53 UTC
> Now I get a dialog when adding that works

This means the code in gnome-online-accounts is still working as before.

> a dialog when mounting that works

That's gvfs, and it's also working as before.

> a dialog in using the Calendar (flatpak) that when accepted
> just keeps reappearing, and can only be removed by "cancelling"
> (not "rejecting"). Contacts simply doesn't work at all or
> crashes when starting.

Looks like there's something wrong with Calendar and Contacts, or maybe evolution-data-server. At this point, gnome-online-accounts is no longer involved with the certificates.

Let's try looking at Calendar first, for no good reason other than it's alphabetically above Contacts.

Comment 2 Ben Cotton 2022-05-12 15:30:17 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-06-07 22:00:30 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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