[Touch-packages] [Bug 2060102] Re: apt dist-upgrade uninstalls quassel-client

[Dmitry Shachnev]

Hi Heinrich!

The noble archive for amd64 is currently in a semi-broken state. As an
attempt to mitigate the consequences of CVE-2024-3094, all amd64
binaries built with compromised xz-utils were removed from the archive,
which rendered some packages uninstallable.

If you want a stable archive, try using noble-updates only (without the
release pocket). It contains an older, pre-CVE-2024-3094 snapshot. Or
wait until things settle down and packages become installable in noble
again.

Also, installing the packages using "dpkg -i" may break your system, as
that command does not check the dependencies. Use "apt install ./*.deb"
instead, which is safer.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094

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

Title:
  apt dist-upgrade uninstalls quassel-client

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

Bug description:
  Trying to run dist-upgrade asks for uninstalling quassel-client on
  amd64. This is related to some unfullfillable dependencies:

  The following packages have unmet dependencies:
   quassel-client : Depends: libqt5core5t64 (>= 5.15.1) but it is not 
installable
Depends: libqt5dbus5t64 (>= 5.14.1) but it is not 
installable
Depends: libqt5gui5t64 (>= 5.14.1) but it is not 
installable or
 libqt5gui5-gles (>= 5.14.1) but it is not installed
Depends: libqt5network5t64 (>= 5.15.1) but it is not 
installable
Depends: libqt5widgets5t64 (>= 5.14.1) but it is not 
installable

  $ sudo apt-get dist-upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
quassel-client
  The following packages have been kept back:
2to3 alsa-ucm-conf apache2-data breeze-cursor-theme debconf-kde-data exim4 
gnupg gnupg-agent gvfs-common hplip-data hplip-gui kde-cli-tools-data 
khotkeys-data kio-extras-data
ktexteditor-data kubuntu-desktop kwayland-data kwin-data 
libavahi-client3:i386 libavahi-common-data:i386 libavahi-common3:i386 
libblkid1:i386 libcairo-gobject2:i386
libcairo2:i386 libcanberra-gtk-module:i386 libcanberra-gtk0:i386 
libcom-err2:i386 libdbus-1-3:i386 libfreetype6:i386 libgail-common:i386 
libgdk-pixbuf-2.0-0:i386
libgl1-mesa-dri:i386 libglapi-mesa:i386 libglx-mesa0:i386 
libgssapi-krb5-2:i386 libharfbuzz0b:i386 libk5crypto3:i386 libkf5bluezqt-data 
libkf5contacts-data
libkf5declarative-data libkf5dnssd-data libkf5filemetadata-data 
libkf5holidays-data libkf5kcmutils-data libkf5kdelibs4support-data 
libkf5khtml-data libkf5notifyconfig-data
libkf5package-data libkf5parts-data libkf5people-data libkf5pty-data 
libkf5sane-data libkf5screen-bin libkf5screen-data libkf5screen8 
libkf5screendpms8 libkf5sonnet5-data
libkf5su-data libkf5syntaxhighlighting-data libkf5sysguard-bin 
libkf5sysguard-data libkimageannotator-common libkpim5gapi-data libkrb5-3:i386 
libkrb5support0:i386 libksgrd9
libksysguardformatter1 libksysguardsensorfaces1 libksysguardsensors1 
libksysguardsystemstats1 libmount1:i386 libnsl2:i386 libnss-nisplus:i386 
libnvidia-compute-535:i386
libnvidia-decode-535:i386 libnvidia-encode-535:i386 libnvidia-fbc1-535:i386 
libnvidia-gl-535:i386 libpango-1.0-0:i386 libpangocairo-1.0-0:i386 
libpangoft2-1.0-0:i386
libprocesscore9 libprocessui9 libqt6webengine6-data librsvg2-2:i386 
librsvg2-common:i386 libsane-common libselinux1 libselinux1:i386 
libselinux1-dev libsharpyuv0:i386
libsystemd0:i386 libuuid1:i386 libvirt-daemon-config-network 
libvirt-daemon-config-nwfilter libvirt-daemon-system-systemd libvirt-l10n 
libvolume-key1 libwebp7:i386
libzvbi-common mesa-vulkan-drivers:i386 plasma-desktop-data 
plasma-discover-common powerdevil-data python3-magic 
qml-module-org-kde-ksysguard samba-common
ubuntu-advantage-tools vim vim-common vim-runtime vim-tiny zlib1g:i386
  The following packages will be upgraded:
quassel-data
  1 upgraded, 0 newly installed, 1 to remove and 113 not upgraded.
  Need to get 0 B/866 kB of archives.
  After this operation, 4.382 kB disk space will be freed.
  Do you want to continue? [Y/n]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2060102/+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 2063332] Re: Multiple problems Ubuntu 24.04 with Qt5

[Dmitry Shachnev]

What you describe sounds like an effect of switching from X11 to
Wayland, not a regression in Qt.

In X11, the window decorations can be drawn either by the window manager
or by the application itself. Qt relied on window manager, so the
decorations looked uniform.

In Wayland, there is no choice, and Qt draws its own window decorations,
which may be different from GNOME ones. If you signed into a Wayland
session in Ubuntu 22.04, you would likely get the same effect.

There is a third-party package which may make things better for Qt
applications in GNOME: qgnomeplatform-qt5. After installing it, try
running your application with QT_QPA_PLATFORMTHEME=gnome environment
variable.

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

Title:
  Multiple problems Ubuntu 24.04 with Qt5

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

Bug description:
  After the upgrade to the 24.04 beta Qt5 UI is not at its best. Please,
  notice that all this functionality is working on 22.04.

  1. Windows controls settings from Gnome are not applied
  When you set the Windows Title bar buttons to Placement Left, then Qt apps 
ignore this setting. The default gt4 apps behave properly and place the buttons 
to the left.

  2. Windows actions like double click to maximize from settings also do
  not with in the Qt5 apps unlike in gt4 apps.

  3. Several keyboard shortcuts are passed differently to Qt5 apps.
  The key "Ctrl+Period" is not passed to the qt app at all
  The key "Ctrl+~" is passed as "Ctrl+0"
  The key "Shift+Alt+F7" is also not working
  This means some different handling is applied in Qt5 apps

  4. If you use the env var "export QT_QPA_PLATFORM=xcb" and start the
  Qt5 app, then it all works properly. The windows controls are on the
  right side, you can use double click the title bar to maximize and
  also the shortcuts are working fine. However, in such scenario no app
  starts fullscreen. It starts in a positioned window (the position is
  remembered) instead even if you maximized the window before you exited
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libqt5core5t64 5.15.13+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
  Uname: Linux 6.8.0-28-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 14:20:24 2024
  InstallationDate: Installed on 2020-05-12 (1443 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to noble on 2024-04-20 (4 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-04-19T01:50:32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2063332/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

Thank you for the patch!

Qt 6 still uses unsigned long:
https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/tls/openssl/qsslsocket_openssl_symbols.cpp#n126

Can you please submit your patch to codereview.qt-project.org, or at
least file a bug at bugreports.qt.io?

We usually don't add patches that were not merged upstream.

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

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

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

Thank you. Once the patch is accepted upstream, I will backport it to
Debian/Ubuntu packaging.

In Ubuntu we don't care about older OpenSSL versions, but upstream Qt
does care.

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

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

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

Thank you. I will be offline for a few days, so I will upload this next
week.

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

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

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

I used your patch from comment #10 with only one minor change: for old
OpenSSL versions I replaced long with unsigned long to match the latest
version of upstream patch. But it doesn't matter for Ubuntu anyway.

I am attaching a debdiff for jammy-security and subscribing ~ubuntu-
security-sponsors.

** Patch added: "qtbase-opensource-src_5.15.3+dfsg-2ubuntu0.2.diff"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+attachment/5607636/+files/qtbase-opensource-src_5.15.3+dfsg-2ubuntu0.2.diff

** Also affects: qtbase-opensource-src (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu Jammy)
   Status: New => Confirmed

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Jammy:
  Confirmed

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

I was not able to test it on Ubuntu because I don't have armhf hardware,
but I have just tested it on a Debian porterbox. The only difference
between Debian bookworm and sid versions of Qt is presence of this
patch.

I used this test code and complied it with qmake && make.

mitya57@harris:~/test$ cat test.pro
CONFIG += debug warn_all
QT = core network
SOURCES = test.cpp

mitya57@harris:~/test$ cat test.cpp
#include 
#include 
#include 
#include 

int main(int argc, char **argv) {
QCoreApplication app(argc, argv);
QSslSocket s;
QSslConfiguration cfg = s.sslConfiguration();
cfg.setProtocol(QSsl::TlsV1_3OrLater);
s.setSslConfiguration(cfg);
s.connectToHostEncrypted("www.ubuntu.com", 443);
s.waitForConnected();
qDebug() << s.sessionProtocol();
return 0;
}

Without patch:

(bookworm_armhf-dchroot)mitya57@harris:~/test$ ./test 
-1

With patch:

(sid_armhf-dchroot)mitya57@harris:~/test$ ./test 
15

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Jammy:
  Confirmed

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1986936] Re: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages

[Dmitry Shachnev]

You probably need to install qtbase5-dev:i386, not just libqt5*:i386.

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

Title:
  No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the
  corresponding :i386 packages

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

Bug description:
  While trying to link against corresponding libraries to get i386 executable 
like that:
  > g++ -m32 -o filename . -lQt5Widgets -lQt5Gui -lQt5Core ...

  I get the following errors:

  > /usr/bin/ld: skipping incompatible 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets  

   
  > /usr/bin/ld: cannot find -lQt5Widgets: No such file or directory

  
  > /usr/bin/ld: skipping incompatible 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets  

   
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so 
when searching for -lQt5Gui 

  > /usr/bin/ld: cannot find -lQt5Gui: No such file or directory

  
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so 
when searching for -lQt5Gui 

  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so 
when searching for -lQt5Core
   
  > /usr/bin/ld: cannot find -lQt5Core: No such file or directory   

  
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so 
when searching for -lQt5Core 

  despite corresponging packages are installed (libqt5gui5:i386 and same
  for widgets and core).

  Inspection of /usr/lib/i386-linux-gnu/ reveals that there is no
  symlinks named exactly libQt5Core.so (and same for two other libs).

  Adding those symlinks by hand completely solves the problem.

  I believe however that those symlinks must be installed by
  corresponding .debs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1986936/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

A few days ago I asked on #ubuntu-security about it and was told that it's 
better to make a non-security SRU upload for it:
https://irclogs.ubuntu.com/2022/08/22/%23ubuntu-security.html#t12:01

So I uploaded it, and now it's waiting in unapproved queue for a release team 
member review:
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Jammy:
  Confirmed

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

Oops, forgot about that. Done.

Also, ABI is not affected. We have symbols to track ABI, and there are
no symbols changes for libqt5network5.

** Description changed:

+ [Impact]
+ 
+ Qt 5 Network library does not use TLS 1.3 on armhf, and falls back to
+ less secure protocols.
+ 
+ [Test Plan]
+ 
+ 1. Create test.cpp with the following contents:
+ 
+ #include 
+ #include 
+ #include 
+ #include 
+ 
+ int main(int argc, char **argv) {
+ QCoreApplication app(argc, argv);
+ QSslSocket s;
+ QSslConfiguration cfg = s.sslConfiguration();
+ cfg.setProtocol(QSsl::TlsV1_3OrLater);
+ s.setSslConfiguration(cfg);
+ s.connectToHostEncrypted("www.ubuntu.com", 443);
+ s.waitForConnected();
+ qDebug() << s.sessionProtocol();
+ return 0;
+ }
+ 
+ 2. Create test.pro with the following contents:
+ 
+ CONFIG += debug warn_all
+ QT = core network
+ SOURCES = test.cpp
+ 
+ 3. Install qtbase5-dev package.
+ 
+ 4. Compile using `qmake && make`.
+ 
+ 5. Run the generated ./test executable. It should print 15, not -1.
+ 
+ [Where problems could occur]
+ 
+ It is unlikely to cause issues on 64-bit platforms because long and
+ uint64_t are both 64 bits long. On armhf potential problems may be
+ related to availability of other protocols.
+ 
+ [Original Description]
+ 
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04
  
  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf
  
  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).
  
  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)
  
  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());
  
  marking it as security since the most secure tls protocol is not used on
  some platforms

** Changed in: qtbase-opensource-src (Ubuntu Jammy)
   Status: Incomplete => Confirmed

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  Qt 5 Network library does not use TLS 1.3 on armhf, and falls back to
  less secure protocols.

  [Test Plan]

  1. Create test.cpp with the following contents:

  #include 
  #include 
  #include 
  #include 

  int main(int argc, char **argv) {
  QCoreApplication app(argc, argv);
  QSslSocket s;
  QSslConfiguration cfg = s.sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s.setSslConfiguration(cfg);
  s.connectToHostEncrypted("www.ubuntu.com", 443);
  s.waitForConnected();
  qDebug() << s.sessionProtocol();
  return 0;
  }

  2. Create test.pro with the following contents:

  CONFIG += debug warn_all
  QT = core network
  SOURCES = test.cpp

  3. Install qtbase5-dev package.

  4. Compile using `qmake && make`.

  5. Run the generated ./test executable. It should print 15, not -1.

  [Where problems could occur]

  It is unlikely to cause issues on 64-bit platforms because long and
  uint64_t are both 64 bits long. On armhf potential problems may be
  related to availability of other protocols.

  [Original Description]

  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions


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

[Touch-packages] [Bug 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

Marking as verified per comment #23. I also restarted the failed
autopkgtest.

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Qt 5 Network library does not use TLS 1.3 on armhf, and falls back to
  less secure protocols.

  [Test Plan]

  1. Create test.cpp with the following contents:

  #include 
  #include 
  #include 
  #include 

  int main(int argc, char **argv) {
  QCoreApplication app(argc, argv);
  QSslSocket s;
  QSslConfiguration cfg = s.sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s.setSslConfiguration(cfg);
  s.connectToHostEncrypted("www.ubuntu.com", 443);
  s.waitForConnected();
  qDebug() << s.sessionProtocol();
  return 0;
  }

  2. Create test.pro with the following contents:

  CONFIG += debug warn_all
  QT = core network
  SOURCES = test.cpp

  3. Install qtbase5-dev package.

  4. Compile using `qmake && make`.

  5. Run the generated ./test executable. It should print 15, not -1.

  [Where problems could occur]

  It is unlikely to cause issues on 64-bit platforms because long and
  uint64_t are both 64 bits long. On armhf potential problems may be
  related to availability of other protocols.

  [Original Description]

  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1999220] Re: libQt5Core.so.5 incompatible with older kernels (<3.15)

[Dmitry Shachnev]

Ubuntu 22.04 (jammy), the current LTS release, has kernel 5.15.
Ubuntu 20.04 (focal), the previous LTS release, has kernel 5.4.
Ubuntu 18.04 (bionic) has kernel 4.15.
Ubuntu 16.04 (xenial) has kernel 4.4.

The version of libQt5Core.so.5 in jammy requires kernel 3.17. This
kernel is present in all mentioned releases. I think it's a reasonable
requirement, we cannot support ancient kernels forever.

This requirement is needed for getrandom feature.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Won't Fix

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

Title:
   libQt5Core.so.5 incompatible with older kernels (<3.15)

Status in qtbase-opensource-src package in Ubuntu:
  Won't Fix

Bug description:
  When running programs that use  libQt5Core.so.5 on pre-3.15 kernels (e.g. 
from a container)
  one gets

  error while loading shared libraries: libQt5Core.so.5: cannot open
  shared object file: No such file or directory

  A workaround (from https://github.com/dnschneid/crouton/wiki/Fix-
  error-while-loading-shared-libraries:-libQt5Core.so.5):

  sudo strip --remove-section=.note.ABI-tag /usr/lib64/libQt5Core.so.5

  At least 20.04 and 22.04 are affected.
  I guess, something can be changed in the way the library compiles to make it 
more portable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1999220/+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 2013095] Re: sphinx autopkgtest needs to be updated for webkit 2.40

[Dmitry Shachnev]

I will fix it via Debian.

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

Title:
  sphinx autopkgtest needs to be updated for webkit 2.40

Status in pygobject package in Ubuntu:
  New
Status in sphinx package in Ubuntu:
  Triaged
Status in texlive-extra package in Ubuntu:
  New

Bug description:
  The sphinx autopkgtest needs to be updated for webkitgtk 2.40 which
  made breaking changes to the gtk4 library (webkit2-5.0 -> webkit-6.0).

  Our usual auto-transition tools didn't detect the autopkgtest-only
  dependency.

  https://github.com/WebKit/WebKit/blob/main/Source/WebKit/gtk/migrating-
  to-webkitgtk-6.0.md

  I am adding some other affected packages for our excuses tracker page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2013095/+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 1926373] Re: Missing header files for Qt3DExtras:

[Dmitry Shachnev]

*** This bug is a duplicate of bug 1878233 ***
https://bugs.launchpad.net/bugs/1878233

This is fixed in Ubuntu 20.10 (Groovy) and newer versions.

Unfortunately it is not possible to fix this for 20.04 (Focal) because
the change does not meet the stable update criteria.

** This bug has been marked a duplicate of bug 1878233
   Unable to locate package/Headers missing

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

Title:
  Missing header files for Qt3DExtras:

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

Bug description:
  Unable to build most examples contained in the qt3d5-examples (and, of
  course, any code that relies on Qt3DExtras). This is caused by a
  missing development package with headers for Qt3DExtras.

  The Qt3DExtras binary library (libQt53DExtras.so) is included in the
  qt3d5-dev package, but all the Qt3DExtras header files are missing
  (Qt3DExtras/QForwardRenderer, Qt3DExtras/QPhongMaterial, etc...). This
  makes QT OpenGL development in Ubuntu pretty much unusable.

  At first, installing mssql-mlservices-python and manually copying it's
  version of the Qt3DExtras headers seemed to be a work-around, but it
  resulted in undefined references during linking.

  I would have tagged "qt3d5-examples" in the "In what package did you
  find this bug?", but it tells me that the package doesn't exist in
  ubuntu, whereas https://packages.ubuntu.com/focal/qt3d5-examples
  clearly lists it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1926373/+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 1850814] Re: Copy & Paste is broken in QT apps after 50 days uptime

