from:"mrvanes"

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

2023-04-25 Thread mrvanes

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/bugs/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017573/+subscriptions


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

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

2023-04-24 Thread mrvanes

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-hinting.png

-- 
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/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017573/+subscriptions


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

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

2023-04-24 Thread mrvanes

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/2017573/+attachment/5668365/+files/hinting.png

-- 
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/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017573/+subscriptions


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

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

2023-04-24 Thread mrvanes

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 an example.

I am not sure what part is responsible for rendering the fonts under
Wayland, hence the ansence of package name on the original post.

-- 
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/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017573/+subscriptions


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

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

2023-04-24 Thread mrvanes

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 the next launch.

** Attachment added: "fonts.conf"
   
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017573/+attachment/5668239/+files/fonts.conf

-- 
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/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017573/+subscriptions


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

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

2023-04-24 Thread mrvanes

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 render correctly hinted EXCEPT the Microsoft fonts, of
which Verdana and Tahoma are the most famous examples.

So the problem is not restricted to Ubuntu and Ubuntu Mono, those are
just a examples of the fonts that I used before and that don't correctly
hint anymore, but there's many more (all except MS?) that now lack
proper hinting.

-- 
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/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017573/+subscriptions


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

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

2023-04-24 Thread mrvanes

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 are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017573/+subscriptions


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

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

2023-04-24 Thread mrvanes

** 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/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017573/+subscriptions


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

[Touch-packages] [Bug 1987736] Re: ssh-sk-helper undefined symbol fido_cred_set_clientdata

2022-08-26 Thread mrvanes

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 because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1987736

Title:
  ssh-sk-helper undefined symbol fido_cred_set_clientdata

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  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 generation.
  Enter PIN for authenticator: 
  /usr/lib/openssh/ssh-sk-helper: error while loading shared libraries: 
libcbor.so.0: cannot open shared object file: No such file or directory
  ssh_msg_recv: read header: Connection reset by peer
  client_converse: receive: unexpected internal error
  reap_helper: helper exited with non-zero exit status
  Key enrollment failed: unexpected internal error

  To start, /usr/lib/openssh/ssh-sk-helper references the shared library
  libcbor by libcbor.so.0, which is not created by the libcbor0.8
  package. After creating a symbolic link for libcbor.so.0 to
  libcbor.so.0.8, ssh-sk-helper continues, but now fails on an undefined
  symbol: fido_cred_set_clientdata:

  $ ssh-keygen -t ed25519-sk -O resident -f ~/.ssh/somu_id
  Generating public/private ed25519-sk key pair.
  You may need to touch your authenticator to authorize key generation.
  Enter PIN for authenticator: 
  /usr/lib/openssh/ssh-sk-helper: symbol lookup error: 
/usr/lib/openssh/ssh-sk-helper: undefined symbol: fido_cred_set_clientdata
  ssh_msg_recv: read header: Connection reset by peer
  client_converse: receive: unexpected internal error
  reap_helper: helper exited with non-zero exit status
  Key enrollment failed: unexpected internal error

  Which is confirmed by the output of ldd:

  $ ldd -r /usr/lib/openssh/ssh-sk-helper
  linux-vdso.so.1 (0x7ffe4af2e000)
  libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 
(0x7fb8621e7000)
  libfido2.so.1 => /usr/local/lib/libfido2.so.1 (0x7fb8621bd000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb861f95000)
  libcbor.so.0 => /lib/x86_64-linux-gnu/libcbor.so.0 
(0x7fb861f87000)
  libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 
(0x7fb861cac000)
  libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 
(0x7fb861c82000)
  /lib64/ld-linux-x86-64.so.2 (0x7fb862672000)
  undefined symbol: fido_cred_set_clientdata  
(/usr/lib/openssh/ssh-sk-helper)
  undefined symbol: fido_dev_get_touch_status 
(/usr/lib/openssh/ssh-sk-helper)
  undefined symbol: fido_cred_set_prot(/usr/lib/openssh/ssh-sk-helper)
  undefined symbol: fido_assert_set_clientdata
(/usr/lib/openssh/ssh-sk-helper)
  undefined symbol: fido_cred_prot(/usr/lib/openssh/ssh-sk-helper)
  undefined symbol: fido_dev_supports_cred_prot   
(/usr/lib/openssh/ssh-sk-helper)
  undefined symbol: fido_dev_get_touch_begin  
(/usr/lib/openssh/ssh-sk-helper)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1987736/+subscriptions


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

[Touch-packages] [Bug 1987736] [NEW] ssh-sk-helper undefined symbol fido_cred_set_clientdata

2022-08-26 Thread mrvanes

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 generation.
Enter PIN for authenticator: 
/usr/lib/openssh/ssh-sk-helper: error while loading shared libraries: 
libcbor.so.0: cannot open shared object file: No such file or directory
ssh_msg_recv: read header: Connection reset by peer
client_converse: receive: unexpected internal error
reap_helper: helper exited with non-zero exit status
Key enrollment failed: unexpected internal error

To start, /usr/lib/openssh/ssh-sk-helper references the shared library
libcbor by libcbor.so.0, which is not created by the libcbor0.8 package.
After creating a symbolic link for libcbor.so.0 to libcbor.so.0.8, ssh-
sk-helper continues, but now fails on an undefined symbol:
fido_cred_set_clientdata:

$ ssh-keygen -t ed25519-sk -O resident -f ~/.ssh/somu_id
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter PIN for authenticator: 
/usr/lib/openssh/ssh-sk-helper: symbol lookup error: 
/usr/lib/openssh/ssh-sk-helper: undefined symbol: fido_cred_set_clientdata
ssh_msg_recv: read header: Connection reset by peer
client_converse: receive: unexpected internal error
reap_helper: helper exited with non-zero exit status
Key enrollment failed: unexpected internal error

Which is confirmed by the output of ldd:

$ ldd -r /usr/lib/openssh/ssh-sk-helper
linux-vdso.so.1 (0x7ffe4af2e000)
libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 
(0x7fb8621e7000)
libfido2.so.1 => /usr/local/lib/libfido2.so.1 (0x7fb8621bd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb861f95000)
libcbor.so.0 => /lib/x86_64-linux-gnu/libcbor.so.0 (0x7fb861f87000)
libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 
(0x7fb861cac000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7fb861c82000)
/lib64/ld-linux-x86-64.so.2 (0x7fb862672000)
undefined symbol: fido_cred_set_clientdata  (/usr/lib/openssh/ssh-sk-helper)
undefined symbol: fido_dev_get_touch_status (/usr/lib/openssh/ssh-sk-helper)
undefined symbol: fido_cred_set_prot(/usr/lib/openssh/ssh-sk-helper)
undefined symbol: fido_assert_set_clientdata(/usr/lib/openssh/ssh-sk-helper)
undefined symbol: fido_cred_prot(/usr/lib/openssh/ssh-sk-helper)
undefined symbol: fido_dev_supports_cred_prot   (/usr/lib/openssh/ssh-sk-helper)
undefined symbol: fido_dev_get_touch_begin  (/usr/lib/openssh/ssh-sk-helper)

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1987736

Title:
  ssh-sk-helper undefined symbol fido_cred_set_clientdata

Status in openssh package in Ubuntu:
  New

Bug description:
  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 generation.
  Enter PIN for authenticator: 
  /usr/lib/openssh/ssh-sk-helper: error while loading shared libraries: 
