New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authenticating and xdg-open #570

b-zee opened this Issue Feb 1, 2019 · 1 comment


2 participants
Copy link

b-zee commented Feb 1, 2019

Due to a bug in xdg-open a registered protocol scheme like safe-alphachars01234 won't be opened correctly due to the digits in there.

Also, because the desktop entry files containing quoted values in the Exec key --- like Exec="/usr/bin/safe-browser" %u --- xdg-open won't be able to open the browser binary. (

Also see this topic on SAFE Dev Forum about users encountering the issue:

@joshuef joshuef added the bug label Feb 7, 2019


This comment has been minimized.

Copy link

joshuef commented Feb 7, 2019

Nice research @b-zee.

We could (potentially) negate the xdg issue with opn perhaps (as that ships with its own), assuming that's up to date...

Coupled with the string escaping this might solve a few xdg type issues 👍

@joshuef joshuef added this to Needs triage in Upcoming release ('master' branch) via automation Feb 7, 2019

@joshuef joshuef added the help wanted label Feb 7, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment