Accepted qtdeclarative-opensource-src 5.10.1-1 (source) into experimental

2018-02-19 Thread Dmitry Shachnev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Feb 2018 01:10:02 +0300
Source: qtdeclarative-opensource-src
Binary: libqt5qml5 libqt5quick5 libqt5quickparticles5 libqt5quicktest5 
libqt5quickwidgets5 qml-module-qtquick-layouts qt5-qmltooling-plugins 
qml-module-qt-labs-folderlistmodel qml-module-qtquick-localstorage 
qml-module-qt-labs-sharedimage qml-module-qtqml-models2 
qml-module-qtqml-statemachine qml-module-qtquick-particles2 qml-module-qtquick2 
qml-module-qtquick-shapes qml-module-qt-labs-handlers 
qml-module-qt-labs-settings qml-module-qttest qml-module-qtquick-window2 
qml-module-qtquick-xmllistmodel qtdeclarative5-dev qtdeclarative5-private-dev 
qtdeclarative5-dev-tools qmlscene qml qtdeclarative5-examples 
qtdeclarative5-doc qtdeclarative5-doc-html
Architecture: source
Version: 5.10.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Description:
 libqt5qml5 - Qt 5 QML module
 libqt5quick5 - Qt 5 Quick library
 libqt5quickparticles5 - Qt 5 Quick particles module
 libqt5quicktest5 - Qt 5 Quick Test library
 libqt5quickwidgets5 - Qt 5 Quick Widgets library
 qml- Qt 5 QML viewer
 qml-module-qt-labs-folderlistmodel - Qt 5 folderlistmodel QML module
 qml-module-qt-labs-handlers - Qt 5 Qt.labs.handlers QML module
 qml-module-qt-labs-settings - Qt 5 settings QML module
 qml-module-qt-labs-sharedimage - Qt 5 SharedImage QML module
 qml-module-qtqml-models2 - Qt 5 Models2 QML module
 qml-module-qtqml-statemachine - Qt 5 State Machine QML module
 qml-module-qtquick-layouts - Qt 5 Quick Layouts QML module
 qml-module-qtquick-localstorage - Qt 5 localstorage QML module
 qml-module-qtquick-particles2 - Qt 5 particles 2 QML module
 qml-module-qtquick-shapes - Qt 5 Qt Quick Shapes QML module
 qml-module-qtquick-window2 - Qt 5 window 2 QML module
 qml-module-qtquick-xmllistmodel - Qt 5 xmllistmodel QML module
 qml-module-qtquick2 - Qt 5 Qt Quick 2 QML module
 qml-module-qttest - Qt 5 test QML module
 qmlscene   - Qt 5 QML scene viewer
 qt5-qmltooling-plugins - Qt 5 qmltooling plugins
 qtdeclarative5-dev - Qt 5 declarative development files
 qtdeclarative5-dev-tools - Qt 5 declarative development programs
 qtdeclarative5-doc - Qt 5 declarative documentation
 qtdeclarative5-doc-html - Qt 5 declarative HTML documentation
 qtdeclarative5-examples - Qt 5 declarative examples
 qtdeclarative5-private-dev - Qt 5 declarative private development files
Changes:
 qtdeclarative-opensource-src (5.10.1-1) experimental; urgency=medium
 .
   * New upstream release.
   * Refresh patches for the new release.
   * Bump Qt build-dependencies to 5.10.1.
   * Update Vcs fields for migration to salsa.debian.org.
   * Update symbols files with 5.10.0 and current build logs.
   * Install plugins.qmltypes in qml-module-qt-labs-handlers.install.
   * Update debian/copyright.
   * Bump qtdeclarative-abi version to 5-10-1.
Checksums-Sha1:
 ddc05bea28304c7454454346a8e26e1aa68690a5 4669 
qtdeclarative-opensource-src_5.10.1-1.dsc
 91d8c0a7a466c68f74d5bcc8db9067b0855cfac9 22041236 
qtdeclarative-opensource-src_5.10.1.orig.tar.xz
 b60b0284053718a70c428a72d2fa34bfcf4b2aab 95352 
qtdeclarative-opensource-src_5.10.1-1.debian.tar.xz
 1decfff24f267e8dc8003a531d296115f9e030c0 7880 
qtdeclarative-opensource-src_5.10.1-1_source.buildinfo
Checksums-Sha256:
 7286915438ff1d38016bbf1cfcdfa0270d14cbdc87d02f2da2de23f2e1125ea7 4669 
qtdeclarative-opensource-src_5.10.1-1.dsc
 3af9ed51bce5b5c6f04c4a67a6008f98765ccde897c43fff670621ab70789553 22041236 
qtdeclarative-opensource-src_5.10.1.orig.tar.xz
 b564195b744c50157decd5e58b18718c0dfe5e02ef60e6081e562d6be501b2dc 95352 
qtdeclarative-opensource-src_5.10.1-1.debian.tar.xz
 75dbbb545aba7494a413f763e371e42f70241b318e8b119077144bd0e7c3de5b 7880 
qtdeclarative-opensource-src_5.10.1-1_source.buildinfo
Files:
 44c6e7d1746e76e8fe7ded79c2ffc1f0 4669 libs optional 
qtdeclarative-opensource-src_5.10.1-1.dsc
 6d44f915f586cd055be9843ab7015e76 22041236 libs optional 
qtdeclarative-opensource-src_5.10.1.orig.tar.xz
 c372f2a9b85727b1c7ed8fd158b76ee6 95352 libs optional 
qtdeclarative-opensource-src_5.10.1-1.debian.tar.xz
 939073f299e7474b47318e9378247f26 7880 libs optional 
qtdeclarative-opensource-src_5.10.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEbEPcK+5mZmLK5jNU1v5xA2P4XdMFAlqLS6AACgkQ1v5xA2P4
XdP4fw/+I7zhSjlmKbnCBVcAD0od5iTvlypADx/1ZNnO8bG15dzA8igvxPtReYTR
QkHEu9knpNZi4EsY2/u0pSjJeSqtNpzDPGCirk7UVReue7fyB/n5zy4W9pvW/IeH
aBqyID+kCMI9K3xtewamzrV6NDmW8NvLOs67IJJSZqQqXzO/U9rPwkPJ6GyjFISt
qq8AoPpXn+T6TV6/rlqbmP54gReAzaM7ATJMqt+RqmBXz+K7yM0HlY1s7bL+A8e6
fRe31bhXNfAH4kCue3HZxXcqPESW+A0RoDbL5TGUDX0tGsbNswrWCOzAn4oCBYuU
fNDKxBLjiTR6HNjrx8L3jNQYIKBsXzXuwJ9lxpaAcMe2WvJzOUdyckPY+U/1i1OT
+Y8BoJDnhZES5RJghtKDLnaNECwE8uD05P8apiqKdhkStIqO/O+24kUb7Wa7aBea
S8cn26nJEj0nj0QC5W3AC4XwoC96g3pyX1Y7geYq0SELBjUPfql/dx6w7Itj0Ywx
JIZQEpjxUV8yMjAttgVeb7pfyRk1vzlB/7FdFyUX49mRPLOlALhIril1VLpYBWT7
f0N0vM6BFWBXJ/XuwBFcOWYuHQoxuMMME8

qtdeclarative-opensource-src_5.10.1-1_source.changes ACCEPTED into experimental

2018-02-19 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Feb 2018 01:10:02 +0300
Source: qtdeclarative-opensource-src
Binary: libqt5qml5 libqt5quick5 libqt5quickparticles5 libqt5quicktest5 
libqt5quickwidgets5 qml-module-qtquick-layouts qt5-qmltooling-plugins 
qml-module-qt-labs-folderlistmodel qml-module-qtquick-localstorage 
qml-module-qt-labs-sharedimage qml-module-qtqml-models2 
qml-module-qtqml-statemachine qml-module-qtquick-particles2 qml-module-qtquick2 
qml-module-qtquick-shapes qml-module-qt-labs-handlers 
qml-module-qt-labs-settings qml-module-qttest qml-module-qtquick-window2 
qml-module-qtquick-xmllistmodel qtdeclarative5-dev qtdeclarative5-private-dev 
qtdeclarative5-dev-tools qmlscene qml qtdeclarative5-examples 
qtdeclarative5-doc qtdeclarative5-doc-html
Architecture: source
Version: 5.10.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Description:
 libqt5qml5 - Qt 5 QML module
 libqt5quick5 - Qt 5 Quick library
 libqt5quickparticles5 - Qt 5 Quick particles module
 libqt5quicktest5 - Qt 5 Quick Test library
 libqt5quickwidgets5 - Qt 5 Quick Widgets library
 qml- Qt 5 QML viewer
 qml-module-qt-labs-folderlistmodel - Qt 5 folderlistmodel QML module
 qml-module-qt-labs-handlers - Qt 5 Qt.labs.handlers QML module
 qml-module-qt-labs-settings - Qt 5 settings QML module
 qml-module-qt-labs-sharedimage - Qt 5 SharedImage QML module
 qml-module-qtqml-models2 - Qt 5 Models2 QML module
 qml-module-qtqml-statemachine - Qt 5 State Machine QML module
 qml-module-qtquick-layouts - Qt 5 Quick Layouts QML module
 qml-module-qtquick-localstorage - Qt 5 localstorage QML module
 qml-module-qtquick-particles2 - Qt 5 particles 2 QML module
 qml-module-qtquick-shapes - Qt 5 Qt Quick Shapes QML module
 qml-module-qtquick-window2 - Qt 5 window 2 QML module
 qml-module-qtquick-xmllistmodel - Qt 5 xmllistmodel QML module
 qml-module-qtquick2 - Qt 5 Qt Quick 2 QML module
 qml-module-qttest - Qt 5 test QML module
 qmlscene   - Qt 5 QML scene viewer
 qt5-qmltooling-plugins - Qt 5 qmltooling plugins
 qtdeclarative5-dev - Qt 5 declarative development files
 qtdeclarative5-dev-tools - Qt 5 declarative development programs
 qtdeclarative5-doc - Qt 5 declarative documentation
 qtdeclarative5-doc-html - Qt 5 declarative HTML documentation
 qtdeclarative5-examples - Qt 5 declarative examples
 qtdeclarative5-private-dev - Qt 5 declarative private development files
Changes:
 qtdeclarative-opensource-src (5.10.1-1) experimental; urgency=medium
 .
   * New upstream release.
   * Refresh patches for the new release.
   * Bump Qt build-dependencies to 5.10.1.
   * Update Vcs fields for migration to salsa.debian.org.
   * Update symbols files with 5.10.0 and current build logs.
   * Install plugins.qmltypes in qml-module-qt-labs-handlers.install.
   * Update debian/copyright.
   * Bump qtdeclarative-abi version to 5-10-1.
Checksums-Sha1:
 ddc05bea28304c7454454346a8e26e1aa68690a5 4669 
qtdeclarative-opensource-src_5.10.1-1.dsc
 91d8c0a7a466c68f74d5bcc8db9067b0855cfac9 22041236 
qtdeclarative-opensource-src_5.10.1.orig.tar.xz
 b60b0284053718a70c428a72d2fa34bfcf4b2aab 95352 
qtdeclarative-opensource-src_5.10.1-1.debian.tar.xz
 1decfff24f267e8dc8003a531d296115f9e030c0 7880 
qtdeclarative-opensource-src_5.10.1-1_source.buildinfo
Checksums-Sha256:
 7286915438ff1d38016bbf1cfcdfa0270d14cbdc87d02f2da2de23f2e1125ea7 4669 
qtdeclarative-opensource-src_5.10.1-1.dsc
 3af9ed51bce5b5c6f04c4a67a6008f98765ccde897c43fff670621ab70789553 22041236 
qtdeclarative-opensource-src_5.10.1.orig.tar.xz
 b564195b744c50157decd5e58b18718c0dfe5e02ef60e6081e562d6be501b2dc 95352 
