Additional observation:
If I refresh into FF latest/stable, the undesired line
/etc/fonts/conf.d
gets written into ~/snap/firefox/current/.config/fontconfig/fonts.conf.
I suppose the reason is that the snap from that channel is linked to
gnome-3-38-2004 which has not (yet) been updated in this r
~/snap/firefox/current/.config/fontconfig/fonts.conf was updated
"automatically" on my mantic installation. Not sure which combo of
circumstances made it happen, but I have core22 from the
latest/candidate channel. Then I refreshed firefox (switched form
latest/stable to latest/stable/ubuntu-23.10)
You still have FF 115.0-2 installed and haven't refreshed into
gnome-42-2204 latest/candidate. But with that said, there seems to be
more into it, even if I'm not able to tell exactly what. :/
If you want to see it "fixed" you can do as I mentioned in comment #16.
But it's not truly fixed until th
Thank you very much for your very speedy response to fix the problem.
New Firefox is released (115.0.1-1 built on 2023-07-07), but doesn't
fixed.
Firefox:
channels:
latest/stable:115.0.1-12023-07-07 (2880) 256MB -
latest/candidate: 115.0.1-12023-07-07 (2880) 256MB -
latest/beta:
I tried on mantic:
* Refreshed gnome-42-2204 to latest/candidate
* Opened FF
But that didn't recreate
~/snap/firefox/current/.config/fontconfig/fonts.conf . Is a later
release of the FF snap needed too?
--
You received this bug notification because you are a member of Desktop
Packages, which is
There is a new build of gnome-42-2204 in the candidate channel now if
someone wants to give it a try and confirm if it indeed fixes the issue
(if you try on firefox you need a core22 based version, which is the
default in lunar)
--
You received this bug notification because you are a member of De
The fix has been merged, we will need a rebuild of the gnome-42-2204
snap next to have it working
** Changed in: language-selector (Ubuntu)
Status: New => Invalid
** Changed in: snappy
Status: In Progress => Fix Committed
--
You received this bug notification because you are a mem
An identical PR against another project...
https://github.com/snapcore/snapcraft-desktop-integration/pull/13
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/2025651
Title:
d
** Changed in: snappy
Status: New => In Progress
** Changed in: snappy
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpa
I submitted this PR:
https://github.com/snapcore/snapcraft/pull/4257
@Sebastien: Please take a look, and if you agree also pls help to get it
in.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.
That FC_DEBUG variable was useful. :)
I dropped the line:
/etc/fonts/conf.d
from:
~/snap/firefox/current/.config/fontconfig/fonts.conf
and that fixed it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
ht
On 2023-07-03 23:05, Sebastien Bacher wrote:
> Ignore my previous comment, I keep forgetting how fonts in snaps
> work. The snap doesn't have access to the /etc configuration and
> /snap/gnome-42-2204/current/etc/fonts/conf.d is used instead
Yes, unfortunately...
> did the configuration change s
Ok, doing
$ FC_DEBUG=1024 LC_CTYPE=ja_JP.UTF-8 fc-match -s sans-serif | less
gives a clue, it seems to read first the
/snap/gnome-42-2204/current/etc/fonts/conf.d configurations but then the
/etc/fonts/conf.d ones.
Confirmed by moving /etc/fonts/conf.avail/65-droid-sans-fallback.conf
away on the
Ignore my previous comment, I keep forgetting how fonts in snaps work.
The snap doesn't have access to the /etc configuration and
/snap/gnome-42-2204/current/etc/fonts/conf.d is used instead
You are right that the snap is built from jammy, did the configuration
change since jammy? Is the problem d
Ignore my previous comment, I keep forgetting how fonts in snaps work.
The snap doesn't have access to the /etc configuration and
/snap/gnome-42-2204/current/etc/fonts/conf.d is used instead
You are right that the snap is built from jammy, did the configuration
change since jammy? Is the problem d
It struck me that fontconfig prefers Noto Sans by default in lunar and
mantic, but not in the snaps if I understand it correctly since the
fonts related packages are grabbed from jammy.
As a test I made this change in mantic:
--- /usr/share/fontconfig/conf.avail/60-latin.conf.orig
+++ /usr/share/
This works for me:
$ snap run --shell firefox
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.
/home/gunnar$ cat
/snap/firefox/current/gnome-platform/etc/fonts/conf.d/70-fonts-noto-cjk.conf
...
--
You received this bug notification because you ar
The issue is probably that in the snap environment
$ cat /etc/fonts/conf.d/70-fonts-noto-cjk.conf
cat: /etc/fonts/conf.d/70-fonts-noto-cjk.conf: No such file or directory
the target /usr/share/fontconfig/conf.avail/70-fonts-noto-cjk.conf seems
to not be available
--
You received this bug notifi
64-language-selector-prefer.conf prefers Noto Sans CJK JP for sans-
serif.
65-droid-sans-fallback.conf prefers Droid Sans Fallback for sans-serif.
64 is lower than 65, so Noto is preferred over Droid.
And on top of that we have 70-fonts-noto-cjk.conf which prepends Noto
Sans CJK JP in case of a
I don't know. The behavior for deb software is expected, the behavior
for lunar and mantic snaps is unexpected.
But we do know that uninstalling fonts-droid-fallback from the host
system makes a difference wrt the snap behavior as regards Japanese font
rendering.
--
You received this bug notific
But fonts-droid-fallback is installed by default on mantic so why isn't
it creating the same problems for deb software?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/2025651
Maybe it would make a difference to simply drop fonts-droid-fallback
from this list:
https://github.com/ubuntu/gnome-
sdk/blob/gnome-42-2204/snapcraft.yaml#L245
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
** Tags added: lunar mantic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/2025651
Title:
default Japanese font in snap apps is ugly
Status in Snappy:
New
Status in langu
I hope we will figure out the reason for this snap behavior.
Otherwise there are workarounds. Not pulling fonts-droid-fallback was
mentioned above. Or this change would probably do it:
--- /usr/share/fontconfig/conf.avail/70-fonts-noto-cjk.conf.orig
+++ /usr/share/fontconfig/conf.avail/70-fonts-n
Inspired by
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/comments/35
Mantic:
$ snap run --shell firefox
$ LC_CTYPE=ja_JP.UTF-8 fc-match -s sans-serif | head
DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular"
DejaVuSans.ttf: "DejaVu Sans" "Book"
DejaVuSans-Bold.ttf: "De
lunar result:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/comments/27
jammy result:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/comments/28
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lang
** Also affects: snappy
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/2025651
Title:
default Japanese font in snap apps is ugly
27 matches
Mail list logo
