After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 790503 - Cannot import calendar from PagerDuty URL
Cannot import calendar from PagerDuty URL
Status: RESOLVED OBSOLETE
Product: gnome-calendar
Classification: Applications
Component: General
3.26.x
Other Linux
: Normal normal
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
Depends on:
Blocks:
 
 
Reported: 2017-11-17 14:40 UTC by domagoj.trsan
Modified: 2017-11-24 22:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description domagoj.trsan 2017-11-17 14:40:55 UTC
I submited the bug originally to Launchpad: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1732496

I noticed I cannot import a calendar from PagerDuty (https://www.pagerduty.com).

When I try to add online calendar (Settings -> Add -> From Web) in "Add calendar" dialog, button "Add" stays disabled when I enter URL.
If I download the calendar and add it via "From file" method, everything works.

When I ran gnome-calendar with debug option (--debug) the following was logged to the console (I removed all sensitive information).

15:00:04.0161 GcalSourceDialog: DEBUG: Detected host: '<REMOVED>.pagerduty.com', path: '/<REMOVED>'
15:00:04.0162 GcalSourceDialog: DEBUG: Trying to connect without credentials...
15:00:04.0912 GcalSourceDialog: DEBUG: [source-dialog] error: Failed to get properties: HTTP error code 404 (Not Found): The server responded with an HTML page, which can mean there’s an error on the server or with the client request. The used URI was: https://<REMOVED>.pagerduty.com/<REMOVED>

Unfortunately, I cannot post PagerDuty URL here because it contains sensitive information.

I can normally download the calendar via curl. It does not require any credentials. I'm also importing it into Google Calendar without any issues. If I create a dummy calendar in Google Calendar and I try to import it via public URL everything works as expected. I'm having issues only with importing of the PagerDuty calendar.

I tried to sniff traffic with mitmproxy but I don't see any requests logged to mitmproxy of URLs I entered to "Add calendar" dialog. Is it possible that "Add calendar" dialog does not respect proxy configuration? I wanted to compare what's different in curl vs gnome-calendar request/response.

Any suggestions how to debug it?

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-calendar 3.26.2-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 15 16:40:36 2017
InstallationDate: Installed on 2017-10-21 (25 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)
Comment 1 Thiago 2017-11-18 22:25:12 UTC
Hi there.

Wondering if it is possible to create a new calendar (PagerDuty) with a few events and share this link with us so we could help you to debug it and fix it.
Comment 2 domagoj.trsan 2017-11-21 19:22:19 UTC
Here is a new calendar: https://boxever.pagerduty.com/private/0f348c33388bb10568fecb471e819ba147b569473cc6d9ea8e0959434eb43942/feed/PY6IUQF


19:17:45.0180          GcalSourceDialog:    DEBUG: [source-dialog] error: Failed to get properties: HTTP error code 404 (Not Found): The server responded with an HTML page, which can mean there’s an error on the server or with the client request. The used URI was: https://boxever.pagerduty.com/private/0f348c33388bb10568fecb471e819ba147b569473cc6d9ea8e0959434eb43942/feed/PY6IUQF 

Thanks!
Comment 3 Georges Basile Stavracas Neto 2017-11-24 22:46:19 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/216.