Public bug reported:
I'm trying to create a resident key on my (SOMU) fido2 key using the
following command:
$ ssh-keygen -t ed25519-sk -O resident -f ~/.ssh/somu_id -O verify-required
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generat
My apologies for the noise, I was referencing an old local compiled
fido2 library instead of the package:
libfido2.so.1 => /usr/local/lib/libfido2.so.1 (0x7fb8621bd000)
Bug can be closed.
** Changed in: openssh (Ubuntu)
Status: New => Invalid
--
You received this bug notification
** Package changed: ubuntu => wayland (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1963818
Title:
Upgrading to 22.04 on wayland session closes session
Status i
** Package changed: ubuntu => fontconfig (Ubuntu)
** Changed in: fontconfig (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/20175
This is about the context in de Plasma desktop. My fonts were set to
Ubuntu and Ubuntu Mono and I use full hinting where anti-aliasing is
disabled to get crisp and clear fonts. This is now broken in 23.04 and
can be worked around using Verdana.
--
You received this bug notification because you ar
So, the idea is that I set anti-Aliasing to exclude 8pt to 15pt and set
hinting to full. This makes the desktop fonts render crisp and sharp,
which used to work for all fonts having decent hints, among which were
e.g. Ubuntu and Ubuntu Mono (but a lot more fonts have this). Now, none
of the fonts r
It's written to ~/.config/fontconfig/fonts.conf and it certainly is
used. I test by re-launching systemsettings. If I remove the file, fonts
are rendered using the system default (anti-aliased). Saving my settings
creates this file and uses the contents (anti-alias exclude range + full
hinting) on
No I think it's somehow deeper. Plasma honours the configuration, but
the hinting for certain fonts is broken. Correctly hinted fonts should
nicely follow pixels on a resolution restricted display. That is no
longer the case and results in ugly rendered fonts. See attachment from
the first post for
See attachment for clarification of bad/broken hinting.
In this example I'm using Verdana (correctly full hinted) to display the dialog
and choose Ubuntu Mono to be previewed (incorrectly full hinted)
** Attachment added: "hinting.png"
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug
This is what Verdana without hinting looks like, so it's clear that
hinting setting has influence on rendering of Verdana font, but doesn't
on other fonts.
** Attachment added: "no-hinting.png"
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017573/+attachment/5668370/+files/no-hint
I was trying to be as complete as possible in my bugreport but I just
checked and there is no difference under X11 (same issue).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
The latest release of Spotify client segfaults in libcurl-gnutls as can be read
in this thread on spotify support forum:
https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479
According to one participant the work-around is to install d
Fixed for me using the above mentioned PPA.
Thx!
And I agree with Guillaume that, for me, this was a major annoyance
nonetheless...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
It seems this systemd bug is related and is supposed to be fixed. I still
experience the problem however:
https://github.com/systemd/systemd/issues/7305
** Bug watch added: github.com/systemd/systemd/issues #7305
https://github.com/systemd/systemd/issues/7305
--
You received this bug notific
The fix is incorporated in 236, but the systemd developer suggests the
fix could be backported to 234. What version of systemd will be in
bionic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.
In the meantime the problem has been narrowed down to QFont::toString()
appending too much fontstyle information.
https://bugs.kde.org/show_bug.cgi?id=376630
https://bugs.kde.org/show_bug.cgi?id=378523
With Qt being alerted and kde having more issues reported I think
problem reveived more than en
No, only half of the problem was caused by libfreetype 2.8.0 (normal TT
hinting) but should indeed be updated as soon as possible in Artful, the
other part (bold/italics) is a Qt 5.9.x problem and needs some love from
Qt.
--
You received this bug notification because you are a member of Ubuntu
To
Then, my advise would be to backport the TT hinting fix to 2.8.0 in
Artful for all those not able to use 2.8.1 from ppa? Bionic is still a
long way to go. Anyway, all is fine for me, so feel free to decide as
you see fit...
--
You received this bug notification because you are a member of Ubuntu
In my (humble) opinion the best way to solve this thinking forward, is to
upgrade to freetype 2.8.1, plasma 5.11 and adjust font queries in kdeglobals
and trolltecht.conf without weight specific strings as described in this bug:
https://bugreports.qt.io/browse/QTBUG-63792
It's also nice to see th
Thanx to the fix in #23 I can now listen to uninterrupted A2DP audio
from my laptop and use (or better, -not- use) the mouse without causing
audio stutter. I'm running Kubuntu Wily (Frameworks 5.15.0, Applications
15.08.2, Plasma 5.4.2, Bluez 5.35).
--
You received this bug notification because y
freetype 2.8.1 fixes hinting of normal fonts, but not bold.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to freetype in Ubuntu.
https://bugs.launchpad.net/bugs/1722508
Title:
Font hinting appears broken on 17.10 beta
Statu
I'm using Ubuntu for all Desktop fonts. Attached is a screenshot of the problem.
Title is Ubuntu 9 bold, menu is Ubuntu 9 and terminal is Ubuntu Mono 9.
This is after updating Artful's libfreetype 2.8.0 to 2.8.1 from Michael
Marley's PPA.
** Attachment added: "Screenshot_20171013_191730.png"
It seems a plasma desktop bug, window title renders fine now, but bold
fonts in panel and kmail still render the ugly way.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to freetype in Ubuntu.
https://bugs.launchpad.net/bugs/172
I meant to write "fine after upgrade to plasma 5.11".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to freetype in Ubuntu.
https://bugs.launchpad.net/bugs/1722508
Title:
Font hinting appears broken on 17.10 beta
Status in f
Fixed, for me, in (K)Ubuntu 17.10, Artful.
libqt4 4.8.7
libqt5 5.9.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1684506
Title:
QT4 Trolltech.conf settings lost after r
I think I'm looking at a Qt problem, but still relevant for 17.10 as a whole I
guess?
https://bugreports.qt.io/browse/QTBUG-63792
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to freetype in Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
Since the update to Kubuntu 17.04 / plasma 5.9.4 all qt4 based
applications (e.g. KeePassX) render using wrong font instead of my
personal configured font. When I run qtconfig-qt4 (4.8.7), change font
and click 'save', a fresh .config/Trolltech.conf is saved, contains the
corr
27 matches
Mail list logo