qtdeclarative-opensource-src_5.10.1-1.debian.tar.xz
 75dbbb545aba7494a413f763e371e42f70241b318e8b119077144bd0e7c3de5b 7880 
qtdeclarative-opensource-src_5.10.1-1_source.buildinfo
Files:
 44c6e7d1746e76e8fe7ded79c2ffc1f0 4669 libs optional 
qtdeclarative-opensource-src_5.10.1-1.dsc
 6d44f915f586cd055be9843ab7015e76 22041236 libs optional 
qtdeclarative-opensource-src_5.10.1.orig.tar.xz
 c372f2a9b85727b1c7ed8fd158b76ee6 95352 libs optional 
qtdeclarative-opensource-src_5.10.1-1.debian.tar.xz
 939073f299e7474b47318e9378247f26 7880 libs optional 
qtdeclarative-opensource-src_5.10.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEbEPcK+5mZmLK5jNU1v5xA2P4XdMFAlqLS6AACgkQ1v5xA2P4
XdP4fw/+I7zhSjlmKbnCBVcAD0od5iTvlypADx/1ZNnO8bG15dzA8igvxPtReYTR
QkHEu9knpNZi4EsY2/u0pSjJeSqtNpzDPGCirk7UVReue7fyB/n5zy4W9pvW/IeH
aBqyID+kCMI9K3xtewamzrV6NDmW8NvLOs67IJJSZqQqXzO/U9rPwkPJ6GyjFISt
qq8AoPpXn+T6TV6/rlqbmP54gReAzaM7ATJMqt+RqmBXz+K7yM0HlY1s7bL+A8e6
fRe31bhXNfAH4kCue3HZxXcqPESW+A0RoDbL5TGUDX0tGsbNswrWCOzAn4oCBYuU
fNDKxBLjiTR6HNjrx8L3jNQYIKBsXzXuwJ9lxpaAcMe2WvJzOUdyckPY+U/1i1OT
+Y8BoJDnhZES5RJghtKDLnaNECwE8uD05P8apiqKdhkStIqO/O+24kUb7Wa7aBea
S8cn26nJEj0nj0QC5W3AC4XwoC96g3pyX1Y7geYq0SELBjUPfql/dx6w7Itj0Ywx
JIZQEpjxUV8yMjAttgVeb7pfyRk1vzlB/7FdFyUX49mRPLOlALhIril1VLpYBWT7
f0N0vM6BFWBXJ/XuwBFcO

Processing of qtdeclarative-opensource-src_5.10.1-1_source.changes

2018-02-19 Thread Debian FTP Masters
qtdeclarative-opensource-src_5.10.1-1_source.changes uploaded successfully to 
localhost
along with the files:
  qtdeclarative-opensource-src_5.10.1-1.dsc
  qtdeclarative-opensource-src_5.10.1.orig.tar.xz
  qtdeclarative-opensource-src_5.10.1-1.debian.tar.xz
  qtdeclarative-opensource-src_5.10.1-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



Bug#884956: Now hidpi scaling is even more broken

2018-02-19 Thread wm4
On Mon, 19 Feb 2018 10:12:55 -0300
Lisandro Damián Nicanor Pérez Meyer  wrote:

> El lunes, 19 de febrero de 2018 08:04:24 -03 wm4 escribió:
> > On Mon, 19 Feb 2018 07:54:11 -0300  
> [snip] 
> > Yeah, that is strange.   
> 
> *Too* strange. According to src/gui/kernel/qhighdpiscaling.cpp:
> 
> 2) Per-screen scale factors
> Some platform plugins support providing a per-screen scale
> factor based on display density information. These platforms
> include X11, Windows, and Android.
> 
> There are two APIs for enabling or disabling this behavior:
> - The QT_AUTO_SCREEN_SCALE_FACTOR environment variable.
> - The AA_EnableHighDpiScaling and AA_DisableHighDpiScaling
>   application attributes
> 
> Enabling either will make QHighDpiScaling call 
> QPlatformScreen::pixelDensity()
> and use the value provided as the scale factor for the screen in
> question. Disabling is done on a 'veto' basis where either the
> environment or the application can disable the scaling. The intended 
> use
> cases are 'My system is not providing correct display density
> information' and 'My application needs to work in display pixels',
> respectively.
> 
> And efectively the code does that in usePixelDensity() from the same code. 
> QPlatformScreen::pixelDensity() in X11 is implemented by
> src/plugins/platforms/xcb/qxcbscreen.cpp, which is the file that the patch 
> touches.
> 
> So the fact that the env variable "does not changes things" for you is really 
> really strange.

