from:"Andrew Shadura"

[Touch-packages] [Bug 1695618] Re: Qt5 apps don’t pick up the GTK+ style anymore

2018-02-23 Thread Andrew Shadura

I've just ran into this issue once again on a freshly installed Ubuntu.
It exports QT_STYLE_OVERRIDE=gtk somewhere, and that makes e.g. Dropbox
not work correctly.

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

Title:
  Qt5 apps don’t pick up the GTK+ style anymore

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu
  (GTK+, I presume) theme, and look very Windowsy. I have qt5-gtk-
  platformtheme installed, and I tried forcing it by setting
  QT_QPA_PLATFORMTHEME, but to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1695618/+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 1695618] Re: Qt5 apps don’t pick up the GTK+ style anymore

2018-02-23 Thread Andrew Shadura

Oh, in fact it's the same with other Qt5 apps.

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

Title:
  Qt5 apps don’t pick up the GTK+ style anymore

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu
  (GTK+, I presume) theme, and look very Windowsy. I have qt5-gtk-
  platformtheme installed, and I tried forcing it by setting
  QT_QPA_PLATFORMTHEME, but to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1695618/+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 1695618] Re: Qt5 apps don’t pick up the GTK+ style anymore

2018-02-23 Thread Andrew Shadura

Oh, I found it, in was in my ~ :D

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

Title:
  Qt5 apps don’t pick up the GTK+ style anymore

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu
  (GTK+, I presume) theme, and look very Windowsy. I have qt5-gtk-
  platformtheme installed, and I tried forcing it by setting
  QT_QPA_PLATFORMTHEME, but to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1695618/+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 415134] Re: Bad font rendering (Freetype, bytecode interpreter)

2018-01-03 Thread Andrew Shadura

Fixed in Artful and Bionic.

** Changed in: freetype (Ubuntu)
   Status: New => Fix Released

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

Title:
  Bad font rendering (Freetype, bytecode interpreter)

Status in freetype package in Ubuntu:
  Fix Released

Bug description:
  A screenshot demonstrating the issues: http://zi.fi/fonttest/fonttest-
  bytecode-enabled.png

  The shot was taken with Ubuntu 9.04 fontconfig-config default
  settings, AA enabled, full hinting enabled, subpixel rendering
  disabled (in Gnome settings). The text is written in OpenOffice (
  http://zi.fi/fonttest/fonttest.odt ).

  Times New Roman italic z is missing the diagonal line (or in fact it
  is just extremely thin). All Microsoft fonts display bad kerning
  (possibly due to OpenOffice) and sudden line thickness changes in
  italic text of different sizes (hinting switching to 2 pixel lines
  instead of 1 pixel would explain the change, but without hinting as is
  the case in italic text this makes no sense). The free fonts (which
  presumably contain no bytecode) have no hinting at all, not even in
  regular rendering (soft edges on FreeSans and FreeSerif titles).

  Freetype autohinter should be used at least for the fonts with no
  bytecode in them and possibly for all fonts, as it often seems to
  produce better results than the bytecode does. This is because the
  bytecode is designed for non-AA rendering. Microsoft's workaround is
  to disable AA entirely in smaller sizes, but that doesn't produce very
  good results either.

  I am reporting this against Ubuntu because apparently it is the
  patches that Ubuntu use that break this instead of Freetype itself
  being broken. Times New Roman bytecode in deed seems broken (for anti-
  aliased rendering at least), but an easier and possibly better fix
  would be to enable the autohinter, which seems to have very good
  rendering quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/415134/+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 415134] Re: Bad font rendering (Freetype, bytecode interpreter)

2018-01-03 Thread Andrew Shadura

This has been fixed upstream:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/src/truetype/ttdriver.c?id=bcc74f4dafee25ea89f1d3144646cba7e30f9908

The fix is included in freetype 2.8+.

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

Title:
  Bad font rendering (Freetype, bytecode interpreter)

Status in freetype package in Ubuntu:
  Fix Released

Bug description:
  A screenshot demonstrating the issues: http://zi.fi/fonttest/fonttest-
  bytecode-enabled.png

  The shot was taken with Ubuntu 9.04 fontconfig-config default
  settings, AA enabled, full hinting enabled, subpixel rendering
  disabled (in Gnome settings). The text is written in OpenOffice (
  http://zi.fi/fonttest/fonttest.odt ).

  Times New Roman italic z is missing the diagonal line (or in fact it
  is just extremely thin). All Microsoft fonts display bad kerning
  (possibly due to OpenOffice) and sudden line thickness changes in
  italic text of different sizes (hinting switching to 2 pixel lines
  instead of 1 pixel would explain the change, but without hinting as is
  the case in italic text this makes no sense). The free fonts (which
  presumably contain no bytecode) have no hinting at all, not even in
  regular rendering (soft edges on FreeSans and FreeSerif titles).

  Freetype autohinter should be used at least for the fonts with no
  bytecode in them and possibly for all fonts, as it often seems to
  produce better results than the bytecode does. This is because the
  bytecode is designed for non-AA rendering. Microsoft's workaround is
  to disable AA entirely in smaller sizes, but that doesn't produce very
  good results either.

  I am reporting this against Ubuntu because apparently it is the
  patches that Ubuntu use that break this instead of Freetype itself
  being broken. Times New Roman bytecode in deed seems broken (for anti-
  aliased rendering at least), but an easier and possibly better fix
  would be to enable the autohinter, which seems to have very good
  rendering quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/415134/+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 1547196] Re: Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail

2018-01-03 Thread Andrew Shadura

This has been fixed upstream:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/src/truetype/ttdriver.c?id=bcc74f4dafee25ea89f1d3144646cba7e30f9908

The fix is included in freetype 2.8+.

Fixed in Artful and Bionic.

** Changed in: freetype (Ubuntu)
Status: Confirmed => Fix Released

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

Title:
Removal of revert_scalable_fonts_metric.patch causes ugliness in
Claws-Mail

Status in freetype package in Ubuntu:
Fix Released
Status in freetype package in Debian:
New

Bug description:
This is mostly a tracking bug for this discussion on ubuntu-devel:

https://lists.ubuntu.com/archives/ubuntu-
devel/2016-February/039224.html

The following precise-era patch was recently removed from freetype:

http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/wily/freetype/wily/view/head:/debian/patches-
freetype/revert_scalable_fonts_metric.patch

which caused a number of visual effects in various applications. In
Emacs, the lines get vertically closer so that more lines are visible
on screen. This is subtle and doesn't look too bad otherwise.

However, in Claws-Mail several negative effects were noticed. The
lines in the Summary window are more squished together and the
characters appear squished too. This is with Sans 10 font. This is
less readable.

In the Message window it's worse. There I use Ubuntu Mono 14. The
problem isn't the vertical spacing, but the horizontal spacing. Now
there is more space between characters and that actually makes the
window less readable.

I will contact the upstream Claws mailing list to see if they have any
thoughts.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libfreetype6 2.6.1-0.1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Feb 18 14:34:57 2016
Dependencies:
gcc-6-base 6-20160217-0ubuntu1
libc6 2.21-0ubuntu6
libgcc1 1:6-20160217-0ubuntu1
libpng12-0 1.2.54-1ubuntu1
zlib1g 1:1.2.8.dfsg-2ubuntu4
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-01-22 (27 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
SourcePackage: freetype
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1547196/+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 972223] Re: regression in gtk underlining rendering

2018-01-03 Thread Andrew Shadura

The upstream has acknowledged the change:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/src/truetype/ttdriver.c?id=bcc74f4dafee25ea89f1d3144646cba7e30f9908

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

Title:
  regression in gtk underlining rendering

Status in FreeType:
  New
Status in freetype package in Ubuntu:
  Fix Released

Bug description:
  The issue started with 2.4.6 and got tracked to
  
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0962ac34e66052ccfee7996e5468f30d4bd5a72

  Michael Vogt came with a testcase on
  https://bugs.launchpad.net/ubuntu/+source/software-
  center/+bug/955030/+attachment/2988350/+files/lala.py

  The commit also created http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=636776

  I talked to Steve and I'm going to revert that commit for precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/freetype/+bug/972223/+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 1730399] Re: Add krackattacks mitigation

2017-11-24 Thread Andrew Shadura

** Changed in: wpa (Ubuntu)
   Status: New => Confirmed

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

Title:
  Add krackattacks mitigation

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  See for reference:
  https://www.krackattacks.com/#ap-mitigations

  Yes this is not a bug. However, it has been noted on ubuntu-devel that adding 
some features even to stable releases could be justified in *some* cases.
  First of paramount importance is that the fix introduces no regression.
  In this case this code is *only* used if a new parameter is set:

  wpa_disable_eapol_key_retries=1

  if this parameter is missing, behaviour will not change.
  So any regression introduced will be caused by a deliberate admin decision, 
from where all responsability could be denied (use at your own risk, yadda, 
yadda...)

  Then is this parameter useful: it could be for the hundred of millions
  of Android Phone that are not yet patched (6.0 et upper) and will
  never be patched (about 50% of existing Android Phones).

  Please note that at least one wifi provider has already decided to
  provide this feature to help its users:

  https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory
  /cisco-sa-20171016-wpa

  so this is something that leaders do :-)

  I have already patched my AP that runs Ubuntu 16 LTS (see attached
  patch against 2.4-0ubuntu6.2, I have used my AP for 3 days now with a
  Ubuntu and an Android client without problem) and I could try to
  provide a patch for Ubuntu 17. This kind of patch is really trivial
  anyway, since it's just a port of the upstream patch in hostapd:

  https://w1.fi/cgit/hostap/commit/?id=6f234c1e2ee1ede29f2412b7012b3345ed8e52d3

  
  However I have a big problem. Any security patch (and this is a security 
enhancing patch at least) is only worth as much as it is *tested*. And I don't 
have the means to verify that mitigation is effective, as the vulnerability 
discoverer has not provided (for obvious reasons) public testing code for 
clients.
  I think that Ubuntu should have this code (or did you just distribute 
security patches without testing that they are effective ? that would not be 
very serious IMO). 
  There is no chance that M. Vanhoef sends his code to any old dog on the 
internet, so Canonical is my only chance for a real test of this feature on an 
Ubuntu AP (short of rewriting the attack code myself, not an attractive 
proposition). 
  If in fact you don't have the testing (well, attack) code feel free to 
dismiss my bug report as irrelevant. But if you have please consider the 
opportunity to add some goodwill to Ubuntu. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1730399/+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

39 matches

Mail list logo