Snaps not running in fedora based app qube

After a reboot, previously running snaps in an app-vm are not working and the template says:

[user@fedora-35 ~]$ snap install bitwarden
error: cannot install "bitwarden": persistent network error: Post
       "https://api.snapcraft.io/v2/snaps/refresh": dial tcp: lookup api.snapcraft.io: Temporary
       failure in name resolution

The docs have been followed precisely, the system is up-to-date by minute and looks healthy.

Are you trying to install bitwarden in template? You need to install it in app qube as per docs:

1 Like

My mistake. However, in my app qube called snap-fedora, bitwarden and telegram-desktop are not working, only teams is.

The exact same installation of QubesOS on the Laptop as for the Workstation here, works fine for all three snaps.

[user@snap-fedora ~]$ snap run bitwarden
/snap/bitwarden/67/bitwarden: error while loading shared libraries: libatk-1.0.so.0: cannot open shared object file: No such file or directory
[user@snap-fedora ~]$ snap remove bitwarden
bitwarden removed
[user@snap-fedora ~]$ snap install bitwarden
bitwarden 2022.5.0 from 8bit Solutions LLC (bitwarden✓) installed
[user@snap-fedora ~]$ snap run bitwarden
A JavaScript error occurred in the main process
Uncaught Exception:
SystemError [ERR_SYSTEM_ERROR]: A system error occurred: uv_interface_addresses returned Unknown system error 1 (Unknown system error 1)
    at Object.networkInterfaces (node:os:259:16)
    at getIPType (/snap/bitwarden/67/resources/app.asar/main.js:31987:34)
    at new Defaults (/snap/bitwarden/67/resources/app.asar/main.js:31962:21)
    at new Parser (/snap/bitwarden/67/resources/app.asar/main.js:32016:14)
    at Object.73853 (/snap/bitwarden/67/resources/app.asar/main.js:31257:19)
    at __webpack_require__ (/snap/bitwarden/67/resources/app.asar/main.js:57309:42)
    at Object.65186 (/snap/bitwarden/67/resources/app.asar/main.js:32081:14)
    at __webpack_require__ (/snap/bitwarden/67/resources/app.asar/main.js:57309:42)
    at Object.75898 (/snap/bitwarden/67/resources/app.asar/main.js:32051:13)
    at __webpack_require__ (/snap/bitwarden/67/resources/app.asar/main.js:57309:42)
[1810:0604/063942.286315:ERROR:browser_main_loop.cc(269)] Gdk: gdk_atom_intern: assertion 'atom_name != NULL' failed
[1810:0604/063942.287096:ERROR:browser_main_loop.cc(269)] Gdk: gdk_atom_intern: assertion 'atom_name != NULL' failed
Gtk-Message: 06:39:42.404: Failed to load module "pk-gtk-module"
Gtk-Message: 06:39:42.425: Failed to load module "pk-gtk-module"
[1810:0604/063942.615841:ERROR:address_tracker_linux.cc(196)] Could not create NETLINK socket: Operation not permitted (1)
[1810:0604/063942.714577:ERROR:udev_watcher.cc(52)] Failed to initialize a udev monitor.
[1989:0604/063943.997044:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[2004:0604/063944.019995:ERROR:address_tracker_linux.cc(196)] Could not create NETLINK socket: Operation not permitted (1)
[2011:0604/063944.231003:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
^C[user@snap-fedora ~]$ snap run telegram-desktop

(telegram-desktop:2036): Gdk-CRITICAL **: 06:42:39.820: gdk_atom_intern: assertion 'atom_name != NULL' failed

(telegram-desktop:2036): Gdk-CRITICAL **: 06:42:39.821: gdk_atom_intern: assertion 'atom_name != NULL' failed
Gtk-Message: 06:42:39.849: Failed to load module "canberra-gtk-module"
Gtk-Message: 06:42:39.849: Failed to load module "pk-gtk-module"
Gtk-Message: 06:42:39.855: Failed to load module "canberra-gtk-module"
Gtk-Message: 06:42:39.855: Failed to load module "pk-gtk-module"
[user@snap-fedora ~]$ snap run teams

[user@snap-fedora ~]$

Do you have the same fedora-35 template on your laptop? If yes then maybe you have some additional packages installed there?

Nope, all is identical.

If bitwarden was working half an hour ago and I reboot, then it ceases to just now on the more reliable Laptop. In my experience snaps are unstable. Can anyone reproduce this behaviour?

Are the developers aware, should I create an issue on github at best?

I figured part of the problem after a long time:

snap remove name
snap install name

as opposed to

snap refresh

gets all those snaps up and running again e.g. after an template update.

That said, snaps do not seem to work on a desktop workstation with non-integrated graphics i.e. a graphics card. Only teams under fedora-36 runs fine, bitwarden and telegram-desktop are not.