Skip to content
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

Link not opening in browser when clicked #38

Closed
Fire-Dragon-DoL opened this issue Aug 3, 2018 · 9 comments
Closed

Link not opening in browser when clicked #38

Fire-Dragon-DoL opened this issue Aug 3, 2018 · 9 comments

Comments

@Fire-Dragon-DoL
Copy link

Fire-Dragon-DoL commented Aug 3, 2018

Whenever I click on a link in discord, nothing happens. Nothing is opened in the browser.

If I use the discord debian package, all good.

I'm not sure what's causing this only with the snap version. I'm on Kubuntu 18.04 and use google chrome (install from apt).

I'd love some direction on how to debug this. I know there is very little information, so it's a hard guess.

@Sslaxx
Copy link

Sslaxx commented Nov 10, 2018

Don't think this is a Snap-only bug - running into this issue using the official deb packages from the Discord site.

@Fire-Dragon-DoL
Copy link
Author

I swapped between the two and the official package works perfectly for me @Sslaxx

@Fuseteam
Copy link

Snap worked perfectly for me tho

@MuffinCollector
Copy link
Contributor

Installing xdg-utils (in arch) fixed this for me.

@Fire-Dragon-DoL
Copy link
Author

That can explain the problem. In Kubuntu there is currently a bug where xg-utils doesn't work, unless you install conqueror (which is not default)

@emil-backstrand
Copy link

I have the same problem(arch), I do believe my problem started when I installed Chrome/Chromium to try a few things out(my default browser is Firefox) and no no links will work any more.
I'd very much appreciate any help fixing this issue.

@Storm-Engineer
Copy link

Also having this on Arch, and it's not only links but anything, including viewing the original of images.

It just started on its own, though Chrome was installed already before that so could still be related.

@Fuseteam
Copy link

i do not have this issue fwiw

@merlijn-sebrechts
Copy link
Member

Thanks for reporting everyone!!

This appears to be fixed now in the latest version of the snap, so I'm closing this issue now. Please comment if this is not the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants