Cannot launch snaps

Bug #1905077 reported by Radu Cosma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snap-store-desktop
New
Undecided
Unassigned
snapd
Incomplete
Undecided
Unassigned

Bug Description

Installed Ubuntu 20.10. Tried to run snap-store and on X server I get:

19:05:33:0778 Gtk cannot open display: :0

On Wayland, I get an error about snap not finding my theme and a segmentation fault.

I also ran the chromium snap and that also did not work.

I have a dual monitor setup, both 1920x1080 @ 60hz.

Revision history for this message
Radu Cosma (raduacosma) wrote :

As an update, now on Wayland, the first time I run snap-store in the terminal I get no console output and nothing happens, the second time this is reported:

❯ snap-store
19:20:35:0813 dbind Could not open X display
19:20:35:0815 Gtk Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /var/lib/snapd/hostfs/usr/share/themes/Adwaita-nord/gtk-3.0/gtk.css: Permission denied
19:20:35:0851 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, hardcoded-popular, modalias, odrs, packagekit-refine, rewrite-resource, packagekit-history, provenance, snap, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata
19:20:35:0851 Gs disabled plugins: dpkg, dummy, fedora-langpacks, fedora-pkgdb-collections, repos
19:20:35:0908 Gs /etc/PackageKit/Vendor.conf file not found
19:20:36:0026 Pango pango_font_get_hb_font: assertion 'PANGO_IS_FONT (font)' failed
[1] 17938 segmentation fault (core dumped) snap-store

Revision history for this message
Radu Cosma (raduacosma) wrote :

For Chromium on Wayland, running chromium in the terminal yields this:

[18845:18845:1120/202231.087920:ERROR:browser_main_loop.cc(1434)] Unable to open X display.

Revision history for this message
Radu Cosma (raduacosma) wrote :

Update: since this all seems very similar to Bug #1897224, I will report back when the fix lands. However, my apps not only do not work on wayland, they do not work on X either, so maybe that is a different issue. Furthermore, a segmentation fault should not occur in any case for the snap-store. Therefore, I will keep this bug open.

Revision history for this message
Maciej Borzecki (maciek-borzecki) wrote :

Do you have any logs? Is it a problem connecting to the X server or does the snap (snap store?) segfault after it has started?

Revision history for this message
Radu Cosma (raduacosma) wrote :

Those mentioned in the above comments (the snap-store one is in the seccond comment) are all I have. If you can tell me how to get more logs I'll do that. But from the log that I posted above, it seems that there is a problem with the X server, which also impacts Chromium, but there is a problem with the font loading, as there is an assert error, and then a segmentation fault that occurs afterwards. I am not sure why the X-server is called at all for the snap-store, as gtk uses Wayland.

Revision history for this message
Maciej Borzecki (maciek-borzecki) wrote :

Try disabling access control by running `xhost +` and see what happens then.

For snap-store you can try the edge channel (snap refresh --edge snap-store), afaik it contains some improvements related to font cache handling which may well fix the segfault.

Changed in snappy:
status: New → Incomplete
Michael Vogt (mvo)
affects: snappy → snapd
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.