Whitelisted allowedURLschemes breaks some desktop apps

Bug #1776873 reported by Alan Pope 🍺🐧🐱 🦄 on 2018-06-14
This bug affects 6 people
Affects Status Importance Assigned to Milestone

Bug Description


snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap".

We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible.


Telegram Desktop: tg:/
Github Desktop: git:/
IRCCloud Desktop: irc:/

These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers?

Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes.

Zygmunt Krynicki (zyga) on 2019-09-20
Changed in snapd:
status: New → Triaged
importance: Undecided → Wishlist
Zygmunt Krynicki (zyga) wrote :

The whitelist exists because it acts as a mediation layer where we can at least review the application interpreting the input from the snap world. It is true that this is an inconvenience but the _current_ plan is to keep the whitelist in place and expand it on a case-by-case.

Kevin Funk (kfunk) wrote :

This causes a significant annoyance in the Snap-based Chromium (from Ubuntu 19.10).

There should be a way to a) ignore that whitelist or b) make it extendable by the user. Having that hard-coded in code makes no sense.

Is there an upstream task / bug report for this I can track?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers