barrel0luck

Sorry, I'm still facing the issue. I'm on Fedora 31 as well. Using the default GNOME Wayland session. All extensions disabled. On Fri, Jan 24, 2020 at 11:53 AM Aadil...

Sure! And thanks for developing this awesome package! I hope you can maintain it for long! Here's the code you can use to reproduce the issue on a low end...

I must note that I'm using R on Fedora Linux. However, if the issue is with the code, maybe a variable (or more) that grows with each iteration of a...

Thanks for the quick reply. I'd tried using that path before, but then I get this message: **Julia could not be started. We tried to launch Julia from: /snap/bin/julia This...

I think I made some progress. I tried changing the path to **/snap/bin/julia-stable** This produces the following message: **Julia could not be started. We tried to launch Julia from: /snap/bin/julia-stable...

To start Julia in a terminal, I just run `julia-stable`. Running `julia-stable --version` in the terminal works and produces the output `julia version 1.0.0`. But I can't get Juila to...

Yup, doing that gives the `Coudln't resolve version.` error as well.

Thanks for this. I've been able to use the non-snap version of Julia in Atom as well, but not the snap version, which is the subject of this bug. So...

That's throwing the same error. Maybe someone else can try?

Is this relevant?: https://github.com/mortenpi/julia-snaps