I didn't say it didn't change anything. I just couldn't make it do the
right thing. In fact, even with -10, QT_AUTO_SCREEN_SCALE_FACTOR=0 will
break it, probably in a similar way like with -12. If that env var is
set, QT_SCALE_FACTOR=1 will make the window too small, and
QT_SCALE_FACTOR=2 will make it too big. So either way, something else
must factor into this, but I didn't check the code.

The effects with -10 are as follows:

  QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCALE_FACTOR=1:

 Window and UI elements like scrollbars are too small. The font
 size is correct. Fonts and icons have the correct size.

  QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCALE_FACTOR=2:

 Window and UI elements have correct size, but fonts and symbols
 are scaled 4 times (!!!?).

  QT_AUTO_SCREEN_SCALE_FACTOR=1 (QT_SCALE_FACTOR unset):

 Everything looks correct, apparently scaling 2x compared to HiDPI
 disabled.

  QT_AUTO_SCREEN_SCALE_FACTOR=1 QT_SCALE_FACTOR=1:

 Same as previous.

  QT_AUTO_SCREEN_SCALE_FACTOR=1 QT_SCALE_FACTOR=2:

 Looks correct, except it scales 4x instead of 2x, so everything
 has double the size it should have.

> Let's also look at the patch:
> 
> -m_pixelDensity = qMax(1, qRound(dpi/96));
> +m_pixelDensity = qMax(1, (int) (dpi/96));
> 
> The first line is the original code. The only way I see this could work for 
> you in -10 but not in -12 is that (dpi/96) > 2.
> 
> Please tell me which exact branch and model of monitor you have please, so I 
> can check this value.

xdpyinfo contains:

  dimensions:3840x2160 pixels (530x301 millimeters)
  resolution:184x182 dots per inch

Assuming Qt computes the dpi value the same way, that makes dpi/96
approximately 1.9. (int)1.9 is 1, qRound(1.9) is 2. I'm not sure why
you're arguing with something about "> 2".

Now I don't even know if that specific patch caused the bug, since
apparently there were other Qt builds between -10 and -12, but it seems
like a rather likely candidate.

> 
> 
> > I didn't create a new user, because that would
> > change nothing. I made sure to override all environment variables for
> > the test.  
> 
> OK, but don't complain later if things do not work out for you.

What environment variable or config setting do you suppose could have
influence that a new user would remove? I set these environment
variables for my whole system anyway _and_ I tested with overwriting
their values locally from the terminal. Also before you suspect I'm
unable to set environment variables correctly: setting them certainly
had an effect.

Anyway, as it was just suggested, I also tried with setting HOME to
something else, and the result was the same.