libcbor.so.0: cannot open shared object file: No such file or directory
  ssh_msg_recv: read header: Connection reset by peer
  client_converse: receive: unexpected internal error
  reap_helper: helper exited with non-zero exit status
  Key enrollment failed: unexpected internal error

  To start, /usr/lib/openssh/ssh-sk-helper references the shared library
  libcbor by libcbor.so.0, which is not created by the libcbor0.8
  package. After creating a symbolic link for libcbor.so.0 to
  libcbor.so.0.8, ssh-sk-helper continues, but now fails on an undefined
  symbol: fido_cred_set_clientdata:

  $ ssh-keygen -t ed25519-sk -O resident -f ~/.ssh/somu_id
  Generating public/private ed25519-sk key pair.
  You may need to touch your authenticator to authorize key generation.
  Enter PIN for authenticator: 
  /usr/lib/openssh/ssh-sk-helper: symbol lookup error: 
/usr/lib/openssh/ssh-sk-helper: undefined symbol: fido_cred_set_clientdata
  ssh_msg_recv: read header: Connection reset by peer
  client_converse: receive: unexpected internal error
  reap_helper: helper exited with non-zero exit status
  Key enrollment failed: unexpected internal error

  Which is confirmed by the output of ldd:

  $ ldd -r /usr/lib/openssh/ssh-sk-helper
  linux-vdso.so.1 (0x7ffe4af2e000)
  libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 
(0x7fb8621e7000)
  libfido2.so.1 => /usr/local/lib/libfido2.so.1 (0x7fb8621bd000)
  libc.so.6

[Touch-packages] [Bug 1963818] Re: Upgrading to 22.04 on wayland session closes session

2022-03-06 Thread mrvanes

** 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 in wayland package in Ubuntu:
  New

Bug description:
  Just tried to upgrade Kubuntu from 21.10 to 22.04 in a konsole on a
  Wayland session (using do-release-upgrade) and while setting up one of
  the packages I lost the Wayland session and was left with a tiny
  cursor in the upper left corner. No way to restart a new session or
  connect a tty to inspect the running upgrade process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1963818/+subscriptions


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

[Touch-packages] [Bug 1832882] [NEW] libcurl-gnutls segfaults spotify client

2019-06-14 Thread mrvanes

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 debian
packages libgnutls30_3.6.8-1_amd64.deb and
libcurl3-gnutls_7.64.0-3_amd64.deb

Ubuntu 19.04 version of the packages:
libgnutls30 3.6.5-2ubuntu1.1
libcurl3-gnutls 7.64.0-2ubuntu1.1

As the bug can be resolved by installing debian packages, I assume
Ubuntu's version of the packages is at fault and should be upgraded to
match debian's level as soon as possible.

** Affects: curl (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1832882

Title:
  libcurl-gnutls segfaults spotify client

Status in curl package in Ubuntu:
  New

Bug description:
  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 debian
  packages libgnutls30_3.6.8-1_amd64.deb and
  libcurl3-gnutls_7.64.0-3_amd64.deb

  Ubuntu 19.04 version of the packages:
  libgnutls30 3.6.5-2ubuntu1.1
  libcurl3-gnutls 7.64.0-2ubuntu1.1

  As the bug can be resolved by installing debian packages, I assume
  Ubuntu's version of the packages is at fault and should be upgraded to
  match debian's level as soon as possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+subscriptions

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-05-17 Thread mrvanes

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/bugs/1759628

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Confirmed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+subscriptions

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

[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects

2018-02-17 Thread mrvanes

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.launchpad.net/bugs/1717995

Title:
  extra domains not removed from resolv.conf when VPN disconnects

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I use a VPN (network manager "vpnc" config) to connect to my work
  network.  The gateway is "webvpn.purestorage.com".  When I connect, I
  get "purestorage.com" added to the "search" line in my
  /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) -
  which makes perfect sense, the VPN passes this info to me and then I
  can connect to systems within the work network without having to use a
  FQDN.

  The bug (which is a regression from older versions of Ubuntu) is that
  when I lose my connection to the VPN (either because I disconnect
  explicitly, or because the network goes down or I suspend my laptop),
  the "purestorage.com" domain is not removed from those "search" lines.
  And for some reason this prevents me from resolving
  webvpn.purestorage.com (which prevents me from reconnecting to the
  VPN).

  In particular, if I connect and disconnect my VPN, I get:

   $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: resolve call failed: No appropriate name servers or 
networks for name found

  If I then edit /etc/resolv.conf by hand to remove all the
  purestorage.com entries from the search line - in other words, change

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search home.digitalvampire.org purestorage.com dev.purestorage.com

  to

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search home.digitalvampire.org

  and change nothing else, then:

   $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: 192.30.189.1
  (vpn.purestorage.com)

  -- Information acquired via protocol DNS in 25.9ms.
  -- Data is authenticated: no

  
  I'm not sure if the bug is in systemd, network manager, or some other 
package, but I'm happy to try any debugging that is helpful to resolve this (no 
pun intended).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu10
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 11:20:17 2017
  InstallationDate: Installed on 2016-09-01 (381 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901)
  MachineType: LENOVO 20FRS2FK00
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET53W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2FK00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2FK00
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717995/+subscriptions

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

