--->
But before we continue, please clarify this: You only notice it not only
in the stderr log but also in the user interface itself, which doesn't
use your custom theme, as it did before that release, right?

I first noticed the problem when I started the chromium snap normally using a 
desktop file.  It was not using my system theme like all previous versions of 
the chromium snap.  It was using some sort of dark theme where my system theme 
is light.  At that point I started the chromium snap from the terminal where I 
noticed the "Permission denied" error I mention in the Bug Description.
<---

--->
How do you set your theme?

I set my theme using xfce4-settings-manager "Appearance" and "Window Manager" 
selections.  Should I be doing something else?
<---

--->
$HOME/snap/chromium/current/.local/share/themes is a broken link because 
/snap/chromium/XXXX/data-dir does not exist in either snap 2655 (the one I am 
complaining about) or snap 2642 (which works fine for me).
<---

--->
chromium file:///snap/chromium/current/data-dir/themes

Does list a bunch of theme directories
<---

--->
As I stated at the end of Comment #2, the chromium snap works fine if I add 
GTK_THEME=Adwaita to the Exec= line in the application's desktop file.
<---

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2038727

Title:
  Chromium snap theme parsing error

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not
  following my GTK theme.  Starting the Chromium snap from the terminal
  yields a theme parsing error:

  (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error:
  gtk.css:1:0: Failed to import: Error opening file
  /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css:
  Permission denied

  Previous versions of the Chromium snap have not had this problem.
  Debian 11 + XFCE.  I have been running the chromium snap for about two
  years without an issue like this on this system.  I have reverted to
  the previous version of the chromium snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to