This bug was fixed in the package pango1.0 - 1.46.2-3
---
pango1.0 (1.46.2-3) unstable; urgency=medium
* Team upload
* d/p/fc_Sort-faces-of-a-family.patch,
d/p/fontconfig_Try-harder-to-return-a-default-face.patch:
- Show regular monospace fonts in gnome-terminal's profile
This bug was fixed in the package gtk+3.0 - 3.24.23-1ubuntu2
---
gtk+3.0 (3.24.23-1ubuntu2) hirsute; urgency=medium
* debian/patches/fontchooser_Fix_family-only_mode.patch:
- Show regular monospace fonts in gnome-terminal's profile editor
and not arbitrary font styles
gtk and pango are both blocked by glib before they can migrate. In
addition to that there are a few other autopkgtest regressions blocking
pango.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900729
This bug was fixed in the package gnome-terminal - 3.38.0-1ubuntu1.1
---
gnome-terminal (3.38.0-1ubuntu1.1) groovy; urgency=medium
* debian/patches/show-font-weight-and-style-in-profile-editor.patch:
- Reverses upstream commit e5c0b4f5 for now (LP: #1900729)
-- Gunnar
pango fix uploaded to Debian
** Changed in: pango1.0 (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: pango1.0 (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Yep, works like a charm with 3.38.0-1ubuntu1.1 from groovy-proposed here
as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900729
Title:
gnome-terminal font settings show only italic version
Verified the test case using version 3.38.0-1ubuntu1.1 of gnome-
terminal, gnome-terminal-data and nautilus-extension-gnome-terminal from
groovy-proposed.
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received
Hello Darko, or anyone else affected,
Accepted gnome-terminal into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
terminal/3.38.0-1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Current status of this bug:
The gnome-terminal fix for groovy has been pushed to the VCS repo. I'm
waiting for a sponsor to upload it.
As regards hirsute: We have identified three upstream pango commits
which together with the gtk fix in hirsute-proposed fix the issue the
'right' way. The pango
** Description changed:
[Impact]
When you want to select a monospace font in gnome-terminal's profile
editor, it does not always show the regular font but rather an
- arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
- upstream commit which fixes it.
+ arbitrarily
@Gunnar, if you want to go with a revert it shouldn't need to block on
hirsute since we aren't going to go that way in the new serie but rather
cherrypick the new pango fix (we could do that now in Debian and sync
over, let know if you need help with an upload)
--
You received this bug
This is getting too complicated to handle as an SRU considering that
it's a not-so-important issue after all. So I think we should simply
revert the problematic gnome-terminal commit in groovy only, and hope
that upstream sorts it out for hirsute. So I would like to upload this
fix to groovy:
** Tags removed: verification-done
** Tags added: verification-failed
** Tags removed: verification-done-groovy
** Tags added: verification-failed-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Good catch, @Rasmus. I see the same thing, and posted my theory about
what causes it here:
https://gitlab.gnome.org/GNOME/pango/-/issues/483#note_953154
Hmm.. I'm afraid this can be called a regression. Even if the wrong
styles were shown previously, selecting any of those at least didn't
cause
indeed, i get a crash if i click on the following fonts: Bitstream Vera
Sans Mono, DejaVu Sans Mono, Inconsolata, MathJax_Vector-Bold, and
Terminus.
note that in the font chooser these font names appear to be rendered not
in their particular typeface but with the default system font so is
seems
Thanks for the speedy work! I'm afraid I'm registering problems with the
update, however.
I just got gir1.2-gtk-3.0 through -proposed, and whereas it works as
intended in so far as I can now choose Ubuntu Mono in Gnome Terminal and
get the regular font face, it seemingly introduces a bug where
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900729
Title:
gnome-terminal font settings show only italic version of ubuntu
@Darko: Yeah, it's indeed different compared to focal. But as was stated
on the upstream issue, it's an intentional design change, and probably
better for most use cases given this gtk fix.
Thanks for verifying!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
i tested it after installing libgtk-3-0 libgtk-3-common from proposed. i
can confirm that the gnome-terminal settings custom font now shows only
"ubuntu mono" when "ubuntu" is typed into the search box and therefore
solves the issue.
nevertheless, note that this is still different than what we
Ok, I think I have enough information to give a green light for this
change (especially that the Iain was +1 on getting it in as a single
fix).
** Description changed:
[Impact]
When you want to select a monospace font in gnome-terminal's profile
editor, it does not always show the
Hi Łukasz,
As regards other concurrent fixes, I first asked Iain Lane if there is
such a plan for groovy, but the most likely SRU in pipeline would be a
focal update to 3.24.23, so he gave me a 'green light' for this groovy
one.
The bug is an annoying one. Maybe the importance was set too low...
Thank you for providing fix for this! This is a bit of a tricky fix for
SRUing, because generally this is a very low-profile bug. Generally, by
principle, we usually SRU high-impact bug fixes (or other cases, as per
[1]). The main reason for this is that every change introduces risk of
new
** Description changed:
+ [Impact]
+
+ When you want to select a monospace font in gnome-terminal's profile
+ editor, it does not always show the regular font but rather an
+ arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
+ upstream commit which fixes it.
+
+ [Test case]
+
** Package changed: gnome-terminal (Ubuntu) => gtk+3.0 (Ubuntu)
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900729
Title:
On 2020-10-30 02:29, Gunnar Hjalmarsson wrote:
> Is that what we want to do?
Probably not.
https://gitlab.gnome.org/GNOME/pango/-/issues/483#note_949138
Matthias' gtk commits seem to fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Now we know from the upstream pango issue which commit caused this bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/e5c0b4f5
I confirmed that reversing that commit fixes it:
https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome-terminal
Is that what we want to do?
--
You received
this is just going in circles. i don't understand the details but it seems that:
* it's quite ok to have a monospace filter built into the gnome-terminal font
selector
* this job is really delegated to the pango lib, which uses the first fc result
to determine the spacing for the *whole* family
Thanks for upstream it, it was not unexpected they would close it,
indeed the issue is probably in pango, still they use a feature which
isn't correctly working and it's reflecting negatively on the
application so they could have decided to revert the filter until the
api behavior is corrected...
upstream has closed the issue on gnome-terminal, saying
"gnome-terminal only shows fonts that are monospace, as reported by pango. So
if this font doesn't show up correctly, it's a problem in the font (or pango),
not gnome-terminal."
i've poked the
@seb128 done https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/308
** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #308
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/308
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for your bug report, could you perhaps report it upstream on
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues
the behaviour changed due to https://gitlab.gnome.org/GNOME/gnome-
terminal/-/commit/0760f28a
could be due to https://gitlab.gnome.org/GNOME/pango/-/issues/483 or
similar
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-terminal (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900729
32 matches
Mail list logo