[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects

2018-02-16 Thread mrvanes

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 notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1717995

Title:
  extra domains not removed from resolv.conf when VPN disconnects

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I use a VPN (network manager "vpnc" config) to connect to my work
  network.  The gateway is "webvpn.purestorage.com".  When I connect, I
  get "purestorage.com" added to the "search" line in my
  /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) -
  which makes perfect sense, the VPN passes this info to me and then I
  can connect to systems within the work network without having to use a
  FQDN.

  The bug (which is a regression from older versions of Ubuntu) is that
  when I lose my connection to the VPN (either because I disconnect
  explicitly, or because the network goes down or I suspend my laptop),
  the "purestorage.com" domain is not removed from those "search" lines.
  And for some reason this prevents me from resolving
  webvpn.purestorage.com (which prevents me from reconnecting to the
  VPN).

  In particular, if I connect and disconnect my VPN, I get:

   $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: resolve call failed: No appropriate name servers or 
networks for name found

  If I then edit /etc/resolv.conf by hand to remove all the
  purestorage.com entries from the search line - in other words, change

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search home.digitalvampire.org purestorage.com dev.purestorage.com

  to

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search home.digitalvampire.org

  and change nothing else, then:

   $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: 192.30.189.1
  (vpn.purestorage.com)

  -- Information acquired via protocol DNS in 25.9ms.
  -- Data is authenticated: no

  
  I'm not sure if the bug is in systemd, network manager, or some other 
package, but I'm happy to try any debugging that is helpful to resolve this (no 
pun intended).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu10
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 11:20:17 2017
  InstallationDate: Installed on 2016-09-01 (381 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901)
  MachineType: LENOVO 20FRS2FK00
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET53W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2FK00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2FK00
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717995/+subscriptions

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-06 Thread mrvanes

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 that trolltech is working on it!

-- 
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 freetype package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+subscriptions

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-29 Thread mrvanes

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
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 freetype package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+subscriptions

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-26 Thread mrvanes

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
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 freetype package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+subscriptions

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-26 Thread mrvanes

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 enough attention and more important, there's
an easy work-around.

** Bug watch added: KDE Bug Tracking System #376630
   https://bugs.kde.org/show_bug.cgi?id=376630

** Bug watch added: KDE Bug Tracking System #378523
   https://bugs.kde.org/show_bug.cgi?id=378523

-- 
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 freetype package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+subscriptions

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-16 Thread mrvanes

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/bugs/1722508

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+subscriptions

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

[Touch-packages] [Bug 1684506] Re: QT4 Trolltech.conf settings lost after reboot

2017-10-15 Thread mrvanes

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 reboot

Status in qt4-x11 package in Ubuntu:
  Confirmed

