Open dandv opened 1 year ago
That's weird!
I'm quite sure it can't be a conflict with the Flatpak. Snap and flatpak shouldn't conflict at all.
The two reviews are due to an issue that's already fixed. We accidentally pushed an ancient version of signal to users, but everyone should have automatically updated to a later version.
{"level":50,"time":"2023-11-25T22:34:48.250Z","msg":"Error occurred in handler for 'net.resolveHost': {}"}
- looks like DNS?
One rather brutal way to test the network connectivity from inside the snap is to get a shell inside the snap, and use netcat, like this:
alan@earth:~$ snap run --shell signal-desktop
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
alan@earth:/home/alan$ nc google.com 80
GET / HTTP/1.0
If after typing the nc line you get a host resolution issue, then there's a DNS issue. If you can get to type the GET
line, and press enter, you should get a screen full of javascript.
Exit with CTRL+D.
I get a slightly different prompt, but indeed, the DNS lookup fails:
How can I troubleshoot this?
@dandv are you running any other snaps? This seems to be a snapd problem. It might be useful to create a post on forum.snapcraft.io explaining this issue so the snapd folks can help us out.
What happened?
When I launch the snap, I get this screen:
I installed accidentally both the flatpak and the snap installed, then I deleted the flatpak. Is it possible that this caused the issue?
What should have happened?
I do have Internet access, and "Retry" doesn't work. Here are the permissions of the snap:
Output of
snap info $snap_name
Output of
snap connections $snap_name
Output of
snap version
Relevant log output
Teminal output of app
Other info
The Discover reviews mention that the app can't connect:
At https://snapcraft.io/signal-desktop I don't see any way to install an older version.