[Dmitry Shachnev]

This bug is fixed in Qt 5.12.3 and newer. The current LTS version,
Ubuntu 20.04, has Qt 5.12.8. So this bug is already fixed for some time.

Unfortunately I don't have time to support older releases like 18.04.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => Fix Released

** Bug watch added: Debian Bug tracker #961293
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961293

** Also affects: qtbase-opensource-src (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961293
   Importance: Unknown
   Status: Unknown

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

Title:
  Copy & Paste is broken in QT apps after 50 days uptime

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Debian:
  Unknown

Bug description:
  Please see this bug report:
  https://bugreports.qt.io/browse/QTBUG-65145

  And this corresponding fix:
  https://codereview.qt-project.org/c/qt/qtbase/+/254187/

  Any way to get this included in a Ubuntu 18.04 package update?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libqt5core5a 5.9.5+dfsg-0ubuntu2.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Oct 31 09:14:55 2019
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1850814/+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 1926802] Re: qt5-default package is missed in 21.04

[Dmitry Shachnev]

Qt 4 was removed, Qt 5 is now default, so that package is no longer
needed.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  qt5-default package is missed in 21.04

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

Bug description:
  Previous 20.10 version has the qt5-default package in place (see
  https://packages.ubuntu.com/groovy/qt5-default ).

  Please upload the  qt5-default package for 21.04 Ubuntu version.

  What is interesting - all its dependencies can be simply installed
  with `sudo apt-get install qtbase5-dev qtchooser qt5-qmake qtbase5
  -dev-tools` .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1926802/+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 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

Hi Owen,

Thanks a lot for sharing the log. Indeed, qt5-default seems to be the
cause of this bug. In https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=976389#15 I explained in more detail my
understanding of why this is happening.

The fix should land in Impish (development release) in a few hours, and
then I will look at a fix for Hirsute (21.04).

** Package changed: qtdeclarative-opensource-src (Ubuntu) =>
qtdeclarative-opensource-src-gles (Ubuntu)

** Changed in: qtdeclarative-opensource-src-gles (Ubuntu)
   Status: Won't Fix => Fix Committed

** Also affects: qtdeclarative-opensource-src-gles (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

Title:
  System icons missing in kubuntu 21.04

Status in qtdeclarative-opensource-src-gles package in Ubuntu:
  Fix Committed
Status in qtdeclarative-opensource-src-gles source package in Hirsute:
  New
Status in qtdeclarative-opensource-src-gles package in Debian:
  New

Bug description:
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors 
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  QSGTextureAtlas: texture atlas allocation failed, code=501
  file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML 
ColumnLayout: Cannot anchor to an item that 
  isn't a parent or sibling.
  xsettingsd: Reloading configuration
  xsettingsd: Loaded 11 settings from 
/home/paul/.config/xsettingsd/xsettingsd.conf
  kdeinit5: Got SETENV 
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from 
launcher.
  kdeinit5: Got SETENV 
'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0'
 from launch
  er.
  QDBusConnection: error: could not send signal to service "" path 
"//home/paul/.kde/share/config/kdeglobals" interface 
  "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: 
//home/p

[Touch-packages] [Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

[Dmitry Shachnev]

Qt actually prefers system copy from shared-mime-info if it's available.
Here is the code for 5.12.8 (used in Ubuntu 20.04):

https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/mimetypes/qmimedatabase.cpp?h=5.12.8#n99

The internal copy (":/qt-project.org/qmime") is only used when the
system one is missing (fdoIterator == mimeDirs.constEnd()).

Furthermore, in Ubuntu 20.10 and 21.04 we are building Qt with -no-
mimetype-database, which makes Qt use *only* the system copy:

https://salsa.debian.org/qt-kde-team/qt/qtbase/-/commit/f0d53be16a31ea55

So I think it is a bug in shared-mime-info only, not in Qt. Do you
agree?

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

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

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
  http://www.w3.org/1999/xhtml";>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

[Dmitry Shachnev]

Thank you for the links!

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => In Progress

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Dmitry Shachnev (mitya57)

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
  http://www.w3.org/1999/xhtml";>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

As it turns out, this also needs a change in qtbase-opensource-src.
Change in -gles is not enough:

https://lists.debian.org/debian-devel/2021/05/msg00076.html
https://lists.debian.org/debian-devel/2021/05/msg00150.html

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  System icons missing in kubuntu 21.04

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src-gles package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Hirsute:
  New
Status in qtbase-opensource-src-gles source package in Hirsute:
  New
Status in qtbase-opensource-src-gles package in Debian:
  Fix Released

Bug description:
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors 
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  QSGTextureAtlas: texture atlas allocation failed, code=501
  file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML 
ColumnLayout: Cannot anchor to an item that 
  isn't a parent or sibling.
  xsettingsd: Reloading configuration
  xsettingsd: Loaded 11 settings from 
/home/paul/.config/xsettingsd/xsettingsd.conf
  kdeinit5: Got SETENV 
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from 
launcher.
  kdeinit5: Got SETENV 
'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0'
 from launch
  er.
  QDBusConnection: error: could not send signal to service "" path 
"//home/paul/.kde/share/config/kdeglobals" interface 
  "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: 
//home/paul/.kde/share/config/kdeglobals
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25:
 QML ScrollBar: Bindi
  ng loop detected for property 

[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

** Description changed:

+ [Impact]
+ 
+ This affects Groovy → Hirsute upgrades for users who had qt5-default
+ package installed.
+ 
+ For these users, apt could replace libqt5gui5 with libqt5gui5-gles,
+ which is not suitable for most desktop systems and can result in all
+ kinds of broken UI (such as missing icons).
+ 
+ [Test Plan]
+ 
+ 1. Get a groovy amd64 system (e.g. a chroot).
+ 2. Install qt5-default package.
+ 3. Replace groovy with hirsute in /etc/apt/sources.list.
+ 4. Run "apt update".
+ 5. Run "apt dist-upgade".
+ 
+ Incorrect behavior:
+ 
+ The following packages will be REMOVED:
+   libqt5gui5 qt5-default qtbase5-dev
+ The following NEW packages will be installed:
+   ... libqt5gui5-gles ...
+ 
+ Correct behavior: only qt5-default is removed, libqt5gui5 is not removed
+ and libqt5gui5-gles is not installed.
+ 
+ [Where problems could occur]
+ 
+ The fix is adding "Breaks: qt5-default" in three packages:
+ - qtbase5-dev (built from qtbase-opensource-src source).
+ - qtbase5-gles-dev (built from qtbase-opensource-src-gles source).
+ - libqt5gui5-gles (built from qtbase-opensource-src-gles source).
+ 
+ It can affect apt's dependency resolver. Example of a problem may be the
+ resolver keeping the old behavior in some cases.
+ 
+ [Other Info]
+ 
+ See this post for details on what the -gles packages are:
+ https://mitya57.me/weblog/2020/01/qt-opengl-es-packages-available.html
+ 
+ See my discussion with one of the developers of apt on this issue:
+ https://lists.debian.org/debian-devel/2021/05/msg00076.html
+ https://lists.debian.org/debian-devel/2021/05/msg00150.html
+ https://lists.debian.org/debian-devel/2021/05/msg00162.html
+ 
+ Also see this comment where I collected some links to stories of users who 
were affected by this bug:
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976389#10
+ 
+ [Original Description]
+ 
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially
  was fine, but I then install kdenlive and krita which has messed up the
  system icons and window decorations (corners of windows are showing
  black squares).
  
  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.
  
  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04
  
  Looking at the following may shed some light on the problem...
  
  Thanks, Paul.
  
- more .xsession-errors 
+ more .xsession-errors
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
- 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
+  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
+ 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
+  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
-  of null
+  of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
- 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or ances

[Touch-packages] [Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

[Dmitry Shachnev]

The fix should land in Impish (21.10) very soon:
https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.15.2+dfsg-6.

Do you also want a fix for Hirsute (21.04)? If yes, you can help me by
filling the SRU template in the description (see
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template).

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
  http://www.w3.org/1999/xhtml";>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

I have performed the verification following the Test Plan. The full log
is attached.

Relevant part:

The following packages will be REMOVED:
  qt5-default
The following NEW packages will be installed:
  gcc-11-base libboost-iostreams1.74.0 libcap2 libisl23 libmd0 libperl5.32 
libxrender1 libxxhash0 lto-disabled-list perl-modules-5.32
The following packages will be upgraded:
  ... libqt5core5a libqt5dbus5 libqt5gui5 ...

As can be seen here, no *-gles packages are installed.

** Attachment added: "chroot-upgrade.txt"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src-gles/+bug/1920130/+attachment/5504247/+files/chroot-upgrade.txt

** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute

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

Title:
  System icons missing in kubuntu 21.04

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src-gles package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Hirsute:
  Fix Committed
Status in qtbase-opensource-src-gles source package in Hirsute:
  Fix Committed
Status in qtbase-opensource-src-gles package in Debian:
  Fix Released

Bug description:
  [Impact]

  This affects Groovy → Hirsute upgrades for users who had qt5-default
  package installed.

  For these users, apt could replace libqt5gui5 with libqt5gui5-gles,
  which is not suitable for most desktop systems and can result in all
  kinds of broken UI (such as missing icons).

  [Test Plan]

  1. Get a groovy amd64 system (e.g. a chroot).
  2. Install qt5-default package.
  3. Replace groovy with hirsute in /etc/apt/sources.list.
  4. Run "apt update".
  5. Run "apt dist-upgade".

  Incorrect behavior:

  The following packages will be REMOVED:
libqt5gui5 qt5-default qtbase5-dev
  The following NEW packages will be installed:
... libqt5gui5-gles ...

  Correct behavior: only qt5-default is removed, libqt5gui5 is not
  removed and libqt5gui5-gles is not installed.

  [Where problems could occur]

  The fix is adding "Breaks: qt5-default" in three packages:
  - qtbase5-dev (built from qtbase-opensource-src source).
  - qtbase5-gles-dev (built from qtbase-opensource-src-gles source).
  - libqt5gui5-gles (built from qtbase-opensource-src-gles source).

  It can affect apt's dependency resolver. Example of a problem may be
  the resolver keeping the old behavior in some cases.

  [Other Info]

  See this post for details on what the -gles packages are:
  https://mitya57.me/weblog/2020/01/qt-opengl-es-packages-available.html

  See my discussion with one of the developers of apt on this issue:
  https://lists.debian.org/debian-devel/2021/05/msg00076.html
  https://lists.debian.org/debian-devel/2021/05/msg00150.html
  https://lists.debian.org/debian-devel/2021/05/msg00162.html

  Also see this comment where I collected some links to stories of users who 
were affected by this bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976389#10

  [Original Description]

  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
Typ

[Touch-packages] [Bug 1933669] Re: qt3d5-dev - cmake support missing for Qt3D Animation

[Dmitry Shachnev]

*** This bug is a duplicate of bug 1878233 ***
https://bugs.launchpad.net/bugs/1878233

Unfortunately these files are only available in newer Ubuntu versions (≥
20.10). See bug 1878233 for details.

** This bug has been marked a duplicate of bug 1878233
   Unable to locate package/Headers missing

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

Title:
  qt3d5-dev - cmake support missing for Qt3D Animation

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

Bug description:
  Hello,

  I'm working on a Qt application which uses the Qt3D module. The
  application is spec'd to support ubuntu 20.04 at least.

  The qt3d-dev package (at least on focal) is missing the following
  files:

  /usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfig.cmake
  
/usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfigVersion.cmake

  All others Qt3D modules have their own similar files but not the Animation 
module.
  This prevent me from building my application using official packages.
  Are they missing on purpose? Is there any work around?

  All the best

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1933669/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

** Description changed:

+ [Impact]
+ 
  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593
  
  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942
  
- The original issue is public since July 29th. If I'm allowed to upload
- further files, I'll send a simple test program.
+ The original issue is public since July 29th.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
- Package: libqt5svg5 5.12.8-0ubuntu1
- ProcVersionSignature: Ubuntu 5.14.0-1005.5-oem 5.14.9
- Uname: Linux 5.14.0-1005-oem x86_64
- ApportVersion: 2.20.11-0ubuntu27.21
- Architecture: amd64
- CasperMD5CheckResult: skip
- CurrentDesktop: GNOME
- Date: Mon Nov  8 20:24:34 2021
- InstallationDate: Installed on 2012-07-06 (3411 days ago)
- InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
- ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
- SourcePackage: qtsvg-opensource-src
- UpgradeStatus: Upgraded to focal on 2020-10-03 (400 days ago)
+ [Test Plan]
+ 
+ 1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
+ 2. Build the attached project with the system's version of Qt:
+/usr/lib/qt5/bin/qmake test-2021-38593.pro && make
+ 3. Start the resulting binary and pass the path to the included input file as 
first parameter:
+./test-2021-38593 ./input.svg
+The binary should return immediately and without error messages. If it 
doesn't, you might be affected.
+ 
+ [Where problems could occur]
+ 
+ The fix tries to skip drawing dashes that would be invisible anyway. So
+ a potential problem may that it skips too much. In fact, this has
+ already happened, and upstream had to adjust the fix.
+ 
+ [Other Info]
+ 
+ The patch is a combination of the following upstream commits:
+ 
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  New

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

** Also affects: qtbase-opensource-src (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  New
Status in qtbase-opensource-src source package in Impish:
  New

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

Tested in an Impish chroot:

root@mitya57:/test# time ./test-2021-38593 ./input.svg
Testing for CVE-2021-38593...
If the test doesn't finish immediately, you probably are affected.
Test finished.

real0m0.033s
user0m0.004s
sys 0m0.017s
root@mitya57:/test# echo $?
0
root@mitya57:/test# apt policy libqt5gui5
libqt5gui5:
  Installed: 5.15.2+dfsg-12ubuntu1
  Candidate: 5.15.2+dfsg-12ubuntu1
  Version table:
 *** 5.15.2+dfsg-12ubuntu1 500
500 http://archive.ubuntu.com/ubuntu impish-proposed/universe amd64 
Packages
100 /var/lib/dpkg/status
 5.15.2+dfsg-12 500
500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages

With the version from release pocket, the test program does not finish
after 30 seconds.

** Tags removed: verification-needed verification-needed-impish
** Tags added: verification-done verification-done-impish

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  Fix Committed
Status in qtbase-opensource-src source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

Marc, can you do it please? You can take my changes but use a different
version number so that it's rebuilt. Then we will ask the SRU team to
remove the versions in -proposed.

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  Fix Committed
Status in qtbase-opensource-src source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

Ok, thank you Paulo.

As advised by Brian, I'm adding block-proposed tags to make sure the
current packages don't get accidentally released.

** Tags added: block-proposed-focal block-proposed-impish

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  Fix Committed
Status in qtbase-opensource-src source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1946595] Re: indicator-applet-complete clock occasionally shows UTC

[Dmitry Shachnev]

The applet just shows what the actual indicator provides, so reassigning
to indicator-datetime.

** Package changed: indicator-applet (Ubuntu) => indicator-datetime
(Ubuntu)

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

Title:
  indicator-applet-complete clock occasionally shows UTC

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Sometimes at login, but sometimes at other times, the clock in
  indicator-applet-complete starts showing UTC instead of local.

  It is not a system clock problem, in the terminal and in the
  standalone clock applet the time is correct. See
  https://i.stack.imgur.com/x11A4.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: indicator-applet-complete (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Oct 10 08:37:00 2021
  InstallationDate: Installed on 2018-04-27 (1261 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: indicator-applet
  UpgradeStatus: Upgraded to focal on 2021-10-03 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1946595/+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 1946595] Re: indicator-applet-complete clock occasionally shows UTC

[Dmitry Shachnev]

Standalone is not indicator, it's mate-panel's built-in clock applet.

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

Title:
  indicator-applet-complete clock occasionally shows UTC

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Sometimes at login, but sometimes at other times, the clock in
  indicator-applet-complete starts showing UTC instead of local.

  It is not a system clock problem, in the terminal and in the
  standalone clock applet the time is correct. See
  https://i.stack.imgur.com/x11A4.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: indicator-applet-complete (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Oct 10 08:37:00 2021
  InstallationDate: Installed on 2018-04-27 (1261 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: indicator-applet
  UpgradeStatus: Upgraded to focal on 2021-10-03 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1946595/+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 1951470] Re: webkit javascript segmentation fault

[Dmitry Shachnev]

I have uploaded Focal, Impish and Hirsute debdiffs, they are now waiting
for approval in review queues.

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

Title:
  webkit javascript segmentation fault

Status in Ubuntu on IBM z Systems:
  In Progress
Status in qtwebkit-opensource-src package in Ubuntu:
  Fix Released
Status in qtwebkit-opensource-src source package in Focal:
  In Progress
Status in qtwebkit-opensource-src source package in Hirsute:
  In Progress
Status in qtwebkit-opensource-src source package in Impish:
  In Progress
Status in qtwebkit-opensource-src source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

   * WebKit Javascript engine is causing a segmentation fault on big
  endian (s390x) systems.

   * This happens for example when transferring an html to a pdf file
  using wkhtmltopdf.

   * The fix is relatively simple with changing loadisFromInstruction to 
loadpFromInstruction
 in macro getProperty(slow), which solves this unpleasant situation.

   * The JIT ocde is 32bit (even on 64bit systems),
 hence is crucial to make sure the lower part of a 64bit value is taken on 
big endian systems.

  [Test Plan]

   * Testing is very straight forward by following these steps:

   * install the following packages (incl. their dependencies):
 $ sudo apt install libqt5webkit5 wkhtmltopdf

   * create an html file like this:
 $ vi index.html
 $ cat index.html
 
 
   
   
 
   
 
   
 

   * create a JavaScript file like this:
 $ vi min.js
 $ cat min.js
 var i = Math.max

   * call wkhtmltopdf to process the local files:
 $ wkhtmltopdf --enable-local-file-access index.html test.pdf

   * if it's broken one gets this output:
 Loading page (1/2)
 Segmentation fault (core dumped) ] 50%
 and no pdf file was generated:
 $ ls *.pdf
 ls: cannot access '*.pdf': No such file or directory

   * in case it's fixed one gets this output:
 Loading page (1/2)
 Printing pages (2/2)   
 Done   
 and a pdf file was generated and in placed in the current directory (with 
more than 0 bytes size):
 $ ls -l ./*.pdf
 -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf

  [Where problems could occur]

   * While this issue only affects big endian systems (like s390x),
 a bad fix may have an impact on little endian systems, too
 for example in case the wrong function got used in the macro.

   * But loadpFromInstruction is known to work for LE and BE systems;

   * and on top cross-architecture builds were done:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470

   * and tested on s390x (if the fix works) and on non-s390x (regression
  testing).

   * The changes are otherwise very limited, just:
 macro getProperty(slow)
 -loadisFromInstruction(6, t1)
 +loadpFromInstruction(6, t1)
 hence I think there is not much more to say.

  [Other Info]
   
   * The maintainer of the Debian packages (Dmitry Shachnev)
 is going to add this to the Debian package, too.

   * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs
  are ongoing.

   * The issue does not occur with the very latest upstream version anymore,
 and was fixed in a similar way as part of a commit
 that fixes numerous other CLoop issues on top:
 "Fix all CLoop JSC test failures (including some LLInt bugs due to recent 
bytecode format change)."
 commit 3fdde71c7d95d758a61fcbc4c58168616794c102

  __

  == Comment: #0 - Andreas Krebbel  - 2021-11-15 
09:29:44 ==
  ---Problem Description---
  Segmentation fault from WebKit Javascript engine

  Contact Information = andreas.kreb...@de.ibm.com

  ---uname output---
  Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 
s390x s390x s390x GNU/Linux

  Machine Type = IBM Z

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   index.html:
  
  
    
    

    
  
    
  

  min.js:
  var i = Math.max

  wkhtmltopdf index.html test.pdf
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Loading page (1/2)
  Segmentation fault (core dumped) ] 17%

  Userspace tool common name: wkhtmltopdf

  The userspace tool has the following bit modes: 64

  Userspace rpm: libqt5webkit5

  Userspace tool obtained from project website:  na

  *Additional Instructions for andreas.kreb...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Andreas Krebbel  - 2021-11-15 
09:44:04 ==
  In CodeBlock.cpp the code preparing the operands of op_get_f

[Touch-packages] [Bug 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

** Package changed: qtsvg-opensource-src (Ubuntu) => qtbase-opensource-
src (Ubuntu)

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Dmitry Shachnev (mitya57)

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th. If I'm allowed to upload
  further files, I'll send a simple test program.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libqt5svg5 5.12.8-0ubuntu1
  ProcVersionSignature: Ubuntu 5.14.0-1005.5-oem 5.14.9
  Uname: Linux 5.14.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Nov  8 20:24:34 2021
  InstallationDate: Installed on 2012-07-06 (3411 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: qtsvg-opensource-src
  UpgradeStatus: Upgraded to focal on 2020-10-03 (400 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

> Anything I can do now to help this arrive in 20.04?

No, I just need to find some free time again. Thanks for reminding me.

** Also affects: qtbase-opensource-src (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  New

Bug description:
  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th. If I'm allowed to upload
  further files, I'll send a simple test program.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libqt5svg5 5.12.8-0ubuntu1
  ProcVersionSignature: Ubuntu 5.14.0-1005.5-oem 5.14.9
  Uname: Linux 5.14.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Nov  8 20:24:34 2021
  InstallationDate: Installed on 2012-07-06 (3411 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: qtsvg-opensource-src
  UpgradeStatus: Upgraded to focal on 2020-10-03 (400 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 2016703] Re: qbusmacros.h fails to compile: wrong case on case-sensitive include

[Dmitry Shachnev]

This bug is still present in Qt 6. Submitted a fix upstream:
https://codereview.qt-project.org/c/qt/qtbase/+/472832.

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

Title:
  qbusmacros.h fails to compile: wrong case on case-sensitive include

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

Bug description:
  /usr/include/arm-linux-gnueabihf/qt5/QtDBus/qdbusmacros.h in
  qtbase5-dev cannot compile:

  /usr/include/arm-linux-gnueabihf/qt5/QtDBus/qdbusmacros.h:8:10: fatal error: 
QtDbus/qtdbusglobal.h: No such file or directory
  8 | #include 
|  ^~~
  compilation terminated.

  
  The correct filename is , not .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2016703/+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 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04

[Dmitry Shachnev]

I don't remember why I disabled animation in that commit. Probably I had
some build failure when it's enabled.

Anyway, qtstyleplugins is abandoned and no longer developed (the last
commit was more than 6 years ago). I recommend to NOT include it in
dependencies of any package.

Qt 6.5.0 will have a much improved GTK 3 integration support:
https://code.qt.io/cgit/qt/qtbase.git/commit/?id=4ca8a6840842d5ff.

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

Title:
  Indeterminate Qt progress bars don't display properly in 20.04

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

Bug description:
  In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar
  (meaning its minimum and maximum values have both been set to zero)
  does not display properly. It is supposed to animate in a way that
  shows that something is happening with an unknown time remaining.
  Instead, it sits still with its progress bar showing approximately 25
  to 30% progress.

  To test this, make a simple Qt program with a QProgressBar in the main
  window, and add these lines to the constructor of the main window:

  ui->progressBar->setMinimum(0);
  ui->progressBar->setMaximum(0);

  This problem is not present in standard Ubuntu 20.04. Standard Ubuntu
  correctly animates the indeterminate progress bar. It's unclear to me
  which package is at fault, but it seems to be something specific to
  Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem.

  Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it
  doesn't have this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1906138/+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 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04

[Dmitry Shachnev]

Okay, I can try patching out the QT_NO_ANIMATION line in our packaging.

** No longer affects: qtbase-opensource-src (Ubuntu)

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

Title:
  Indeterminate Qt progress bars don't display properly in 20.04

Status in qtstyleplugins-src package in Ubuntu:
  New

Bug description:
  In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar
  (meaning its minimum and maximum values have both been set to zero)
  does not display properly. It is supposed to animate in a way that
  shows that something is happening with an unknown time remaining.
  Instead, it sits still with its progress bar showing approximately 25
  to 30% progress.

  To test this, make a simple Qt program with a QProgressBar in the main
  window, and add these lines to the constructor of the main window:

  ui->progressBar->setMinimum(0);
  ui->progressBar->setMaximum(0);

  This problem is not present in standard Ubuntu 20.04. Standard Ubuntu
  correctly animates the indeterminate progress bar. It's unclear to me
  which package is at fault, but it seems to be something specific to
  Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem.

  Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it
  doesn't have this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1906138/+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 1986936] Re: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages

[Dmitry Shachnev]

> what package the link libQt5Core.so is supposed to be a part of

qtbase5-dev

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the
  corresponding :i386 packages

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

Bug description:
  While trying to link against corresponding libraries to get i386 executable 
like that:
  > g++ -m32 -o filename . -lQt5Widgets -lQt5Gui -lQt5Core ...

  I get the following errors:

  > /usr/bin/ld: skipping incompatible 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets  

   
  > /usr/bin/ld: cannot find -lQt5Widgets: No such file or directory

  
  > /usr/bin/ld: skipping incompatible 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets  

   
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so 
when searching for -lQt5Gui 

  > /usr/bin/ld: cannot find -lQt5Gui: No such file or directory

  
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so 
when searching for -lQt5Gui 

  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so 
when searching for -lQt5Core
   
  > /usr/bin/ld: cannot find -lQt5Core: No such file or directory   

  
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so 
when searching for -lQt5Core 

  despite corresponging packages are installed (libqt5gui5:i386 and same
  for widgets and core).

  Inspection of /usr/lib/i386-linux-gnu/ reveals that there is no
  symlinks named exactly libQt5Core.so (and same for two other libs).

  Adding those symlinks by hand completely solves the problem.

  I believe however that those symlinks must be installed by
  corresponding .debs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1986936/+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 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

Hi! I am the Qt maintainer here.

The fix mentioned in https://bugs.launchpad.net/ubuntu/+source
/qtdeclarative-opensource-src/+bug/1920130/comments/4 is the correct
one. libqt5quick5-gles is not intended for general use, it should be
only installed on OpenGL ES capable hardware.

However, I really want to understand how users end up with this package
being installed. See this related thread in Debian:
https://lists.debian.org/debian-devel/2021/01/msg00404.html.

If anyone else upgrading from Groovy to Hirsute sees this, please attach
here these log files (or, if you think they are private, send them
directly to me mity...@ubuntu.com):

- /var/log/apt/history.log
- /var/log/apt/term.log

Also if removing libqt5quick5-gles tries to remove any other package
(which does not have -gles in name), please paste the list of those
packages.

** Bug watch added: Debian Bug tracker #976389
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976389

** Also affects: qtdeclarative-opensource-src-gles (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976389
   Importance: Unknown
   Status: Unknown

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

Title:
  System icons missing in kubuntu 21.04

Status in qtdeclarative-opensource-src package in Ubuntu:
  Won't Fix
Status in qtdeclarative-opensource-src-gles package in Debian:
  Unknown

Bug description:
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors 
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  QSGTextureAtlas: texture atlas allocation failed, code=501
  file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML 
ColumnLayout: Cannot anchor to an item that 
  isn't a parent or sibling.
  xsettingsd: Reloading configuration
  xsettingsd: Loaded 11 settings from 
/home/paul/.config/xsettingsd/xsettingsd.conf
  kdeinit5: Got SETENV 
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home

[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

@poet_imp Thanks for the logs! Unfortunately, these are only the latest
logs and they don't explain what happened when you upgraded Ubuntu.

Maybe you can attach the historical logs from /var/log/apt too? They
have names like history.log.*.gz and term.log.*.gz. If you upgraded
recently, then I guess it would be *.1.gz. Otherwise you can look at
modification dates.

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

Title:
  System icons missing in kubuntu 21.04

Status in qtdeclarative-opensource-src package in Ubuntu:
  Won't Fix
Status in qtdeclarative-opensource-src-gles package in Debian:
  New

Bug description:
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors 
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  QSGTextureAtlas: texture atlas allocation failed, code=501
  file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML 
ColumnLayout: Cannot anchor to an item that 
  isn't a parent or sibling.
  xsettingsd: Reloading configuration
  xsettingsd: Loaded 11 settings from 
/home/paul/.config/xsettingsd/xsettingsd.conf
  kdeinit5: Got SETENV 
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from 
launcher.
  kdeinit5: Got SETENV 
'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0'
 from launch
  er.
  QDBusConnection: error: could not send signal to service "" path 
"//home/paul/.kde/share/config/kdeglobals" interface 
  "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: 
//home/paul/.kde/share/config/kdeglobals
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25:
 QML ScrollBar: Bindi
  ng loop detected for property "visible"
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kcm/GridViewKCM.qml:65:5: 
QML GridView: Binding loop detected for pro
 

[Touch-packages] [Bug 1926802] Re: qt5-default package is missed in 21.04

[Dmitry Shachnev]

What is the point of installing runtime libraries by hand?

The idea is that you install some application that you want to use, and
it pulls the library packages as dependencies.

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

Title:
  qt5-default package is missed in 21.04

Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in Unity Linux:
  New

Bug description:
  Previous 20.10 version has the qt5-default package in place (see
  https://packages.ubuntu.com/groovy/qt5-default ).

  Please upload the  qt5-default package for 21.04 Ubuntu version.

  What is interesting - all its dependencies can be simply installed
  with `sudo apt-get install qtbase5-dev qtchooser qt5-qmake
  qtbase5-dev-tools` .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1926802/+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 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

[Dmitry Shachnev]

OK, I have just uploaded the fix for Cosmic too. If you want to test it
before it is accepted into -proposed, it is also available here:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3634.

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  In Progress
Status in qtbase-opensource-src source package in Cosmic:
  In Progress

Bug description:
  [Impact]
  All kde applications shipped with ubuntu and particularly kubuntu bionic 
print via the qt print dialog, that, unfortunately, does not seem to respect 
the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  [Test Case]
  1) Install a printer that can duplex and configure it to do duplex with 
long-edge binding from the printer setup dialog.

  2) Open a PDF with okular, and open the print dialog. Select the
  printer above.

  3) Press the "Options" button to enlarge the dialog to also present
  the options. Select the "options" tab, right of "copies". Verify that
  Duplex Printing is preset to "None"

  This is wrong, because the printer was configured to do duplex with
  long-edge binding.

  4) Print and close okular.

  5) Reopen okular (with the same or another PDF file). Open again the
  print dialog and select the same printer.

  6) Redo 3). Again see that Duplex Printing is preset to "None",
  instead of being at the default or at the previously used setup.

  [Regression Potential]
  The proposed patch only changes the default settings. The regression 
potential may be that the values are wrong, although they are already wrong.

  In case there is some bug it may lead to crashes. But this code is in
  the latest stable Qt release and I am not aware of any such crashes
  reported.

  [Other Info]
  The proposed patch is a backport of the following upstream commits:
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e

  [Original Description]
  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

[Dmitry Shachnev]

** Changed in: qtbase-opensource-src (Ubuntu Cosmic)
   Status: Incomplete => In Progress

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  In Progress
Status in qtbase-opensource-src source package in Cosmic:
  In Progress

Bug description:
  [Impact]
  All kde applications shipped with ubuntu and particularly kubuntu bionic 
print via the qt print dialog, that, unfortunately, does not seem to respect 
the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  [Test Case]
  1) Install a printer that can duplex and configure it to do duplex with 
long-edge binding from the printer setup dialog.

  2) Open a PDF with okular, and open the print dialog. Select the
  printer above.

  3) Press the "Options" button to enlarge the dialog to also present
  the options. Select the "options" tab, right of "copies". Verify that
  Duplex Printing is preset to "None"

  This is wrong, because the printer was configured to do duplex with
  long-edge binding.

  4) Print and close okular.

  5) Reopen okular (with the same or another PDF file). Open again the
  print dialog and select the same printer.

  6) Redo 3). Again see that Duplex Printing is preset to "None",
  instead of being at the default or at the previously used setup.

  [Regression Potential]
  The proposed patch only changes the default settings. The regression 
potential may be that the values are wrong, although they are already wrong.

  In case there is some bug it may lead to crashes. But this code is in
  the latest stable Qt release and I am not aware of any such crashes
  reported.

  [Other Info]
  The proposed patch is a backport of the following upstream commits:
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e

  [Original Description]
  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

[Dmitry Shachnev]

Sergio, Robert: can you please test the packages in bionic-proposed and
cosmic-proposed?

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  All kde applications shipped with ubuntu and particularly kubuntu bionic 
print via the qt print dialog, that, unfortunately, does not seem to respect 
the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  [Test Case]
  1) Install a printer that can duplex and configure it to do duplex with 
long-edge binding from the printer setup dialog.

  2) Open a PDF with okular, and open the print dialog. Select the
  printer above.

  3) Press the "Options" button to enlarge the dialog to also present
  the options. Select the "options" tab, right of "copies". Verify that
  Duplex Printing is preset to "None"

  This is wrong, because the printer was configured to do duplex with
  long-edge binding.

  4) Print and close okular.

  5) Reopen okular (with the same or another PDF file). Open again the
  print dialog and select the same printer.

  6) Redo 3). Again see that Duplex Printing is preset to "None",
  instead of being at the default or at the previously used setup.

  [Regression Potential]
  The proposed patch only changes the default settings. The regression 
potential may be that the values are wrong, although they are already wrong.

  In case there is some bug it may lead to crashes. But this code is in
  the latest stable Qt release and I am not aware of any such crashes
  reported.

  [Other Info]
  The proposed patch is a backport of the following upstream commits:
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e

  [Original Description]
  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

[Dmitry Shachnev]

** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  All kde applications shipped with ubuntu and particularly kubuntu bionic 
print via the qt print dialog, that, unfortunately, does not seem to respect 
the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  [Test Case]
  1) Install a printer that can duplex and configure it to do duplex with 
long-edge binding from the printer setup dialog.

  2) Open a PDF with okular, and open the print dialog. Select the
  printer above.

  3) Press the "Options" button to enlarge the dialog to also present
  the options. Select the "options" tab, right of "copies". Verify that
  Duplex Printing is preset to "None"

  This is wrong, because the printer was configured to do duplex with
  long-edge binding.

  4) Print and close okular.

  5) Reopen okular (with the same or another PDF file). Open again the
  print dialog and select the same printer.

  6) Redo 3). Again see that Duplex Printing is preset to "None",
  instead of being at the default or at the previously used setup.

  [Regression Potential]
  The proposed patch only changes the default settings. The regression 
potential may be that the values are wrong, although they are already wrong.

  In case there is some bug it may lead to crashes. But this code is in
  the latest stable Qt release and I am not aware of any such crashes
  reported.

  [Other Info]
  The proposed patch is a backport of the following upstream commits:
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e

  [Original Description]
  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

[Dmitry Shachnev]

Thanks to you both for testing! Adjusting the tags accordingly.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  All kde applications shipped with ubuntu and particularly kubuntu bionic 
print via the qt print dialog, that, unfortunately, does not seem to respect 
the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  [Test Case]
  1) Install a printer that can duplex and configure it to do duplex with 
long-edge binding from the printer setup dialog.

  2) Open a PDF with okular, and open the print dialog. Select the
  printer above.

  3) Press the "Options" button to enlarge the dialog to also present
  the options. Select the "options" tab, right of "copies". Verify that
  Duplex Printing is preset to "None"

  This is wrong, because the printer was configured to do duplex with
  long-edge binding.

  4) Print and close okular.

  5) Reopen okular (with the same or another PDF file). Open again the
  print dialog and select the same printer.

  6) Redo 3). Again see that Duplex Printing is preset to "None",
  instead of being at the default or at the previously used setup.

  [Regression Potential]
  The proposed patch only changes the default settings. The regression 
potential may be that the values are wrong, although they are already wrong.

  In case there is some bug it may lead to crashes. But this code is in
  the latest stable Qt release and I am not aware of any such crashes
  reported.

  [Other Info]
  The proposed patch is a backport of the following upstream commits:
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e

  [Original Description]
  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1820536] Re: print dialog cups "advanced tab" missing in qt5/kf5 based applications

[Dmitry Shachnev]

*** This bug is a duplicate of bug 1776173 ***
https://bugs.launchpad.net/bugs/1776173

The duplex settings were added in qtbase 5.9.5+dfsg-0ubuntu2, which is
currently available in bionic-proposed.

The whole "Advanced" tab is impossible to backport. If you look at
openSUSE, they have not just patch 0010, but also a lot of patches
related to printing:

https://build.opensuse.org/package/show/openSUSE:Leap:15.0/libqt5-qtbase

These patches change the code completely and also change (private)
API/ABI, so they do not meet the Ubuntu stable release criteria.

** This bug has been marked a duplicate of bug 1776173
   qt print dialog shipped with bionic ignores printer defaults

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

Title:
  print dialog cups "advanced tab" missing in qt5/kf5 based applications

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

Bug description:
  Qt5 (KDE) print dialogs do not show the "Advanced" for cups printers
  in Qt 5.9.5, making the user unable to change settings like duplex
  printing.

  The problem has been reported at
  https://bugreports.qt.io/browse/QTBUG-54464

  It has been fixed in https://codereview.qt-project.org/#/c/213391/

  Please backport this fix to 18.04 since this is an essential feature
  missing in a LTS release.

  There is a patch to Qt 5.9.4 made by the openSUSE devs:

  
https://build.opensuse.org/package/view_file/openSUSE:Leap:15.0/libqt5-qtbase/0010
  -Reintroduce-the-Advanced-tab-in-the-QPrintProperties.patch?expand=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1820536/+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 1821091] [NEW] [FFe] Qt 5.12.2 update

[Dmitry Shachnev]

Public bug reported:

Dear Release Team,

I would like to update Qt in disco from 5.11.3 to 5.12.2.

The reasons are the following:

1) The 5.11 branch is EOL and no longer receiving any fixes. The 5.12
branch is LTS and will be supported for three years.

2) New versions of Plasma are going to require Qt 5.12, and the Kubuntu
team would like to be able to package them in their backports PPA for
disco.

3) In Qt 5.12, the memory usage of the QML Engine is reduced by up to 30
%.

4) Finally we will be able to sync all packages from Debian. I have
managed to drop the delta in qtbase, qtmultimedia and qtwebkit.

Why we haven’t packaged it early: we did not want to package 5.12.1
because it had some known bugs. And 5.12.2 was released upstream later
than it was originally planned.

Changelog: https://wiki.qt.io/New_Features_in_Qt_5.12

The packages are being prepared in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3680/+packages, but these will be replaced with
syncs from Debian when qtbase and qtdeclarative get accepted from
Debian’s NEW queue.

This transition will require syncs of all Qt packages, and no-change
rebuilds of packages that build-depend on qtbase5-private-dev or
qtdeclarative5-private-dev.

All Qt modules are in universe.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [FFe] Qt 5.12.2 update

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

Bug description:
  Dear Release Team,

  I would like to update Qt in disco from 5.11.3 to 5.12.2.

  The reasons are the following:

  1) The 5.11 branch is EOL and no longer receiving any fixes. The 5.12
  branch is LTS and will be supported for three years.

  2) New versions of Plasma are going to require Qt 5.12, and the
  Kubuntu team would like to be able to package them in their backports
  PPA for disco.

  3) In Qt 5.12, the memory usage of the QML Engine is reduced by up to
  30 %.

  4) Finally we will be able to sync all packages from Debian. I have
  managed to drop the delta in qtbase, qtmultimedia and qtwebkit.

  Why we haven’t packaged it early: we did not want to package 5.12.1
  because it had some known bugs. And 5.12.2 was released upstream later
  than it was originally planned.

  Changelog: https://wiki.qt.io/New_Features_in_Qt_5.12

  The packages are being prepared in https://launchpad.net/~ci-train-
  ppa-service/+archive/ubuntu/3680/+packages, but these will be replaced
  with syncs from Debian when qtbase and qtdeclarative get accepted from
  Debian’s NEW queue.

  This transition will require syncs of all Qt packages, and no-change
  rebuilds of packages that build-depend on qtbase5-private-dev or
  qtdeclarative5-private-dev.

  All Qt modules are in universe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1821091/+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 1821091] Re: [FFe] Qt 5.12.2 update

[Dmitry Shachnev]

Hi Łukasz!

I have not yet rebuilt reverse dependencies, but if there is a chance of
getting this FFe approved I can add them to the PPA tomorrow.

If you are not going to approve this, then no problem for me personally,
we will land 5.12.2 (or even .3) at the beginning of next release cycle.

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

Title:
  [FFe] Qt 5.12.2 update

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

Bug description:
  Dear Release Team,

  I would like to update Qt in disco from 5.11.3 to 5.12.2.

  The reasons are the following:

  1) The 5.11 branch is EOL and no longer receiving any fixes. The 5.12
  branch is LTS and will be supported for three years.

  2) New versions of Plasma are going to require Qt 5.12, and the
  Kubuntu team would like to be able to package them in their backports
  PPA for disco.

  3) In Qt 5.12, the memory usage of the QML Engine is reduced by up to
  30 %.

  4) Finally we will be able to sync all packages from Debian. I have
  managed to drop the delta in qtbase, qtmultimedia and qtwebkit.

  Why we haven’t packaged it early: we did not want to package 5.12.1
  because it had some known bugs. And 5.12.2 was released upstream later
  than it was originally planned.

  Changelog: https://wiki.qt.io/New_Features_in_Qt_5.12

  The packages are being prepared in https://launchpad.net/~ci-train-
  ppa-service/+archive/ubuntu/3680/+packages, but these will be replaced
  with syncs from Debian when qtbase and qtdeclarative get accepted from
  Debian’s NEW queue.

  This transition will require syncs of all Qt packages, and no-change
  rebuilds of packages that build-depend on qtbase5-private-dev or
  qtdeclarative5-private-dev.

  All Qt modules are in universe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1821091/+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 1821091] Re: [FFe] Qt 5.12.2 update

[Dmitry Shachnev]

> The most ironic part is that you can not update it independently
without having Qt 5.12.

In fact you can, at least that was the case with previous Qt WebEngine
versions:

https://doc.qt.io/qt-5/qtwebengine-platform-notes.html#using-earlier-qt-
versions-to-build-qt-webengine

But anyway, any version will be insecure at some point of time. I
personally do not have time to backport security fixes to stable
releases, and we have no other volunteers.

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

Title:
  [FFe] Qt 5.12.2 update

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

Bug description:
  Dear Release Team,

  I would like to update Qt in disco from 5.11.3 to 5.12.2.

  The reasons are the following:

  1) The 5.11 branch is EOL and no longer receiving any fixes. The 5.12
  branch is LTS and will be supported for three years.

  2) New versions of Plasma are going to require Qt 5.12, and the
  Kubuntu team would like to be able to package them in their backports
  PPA for disco.

  3) In Qt 5.12, the memory usage of the QML Engine is reduced by up to
  30 %.

  4) Finally we will be able to sync all packages from Debian. I have
  managed to drop the delta in qtbase, qtmultimedia and qtwebkit.

  Why we haven’t packaged it early: we did not want to package 5.12.1
  because it had some known bugs. And 5.12.2 was released upstream later
  than it was originally planned.

  Changelog: https://wiki.qt.io/New_Features_in_Qt_5.12

  The packages are being prepared in https://launchpad.net/~ci-train-
  ppa-service/+archive/ubuntu/3680/+packages, but these will be replaced
  with syncs from Debian when qtbase and qtdeclarative get accepted from
  Debian’s NEW queue.

  This transition will require syncs of all Qt packages, and no-change
  rebuilds of packages that build-depend on qtbase5-private-dev or
  qtdeclarative5-private-dev.

  All Qt modules are in universe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1821091/+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 1821091] Re: [FFe] Qt 5.12.2 update

[Dmitry Shachnev]

Hi, I have three things to mention:

1) We now have successfully rebuilt all reverse dependencies in the PPA.

2) I have checked whether Qt WebEngine 5.12 builds fine against Qt 5.11
and the answer is no. So I was wrong, and the only way to get Qt
WebEngine security updates is updating all of Qt.

3) PyQt5 WebEngine module was split into a separate module upstream, so
we have a new source package: pyqt5webengine. There are no functional
changes, just packaging change. See
https://www.riverbankcomputing.com/news/pyqt-512.

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

Title:
  [FFe] Qt 5.12.2 update

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

Bug description:
  Dear Release Team,

  I would like to update Qt in disco from 5.11.3 to 5.12.2.

  The reasons are the following:

  1) The 5.11 branch is EOL and no longer receiving any fixes. The 5.12
  branch is LTS and will be supported for three years.

  2) New versions of Plasma are going to require Qt 5.12, and the
  Kubuntu team would like to be able to package them in their backports
  PPA for disco.

  3) In Qt 5.12, the memory usage of the QML Engine is reduced by up to
  30 %.

  4) Finally we will be able to sync all packages from Debian. I have
  managed to drop the delta in qtbase, qtmultimedia and qtwebkit.

  Why we haven’t packaged it early: we did not want to package 5.12.1
  because it had some known bugs. And 5.12.2 was released upstream later
  than it was originally planned.

  Changelog: https://wiki.qt.io/New_Features_in_Qt_5.12

  The packages are being prepared in https://launchpad.net/~ci-train-
  ppa-service/+archive/ubuntu/3680/+packages, but these will be replaced
  with syncs from Debian when qtbase and qtdeclarative get accepted from
  Debian’s NEW queue.

  This transition will require syncs of all Qt packages, and no-change
  rebuilds of packages that build-depend on qtbase5-private-dev or
  qtdeclarative5-private-dev.

  All Qt modules are in universe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1821091/+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 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

[Dmitry Shachnev]

This needs fixes in both qtbase and qttools. In addition, I will upload
a no-change rebuild of qtdeclarative to demonstrate that the fix works.

Updating the description accordingly.

** Description changed:

  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.
  
  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine, etc.).
- I am now fixing it for qtbase, the largest module, but I may fix it for
- other modules if someone requests it.
+ 
+ To properly fix this bug, we need changes in qtbase and qttools modules.
+ In addition, I will be uploading a no-change rebuild of qtdeclarative
+ module to demonstrate that the fixes work.
+ 
+ If requested, I can also upload no-change rebuilds of some other modules
+ to get their -doc packages properly regenerated.
  
  [Test Case]
+ For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.
  
+ For qtdeclarative5-doc-html:
+ 1. Install qtdeclarative5-doc-html package.
+ 2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.
+ 
  [Regression Potential]
- The proposed fix only adds a new build-dependency. There is absolutely no 
regression potential.
+ The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.
+ 
+ The proposed change in qttools can affect more packages. It can result
+ in qdoc passing more -isystem flags to clang code analyzer. I am not
+ aware of negative consequences of this, but if they happen, these
+ consequences will be limited to potential build failures or wrong
+ documentation contents.
  
  [Other Info]
  Description of the fix:
  
  qdoc is a tool that parses C++ source files and generates documentation
  from them. Recently, qdoc began using clang instead of its own C++
- parser. Clang needs the C++ standard library to work. qdoc build system
- uses a build-time macro (CLANG_RESOURCE_DIR) that hard-codes the path to
- standard library in the executable:
- https://code.qt.io/cgit/qt/qttools.git/tree/src/qdoc/qdoc.pro?h=5.11#n19.
+ parser. Clang needs the C++ standard library to work. Starting with
+ llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard library is no
+ longer on clang’s default search paths, so we need to pass it explicitly
+ as -I flag. The proposed qtbase patch (qdoc_default_incdirs.diff) does
+ that.
  
- From qttools-opensource-src 5.11.1-5 build log in Cosmic amd64, one can
- see that qdoc was compiled with
- -D'CLANG_RESOURCE_DIR="/usr/lib/llvm-6.0/lib/clang/6.0.1/include"'. So
- this directory needs to be present when qdoc is used. This directory is
- provided by libclang-common-6.0-dev package. So adding it to build-
- dependencies makes the documentation build correctly.
- 
- This is the minimal fix for Cosmic. For Ubuntu 19.04, I will try to use
- a better solution like moving the clang standard library detection from
- build time to run time, or making qttools5-dev-tools depend on the
- needed -dev packages.
+ That patch fixes documentation build for qtbase, but for other modules
+ there is another problem. The Qt headers are installed into
+ /usr/include//qt5 directory, but it is also not on Clang
+ default search path. qmake passes these directories as -isystem flags,
+ but qdoc ignores -isystem by default, unless it is built with
+ QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is building
+ with this define.
  
  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

** Also affects: qttools-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qtdeclarative-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qtbase-opensource-src (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: qtdeclarative-opensource-src (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: qttools-opensource-src (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in qttools-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src source package in Cosmic:
  New
Status in qtdeclarativ

[Touch-packages] [Bug 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

[Dmitry Shachnev]

The latest qtdeclarative build in Disco contains the properly built
documentation, so marking this bug as fixed there.

I am working on a backport to Cosmic now.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qttools-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Cosmic:
  New
Status in qtdeclarative-opensource-src source package in Cosmic:
  New
Status in qttools-opensource-src source package in Cosmic:
  New
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.

  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine,
  etc.).

  To properly fix this bug, we need changes in qtbase and qttools
  modules. In addition, I will be uploading a no-change rebuild of
  qtdeclarative module to demonstrate that the fixes work.

  If requested, I can also upload no-change rebuilds of some other
  modules to get their -doc packages properly regenerated.

  [Test Case]
  For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.

  For qtdeclarative5-doc-html:
  1. Install qtdeclarative5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.

  [Regression Potential]
  The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.

  The proposed change in qttools can affect more packages. It can result
  in qdoc passing more -isystem flags to clang code analyzer. I am not
  aware of negative consequences of this, but if they happen, these
  consequences will be limited to potential build failures or wrong
  documentation contents.

  [Other Info]
  Description of the fix:

  qdoc is a tool that parses C++ source files and generates
  documentation from them. Recently, qdoc began using clang instead of
  its own C++ parser. Clang needs the C++ standard library to work.
  Starting with llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard
  library is no longer on clang’s default search paths, so we need to
  pass it explicitly as -I flag. The proposed qtbase patch
  (qdoc_default_incdirs.diff) does that.

  That patch fixes documentation build for qtbase, but for other modules
  there is another problem. The Qt headers are installed into
  /usr/include//qt5 directory, but it is also not on Clang
  default search path. qmake passes these directories as -isystem flags,
  but qdoc ignores -isystem by default, unless it is built with
  QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is
  building with this define.

  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1799111/+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 1806186] Re: qtbase5-dev package depends on qtwayland5 but doesn't install it

[Dmitry Shachnev]

This dependency is in Qt5Gui_QWaylandEglPlatformIntegrationPlugin.cmake.
It is shipped in libqt5waylandcompositor5-dev, not in qtbase5-dev, so I
am reassigning this bug accordingly.

I have fixed it in this commit in our packaging Git:
https://salsa.debian.org/qt-kde-
team/qt/qtwayland/commit/058587ef88cf5f6c. It will be available in
Ubuntu Disco (development series) in the next upload.

** Package changed: qtbase-opensource-src (Ubuntu) => qtwayland-
opensource-src (Ubuntu)

** Changed in: qtwayland-opensource-src (Ubuntu)
   Status: New => Fix Committed

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

Title:
  qtbase5-dev package depends on qtwayland5 but doesn't install it

Status in qtwayland-opensource-src package in Ubuntu:
  Fix Committed

Bug description:
  When building obs-studio from github i encored a problem:
  ```
  CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:27 
(message):
The imported target "Qt5::Gui" references the file

   "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqwayland-
  egl.so"

but this file does not exist.  Possible reasons include:

* The file was deleted, renamed, or moved to another location.

* An install or uninstall procedure did not complete successfully.

* The installation package was faulty and contained

   "/usr/lib/x86_64-linux-
  gnu/cmake/Qt5Gui/Qt5Gui_QWaylandEglPlatformIntegrationPlugin.cmake"

but not all the files it references.
  ```
  i found that 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqwayland-egl.so" file is 
exist on "qtwayland5" package and installing it fixed the problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1806186/+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 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

[Dmitry Shachnev]

The packages are waiting in the review queue since November 27th:
https://launchpad.net/ubuntu/cosmic/+queue?queue_state=1. Now it’s up to
SRU team to review them.

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qttools-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Cosmic:
  Confirmed
Status in qtdeclarative-opensource-src source package in Cosmic:
  Confirmed
Status in qttools-opensource-src source package in Cosmic:
  Confirmed
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.

  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine,
  etc.).

  To properly fix this bug, we need changes in qtbase and qttools
  modules. In addition, I will be uploading a no-change rebuild of
  qtdeclarative module to demonstrate that the fixes work.

  If requested, I can also upload no-change rebuilds of some other
  modules to get their -doc packages properly regenerated.

  [Test Case]
  For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.

  For qtdeclarative5-doc-html:
  1. Install qtdeclarative5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.

  [Regression Potential]
  The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.

  The proposed change in qttools can affect more packages. It can result
  in qdoc passing more -isystem flags to clang code analyzer. I am not
  aware of negative consequences of this, but if they happen, these
  consequences will be limited to potential build failures or wrong
  documentation contents.

  [Other Info]
  Description of the fix:

  qdoc is a tool that parses C++ source files and generates
  documentation from them. Recently, qdoc began using clang instead of
  its own C++ parser. Clang needs the C++ standard library to work.
  Starting with llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard
  library is no longer on clang’s default search paths, so we need to
  pass it explicitly as -I flag. The proposed qtbase patch
  (qdoc_default_incdirs.diff) does that.

  That patch fixes documentation build for qtbase, but for other modules
  there is another problem. The Qt headers are installed into
  /usr/include//qt5 directory, but it is also not on Clang
  default search path. qmake passes these directories as -isystem flags,
  but qdoc ignores -isystem by default, unless it is built with
  QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is
  building with this define.

  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1799111/+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 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard

[Dmitry Shachnev]

The Debian bug is marked as fixed in Qt 5.11. Can you please check if
this bug is present in Disco (which has 5.12)?

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

Title:
  Qt5 incorrectly interpret keypresses from remote VNC keyboard

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qttools-opensource-src package in Ubuntu:
  New
Status in tightvnc package in Ubuntu:
  New
Status in qtbase-opensource-src package in Debian:
  Unknown

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.04 LTS installed with VNC server
  2. Connect to Ubuntu 18.04 LTS from other machine with VNC client
  3. Launch any Qt5 based application such as `assistant`, `kate` or `retext`
  4. Press keyboard combination on VNC client

  Expected results:
  all keypresses are recognized successfully

  Actual results:
  *  produces `1`
  *  produces `5`
  * <`> produces `p`
  *  and  are not working
  * all letters are messed

  
  Note:
  only Qt applications are affected, the GTK-based work as expected (including 
Chromium from which I write this bug-report)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qt5-assistant 5.9.5-0ubuntu1
  Uname: Linux 4.4.78-perf+ aarch64
  NonfreeKernelModules: wlan exfat
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: armhf
  CurrentDesktop: MATE
  Date: Tue Jun  4 00:46:55 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: qttools-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+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 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard

[Dmitry Shachnev]

** No longer affects: qttools-opensource-src (Ubuntu)

** No longer affects: tightvnc (Ubuntu)

** Also affects: qtbase-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  Qt5 incorrectly interpret keypresses from remote VNC keyboard

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New
Status in qtbase-opensource-src package in Debian:
  Unknown

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.04 LTS installed with VNC server
  2. Connect to Ubuntu 18.04 LTS from other machine with VNC client
  3. Launch any Qt5 based application such as `assistant`, `kate` or `retext`
  4. Press keyboard combination on VNC client

  Expected results:
  all keypresses are recognized successfully

  Actual results:
  *  produces `1`
  *  produces `5`
  * <`> produces `p`
  *  and  are not working
  * all letters are messed

  
  Note:
  only Qt applications are affected, the GTK-based work as expected (including 
Chromium from which I write this bug-report)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qt5-assistant 5.9.5-0ubuntu1
  Uname: Linux 4.4.78-perf+ aarch64
  NonfreeKernelModules: wlan exfat
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: armhf
  CurrentDesktop: MATE
  Date: Tue Jun  4 00:46:55 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: qttools-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+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 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard

[Dmitry Shachnev]

Can you please try packages from https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3731/+packages and see if they fix the issue?

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

Title:
  Qt5 incorrectly interpret keypresses from remote VNC keyboard

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.04 LTS installed with VNC server
  2. Connect to Ubuntu 18.04 LTS from other machine with VNC client
  3. Launch any Qt5 based application such as `assistant`, `kate` or `retext`
  4. Press keyboard combination on VNC client

  Expected results:
  all keypresses are recognized successfully

  Actual results:
  *  produces `1`
  *  produces `5`
  * <`> produces `p`
  *  and  are not working
  * all letters are messed

  
  Note:
  only Qt applications are affected, the GTK-based work as expected (including 
Chromium from which I write this bug-report)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qt5-assistant 5.9.5-0ubuntu1
  Uname: Linux 4.4.78-perf+ aarch64
  NonfreeKernelModules: wlan exfat
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: armhf
  CurrentDesktop: MATE
  Date: Tue Jun  4 00:46:55 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: qttools-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+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 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard

[Dmitry Shachnev]

It was quite difficult to backport this even to 18.04, as I had to
change the code in several places to make it compile.

That was backporting only two releases back (5.11 → 5.9). 16.04 has 5.5
so that sounds impossible, however patches are welcome.

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

Title:
  Qt5 incorrectly interpret keypresses from remote VNC keyboard

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.04 LTS installed with VNC server
  2. Connect to Ubuntu 18.04 LTS from other machine with VNC client
  3. Launch any Qt5 based application such as `assistant`, `kate` or `retext`
  4. Press keyboard combination on VNC client

  Expected results:
  all keypresses are recognized successfully

  Actual results:
  *  produces `1`
  *  produces `5`
  * <`> produces `p`
  *  and  are not working
  * all letters are messed

  
  Note:
  only Qt applications are affected, the GTK-based work as expected (including 
Chromium from which I write this bug-report)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qt5-assistant 5.9.5-0ubuntu1
  Uname: Linux 4.4.78-perf+ aarch64
  NonfreeKernelModules: wlan exfat
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: armhf
  CurrentDesktop: MATE
  Date: Tue Jun  4 00:46:55 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: qttools-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+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 1811678] Re: Inconsistent OpenGL support across architectures

[Dmitry Shachnev]

Sorry for the delay, for some reason I have not received a mail about
this bug.

Starting with Ubuntu 19.04 release, there is no difference between
Debian and Ubuntu: both use OpenGL ES on armel/armhf, and desktop OpenGL
on the other architectures. Initially I wanted to add arm64 to that list
too, but after the discussion in https://lists.debian.org/debian-
devel/2018/11/msg00457.html the plan was changed.

The reason for using OpenGL ES on armel/armhf is that the majority of
devices with that architecture are mobile devices that have video chips
supporting only OpenGL ES natively.

It looks like v4l-utils currently builds fine on all supported Ubuntu
releases, but if you have problems with supporting OpenGL ES versions,
please let me know.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  Inconsistent OpenGL support across architectures

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  today I noticed build failures of v4l-utils on arm64 hosts:
  
https://launchpadlibrarian.net/406083796/buildlog_ubuntu-bionic-arm64.v4l-utils_1.17.1-201901131615~ubuntu18.04.1_BUILDING.txt.gz

  This is due to the OpenGLES2 feature is enabled on arm64 (but this
  feature is not enabled for amd64):

  > /usr/include/x86_64-linux-gnu/qt5/QtGui# grep -i opengl qtgui-config.h
  > #define QT_FEATURE_opengles2 -1
  > #define QT_FEATURE_opengl 1
  > #define QT_FEATURE_opengles3 -1
  > #define QT_FEATURE_opengles31 -1

  vs:

  > /usr/include/aarch64-linux-gnu/qt5/QtGui$ grep -i opengl qtgui-config.h
  > #define QT_FEATURE_opengles2 1
  > #define QT_OPENGL_ES true
  > #define QT_OPENGL_ES_2 true
  > #define QT_FEATURE_opengl 1
  > #define QT_FEATURE_opengles3 1
  > #define QT_OPENGL_ES_3 true
  > #define QT_FEATURE_opengles31 1
  > #define QT_OPENGL_ES_3_1 true 

  Is the inconsistent feature setting intentional? The Debian Qt
  packages seem to select Desktop OpenGL across architectures.

  Thanks,
  Gregor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1811678/+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 1795358] Re: FTBFS with MySQL 8.0

[Dmitry Shachnev]

Ubuntu 19.04 release has Qt 5.12, so marking this as fixed.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  FTBFS with MySQL 8.0

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  MySQL 8.0 removes the my_bool symbol, and it should simply be replaced
  with int or bool (this is also backwards-compatible with older
  versions of MySQL)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1795358/+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 1810346] Re: VLC interface not displayed correctly

[Dmitry Shachnev]

Can one of you please check if the issue still exists with Ubuntu 19.04
(which has Qt 5.12)?

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

Title:
  VLC interface not displayed correctly

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

Bug description:
  I use vlc on a Dell E-5530 laptop seated on its docking station.
  The laptop display cover is closed, the output is sent on an external LG TV 
with 1920x1080.
  This system has been working flawlessly for many years, resp. under late 
14.04 and 16.04.
  After recently upgrading to 18.04, I noticed VLC wouldn't display correctly - 
see attachment.
  This only occurs on the external display ; if I open the cover and use the 
internal display, there is no problem - except I cannot work on the internal 
display.
  regards,
  J.-Luc

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vlc-bin 3.0.4-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 23:38:36 2019
  ExecutablePath: /usr/bin/vlc
  InstallationDate: Installed on 2018-12-19 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+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 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard

[Dmitry Shachnev]

** Description changed:

- Steps to reproduce:
+ [Impact]
+ Qt applications incorrectly interpret keyboard input when running over some 
VNC clients such as TightVNC.
+ 
+ [Test Case]
  1. Have Ubuntu 18.04 LTS installed with VNC server
  2. Connect to Ubuntu 18.04 LTS from other machine with VNC client
  3. Launch any Qt5 based application such as `assistant`, `kate` or `retext`
  4. Press keyboard combination on VNC client
  
  Expected results:
  all keypresses are recognized successfully
  
  Actual results:
  *  produces `1`
  *  produces `5`
  * <`> produces `p`
  *  and  are not working
  * all letters are messed
  
+ [Proposed Fix]
+ The proposed fix is a backport of two upstream commits: the second being the 
actual fix, the first one is some refactoring of the code to make it easier to 
write the second. The commits are:
  
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f8b164e1c37ca901
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=3edcd9420e3ad661
+ 
+ [Regression Potential]
+ Most of the new code is triggered only when the keymap is missing rules, 
models, or layout (i.e. rmlvo_is_incomplete == true). This minimizes the risk 
of regressions when working with simple X11 server. In any case, the potential 
regressions will be related to input handling.
+ 
+ [Other Info]
  Note:
  only Qt applications are affected, the GTK-based work as expected (including 
Chromium from which I write this bug-report)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qt5-assistant 5.9.5-0ubuntu1
  Uname: Linux 4.4.78-perf+ aarch64
  NonfreeKernelModules: wlan exfat
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: armhf
  CurrentDesktop: MATE
  Date: Tue Jun  4 00:46:55 2019
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: qttools-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Qt5 incorrectly interpret keypresses from remote VNC keyboard

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  Qt applications incorrectly interpret keyboard input when running over some 
VNC clients such as TightVNC.

  [Test Case]
  1. Have Ubuntu 18.04 LTS installed with VNC server
  2. Connect to Ubuntu 18.04 LTS from other machine with VNC client
  3. Launch any Qt5 based application such as `assistant`, `kate` or `retext`
  4. Press keyboard combination on VNC client

  Expected results:
  all keypresses are recognized successfully

  Actual results:
  *  produces `1`
  *  produces `5`
  * <`> produces `p`
  *  and  are not working
  * all letters are messed

  [Proposed Fix]
  The proposed fix is a backport of two upstream commits: the second being the 
actual fix, the first one is some refactoring of the code to make it easier to 
write the second. The commits are:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f8b164e1c37ca901
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=3edcd9420e3ad661

  [Regression Potential]
  Most of the new code is triggered only when the keymap is missing rules, 
models, or layout (i.e. rmlvo_is_incomplete == true). This minimizes the risk 
of regressions when working with simple X11 server. In any case, the potential 
regressions will be related to input handling.

  [Other Info]
  Note:
  only Qt applications are affected, the GTK-based work as expected (including 
Chromium from which I write this bug-report)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qt5-assistant 5.9.5-0ubuntu1
  Uname: Linux 4.4.78-perf+ aarch64
  NonfreeKernelModules: wlan exfat
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: armhf
  CurrentDesktop: MATE
  Date: Tue Jun  4 00:46:55 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: qttools-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+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 1833536] Re: QuiteRSS crashes intermittently

[Dmitry Shachnev]

** Description changed:

- After opening QuiteRSS it will run until crash happens.  This happens
- intermittently within the hour usually.
+ [Impact]
+ This bug affects QuiteRSS and other Qt applications, like plasma-discover 
(see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 
1814375). All they crash with similar stack traces.
+ 
+ [Test Case]
+ 1. Open QuiteRSS.
+ 2. Leave it running for several hours.
+ 3. It should not crash.
+ 
+ [Proposed Fix]
+ The proposed fix is a backport of the following commit from upstream 5.12 
branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db
+ 
+ [Regression Potential]
+ This patch adds an additional check before re-sending the request. 
Regressions chance is minimal, but the potential regressions may be that the 
request is not re-sent where it was re-sent with the previous code.
+ 
+ [Original Description]
+ After opening QuiteRSS it will run until crash happens.  This happens 
intermittently within the hour usually.
  
  (gdb) bt
  #0  QHttpNetworkConnectionChannel::sendRequest (this=)
- at access/qhttpnetworkconnectionchannel.cpp:238
+ at access/qhttpnetworkconnectionchannel.cpp:238
  #1  0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest (
- this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015
- #2  0x72736122 in QObject::event (this=0x7fff48da89b0, 
- e=) at kernel/qobject.cpp:1247
+ this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015
+ #2  0x72736122 in QObject::event (this=0x7fff48da89b0,
+ e=) at kernel/qobject.cpp:1247
  #3  0x76f2482c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
- () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
+ () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #4  0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) ()
-from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
+    from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #5  0x727069a8 in QCoreApplication::notifyInternal2 (
- receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0)
- at kernel/qcoreapplication.cpp:1024
- #6  0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0, 
- receiver=)
- at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
- #7  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, 
- event_type=event_type@entry=0, data=0x7fff60008e90)
- at kernel/qcoreapplication.cpp:1699
+ receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0)
+ at kernel/qcoreapplication.cpp:1024
+ #6  0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0,
+ receiver=)
+ at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
+ #7  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
+ event_type=event_type@entry=0, data=0x7fff60008e90)
+ at kernel/qcoreapplication.cpp:1699
  #8  0x727096a8 in QCoreApplication::sendPostedEvents (
- receiver=receiver@entry=0x0, event_type=event_type@entry=0)
- at kernel/qcoreapplication.cpp:1553
+ receiver=receiver@entry=0x0, event_type=event_type@entry=0)
+ at kernel/qcoreapplication.cpp:1553
  #9  0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10)
- ---Type  to continue, or q  to quit---
- at kernel/qeventdispatcher_glib.cpp:276
+ at kernel/qeventdispatcher_glib.cpp:276
  #10 0x7fffece96317 in g_main_context_dispatch ()
-from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
+    from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7fffece96550 in ?? () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x7fffece965dc in g_main_context_iteration ()
-from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
+    from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #13 0x7275f8ef in QEventDispatcherGlib::processEvents (
- this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
- #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60, 
- flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
+ this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
+ #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60,
+ flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
  #15 0x7252322a in QThread::exec (this=)
- at thread/qthread.cpp:515
+ at thread/qthread.cpp:515
  #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20)
- at thread/qthread_unix.cpp:368
+ at thread/qthread_unix.cpp:368
  #17 0x722646db in start_thread (arg=0x7fff4700)
- at pthread_create.c:463
+ at pthread_create.c:463
  #18 0x719ec88f in clone ()
- at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
+ at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

** Also affects: qtbase-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Statu

[Touch-packages] [Bug 1833536] Re: QuiteRSS crashes intermittently

[Dmitry Shachnev]

** Also affects: qtbase-opensource-src (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Changed in: qtbase-opensource-src (Ubuntu Disco)
   Status: New => In Progress

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

Title:
  QuiteRSS crashes intermittently

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  In Progress
Status in qtbase-opensource-src source package in Disco:
  In Progress

Bug description:
  [Impact]
  This bug affects QuiteRSS and other Qt applications, like plasma-discover 
(see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 
1814375). All they crash with similar stack traces.

  [Test Case]
  1. Open QuiteRSS.
  2. Leave it running for several hours.
  3. It should not crash.

  [Proposed Fix]
  The proposed fix is a backport of the following commit from upstream 5.12 
branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db

  [Regression Potential]
  This patch adds an additional check before re-sending the request. 
Regressions chance is minimal, but the potential regressions may be that the 
request is not re-sent where it was re-sent with the previous code.

  [Original Description]
  After opening QuiteRSS it will run until crash happens.  This happens 
intermittently within the hour usually.

  (gdb) bt
  #0  QHttpNetworkConnectionChannel::sendRequest (this=)
  at access/qhttpnetworkconnectionchannel.cpp:238
  #1  0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest (
  this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015
  #2  0x72736122 in QObject::event (this=0x7fff48da89b0,
  e=) at kernel/qobject.cpp:1247
  #3  0x76f2482c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
  () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #4  0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) ()
     from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #5  0x727069a8 in QCoreApplication::notifyInternal2 (
  receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0)
  at kernel/qcoreapplication.cpp:1024
  #6  0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0,
  receiver=)
  at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
  #7  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
  event_type=event_type@entry=0, data=0x7fff60008e90)
  at kernel/qcoreapplication.cpp:1699
  #8  0x727096a8 in QCoreApplication::sendPostedEvents (
  receiver=receiver@entry=0x0, event_type=event_type@entry=0)
  at kernel/qcoreapplication.cpp:1553
  #9  0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10)
  at kernel/qeventdispatcher_glib.cpp:276
  #10 0x7fffece96317 in g_main_context_dispatch ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7fffece96550 in ?? () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x7fffece965dc in g_main_context_iteration ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #13 0x7275f8ef in QEventDispatcherGlib::processEvents (
  this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
  #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60,
  flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
  #15 0x7252322a in QThread::exec (this=)
  at thread/qthread.cpp:515
  #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20)
  at thread/qthread_unix.cpp:368
  #17 0x722646db in start_thread (arg=0x7fff4700)
  at pthread_create.c:463
  #18 0x719ec88f in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1846821] Re: Qt print dialog has wrong default page size

[Dmitry Shachnev]

The fix is included in Qt 5.11, so I am marking it as affecting only
Bionic.

** Also affects: qtbase-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  Qt print dialog has wrong default page size

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  In Qt5 applications, print dialog (Printer Properties) always defaults
  to A4 paper size, even when Letter is set as a default in all system
  and KDE preferences. After changing manually, Letter-size pages print
  correctly, but the setting does not stick. The issue also affects
  other print settings, e.g. margins, though the aforementioned patch
  does not deal with these. A similar issue regarding the duplex setting
  was reported as Launchpad bug 1776173, and subsequently fixed, but
  other print settings continue to cause problems.

  Behavior expected: Print dialog would default to Letter paper size,
  which is set in all available system and KDE preferences, and that was
  selected for previous prints.

  Behavior observed: Print dialog always defaults to A4, and page size
  needs to be changed manually before every print.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1848784] [NEW] Crash in Qt 5.12.2

[Dmitry Shachnev]

Public bug reported:

Originally reported by Robert Loehning in
:

Every application based on Qt will crash when opening a crafted plain
text file. Could you please add the patch below to your builds to fix
this?

https://codereview.qt-project.org/c/qt/qtbase/+/271889

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Crash in Qt 5.12.2

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

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+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 1846821] Re: Qt print dialog has wrong default page size

[Dmitry Shachnev]

Can you please test the packages in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3833?

The patch did not apply to 5.9 branch so I had to make some changes to
it.

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

Title:
  Qt print dialog has wrong default page size

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  In Qt5 applications, print dialog (Printer Properties) always defaults
  to A4 paper size, even when Letter is set as a default in all system
  and KDE preferences. After changing manually, Letter-size pages print
  correctly, but the setting does not stick. The issue also affects
  other print settings, e.g. margins, though the aforementioned patch
  does not deal with these. A similar issue regarding the duplex setting
  was reported as Launchpad bug 1776173, and subsequently fixed, but
  other print settings continue to cause problems.

  Behavior expected: Print dialog would default to Letter paper size,
  which is set in all available system and KDE preferences, and that was
  selected for previous prints.

  Behavior observed: Print dialog always defaults to A4, and page size
  needs to be changed manually before every print.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1848784] Re: Crash in Qt 5.12.2

[Dmitry Shachnev]

** Information type changed from Public to Public Security

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

Title:
  Crash in Qt 5.12.2

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

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+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 1846821] Re: Qt print dialog has wrong default page size

[Dmitry Shachnev]

Thanks for the quick feedback!

I have just uploaded this fix to Ubuntu, it is waiting in the review
queue. Per the procedure, when it is accepted you will be asked to test
the fix again, this time installing the packages from bionic-proposed
repository.

Also updated the bug description to contain the needed fields for stable
release procedure.

** Description changed:

  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677
  
- In Qt5 applications, print dialog (Printer Properties) always defaults
- to A4 paper size, even when Letter is set as a default in all system and
- KDE preferences. After changing manually, Letter-size pages print
- correctly, but the setting does not stick. The issue also affects other
- print settings, e.g. margins, though the aforementioned patch does not
- deal with these. A similar issue regarding the duplex setting was
- reported as Launchpad bug 1776173, and subsequently fixed, but other
- print settings continue to cause problems.
+ [Impact]
+ In Qt5 applications, print dialog (Printer Properties) always defaults to A4 
paper size, even when Letter is set as a default in all system and KDE 
preferences. After changing manually, Letter-size pages print correctly, but 
the setting does not stick.
  
- Behavior expected: Print dialog would default to Letter paper size,
- which is set in all available system and KDE preferences, and that was
- selected for previous prints.
+ This impacts users of Qt applications who print things and live in
+ countries where ISO 216 is not default, most notably the United States.
  
- Behavior observed: Print dialog always defaults to A4, and page size
- needs to be changed manually before every print.
+ [Test Case]
+ 1) Use system settings (KDE preferences, gnome-control-center or 
system-config-printer) to set the printer size to Letter.
+ 2) Open any Qt application (e.g. KWrite or Falkon).
+ 3) Open a print dialog.
+ 4) Behavior expected: Print dialog would default to Letter paper size and not 
A4.
+ 
+ [Regression Potential]
+ Two possibilities for regressions that I can imagine are:
+ - crashes because something is not defined;
+ - wrong default paper size (A4 wanted but CUPS returns something else).
+ 
+ [Additional Information]
+ The issue also affects other print settings, e.g. margins, though the 
aforementioned patch does not deal with these. A similar issue regarding the 
duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, 
but other print settings continue to cause problems.
  
  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

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

Title:
  Qt print dialog has wrong default page size

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  [Impact]
  In Qt5 applications, print dialog (Printer Properties) always defaults to A4 
paper size, even when Letter is set as a default in all system and KDE 
preferences. After changing manually, Letter-size pages print correctly, but 
the setting does not stick.

  This impacts users of Qt applications who print things and live in
  countries where ISO 216 is not default, most notably the United
  States.

  [Test Case]
  1) Use system settings (KDE preferences, gnome-control-center or 
system-config-printer) to set the printer size to Letter.
  2) Open any Qt application (e.g. KWrite or Falkon).
  3) Open a print dialog.
  4) Behavior expected: Print dialog would default to Letter paper size and not 
A4.

  [Regression Potential]
  Two possibilities for regressions that I can imagine are:
  - crashes because something is not defined;
  - wrong default paper size (A4 wanted but CUPS returns something else).

  [Additional Information]
  The issue also affects other print settings, e.g. margins, though the 
aforementioned patch does not deal with these. A similar issue regarding the 
duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, 
but other print settings continue to cause problems.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1848784] Re: Crash in Qt 5.12.2

[Dmitry Shachnev]

Focal now has Qt 5.12.5 where this is fixed.

** Also affects: qtbase-opensource-src (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: qtbase-opensource-src (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: qtbase-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu Bionic)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

** Changed in: qtbase-opensource-src (Ubuntu Disco)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

** Changed in: qtbase-opensource-src (Ubuntu Eoan)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  Crash in Qt 5.12.2

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New
Status in qtbase-opensource-src source package in Disco:
  New
Status in qtbase-opensource-src source package in Eoan:
  New

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+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 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard

[Dmitry Shachnev]

> Packages from bionic-proposed fix the issue.

Thanks, marking as verified then.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  Qt5 incorrectly interpret keypresses from remote VNC keyboard

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  Qt applications incorrectly interpret keyboard input when running over some 
VNC clients such as TightVNC.

  [Test Case]
  1. Have Ubuntu 18.04 LTS installed with VNC server
  2. Connect to Ubuntu 18.04 LTS from other machine with VNC client
  3. Launch any Qt5 based application such as `assistant`, `kate` or `retext`
  4. Press keyboard combination on VNC client

  Expected results:
  all keypresses are recognized successfully

  Actual results:
  *  produces `1`
  *  produces `5`
  * <`> produces `p`
  *  and  are not working
  * all letters are messed

  [Proposed Fix]
  The proposed fix is a backport of two upstream commits: the second being the 
actual fix, the first one is some refactoring of the code to make it easier to 
write the second. The commits are:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f8b164e1c37ca901
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=3edcd9420e3ad661

  [Regression Potential]
  Most of the new code is triggered only when the keymap is missing rules, 
models, or layout (i.e. rmlvo_is_incomplete == true). This minimizes the risk 
of regressions when working with simple X11 server. In any case, the potential 
regressions will be related to input handling.

  [Other Info]
  Note:
  only Qt applications are affected, the GTK-based work as expected (including 
Chromium from which I write this bug-report)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qt5-assistant 5.9.5-0ubuntu1
  Uname: Linux 4.4.78-perf+ aarch64
  NonfreeKernelModules: wlan exfat
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: armhf
  CurrentDesktop: MATE
  Date: Tue Jun  4 00:46:55 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: qttools-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+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 1833536] Re: QuiteRSS crashes intermittently

[Dmitry Shachnev]

Hi Łukasz,

For disco, all autopkgtests are passing now.

For bionic, the only failing package is kdeconnect. These failures are
caused by OpenSSL update to 1.1.1, not by Qt update. Also, it is a bug
in tests, not in real code. It was fixed upstream yesterday in
https://invent.kde.org/kde/kdeconnect-kde/merge_requests/42. As it is a
bug in tests, I would ignore it.

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

Title:
  QuiteRSS crashes intermittently

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  This bug affects QuiteRSS and other Qt applications, like plasma-discover 
(see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 
1814375). All they crash with similar stack traces.

  [Test Case]
  1. Open QuiteRSS.
  2. Leave it running for several hours.
  3. It should not crash.

  [Proposed Fix]
  The proposed fix is a backport of the following commit from upstream 5.12 
branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db

  [Regression Potential]
  This patch adds an additional check before re-sending the request. 
Regressions chance is minimal, but the potential regressions may be that the 
request is not re-sent where it was re-sent with the previous code.

  [Original Description]
  After opening QuiteRSS it will run until crash happens.  This happens 
intermittently within the hour usually.

  (gdb) bt
  #0  QHttpNetworkConnectionChannel::sendRequest (this=)
  at access/qhttpnetworkconnectionchannel.cpp:238
  #1  0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest (
  this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015
  #2  0x72736122 in QObject::event (this=0x7fff48da89b0,
  e=) at kernel/qobject.cpp:1247
  #3  0x76f2482c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
  () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #4  0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) ()
     from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #5  0x727069a8 in QCoreApplication::notifyInternal2 (
  receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0)
  at kernel/qcoreapplication.cpp:1024
  #6  0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0,
  receiver=)
  at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
  #7  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
  event_type=event_type@entry=0, data=0x7fff60008e90)
  at kernel/qcoreapplication.cpp:1699
  #8  0x727096a8 in QCoreApplication::sendPostedEvents (
  receiver=receiver@entry=0x0, event_type=event_type@entry=0)
  at kernel/qcoreapplication.cpp:1553
  #9  0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10)
  at kernel/qeventdispatcher_glib.cpp:276
  #10 0x7fffece96317 in g_main_context_dispatch ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7fffece96550 in ?? () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x7fffece965dc in g_main_context_iteration ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #13 0x7275f8ef in QEventDispatcherGlib::processEvents (
  this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
  #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60,
  flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
  #15 0x7252322a in QThread::exec (this=)
  at thread/qthread.cpp:515
  #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20)
  at thread/qthread_unix.cpp:368
  #17 0x722646db in start_thread (arg=0x7fff4700)
  at pthread_create.c:463
  #18 0x719ec88f in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1833536] Re: QuiteRSS crashes intermittently

[Dmitry Shachnev]

Dear William and Brian,

Please test the updated Qt packages in -proposed and let us know your
results and the version you tested with. Without this the update will
not be released.

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

Title:
  QuiteRSS crashes intermittently

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  This bug affects QuiteRSS and other Qt applications, like plasma-discover 
(see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 
1814375). All they crash with similar stack traces.

  [Test Case]
  1. Open QuiteRSS.
  2. Leave it running for several hours.
  3. It should not crash.

  [Proposed Fix]
  The proposed fix is a backport of the following commit from upstream 5.12 
branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db

  [Regression Potential]
  This patch adds an additional check before re-sending the request. 
Regressions chance is minimal, but the potential regressions may be that the 
request is not re-sent where it was re-sent with the previous code.

  [Original Description]
  After opening QuiteRSS it will run until crash happens.  This happens 
intermittently within the hour usually.

  (gdb) bt
  #0  QHttpNetworkConnectionChannel::sendRequest (this=)
  at access/qhttpnetworkconnectionchannel.cpp:238
  #1  0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest (
  this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015
  #2  0x72736122 in QObject::event (this=0x7fff48da89b0,
  e=) at kernel/qobject.cpp:1247
  #3  0x76f2482c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
  () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #4  0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) ()
     from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #5  0x727069a8 in QCoreApplication::notifyInternal2 (
  receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0)
  at kernel/qcoreapplication.cpp:1024
  #6  0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0,
  receiver=)
  at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
  #7  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
  event_type=event_type@entry=0, data=0x7fff60008e90)
  at kernel/qcoreapplication.cpp:1699
  #8  0x727096a8 in QCoreApplication::sendPostedEvents (
  receiver=receiver@entry=0x0, event_type=event_type@entry=0)
  at kernel/qcoreapplication.cpp:1553
  #9  0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10)
  at kernel/qeventdispatcher_glib.cpp:276
  #10 0x7fffece96317 in g_main_context_dispatch ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7fffece96550 in ?? () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x7fffece965dc in g_main_context_iteration ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #13 0x7275f8ef in QEventDispatcherGlib::processEvents (
  this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
  #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60,
  flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
  #15 0x7252322a in QThread::exec (this=)
  at thread/qthread.cpp:515
  #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20)
  at thread/qthread_unix.cpp:368
  #17 0x722646db in start_thread (arg=0x7fff4700)
  at pthread_create.c:463
  #18 0x719ec88f in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

[Dmitry Shachnev]

Hi Dima!

This looks like https://bugreports.qt.io/browse/QTBUG-58508 to me.
According to that bug, it is fixed in Qt 5.11, however the change is too
large to backport to 5.9.

Exporting QML_DISABLE_DISK_CACHE=1 should help as a workaround — can you
try that?

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

Title:
  twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in twinkle package in Ubuntu:
  New

Bug description:
  The console output:

  $ twinkle 
  QApplication: invalid style override passed, ignoring it.
  Language name: "en"
  mprotect failed in ExecutableAllocator::makeExecutable: Permission denied
  *** stack smashing detected ***:  terminated
  Aborted (core dumped)
  $

  I've attached a strace output file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: twinkle 1:1.10.1+dfsg-3
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Apr 16 15:29:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-11 (309 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: twinkle
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1824986/+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 1658836] Re: /usr/bin/twinkle:11:QBasicAtomicOps:QBasicAtomicInteger:QtSharedPointer::ExternalRefCountData::getAndRef:QWeakPointer:QPointer

[Dmitry Shachnev]

https://codereview.qt-project.org/c/qt/qtbase/+/188320 says that the fix
is included in Qt 5.9.0 and later versions (see the “Included in”
button).

As the latest Ubuntu LTS release has Qt 5.9.5, I think we can close
this.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  
/usr/bin/twinkle:11:QBasicAtomicOps:QBasicAtomicInteger:QtSharedPointer::ExternalRefCountData::getAndRef:QWeakPointer:QPointer

Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in twinkle package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
twinkle.  This problem was most recently seen with package version 
1:1.9.0+dfsg-3, the problem page at 
https://errors.ubuntu.com/problem/a45473614cc4679d018ae4d6e0290d08524b768e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1658836/+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 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

[Dmitry Shachnev]

Thanks for confirming, adjusting the bug status accordingly.

** No longer affects: twinkle (Ubuntu)

** Also affects: qtdeclarative-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Fix Released

** Changed in: qtdeclarative-opensource-src (Ubuntu Bionic)
   Status: New => Won't Fix

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

Title:
  twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src source package in Bionic:
  Won't Fix

Bug description:
  The console output:

  $ twinkle 
  QApplication: invalid style override passed, ignoring it.
  Language name: "en"
  mprotect failed in ExecutableAllocator::makeExecutable: Permission denied
  *** stack smashing detected ***:  terminated
  Aborted (core dumped)
  $

  I've attached a strace output file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: twinkle 1:1.10.1+dfsg-3
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Apr 16 15:29:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-11 (309 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: twinkle
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1824986/+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 1838891] Re: qt5 applications crash when opening file chooser in gtk desktops

[Dmitry Shachnev]

Can you please specify some more details about this issue:

1) Which Ubuntu release are you using? 18.04 (Bionic), 19.04 (Disco), 19.10 
(Eoan) or some other?
2) What is the version of Qt package? I.e. the output of “apt policy 
qt5-gtk-platformtheme”.
3) What desktop environment does this happen on? Is this X11 or Wayland? If 
Wayland, is Qt using XWayland or running natively (does this happen when you 
run app with “-platform wayland”)?
4) What applications does this happen with? If this happens with many 
applications please name a few, so that I can look for crash logs in our error 
tracker.

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

Title:
  qt5 applications crash when opening file chooser in gtk desktops

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

Bug description:
  Issue is apparently related to qt5-gtk-platformtheme. When you're in a
  non-Qt desktop environment and you open a file selection dialog from a
  Qt app it crashes.

  See also:
  https://bugzilla.redhat.com/show_bug.cgi?id=1392605
  https://bugs.archlinux.org/task/57984
  https://github.com/TheAssassin/AppImageLauncher/issues/218

  In my opinion this is a very serious issue and if newer Qt releases
  have fixed this it should be backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1838891/+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 1832019] Re: Error when going to 'Tools -> Preferences -> Keyboard shortcuts' in Spyder3 in Bionic

[Dmitry Shachnev]

I cannot reproduce this issue with a fresh Ubuntu 18.04.3 VM.

Please make sure you are using all packages from Ubuntu repository and
not from PyPI.

In any case, it would be a bug in spyder, not in qtbase or pyqt5.

** Attachment added: "VirtualBox_Ubuntu 18.04.3 LTS_21_08_2019_21_00_23.png"
   
https://bugs.launchpad.net/ubuntu/+source/pyqt5/+bug/1832019/+attachment/5283795/+files/VirtualBox_Ubuntu%2018.04.3%20LTS_21_08_2019_21_00_23.png

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

** Changed in: pyqt5 (Ubuntu)
   Status: New => Invalid

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

Title:
  Error when going to 'Tools -> Preferences -> Keyboard shortcuts' in
  Spyder3 in Bionic

Status in pyqt5 package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in spyder package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04 LTS
  Steps:

  1. Install spyder3 (sudo apt install spyder3)
  2. Run spyder3
  3. Go to Tools -> Preferences -> Keyboard shortcuts
  4. Error

  Keyboard shortcuts are not accessible.

  Here is the error:

    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/hel

[Touch-packages] [Bug 1838891] Re: qt5 applications crash when opening file chooser in gtk desktops

[Dmitry Shachnev]

I just managed to reproduce the crash locally. Just before the crash,
the following lines are printed to stderr:

(AppImageLauncherSettings:27871): Gtk-WARNING **: 21:45:01.935: Could not load 
a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: 
assertion failed (error == NULL): Failed to load 
/usr/share/icons/Adwaita/16x16/status/image-missing.png: Fatal error reading 
PNG image file: bad parameters to zlib (gdk-pixbuf-error-quark, 0)

I think most important part here is “bad parameters to zlib”.
AppImageLauncher uses its own static zlib
(lib/AppImageUpdate/lib/zsync2/lib/zlib/libzsync2_libz.a) which is
incompatible with public zlib (/lib/x86_64-linux-gnu/libz.so.1) that GTK
was compiled against.

Recompiling AppImageLauncher with system zlib should help, but I haven’t
found a way to do that. I suggest you to ask AppImageLauncher developer
about that.

Attaching a stacktrace for future reference.

** Attachment added: "stacktrace.txt"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1838891/+attachment/5283815/+files/stacktrace.txt

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  qt5 applications crash when opening file chooser in gtk desktops

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

Bug description:
  Issue is apparently related to qt5-gtk-platformtheme. When you're in a
  non-Qt desktop environment and you open a file selection dialog from a
  Qt app it crashes.

  See also:
  https://bugzilla.redhat.com/show_bug.cgi?id=1392605
  https://bugs.archlinux.org/task/57984
  https://github.com/TheAssassin/AppImageLauncher/issues/218

  In my opinion this is a very serious issue and if newer Qt releases
  have fixed this it should be backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1838891/+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 1832019] Re: Error when going to 'Tools -> Preferences -> Keyboard shortcuts' in Spyder3 in Bionic

[Dmitry Shachnev]

Thanks for the additional information. Still it is a bug in Spyder, not
in Qt:

1) Cleanlooks and Plastique styles are inheriting from QProxyStyle.
2) So in Spyder’s HTMLDelegate.paint method, options.widget.style() returns a 
QProxyStyle.
3) In QProxyStyle.subElementRect method, the third argument is not optional, so 
should be specified: https://doc.qt.io/qt-5/qproxystyle.html#subElementRect

In C++, if the two-argument call is used, the compiler would ignore
QProxyStyle::subElementRect and fall back to
QCommonStyle::subElementRect. However, in Python there is no concept of
overloading methods so this is not possible.

So Qt and PyQt behave according to their documentation.

Replacing style.subElementRect(QStyle.SE_ItemViewItemText, options) with
style.subElementRect(QStyle.SE_ItemViewItemText, options, None) in
Spyder code seems to help.

With regards to crash when using GTK2, it is a different and known
issue. Qt uses GTK3 platformtheme (i.e. dialogs) by default, and it is
incompatible with GTK2. If you want to use GTK2 then you should export
QT_QPA_PLATFORMTHEME=gtk2. But I recommend against using GTK2 as it is
deprecated.

** Changed in: qtstyleplugins-src (Ubuntu)
   Status: New => Invalid

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

Title:
  Error when going to 'Tools -> Preferences -> Keyboard shortcuts' in
  Spyder3 in Bionic

Status in pyqt5 package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in qtstyleplugins-src package in Ubuntu:
  Invalid
Status in spyder package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04 LTS
  Steps:

  1. Install spyder3 and qt5-style-plugins (sudo apt install spyder3 
qt5-style-plugins)
  2. Run spyder3
  3. Go to Tools → Preferences → General → Appearance
  4. Change the Qt window style to cleanlooks, gtk2 or plastique
  5. Go to Tools → Preferences → Keyboard shortcuts
  6. Error (or crash in case of gtk2)

  Keyboard shortcuts are not accessible.

  Here is the error:

    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
 

[Touch-packages] [Bug 1834333] Re: Scaling problem with Qt apps

[Dmitry Shachnev]

This should be fixed by https://codereview.qt-
project.org/c/qt/qtbase/+/265653, which will be included in Qt 5.12.5.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => In Progress

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

Title:
  Scaling problem with Qt apps

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Hi
  I have problem with scaling for Qt apps.
  when i open Kolourpaint scaling is too small 
  i have Ubuntu 18.04 and install from snap and apt
  i first report to bugs.kde.org and they tell me to report here 
  https://bugs.kde.org/show_bug.cgi?id=407668

  Kolourpaint its not only app with problem , anydesk , filezilla ,
  pylon viewer ,  dukto , stacer , vmware horizon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1834333/+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 1834333] Re: Scaling problem with Qt apps

[Dmitry Shachnev]

It is an upstream fix that is not yet released. Note that the bug status
is “In progress”.

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

Title:
  Scaling problem with Qt apps

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Hi
  I have problem with scaling for Qt apps.
  when i open Kolourpaint scaling is too small 
  i have Ubuntu 18.04 and install from snap and apt
  i first report to bugs.kde.org and they tell me to report here 
  https://bugs.kde.org/show_bug.cgi?id=407668

  Kolourpaint its not only app with problem , anydesk , filezilla ,
  pylon viewer ,  dukto , stacer , vmware horizon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1834333/+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 1833536] Re: QuiteRSS crashes intermittently

[Dmitry Shachnev]

So the original reporter does not respond, and we need to somehow verify
the fix to make it reach bionic-updates.

I created a fresh Bionic VM, installed qtbase from -proposed, quiterss
and qbittorrent and left them running for several hours (as you can see
in the attached screenshot).

No crash occurred, so I think we can treat this bug as verified for
bionic.

I will do the same thing for disco a bit later.

** Attachment added: "VirtualBox_Ubuntu 18.04.3 LTS_31_08_2019_15_30_53.png"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+attachment/5285953/+files/VirtualBox_Ubuntu%2018.04.3%20LTS_31_08_2019_15_30_53.png

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  QuiteRSS crashes intermittently

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  This bug affects QuiteRSS and other Qt applications, like plasma-discover 
(see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 
1814375). All they crash with similar stack traces.

  [Test Case]
  1. Open QuiteRSS.
  2. Leave it running for several hours.
  3. It should not crash.

  [Proposed Fix]
  The proposed fix is a backport of the following commit from upstream 5.12 
branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db

  [Regression Potential]
  This patch adds an additional check before re-sending the request. 
Regressions chance is minimal, but the potential regressions may be that the 
request is not re-sent where it was re-sent with the previous code.

  [Original Description]
  After opening QuiteRSS it will run until crash happens.  This happens 
intermittently within the hour usually.

  (gdb) bt
  #0  QHttpNetworkConnectionChannel::sendRequest (this=)
  at access/qhttpnetworkconnectionchannel.cpp:238
  #1  0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest (
  this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015
  #2  0x72736122 in QObject::event (this=0x7fff48da89b0,
  e=) at kernel/qobject.cpp:1247
  #3  0x76f2482c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
  () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #4  0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) ()
     from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #5  0x727069a8 in QCoreApplication::notifyInternal2 (
  receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0)
  at kernel/qcoreapplication.cpp:1024
  #6  0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0,
  receiver=)
  at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
  #7  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
  event_type=event_type@entry=0, data=0x7fff60008e90)
  at kernel/qcoreapplication.cpp:1699
  #8  0x727096a8 in QCoreApplication::sendPostedEvents (
  receiver=receiver@entry=0x0, event_type=event_type@entry=0)
  at kernel/qcoreapplication.cpp:1553
  #9  0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10)
  at kernel/qeventdispatcher_glib.cpp:276
  #10 0x7fffece96317 in g_main_context_dispatch ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7fffece96550 in ?? () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x7fffece965dc in g_main_context_iteration ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #13 0x7275f8ef in QEventDispatcherGlib::processEvents (
  this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
  #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60,
  flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
  #15 0x7252322a in QThread::exec (this=)
  at thread/qthread.cpp:515
  #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20)
  at thread/qthread_unix.cpp:368
  #17 0x722646db in start_thread (arg=0x7fff4700)
  at pthread_create.c:463
  #18 0x719ec88f in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1833536] Re: QuiteRSS crashes intermittently

[Dmitry Shachnev]

And now I have verified the fix for Disco using the same steps.

** Attachment added: "VirtualBox_Ubuntu 19.04_01_09_2019_15_28_44.png"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+attachment/5286070/+files/VirtualBox_Ubuntu%2019.04_01_09_2019_15_28_44.png

** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco

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

Title:
  QuiteRSS crashes intermittently

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  This bug affects QuiteRSS and other Qt applications, like plasma-discover 
(see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 
1814375). All they crash with similar stack traces.

  [Test Case]
  1. Open QuiteRSS.
  2. Leave it running for several hours.
  3. It should not crash.

  [Proposed Fix]
  The proposed fix is a backport of the following commit from upstream 5.12 
branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db

  [Regression Potential]
  This patch adds an additional check before re-sending the request. 
Regressions chance is minimal, but the potential regressions may be that the 
request is not re-sent where it was re-sent with the previous code.

  [Original Description]
  After opening QuiteRSS it will run until crash happens.  This happens 
intermittently within the hour usually.

  (gdb) bt
  #0  QHttpNetworkConnectionChannel::sendRequest (this=)
  at access/qhttpnetworkconnectionchannel.cpp:238
  #1  0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest (
  this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015
  #2  0x72736122 in QObject::event (this=0x7fff48da89b0,
  e=) at kernel/qobject.cpp:1247
  #3  0x76f2482c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
  () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #4  0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) ()
     from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #5  0x727069a8 in QCoreApplication::notifyInternal2 (
  receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0)
  at kernel/qcoreapplication.cpp:1024
  #6  0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0,
  receiver=)
  at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
  #7  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
  event_type=event_type@entry=0, data=0x7fff60008e90)
  at kernel/qcoreapplication.cpp:1699
  #8  0x727096a8 in QCoreApplication::sendPostedEvents (
  receiver=receiver@entry=0x0, event_type=event_type@entry=0)
  at kernel/qcoreapplication.cpp:1553
  #9  0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10)
  at kernel/qeventdispatcher_glib.cpp:276
  #10 0x7fffece96317 in g_main_context_dispatch ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7fffece96550 in ?? () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x7fffece965dc in g_main_context_iteration ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #13 0x7275f8ef in QEventDispatcherGlib::processEvents (
  this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
  #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60,
  flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
  #15 0x7252322a in QThread::exec (this=)
  at thread/qthread.cpp:515
  #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20)
  at thread/qthread_unix.cpp:368
  #17 0x722646db in start_thread (arg=0x7fff4700)
  at pthread_create.c:463
  #18 0x719ec88f in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1812150] Re: qhelpgenerator and qcollectiongenerator will not run

[Dmitry Shachnev]

This is how qtchooser works. You need to install qt5-default package
which provides a proper configuration, or export QT_SELECT=5, or run
“qhelpgenerator -qt5” and so on.

** Changed in: qtchooser (Ubuntu)
   Status: New => Invalid

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

Title:
  qhelpgenerator and qcollectiongenerator will not run

Status in qtchooser package in Ubuntu:
  Invalid

Bug description:
  I have qttols5-dev-tools installed, which provides a qthelpgenerator
  implementation. But when I try to run qhelpgenerator (or
  qcollectiongenerator) through their usual /usr/bin shims, it errors
  out:

  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ dpkg -S 
/usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator 
  qttools5-dev-tools: /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ ls -l 
/usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator
  lrwxrwxrwx 1 root root 31 Apr 14  2018 
/usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator -> 
../../../qt5/bin/qhelpgenerator
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ which qhelpgenerator
  /usr/bin/qhelpgenerator
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ ls -l 
/usr/bin/qhelpgenerator
  lrwxrwxrwx 1 root root 9 Dec 21  2017 /usr/bin/qhelpgenerator -> qtchooser
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ qhelpgenerator -v
  qhelpgenerator: could not find a Qt installation of ''
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ qcollectiongenerator -v
  qcollectiongenerator: could not find a Qt installation of ''
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ 

  Running them directly works:

  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ 
/usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator -v
  Qt Help Generator version 1.0 (Qt 5.9.5)
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ 
/usr/lib/x86_64-linux-gnu/qt5/bin/qcollectiongenerator -v
  Qt Collection Generator version 1.0 (Qt 5.9.5)

  
  But most software will locate the /usr/bin shims instead of this actual 
binary.

  Looks like a problem with qtchooser?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qtchooser 64-ga1b6736-5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 16 20:00:43 2019
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
   libstdc++6 8.2.0-1ubuntu2~18.04
  InstallationDate: Installed on 2019-01-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: qtchooser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1812150/+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 1812150] Re: qhelpgenerator and qcollectiongenerator will not run

[Dmitry Shachnev]

> qtchooser could use a more informative error message, though.

I agree.

> Who maintains qtchooser? Is that you (Ubuntu)?

No, it is maintained here (not very actively, though):

https://code.qt.io/cgit/qtsdk/qtchooser.git/
https://codereview.qt-project.org/#/q/project:qtsdk/qtchooser,n,z

For Qt 6, we will try to get rid of qtchooser in favour of something
else. See the thread starting at:

https://lists.qt-
project.org/pipermail/development/2018-November/068691.html

qt5-default is our (Debian / Ubuntu) specific package, though.

> What's going to happen with the `qcollectiongenerator` shim with Qt
5.12?

With qt5-default installed (or QT_CONFIG=5), you will get exit code 1
and this message:

  qcollectiongenerator: could not exec
'/usr/lib/qt5/bin/qcollectiongenerator': No such file or directory

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

Title:
  qhelpgenerator and qcollectiongenerator will not run

Status in qtchooser package in Ubuntu:
  Invalid

Bug description:
  I have qttols5-dev-tools installed, which provides a qthelpgenerator
  implementation. But when I try to run qhelpgenerator (or
  qcollectiongenerator) through their usual /usr/bin shims, it errors
  out:

  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ dpkg -S 
/usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator 
  qttools5-dev-tools: /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ ls -l 
/usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator
  lrwxrwxrwx 1 root root 31 Apr 14  2018 
/usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator -> 
../../../qt5/bin/qhelpgenerator
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ which qhelpgenerator
  /usr/bin/qhelpgenerator
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ ls -l 
/usr/bin/qhelpgenerator
  lrwxrwxrwx 1 root root 9 Dec 21  2017 /usr/bin/qhelpgenerator -> qtchooser
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ qhelpgenerator -v
  qhelpgenerator: could not find a Qt installation of ''
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ qcollectiongenerator -v
  qcollectiongenerator: could not find a Qt installation of ''
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ 

  Running them directly works:

  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ 
/usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator -v
  Qt Help Generator version 1.0 (Qt 5.9.5)
  janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ 
/usr/lib/x86_64-linux-gnu/qt5/bin/qcollectiongenerator -v
  Qt Collection Generator version 1.0 (Qt 5.9.5)

  
  But most software will locate the /usr/bin shims instead of this actual 
binary.

  Looks like a problem with qtchooser?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qtchooser 64-ga1b6736-5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 16 20:00:43 2019
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
   libstdc++6 8.2.0-1ubuntu2~18.04
  InstallationDate: Installed on 2019-01-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: qtchooser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1812150/+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 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

[Dmitry Shachnev]

Verifying in a cosmic chroot:

# apt install qtbase5-doc-html qtdeclarative5-doc-html
[...]
Get:1 http://archive.ubuntu.com/ubuntu cosmic-proposed/universe amd64 
qtbase5-doc-html all 5.11.1+dfsg-7ubuntu2 [22.1 MB]
Get:2 http://archive.ubuntu.com/ubuntu cosmic-proposed/universe amd64 
qtdeclarative5-doc-html all 5.11.1-6build1 [11.6 MB]
[...]
# dpkg -L qtbase5-doc-html | grep /usr/share/qt5/doc/qtcore/qobject.html
/usr/share/qt5/doc/qtcore/qobject.html
# dpkg -L qtdeclarative5-doc-html | grep 
/usr/share/qt5/doc/qtquick/qquickwidget.html
/usr/share/qt5/doc/qtquick/qquickwidget.html

Note that presence of the file in qtdeclarative5-doc-html is a
verification for qttools-opensource-src too.

** Tags removed: verification-needed
** Tags added: verification-done verification-done-cosmic

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qttools-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Cosmic:
  Confirmed
Status in qtdeclarative-opensource-src source package in Cosmic:
  Confirmed
Status in qttools-opensource-src source package in Cosmic:
  Confirmed
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.

  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine,
  etc.).

  To properly fix this bug, we need changes in qtbase and qttools
  modules. In addition, I will be uploading a no-change rebuild of
  qtdeclarative module to demonstrate that the fixes work.

  If requested, I can also upload no-change rebuilds of some other
  modules to get their -doc packages properly regenerated.

  [Test Case]
  For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.

  For qtdeclarative5-doc-html:
  1. Install qtdeclarative5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.

  [Regression Potential]
  The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.

  The proposed change in qttools can affect more packages. It can result
  in qdoc passing more -isystem flags to clang code analyzer. I am not
  aware of negative consequences of this, but if they happen, these
  consequences will be limited to potential build failures or wrong
  documentation contents.

  [Other Info]
  Description of the fix:

  qdoc is a tool that parses C++ source files and generates
  documentation from them. Recently, qdoc began using clang instead of
  its own C++ parser. Clang needs the C++ standard library to work.
  Starting with llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard
  library is no longer on clang’s default search paths, so we need to
  pass it explicitly as -I flag. The proposed qtbase patch
  (qdoc_default_incdirs.diff) does that.

  That patch fixes documentation build for qtbase, but for other modules
  there is another problem. The Qt headers are installed into
  /usr/include//qt5 directory, but it is also not on Clang
  default search path. qmake passes these directories as -isystem flags,
  but qdoc ignores -isystem by default, unless it is built with
  QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is
  building with this define.

  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1799111/+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 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

[Dmitry Shachnev]

That definitely is not related to my changes. However, it could be
caused by the fact that qtbase is rebuilt against new OpenSSL or
something like that. I found a similar bug in Debian:
https://bugs.debian.org/907339.

Let’s see if retrying the tests against kdeconnect 1.3.3 (which just
migrated to -updates) fixes it.

** Bug watch added: Debian Bug tracker #907339
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907339

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qttools-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Cosmic:
  Confirmed
Status in qtdeclarative-opensource-src source package in Cosmic:
  Confirmed
Status in qttools-opensource-src source package in Cosmic:
  Confirmed
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.

  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine,
  etc.).

  To properly fix this bug, we need changes in qtbase and qttools
  modules. In addition, I will be uploading a no-change rebuild of
  qtdeclarative module to demonstrate that the fixes work.

  If requested, I can also upload no-change rebuilds of some other
  modules to get their -doc packages properly regenerated.

  [Test Case]
  For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.

  For qtdeclarative5-doc-html:
  1. Install qtdeclarative5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.

  [Regression Potential]
  The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.

  The proposed change in qttools can affect more packages. It can result
  in qdoc passing more -isystem flags to clang code analyzer. I am not
  aware of negative consequences of this, but if they happen, these
  consequences will be limited to potential build failures or wrong
  documentation contents.

  [Other Info]
  Description of the fix:

  qdoc is a tool that parses C++ source files and generates
  documentation from them. Recently, qdoc began using clang instead of
  its own C++ parser. Clang needs the C++ standard library to work.
  Starting with llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard
  library is no longer on clang’s default search paths, so we need to
  pass it explicitly as -I flag. The proposed qtbase patch
  (qdoc_default_incdirs.diff) does that.

  That patch fixes documentation build for qtbase, but for other modules
  there is another problem. The Qt headers are installed into
  /usr/include//qt5 directory, but it is also not on Clang
  default search path. qmake passes these directories as -isystem flags,
  but qdoc ignores -isystem by default, unless it is built with
  QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is
  building with this define.

  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1799111/+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 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

[Dmitry Shachnev]

@Łukasz: kdeconnect tests failures is a race condition in tests, not a
real bug.

This patch (which is applied in Disco) https://salsa.debian.org/qt-kde-
team/extras/kdeconnect/blob/master/debian/patches/ssl_socket_race_fix.diff
would fix it. But as it’s a bug in tests and not in real code, I would
just ignore it.

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qttools-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Cosmic:
  Confirmed
Status in qtdeclarative-opensource-src source package in Cosmic:
  Confirmed
Status in qttools-opensource-src source package in Cosmic:
  Confirmed
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.

  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine,
  etc.).

  To properly fix this bug, we need changes in qtbase and qttools
  modules. In addition, I will be uploading a no-change rebuild of
  qtdeclarative module to demonstrate that the fixes work.

  If requested, I can also upload no-change rebuilds of some other
  modules to get their -doc packages properly regenerated.

  [Test Case]
  For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.

  For qtdeclarative5-doc-html:
  1. Install qtdeclarative5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.

  [Regression Potential]
  The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.

  The proposed change in qttools can affect more packages. It can result
  in qdoc passing more -isystem flags to clang code analyzer. I am not
  aware of negative consequences of this, but if they happen, these
  consequences will be limited to potential build failures or wrong
  documentation contents.

  [Other Info]
  Description of the fix:

  qdoc is a tool that parses C++ source files and generates
  documentation from them. Recently, qdoc began using clang instead of
  its own C++ parser. Clang needs the C++ standard library to work.
  Starting with llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard
  library is no longer on clang’s default search paths, so we need to
  pass it explicitly as -I flag. The proposed qtbase patch
  (qdoc_default_incdirs.diff) does that.

  That patch fixes documentation build for qtbase, but for other modules
  there is another problem. The Qt headers are installed into
  /usr/include//qt5 directory, but it is also not on Clang
  default search path. qmake passes these directories as -isystem flags,
  but qdoc ignores -isystem by default, unless it is built with
  QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is
  building with this define.

  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1799111/+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 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

[Dmitry Shachnev]

Hi Robert and Sergio!

Sorry for the delay with fixing this. In Qt packaging team, we are all
volunteers and work in our free time.

Initially I hoped that one of my co-maintainers would take care of this
issue, but looks like they also didn’t have time, so I fixed it myself
for the development release.

I will look at backporting this change to Bionic and Cosmic soon.

Note that I applied only Robert’s patch that fixes duplex printing. For
Ubuntu 19.04 we are going to ship Qt 5.12, which should have much better
printing experience. If there are other patches that can be backported,
please let me know.

Also, if one of you adds a test case (steps to reproduce) for the duplex
issue to the bug description, it will speed up the stable update a bit.

** Also affects: qtbase-opensource-src (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: qtbase-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New
Status in qtbase-opensource-src source package in Cosmic:
  New

Bug description:
  All kde applications shipped with ubuntu and particularly kubuntu
  bionic print via the qt print dialog, that, unfortunately, does not
  seem to respect the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jun 11 10:23:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1641 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

[Dmitry Shachnev]

Uploaded fix for Bionic, it is now waiting for approval in the queue:
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1

Will someone be able to test a Cosmic fix if I do it?

** Description changed:

- All kde applications shipped with ubuntu and particularly kubuntu bionic
- print via the qt print dialog, that, unfortunately, does not seem to
- respect the defaults set for the printer.
+ [Impact]
+ All kde applications shipped with ubuntu and particularly kubuntu bionic 
print via the qt print dialog, that, unfortunately, does not seem to respect 
the defaults set for the printer.
  
  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.
  
  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a total
  of 3 times the paper usage if the print dialog respected the default.
  
+ [Test Case]
+ 1) Install a printer that can duplex and configure it to do duplex with 
long-edge binding from the printer setup dialog.
+ 
+ 2) Open a PDF with okular, and open the print dialog. Select the printer
+ above.
+ 
+ 3) Press the "Options" button to enlarge the dialog to also present the
+ options. Select the "options" tab, right of "copies". Verify that Duplex
+ Printing is preset to "None"
+ 
+ This is wrong, because the printer was configured to do duplex with
+ long-edge binding.
+ 
+ 4) Print and close okular.
+ 
+ 5) Reopen okular (with the same or another PDF file). Open again the
+ print dialog and select the same printer.
+ 
+ 6) Redo 3). Again see that Duplex Printing is preset to "None", instead
+ of being at the default or at the previously used setup.
+ 
+ [Regression Potential]
+ The proposed patch only changes the default settings. The regression 
potential may be that the values are wrong, although they are already wrong.
+ 
+ In case there is some bug it may lead to crashes. But this code is in
+ the latest stable Qt release and I am not aware of any such crashes
+ reported.
+ 
+ [Other Info]
+ The proposed patch is a backport of the following upstream commits:
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e
+ 
+ [Original Description]
  See also https://bugs.kde.org/show_bug.cgi?id=395150
  
  As a final comment and in general, I think that Bionic should be updated
  to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at
  least via a kubuntu ppa). The QT 5 print dialog has always been
  extremely poor, with no possibility to provide information about things
  like print quality and resolution, paper type, stapling (for printers
  supporting it), etc. Now, QT 5.11 has finally a better print dialog and
  it would be great if the bionic users could use it.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
- Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1
- ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
- Uname: Linux 4.15.0-22-generic x86_64
- ApportVersion: 2.20.9-0ubuntu7.2
- Architecture: amd64
- CurrentDesktop: KDE
- Date: Mon Jun 11 10:23:53 2018
- EcryptfsInUse: Yes
- InstallationDate: Installed on 2013-12-12 (1641 days ago)
- InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
- SourcePackage: qtbase-opensource-src
- UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago)

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New
Status in qtbase-opensource-src source package in Cosmic:
  New

Bug description:
  [Impact]
  All kde applications shipped with ubuntu and particularly kubuntu bionic 
print via the qt print dialog, that, unfortunately, does not seem to respect 
the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  [Test Case]
  1) Install a printer that can duplex and configure it to do duplex with 
long-edge binding from the printer setup dialog.

  2) Open a PDF with okular, and open the print dialog. Select the
  printer above.

  3) Press the "Options" button to enlarge the dialog to also present
  the options. Select the "options" tab, right of "copies". Verify that
  Duplex Printing is preset to "None"

  This is wrong, because

[Touch-packages] [Bug 1846821] Re: Qt print dialog has wrong default page size

[Dmitry Shachnev]

I have retried the tests, and now the only failing one is pinentry. But
it has passed only once, and that was by accident. Please ignore it:

http://autopkgtest.ubuntu.com/packages/p/pinentry/bionic/amd64

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Qt print dialog has wrong default page size

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  [Impact]
  In Qt5 applications, print dialog (Printer Properties) always defaults to A4 
paper size, even when Letter is set as a default in all system and KDE 
preferences. After changing manually, Letter-size pages print correctly, but 
the setting does not stick.

  This impacts users of Qt applications who print things and live in
  countries where ISO 216 is not default, most notably the United
  States.

  [Test Case]
  1) Use system settings (KDE preferences, gnome-control-center or 
system-config-printer) to set the printer size to Letter.
  2) Open any Qt application (e.g. KWrite or Falkon).
  3) Open a print dialog.
  4) Behavior expected: Print dialog would default to Letter paper size and not 
A4.

  [Regression Potential]
  Two possibilities for regressions that I can imagine are:
  - crashes because something is not defined;
  - wrong default paper size (A4 wanted but CUPS returns something else).

  [Additional Information]
  The issue also affects other print settings, e.g. margins, though the 
aforementioned patch does not deal with these. A similar issue regarding the 
duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, 
but other print settings continue to cause problems.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1853768] Re: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme

[Dmitry Shachnev]

When an icon is missing (e.g. document-open), Qt first falls back to
splitting the name by dashes and taking the first part of it (document).
Only then it falls back to parent icon themes (Yaru → Humanity). So for
all document-* icons it uses document.png from MimeTypes context.

Doing it vice versa would fix the bug. However, the specification
explicitly tells us to behave as Qt currently does:
https://specifications.freedesktop.org/icon-naming-spec/icon-naming-
spec-latest.html#guidelines

> if the more specific item does not exist in the current theme, and
does exist in a parent theme, the generic icon from the current theme is
preferred, in order to keep consistent style.

Another potential fix would be ignoring the MimeTypes context. The
specification says that fallback happens “for all contexts other than
MimeTypes”. However currently Qt’s icon loader does not take contexts
into account at all. So fixing it in Qt would be difficult.

I have just pinged the Yaru theme maintainer, let’s hope the fix from
Yaru will land in Ubuntu soon.

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

Title:
  Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show
  them as normal document icon under Yaru theme

Status in Yaru Theme:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  Qt apps, like kid3-qt, which uses these legacy icons:

  document-open.png
  document-open-recent.png
  document-save.png
  document-save-as.png
  document-revert.png
  document-import.png
  document-export.png

  The icons are all shown as the same normal document icon under Yaru.

  Qt apps only have a problem with legacy icons starting with
  "document-*" and all other legacy icons are inherited from Humanity
  under Yaru.

  Is there a general solution to force Qt apps to choose the closest
  icon name from Yaru or Humanity?

  Should this bug be issued against upstream Qt?

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1853768/+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 1858141] Re: "Advanced" tab is missing from Print dialog in Qt5 applications

[Dmitry Shachnev]

Thank you for filing this bug and adding the required SRU information.
But I have to reject it:

Actually, that patch is just the tip of the iceberg.

It does not apply cleanly unless you backport many other patches. If you
look at OpenSUSE, they have added 11 patches related to printing dialog
and also 17 other patches related to printing:

https://build.opensuse.org/request/show/569841
https://build.opensuse.org/package/show/KDE:Qt:5.9/libqt5-qtbase

Some of these patches change private API, so they require rebuild of
packages relying on it. Unfortunately, this does not meet our SRU
criteria.

** Also affects: qtbase-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

** Changed in: qtbase-opensource-src (Ubuntu Bionic)
   Status: New => Won't Fix

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

Title:
  "Advanced" tab is missing from Print dialog in Qt5 applications

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Won't Fix

Bug description:
  Please backport Qt patch 213391 to qtbase-opensource-src in Bionic:
  https://codereview.qt-project.org/#/c/213391/

  
  [Impact]
  On Kubuntu 18.04 (bionic), any applications using Qt5 are unable to fully 
configure printers from within the "Print..." dialog because the "Advanced" tab 
is no longer present.  Settings shown here will differ by printer, but this 
includes important settings such as paper type (plain, glossy, photo, etc.), 
print resolution, and ink usage strategies.  Gwenview and Okular are notable 
affected applications.  GTK applications are unaffected and do show the 
advanced options provided by the printer driver.  As a workaround for Qt5 
applications, the printer *default* advanced settings can be successfully 
accessed and changed from within the "Printers" section of Plasma's "System 
Settings", but this is cumbersome, unintuitive, and is not the intended way of 
interacting with these settings on a per-print-job basis.

  
  [Additional Information]
  This was identified as a bug in Qt5 upstream:
  https://bugreports.qt.io/browse/QTBUG-54464

  The bug was fixed upstream in Qt 5.11, but Bionic is stable on Qt 5.9.
  I'd like to request that this patch be backported to Bionic, please.

  
  [Regression Potential]
  OpenSUSE has already backported this patch to their Qt 5.9 stable branch, so 
there is precedent for this patch being low risk:
  
https://build.opensuse.org/package/view_file/KDE:Qt:5.9/libqt5-qtbase/0010-Reintroduce-the-Advanced-tab-in-the-QPrintProperties.patch?expand=1

  
  Software Versions:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.3 LTS
  Release:18.04
  Codename:   bionic

  $ apt-cache policy libqt5printsupport5
  libqt5printsupport5:
Installed: 5.9.5+dfsg-0ubuntu2.4
Candidate: 5.9.5+dfsg-0ubuntu2.4
Version table:
   *** 5.9.5+dfsg-0ubuntu2.4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.9.5+dfsg-0ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   5.9.5+dfsg-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1858141/+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 1771358] Re: qt5-qmake contains mkspecs/linux-pgcc in xenial but not bionic

[Dmitry Shachnev]

Hi Carl!

These mkspecs were deleted upstream in Qt 5.9: https://codereview.qt-
project.org/191927. So it is not our bug, but a result of packaging the
new upstream version.

If you use Launchpad for reporting bugs (and not ubuntu-bug utility),
you need the *source* package name, not the binary package name. A
single source package may build multiple binary packages, which is the
case here.

On your link (https://packages.ubuntu.com/bionic/qt5-qmake) the source
package name is shown above, it is qtbase-opensource-src.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  qt5-qmake contains mkspecs/linux-pgcc in xenial but not bionic

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

Bug description:
  I'm trying to build the CUBE gui using the PGU compiler. This depends on 
qt5-qmake.
  The amd64 / 16.04 build

https://packages.ubuntu.com/xenial/qt5-qmake
https://packages.ubuntu.com/xenial/amd64/qt5-qmake/filelist

  contains these two files

/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qmake.conf
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qplatformdefs.h

  but the and64 / 18.04 version does not

https://packages.ubuntu.com/bionic/qt5-qmake
https://packages.ubuntu.com/bionic/amd64/qt5-qmake/filelist

  Is this an oversight?
  Also, when I tried to file this bug the first time, the tracker said

"qt5-qmake" does not exist in Ubuntu. Please choose a different
  package. If you're unsure, please select "I don't know"

  This doesn't make any sense, since this is the name presented on your
  web-page. The search option gave me a list of packages that didn't
  look closely related, either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1771358/+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: Include qt5-style-plugins into the default installation, otherwise Qt5 apps don’t pick up the GTK+ style

[Dmitry Shachnev]

We cannot do this for two reasons:

1) QGtkStyle is abandoned and unsupported upstream.
2) The goal is to remove GTK+ 2 from the default installation (and later from 
Ubuntu archive).

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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:
  Include qt5-style-plugins into the default installation, otherwise Qt5
  apps don’t pick up the GTK+ style

Status in qtbase-opensource-src package in Ubuntu:
  Won't Fix

Bug description:
  In Artful and Bionic, Qt5 applications look alien because they don’t follow 
the GTK+ style.
  For Qt5 applications to pick up the GTK+ style, qt5-style-plugins must be 
included into the default installation and “export QT_QPA_PLATFORMTHEME=gtk2” 
must be provided.

  Original 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 1732970] Re: Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-opensource-src from archive

[Dmitry Shachnev]

Marius: these packages were dead and unmaintained both in Ubuntu and
upstream. For qtfeedback and qtsystems, the only release (5.0.0 beta 1)
was six years ago (in 2012). Also they were not present in Debian.

If you are willing to maintain them, feel free to reintroduce them, but
to get it right, you will need to synchronize your work with both
upstream and Debian.

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

Title:
  Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-
  opensource-src from archive

Status in cordova-ubuntu-3.4 package in Ubuntu:
  Fix Released
Status in qtfeedback-opensource-src package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  cordova-ubuntu is dead upstream (https://github.com/apache/cordova-
  ubuntu had last commit in Oct 2016), Ubuntu packaging has no active
  maintainer and has not been updated since 2014.

  I have talked to Alberto Mardegan on IRC, he confirmed that it should be safe 
to remove it:
  https://irclogs.ubuntu.com/2017/11/17/%23ubuntu-devel.html#t18:43

  qtfeedback-opensource-src and qtsystems-opensource-src are libraries
  which have never become part of official Qt releases, and their only
  user in Ubuntu was cordova-ubuntu-3.4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cordova-ubuntu-3.4/+bug/1732970/+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 1761708] Re: QWebEngineView crashes

[Dmitry Shachnev]

I think it is a bug in Qt, reported as
https://bugreports.qt.io/browse/QTBUG-67537.

Another possible workaround: export QT_XCB_GL_INTEGRATION=xcb_egl (the
bug is in the xcb_glx integration plugin, this environment variable will
switch to a different integration plugin).

** Package changed: pyqt5 (Ubuntu) => qtbase-opensource-src (Ubuntu)

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

Title:
  QWebEngineView crashes

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

Bug description:
  I have KUbuntu 18.04 with the latest updates. I installed all pyqt3
  stuff plus python3-pyqt5.qtwebengine and tried to execute a tiny
  webengine demo (attached):

  $ python3 browser.py
  Segmentation fault (core dumped)
  [1:1:0100/00.971262:ERROR:broker_posix.cc(41)] Invalid node channel 
message

  Please see the attached core file & gdb bt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1761708/+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 1713961] Re: libqt5declarative5 has unmet dependencies

[Dmitry Shachnev]

This package was coming from qtquick1-opensource-src source. It was
removed from Ubuntu Yakkety and newer versions.

** Package changed: qtdeclarative-opensource-src (Ubuntu) => qtquick1
-opensource-src (Ubuntu)

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

Title:
  libqt5declarative5 has unmet dependencies

Status in qtquick1-opensource-src package in Ubuntu:
  New
Status in twinkle package in Ubuntu:
  New

Bug description:
  Trying to install libqt5declarative5 results in an unmet dependencies
  error:

  $ sudo apt install libqt5declarative5
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) libqt5declarative5 [ amd64 ] < none -> 5.5.1-2build1 > ( 
universe/libs )
  Broken libqt5declarative5:amd64 Depends on qtbase-abi-5-5-1 [ amd64 ] < none 
->  > ( none )
Considering libqt5core5a:amd64 4959 as a solution to 
libqt5declarative5:amd64 
Considering libqt5core5a:amd64 4959 as a solution to 
libqt5declarative5:amd64 
  Broken libqt5declarative5:amd64 Depends on qtscript-abi-5-2-0 [ amd64 ] < 
none ->  > ( none )
Considering libqt5script5:amd64 260 as a solution to 
libqt5declarative5:amd64 
  Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libqt5declarative5 : Depends: qtbase-abi-5-5-1
Depends: qtscript-abi-5-2-0
  E: Unable to correct problems, you have held broken packages.

  This package is itself a dependency of twinkle.
  Ubuntu release here is 16.04 xenial.
  Thank you.

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