Bug description:
  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 correct font config and all qt4 applications now show correct
  font. These settings however do not survive a reboot although
  Trolltech.conf exists and contains correct settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  Uname: Linux 4.10.11 x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr 20 10:33:21 2017
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-04-11 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1684506/+subscriptions

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread mrvanes

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 freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+subscriptions

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread mrvanes

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/1722508

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+subscriptions

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread mrvanes

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"

https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+attachment/4970166/+files/Screenshot_20171013_191730.png

--
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 freetype package in Ubuntu:
Confirmed

Bug description:
It appears that font hinting in 17.10 (beta) doesn't work as expected.
The issue is easy to miss if you have antialiasing enabled system-
wise. However, if you install "gnome-tweak-tool" and disable
antialiasing there, the problem becomes obvious.

Here is how it looks on 17.10 beta:
https://postimg.org/image/3auqsbkqtn/

And here is how it looks on my 16.04 machine (and this is pretty much how
it's supposed to look):
https://postimg.org/image/85n5ss3l4b/

* When comparing the pictures make sure you "Open image in new tab"
and see them without browser zoom, otherwise the problem may no be
obvious.

I suspect that this issue is caused by a bug in some base font
rendering package that Ubuntu uses (edit: the problem is probably
caused by FreeType 2.8.0, see my comments below). A couple of months
ago a similar issue was reported (and promptly fixed) in Chromium
after they had changed something in FreeType rendering
(https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

lsb_release -rd
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+subscriptions

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread mrvanes

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

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+subscriptions

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

[Touch-packages] [Bug 1684506] [NEW] QT4 Trolltech.conf settings lost after reboot

2017-04-20 Thread mrvanes

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
correct font config and all qt4 applications now show correct font.
These settings however do not survive a reboot although Trolltech.conf
exists and contains correct settings.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
Uname: Linux 4.10.11 x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Apr 20 10:33:21 2017
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to zesty on 2017-04-11 (8 days ago)

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug freeze kubuntu zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1684506

Title:
  QT4 Trolltech.conf settings lost after reboot

Status in xorg package in Ubuntu:
  New

Bug description:
  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 correct font config and all qt4 applications now show correct
  font. These settings however do not survive a reboot although
  Trolltech.conf exists and contains correct settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  Uname: Linux 4.10.11 x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr 20 10:33:21 2017
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-04-11 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1684506/+subscriptions

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

[Touch-packages] [Bug 424215] Re: Bluetooth mouse usage makes A2DP audio stutter

2015-11-09 Thread mrvanes

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 you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/424215

Title:
  Bluetooth mouse usage makes A2DP audio stutter

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: bluez

  When I use my Bluetooth A2DP headset (Philips SHB7102) together with
  my mouse (Lenovo Bluetooth Laser Mouse), I notice this:

  Whenever I leave the mouse still for a few seconds (it seems to enter
  some kind of lower-power-mode) and then start to move it, my music
  most of the time skips for a second. This makes using these two
  bluetooth devices together quite annoying...

  The adapter is a Lenovo "ThinkPad Bluetooth with Enhanced Data Rate
  II" (Bus 004 Device 005: ID 0a5c:2145 Broadcom Corp.)

  I am running current karmic amd64 (linux 2.6.31-9).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215/+subscriptions

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

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Touch-packages] [Bug 1987736] Re: ssh-sk-helper undefined symbol fido_cred_set_clientdata

[Touch-packages] [Bug 1987736] [NEW] ssh-sk-helper undefined symbol fido_cred_set_clientdata

[Touch-packages] [Bug 1963818] Re: Upgrading to 22.04 on wayland session closes session

[Touch-packages] [Bug 1832882] [NEW] libcurl-gnutls segfaults spotify client

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects

[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Touch-packages] [Bug 1684506] Re: QT4 Trolltech.conf settings lost after reboot

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Touch-packages] [Bug 1684506] [NEW] QT4 Trolltech.conf settings lost after reboot

[Touch-packages] [Bug 424215] Re: Bluetooth mouse usage makes A2DP audio stutter

27 matches

Site Navigation

Mail list logo

Footer information