> > I can't test anymore because after fighting Debian's
> > absolutely crappy package manager to make it downgrade to testing's
> > Qt packages, it works again. (And I'll defend my word choice "crappy".
> > Why can't it figure out transitive dependencies? It's just bad.
> > aptitude didn't behave better.)  
> 
> And this behavior makes me want to avoid helping you any further. So if you 
> really value our work and are willing to help, please stop with this.

Depends if you find it unreasonable whether a user gets angry about
having to sink time into making a distro maintainer to revert a patch
(that was apparently never accepted in upstream Qt), that was applied as
trial&error for fixing a bug, and which

Bug#884956: Now hidpi scaling is even more broken

2018-02-19 Thread Vincent Lefevre
On 2018-02-19 12:04:24 +0100, wm4 wrote:
> Yeah, that is strange. I didn't create a new user, because that would
> change nothing. I made sure to override all environment variables for
> the test.

Not everything is in the environment variables. There are also
user config files, which might matter even when they shouldn't
(let's recall that we are talking about bugs).

If there are still problems and you don't want to create a new user,
try at least something like (with a correct path):

$ mkdir /path/to/newhome
$ HOME=/path/to/newhome QT_AUTO_SCREEN_SCALE_FACTOR=0 vlc

(possibly with other environment settings).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#884956: Now hidpi scaling is even more broken

2018-02-19 Thread Vincent Lefevre
On 2018-02-19 10:12:55 -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> El lunes, 19 de febrero de 2018 08:04:24 -03 wm4 escribió:
> > On Mon, 19 Feb 2018 07:54:11 -0300
> [snip] 
> > Yeah, that is strange. 
> 
> *Too* strange. According to src/gui/kernel/qhighdpiscaling.cpp:
[...]

I think that wm4 just means that everything is too small.
So this actually does not break anything and is the expected
behavior.

FYI,

  QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCALE_FACTOR=2 vlc

also yields a valid rendering with everything scaled by a factor 2
(wm4, doesn't this solve your issue?).

The issue is that *without* QT_AUTO_SCREEN_SCALE_FACTOR=0, the
text and the icons are not scaled with the same factor.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#884956: Now hidpi scaling is even more broken

2018-02-19 Thread Lisandro Damián Nicanor Pérez Meyer
El lunes, 19 de febrero de 2018 08:04:24 -03 wm4 escribió:
> On Mon, 19 Feb 2018 07:54:11 -0300
[snip] 
> Yeah, that is strange. 

*Too* strange. According to src/gui/kernel/qhighdpiscaling.cpp:

2) Per-screen scale factors
Some platform plugins support providing a per-screen scale
factor based on display density information. These platforms
include X11, Windows, and Android.

There are two APIs for enabling or disabling this behavior:
- The QT_AUTO_SCREEN_SCALE_FACTOR environment variable.
- The AA_EnableHighDpiScaling and AA_DisableHighDpiScaling
  application attributes

Enabling either will make QHighDpiScaling call 
QPlatformScreen::pixelDensity()
and use the value provided as the scale factor for the screen in
question. Disabling is done on a 'veto' basis where either the
environment or the application can disable the scaling. The intended 
use
cases are 'My system is not providing correct display density
information' and 'My application needs to work in display pixels',
respectively.

And efectively the code does that in usePixelDensity() from the same code. 
QPlatformScreen::pixelDensity() in X11 is implemented by
src/plugins/platforms/xcb/qxcbscreen.cpp, which is the file that the patch 
touches.

So the fact that the env variable "does not changes things" for you is really 
really strange.

Let's also look at the patch:

-m_pixelDensity = qMax(1, qRound(dpi/96));
+m_pixelDensity = qMax(1, (int) (dpi/96));

The first line is the original code. The only way I see this could work for 
you in -10 but not in -12 is that (dpi/96) > 2.

Please tell me which exact branch and model of monitor you have please, so I 
can check this value.


> I didn't create a new user, because that would
> change nothing. I made sure to override all environment variables for
> the test.

OK, but don't complain later if things do not work out for you.

> I can't test anymore because after fighting Debian's
> absolutely crappy package manager to make it downgrade to testing's
> Qt packages, it works again. (And I'll defend my word choice "crappy".
> Why can't it figure out transitive dependencies? It's just bad.
> aptitude didn't behave better.)

And this behavior makes me want to avoid helping you any further. So if you 
really value our work and are willing to help, please stop with this.


-- 
 SlackDeb: velo como un entrenamiento shaolin para geeks,
en vez de meditación y tortura física, abstinencia de internet y sexo
  Horacio Francisco Sebastián "Perrito" Durán Barrionuevo, sobre un
  viaje que Federico "SlackDeb" Peretti estaba planeando con su novia.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.


Bug#884956: Now hidpi scaling is even more broken

2018-02-19 Thread wm4
On Mon, 19 Feb 2018 12:26:54 +0100
Vincent Lefevre  wrote:

> On 2018-02-19 12:04:24 +0100, wm4 wrote:
> > Yeah, that is strange. I didn't create a new user, because that would
> > change nothing. I made sure to override all environment variables for
> > the test. I can't test anymore because after fighting Debian's
> > absolutely crappy package manager to make it downgrade to testing's
> > Qt packages, it works again. (And I'll defend my word choice "crappy".
> > Why can't it figure out transitive dependencies? It's just bad.
> > aptitude didn't behave better.)  
> 
> IMHO, dependency resolution would not work well (or even not at all)
> for downgrades. Getting all the installed package from the same source
> package (here, qtbase-opensource-src) could make things easier for
> downgrades.
> 

Well, I had the following situation: I uninstalled some Qt and
application packages as preparation for downgrading. Then I installed
the downgraded Qt packages. Then I wanted to reinstall an application
package. But it showed dozens of errors like this:

 package1 : Depends: package2 (>= version) but it is
 not going to be installed

It turns out the resolution was removing/downgrading just 1 or 2
packages (not package1 or package2) that transitively blocked
installing package2. Not even aptitude after crunching on it for
minutes could come up with the resolution. I'd really expect better.

I don't get why Debian has to split everything into thousands of
packages either, when everything depends on everything anyway.

Sorry for off-topic.



Bug#884956: Now hidpi scaling is even more broken

2018-02-19 Thread Vincent Lefevre
On 2018-02-19 12:04:24 +0100, wm4 wrote:
> Yeah, that is strange. I didn't create a new user, because that would
> change nothing. I made sure to override all environment variables for
> the test. I can't test anymore because after fighting Debian's
> absolutely crappy package manager to make it downgrade to testing's
> Qt packages, it works again. (And I'll defend my word choice "crappy".
> Why can't it figure out transitive dependencies? It's just bad.
> aptitude didn't behave better.)

IMHO, dependency resolution would not work well (or even not at all)
for downgrades. Getting all the installed package from the same source
package (here, qtbase-opensource-src) could make things easier for
downgrades.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#884956: Now hidpi scaling is even more broken

2018-02-19 Thread wm4
On Mon, 19 Feb 2018 12:10:02 +0100
Vincent Lefevre  wrote:

> On 2018-02-18 15:25:35 -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> > wm4, Vincent: can you try setting QT_AUTO_SCREEN_SCALE_FACTOR=0 ?  
> 
> QT_AUTO_SCREEN_SCALE_FACTOR=0 works with -12, just like with -10.
> 
> I suspect that different behaviors are due to the fact that among
> HiDPI cases, screen sizes, DPI's, etc. are different.
> 
> The patch consisted in truncating instead of rounding to nearest,
> so that it might have solved the problem for users where the
> real factor was between 1.5 and 2, thus changed from 2 to 1
> when converted to integer, 1 meaning no HiDPI (for which there
> are no issues) if I understand correctly.
> 
> I suppose that my real factor is between 2 and 2.5, so that truncating
> gives the same result as rounding to nearest. Hence the same behavior.
> 
> I don't know what broke for wm4. "With the patch applied, it scales
> to 1, which is nonsense." is not very meaningful. This is what happens
> for low DPI, for which no issues have been reported.
> 

Maybe I wasn't clear enough, but I have a HiDPI screen, with a scale
factor (as reported by X11) of approximately 1.9. With -12, it reduced
the sizes of windows and GUI elements by half, and no combination of
environment variables made it scale correctly. I suspect there's some
other scaling factoring in somewhere, which somehow controls font sizes.
Now I'm back to -10 (testing), and I won't upgrade it until the patch
is reverted, so no new tests by me.



Bug#884956: Now hidpi scaling is even more broken

2018-02-19 Thread Vincent Lefevre
On 2018-02-18 15:25:35 -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> wm4, Vincent: can you try setting QT_AUTO_SCREEN_SCALE_FACTOR=0 ?

QT_AUTO_SCREEN_SCALE_FACTOR=0 works with -12, just like with -10.

I suspect that different behaviors are due to the fact that among
HiDPI cases, screen sizes, DPI's, etc. are different.

The patch consisted in truncating instead of rounding to nearest,
so that it might have solved the problem for users where the
real factor was between 1.5 and 2, thus changed from 2 to 1
when converted to integer, 1 meaning no HiDPI (for which there
are no issues) if I understand correctly.

I suppose that my real factor is between 2 and 2.5, so that truncating
gives the same result as rounding to nearest. Hence the same behavior.

I don't know what broke for wm4. "With the patch applied, it scales
to 1, which is nonsense." is not very meaningful. This is what happens
for low DPI, for which no issues have been reported.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#884956: Now hidpi scaling is even more broken

2018-02-19 Thread wm4
On Mon, 19 Feb 2018 07:54:11 -0300
Lisandro Damián Nicanor Pérez Meyer  wrote:

> El 19 feb. 2018 4:15 a.m., "wm4"  escribió:
> 
> On Sun, 18 Feb 2018 15:25:35 -0300
> Lisandro Damián Nicanor Pérez Meyer  wrote:
> 
> > I've been digging around and:
> >
> > - One user (wm4, CCed) reported that the fix broke his setup. wm4: can you
> > please test -12 with a new user without any change to any setup?
> >
> > - One user that did not see any change (Vincent, CCed).
> >
> > - One user and fellow developer Dmitry (auto CCed) which found that for  
> him
> > -12 works better than -10. He also tested that using
> >
> >   QT_AUTO_SCREEN_SCALE_FACTOR=0
> >
> > makes VLC work as -12 without that variable set in both -10 or -12,  
> meaning
> > that the patch indeed helps him.
> >
> > wm4, Vincent: can you try setting QT_AUTO_SCREEN_SCALE_FACTOR=0 ? mw4: in  
> your
> > case I would like you to test in your normal user and in the new user I  
> asked
> > you about above.
> >
> > I acknowledge that the bug is still there, but as long as we do not have
> > strong evidence that it backfires for most people we will keep it around  
> until
> > upstream finds a proper fix.
> >
> > Cheers, Lisandro.
> >  
> 
> No combination of these environment variables restores behavior. Please
> unbreak this.
> 
> 
> That's totally strange because that environment variable is supposed to
> override that value. Have you tried by creating a new user?

Yeah, that is strange. I didn't create a new user, because that would
change nothing. I made sure to override all environment variables for
the test. I can't test anymore because after fighting Debian's
absolutely crappy package manager to make it downgrade to testing's
Qt packages, it works again. (And I'll defend my word choice "crappy".
Why can't it figure out transitive dependencies? It's just bad.
aptitude didn't behave better.)



Bug#884956: Now hidpi scaling is even more broken

2018-02-19 Thread Lisandro Damián Nicanor Pérez Meyer
El 19 feb. 2018 4:15 a.m., "wm4"  escribió:

On Sun, 18 Feb 2018 15:25:35 -0300
Lisandro Damián Nicanor Pérez Meyer  wrote:

> I've been digging around and:
>
> - One user (wm4, CCed) reported that the fix broke his setup. wm4: can you
> please test -12 with a new user without any change to any setup?
>
> - One user that did not see any change (Vincent, CCed).
>
> - One user and fellow developer Dmitry (auto CCed) which found that for
him
> -12 works better than -10. He also tested that using
>
>   QT_AUTO_SCREEN_SCALE_FACTOR=0
>
> makes VLC work as -12 without that variable set in both -10 or -12,
meaning
> that the patch indeed helps him.
>
> wm4, Vincent: can you try setting QT_AUTO_SCREEN_SCALE_FACTOR=0 ? mw4: in
your
> case I would like you to test in your normal user and in the new user I
asked
> you about above.
>
> I acknowledge that the bug is still there, but as long as we do not have
> strong evidence that it backfires for most people we will keep it around
until
> upstream finds a proper fix.
>
> Cheers, Lisandro.
>

No combination of these environment variables restores behavior. Please
unbreak this.


That's totally strange because that environment variable is supposed to
override that value. Have you tried by creating a new user?