[Solved] Where or how do I report this bug with Gnome Characters and Communitheme Snap?


#1

Edit: I was certain I checked, contact info for this snap and couldn’t find anything at the time, but now it works (snap info gnome-characters | grep “^contact:”). I filed #LP:1828664

I’m using 18.04 and the Characters snap worked fine until it was updated a few weeks ago. I’m also using the Communitheme snap which seems to be involved in triggering the bug. Window decorations and sidebar of the app are not visible except some white text/glyphs.

Plain text:

(org.gnome.Characters:17824): Gtk-WARNING **: 20:59:46.674: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /snap/communitheme/current/share/themes/Communitheme/gtk-3.20/gtk.css: Permission denied
Gjs-Message: 20:59:46.676: JS LOG: Zeichen-Anwendung gestartet

(org.gnome.Characters:17824): GnomeDesktop-WARNING **: 20:59:47.985: Failed to load XKB rules file /usr/share/X11/xkb/rules/evdev.xml: Failed to open file “/usr/share/X11/xkb/rules/evdev.xml”: No such file or directory

I’m not sure where to report this, it’s said to be an officially supported snap by Canonical but it has no bug tracking on launchpad (1, 2) as far as i can see, not on GitHub, not contact in snap info as other packages have or on the respective snapcraft page. And I also doubt that the Gnome bugtracker is the right place when another snap is involved.

Can someone please give me directions?


#2

I’m not allowed to post more than 2 links, sorry for this crude workaround:

I'm not sure where to report this, it's said to be an [officially supported snap by Canonical](https://forum.snapcraft.io/t/snaps-officially-supported-by-canonical/1719)
but it has no bug tracking on launchpad as far as i can see, not on [GitHub](https://github.com/GNOME/gnome-characters),
not contact in snap info as [other packages](https://askubuntu.com/a/1005850/40581) have or on the [respective snapcraft page](https://snapcraft.io/gnome-characters).
And I also doubt that the Gnome bugtracker is the right place when another snap is involved.

#3

It turns out this only happens with the communitheme snap installed.


#4

I found that his is (also) caused by a broken symlink as described here: https://askubuntu.com/a/1142292/40581