** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
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
Great! Thanks for testing. This will slowly flow into other channels.
--
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
Yes, this build does fix the issue.
** Attachment added: "snap_list_chromium_2023-10-16.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+attachment/5709904/+files/snap_list_chromium_2023-10-16.png
--
You received this bug notification because you are a member of
It's built now, please have a look if it fixes the issue now.
--
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
Ah, sorry, silly I dispatched builds a bit before I committed changes.
At least both of us learned something new about the snapshots.
I'll build again and let you know, thanks for your disposition in
testing the fix.
--
You received this bug notification because you are a member of Desktop
Nathan,
Thanks for the full recipe. I learned something new!
Unfortunately the problem still exists for me with this update.
** Attachment added: "snap_list_chromium_2023-10-13.png"
So I followed up there and now I know the full recipe for you, with no
need to worry about backwards incompatibility:
* [Create a snapshot] snap save chromium
* [Switch to edge] snap refresh --edge chromium
* Launch Chromium normally, see if the problem is fixed
* [Switch back to stable (if
Andy, I released a tentative fix to the edge channel.
If you want to try it, refresh your snap with
snap refresh --edge chromium
Please note that a transition back to stable channel might not always be
smooth (e.g. password storage can become incompatible), so you could
generate a snapshot
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
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
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
--
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
I'll take a good guess that you cannot actually notice the visual
difference between Adwaita and Adwaita-modified in Chromium — please
confirm or deny this.
That is correct. No visual difference between Adwaita and
Adwaita_modified. My modifications are only to the GTK-2.0 portion of
the theme
OK, I managed to reproduce the issue.
> Proposition <
Chromium loads a dark theme when it finds a theme but cannot read it. Chromium
loads a light theme when it doesn't find a theme.
I'll take a good guess that you cannot actually notice the visual
difference between Adwaita and
Does it work with GTK_THEME=Adwaita_modified?
No it does not. Setting GTK_THEME=Adwaita_modified is the same as no
GTK_THEME= entry.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
> --->
> 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?
> <---
I don't think so, that should be a valid use case, we can surely rule
out the possibility of XFCE setting the system
--->
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
Given that this stopped working for you exactly in 117.0.5938.149, which
included some related changes (e.g. changing the default XDG_DATA_HOME),
one of them is probably affecting you here.
But before we continue, please clarify this: You only notice it not only
in the stderr log but also in
Nathan,
$HOME/.config/gtk-3.0/settings.ini does not exist.
--
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
What is $HOME/.config/gtk-3.0/settings.ini?
--
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
Do you have a reproducer recipe?
I tried with various themes I found in /usr/share/themes:
GTK_THEME=Yaru-viridian chromium
GTK_THEME=Yaru-blue chromium
and it seems to be working fine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Sorry, it looks like results from "$snap connections chromium" lost
formatting in my previous post. Attached is a screen shot of the
terminal output
** Attachment added: "snap_connections_chromium.png"
The "Theme parsing error" in the Bug Description appears to be a
permission error. The theme I am using is based on Adwaita. I copied
/usr/share/themes/Adwaita to
/home/aej/.local/share/themes/Adwaita_modified and modified the gtk-2.0
portion of the theme.
More than likely your GTK theme isn't included in the gtk-common-themes
snap, which is required for the chromium snap to be able to follow your
GTK theme.
See https://github.com/ubuntu/gtk-common-themes
Also check your snap connections, such as sudo snap connect
chromium:removable-drives
**
22 matches
Mail list logo
