Bug#881333: tracking OpenGL support for specific boards
> > Many of those chipsets you list, as I understand, have a mesa driver > > for them that support opengl and gles. > > Such as freedreno which supports A4XX series. https://mesamatrix.net/ > > > > Keep in mind, only the proprietary drivers seem to not support opengl > > while the hardware is perfectly capable of doing so. > > Not necessarily. > If the manufacturer specifies OpenGL ES support, then - on the hardware > level - it is a GLES renderer and may or may not support the entire > OpenGL specification natively. It usually requires considerable work to > make GLES hardware support OpenGL. > Eric Anhold can tell you all about the hard work he has put into > bastardising his VC4 mesa driver to make up for the lack of hardware > support: > When Eric jumped from Intel to Broadcom, I was there at the beginning of his VC4 work doing testing and getting OpenMW running on the RPi. One of our conversations revolved around why only GLES support and not full GL support in the binary blob and his answer was that VC4 can do both but only to a point, it depends entirely on what the hardware is capable of. VC4 is fully capable of OpenGL 2.1 but with a few more extensions that were GLES 2.0 specific. No bastardisation. His biggest hurdle (still?) is dealing with the fact that the VC4 has no memory space protection because there is no MMU. He has to use a CMA which is _very_ slow and has had to put in a ton of work to get that working. [1] That has nothing to do with what the GPU was capable of in terms of GL/GLES. You can't have GLES 2.0 without first having GLES 1.1 which is backwards compatible with OpenGL 1.5 in hardware. That is why I stated that it is the driver developer that makes the decision as to what is exposed which is a cost/price decision of the company pushing the hardware. If they only have to target GLES then why expose GL? Less time to market and less money spent in development? Take for example the S3TC opengl extension: EXT_texture_compression_s3tc This is not supported in hardware which is the reason, even after the patent was expired, that Eric (or anyone) could not implement it. Broadcom simply didn't bother (cost cutting?). So if you ever have texture that loads in with a S3TC, all you'll see is pink (or whatever is used as alpha). There is no, if extension doesn't exist, we'll just emulate it in software in VC4. I would be seriously flabbergasted if there was a chipset out there that supported GLES2, that on hardware, wasn't capable of at least OpenGL 1.5. I'm talking about on hardware, not a proprietary binary blog that only exposes GLES. > https://github.com/anholt/mesa/wiki/VC4-OpenGL-support > I know, I've posted this several time in previous Qt related threads. :) Cheers, Bret [1] https://dri.freedesktop.org/docs/drm/gpu/vc4.html
Bug#915090: plasma-wallpapers-addons: No providers for picture of the day
Package: plasma-wallpapers-addons Version: 4:5.13.5-1 Severity: normal Dear Maintainer, There are no providers defined for the picture of the day, so it's impossible to use it, and that's more or less the only thing that this package provies, so it is kinda useless at the moment. Best -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8), LANGUAGE=it (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-wallpapers-addons depends on: ii kdeplasma-addons-data 4:5.13.5-1 ii plasma-framework 5.49.0-1 plasma-wallpapers-addons recommends no packages. plasma-wallpapers-addons suggests no packages. -- no debconf information
Bug#915115: meta-kde: Install xdg-desktop-portal-kde by default
Source: meta-kde Version: 5:102 Flatpak recommends xdg-desktop-portal-gtk | xdg-desktop-portal-backend xdg-desktop-portal-backend is a virtual package provided by the GTK and KDE backends. Since there is a KDE backend, I think one of the KDE metapackage should go ahead and install it by default so that a user who installs Flatpak will get the correct KDE integration without needing to take the further action of finding and installing the KDE backend. For reference, the kubuntu-desktop and kubuntu-full metapackages recommend xdg-desktop-portal-kde. By the way, Snap will soon be using xdg-desktop-portal too. Thanks, Jeremy Bicha
Bug#915122: extra-cmake-modules: FindQHelpGenerator does not work for cross compilation
Package: extra-cmake-modules Version: 5.51.0-1 File: /usr/share/ECM/find-modules/FindQHelpGenerator.cmake Control: affects -1 + src:kconfig User: helm...@debian.org Usertags: rebootstrap kconfig fails to cross build from source, because it fails to find qhelpgenerator using extra-cmake-modules. The failure is due to a combination of assumptions that don't add up. It's not entirely clear which of them is wrong so I'm filing the bug with extra-cmake-modules now even though it might need a fix elsewhere. kconfig uses FindQHelpGenerator. FindQHelpGenerator looks up Qt5::qmake. Since fixing #913499, qtbase-5-dev supplies /usr/lib/$DEB_HOST_MULTIARCH/qt5/bin/qmake, which is a symbolic link to /usr/bin/$DEB_HOST_GNU_TYPE-qmake, which is our cross wrapper for qmake. Now FindQHelpGenerator.cmake uses the directory part of Qt5::qmake and expects to find a qhelpgenerator inside that directory. Unfortunately, it doesn't find one. qhelpgenerator is only located in /usr/bin, /usr/lib/qt5/bin and /usr/lib/$DEB_BUILD_GNU_TYPE/qt5/bin. The assumption of FindQHelpGenerator.cmake that the directory of Qt5::qmake contains qhelpgenerator is not presently a valid one. I cannot tell whether it should be valid or not. If it should be valid, then some qt package should provide an additional symlink for qhelpgenerator. Otherwise FindQHelpGenerator should use a different way for finding qhelpgenerator. I've Cced Dmitry and Lisandro and hope that they'll weigh in on how this is supposed to work. Then we can figure out where this needs to be fixed and how. Thanks for your help Helmut
Processed: extra-cmake-modules: FindQHelpGenerator does not work for cross compilation
Processing control commands: > affects -1 + src:kconfig Bug #915122 [extra-cmake-modules] extra-cmake-modules: FindQHelpGenerator does not work for cross compilation Added indication that 915122 affects src:kconfig -- 915122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915122: extra-cmake-modules: FindQHelpGenerator does not work for cross compilation
Hi Helmut!
On Fri, Nov 30, 2018 at 07:23:20PM +0100, Helmut Grohne wrote:
> kconfig fails to cross build from source, because it fails to find
> qhelpgenerator using extra-cmake-modules. The failure is due to a
> combination of assumptions that don't add up. It's not entirely clear
> which of them is wrong so I'm filing the bug with extra-cmake-modules
> now even though it might need a fix elsewhere.
>
> kconfig uses FindQHelpGenerator. FindQHelpGenerator looks up Qt5::qmake.
> Since fixing #913499, qtbase-5-dev supplies
> /usr/lib/$DEB_HOST_MULTIARCH/qt5/bin/qmake, which is a symbolic link to
> /usr/bin/$DEB_HOST_GNU_TYPE-qmake, which is our cross wrapper for qmake.
> Now FindQHelpGenerator.cmake uses the directory part of Qt5::qmake and
> expects to find a qhelpgenerator inside that directory. Unfortunately,
> it doesn't find one. qhelpgenerator is only located in /usr/bin,
> /usr/lib/qt5/bin and /usr/lib/$DEB_BUILD_GNU_TYPE/qt5/bin.
>
> The assumption of FindQHelpGenerator.cmake that the directory of
> Qt5::qmake contains qhelpgenerator is not presently a valid one. I
> cannot tell whether it should be valid or not.
This is fixed upstream in [1]. With that change, FindQHelpGenerator
uses Qt5HelpConfigExtras.cmake which has the correct path:
set(imported_location "${_qt5Help_install_prefix}/lib/qt5/bin/qhelpgenerator")
However as Qt5HelpConfigExtras.cmake is in qttools5-dev, the affected
packages will need to build-depend on it in order for the fix to work.
That commit will be in 5.53.0 release, to be released on December 8th.
[1]: https://cgit.kde.org/extra-cmake-modules.git/commit/?id=96d169b87292d935
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Processing of knights_18.11.90-1_source.changes
knights_18.11.90-1_source.changes uploaded successfully to localhost along with the files: knights_18.11.90-1.dsc knights_18.11.90.orig.tar.xz knights_18.11.90.orig.tar.xz.asc knights_18.11.90-1.debian.tar.xz knights_18.11.90-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
knights_18.11.90-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 30 Nov 2018 22:38:19 +0100 Source: knights Binary: knights Architecture: source Version: 18.11.90-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Description: knights- chess interface for the KDE Platform Changes: knights (18.11.90-1) unstable; urgency=medium . * Team upload. * New upstream release. * Make sure to use the kf5 buildsystem when invoking dh_auto_configure. Checksums-Sha1: 0ebd72ee1e624e210c1b6cea32977e391fb753fb 2720 knights_18.11.90-1.dsc 0c591aa69f04024705c2e05afa9430862b3c5557 3507448 knights_18.11.90.orig.tar.xz b20e2ebbf1a59e71340340b0f64ef09ca36b4dd5 774 knights_18.11.90.orig.tar.xz.asc d000331e1d8560ec2af32109da73b296e97d2870 10416 knights_18.11.90-1.debian.tar.xz 472a967d0f1d2964d85c01aa4b1094cb3f5a61a9 21017 knights_18.11.90-1_source.buildinfo Checksums-Sha256: 7612a4c4f818a15fe35554d594354670cb114d2dd2cd1aa07eeb01c50d854b25 2720 knights_18.11.90-1.dsc 4ca0fda4b3cb54a82174a2a96c43ebe0d63d90b382db06b3ffa5f5a436ddb8de 3507448 knights_18.11.90.orig.tar.xz 2653bd1e61c2da89d10786ab7e7ceb70163bd7f8f2deb9aab255d719a39d4988 774 knights_18.11.90.orig.tar.xz.asc 659dab4dae4e0344d6c9afef5dbea4d33c5522ce9d9d91b4215bfbc68325bf33 10416 knights_18.11.90-1.debian.tar.xz f1e2f450906554d74bc12a5f5c6f38f96f1df343de4ee64fa2a4fa1aa9c87918 21017 knights_18.11.90-1_source.buildinfo Files: 6752c835502a83ab93788c9779e16a7a 2720 games optional knights_18.11.90-1.dsc 3e50cf4435a674ad9bcf03eafc83a7ce 3507448 games optional knights_18.11.90.orig.tar.xz 249deeb05dcf3424cc8d99d0cfb0c9ce 774 games optional knights_18.11.90.orig.tar.xz.asc 4bceacf4e5be0a5a86cbcb083bc3e8ca 10416 games optional knights_18.11.90-1.debian.tar.xz 522dc2d0cbcc6dd56a2f31b947bcede5 21017 games optional knights_18.11.90-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlwBrikACgkQLRkciEOx P01I5hAAjlb7ta5sIKtxzmDLjejZI4/jXiuyH8XZex3n+MY48/LLd3QnIT/ykLPg WK79o6YW/Kdi9iSPXDtUld7sJ3YkUYVlwi3/EKaKurilEdV18eXKt/PN8f3W+g1V Sbyh6W1XNGcrH5Gr04dbiJauvgQ3t2FxWekeAvuOEYA/04bjnSztxu6RwzBq+qqg 9C+tZi7teML9bJhhWGtDlFpVbJOBYzRW+ENX7Awt9sf/870PAy2DyHpg293Sl3uU G7wZ4El6BhhTL42ItS6MkgoJRTy6V36C33akA7HlOx68ffZHyKmteVbZIoibgKgq I446+Fl/LlUxUz2+B1Qhr9eSxqWk2gwDZmM9Cen94Kfj0PVGkMqpCiOPQX/P31Xy HFelLtmgqJ6jrpAR0oB2RnDtF5uKsG5cDStUmyMv758gQzukVdGg//NmnbiQIAdS +zvBeP6b2+WcB7cGl9MNWTW0ZmQWoCPhad1Cs9xwbnLUpggCFIHS1MausBQtDVko pUWlvL9pqSlvv+hzFUkaC7d+hd3caAt/Rs+W24SINVlhOwyFcYG7RZbNxEs57/mC bHAF+ubA0RIZ6ylx0wwOyt+t+jE+SW8UMRQNZNnfk5SRHsVY7H4+59KniynEKr9X AOhpBZ+95U7R+AGGM9r16C8Mocdw0t0MoBcoXPVkKKtVuAQwQCU= =MjzL -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#906977: parley: diff for NMU version 4:17.08.3-1.1
Control: tags 906977 + pending
Dear maintainer,
I've prepared an NMU for parley (versioned as 4:17.08.3-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
diff -Nru parley-17.08.3/debian/changelog parley-17.08.3/debian/changelog
--- parley-17.08.3/debian/changelog 2017-12-02 09:33:57.0 +0100
+++ parley-17.08.3/debian/changelog 2018-12-01 00:38:45.0 +0100
@@ -1,3 +1,12 @@
+parley (4:17.08.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "FTBFS in buster/sid ('QItemSelection' does not name a type)":
+add patch from upstream Git repo to fix build with Qt 5.11.
+(Closes: #906977)
+
+ -- gregor herrmann Sat, 01 Dec 2018 00:38:45 +0100
+
parley (4:17.08.3-1) unstable; urgency=medium
* Team upload.
diff -Nru parley-17.08.3/debian/patches/qt_5.11.patch parley-17.08.3/debian/patches/qt_5.11.patch
--- parley-17.08.3/debian/patches/qt_5.11.patch 1970-01-01 01:00:00.0 +0100
+++ parley-17.08.3/debian/patches/qt_5.11.patch 2018-12-01 00:38:28.0 +0100
@@ -0,0 +1,70 @@
+From f57328e2ba2074bd9e53794525984447d426c38b Mon Sep 17 00:00:00 2001
+From: Andreas Sturmlechner
+Date: Sat, 17 Mar 2018 20:18:04 +0100
+Subject: Fix build with Qt 5.11 (missing headers)
+
+Reviewers: #kde_edu, aacid
+
+Reviewed By: aacid
+
+Tags: #kde_edu
+
+Differential Revision: https://phabricator.kde.org/D11428
+---
+ src/dashboard/buttondelegate.cpp | 1 +
+ src/editor/latexwidget.h | 1 +
+ src/practice/multiplechoicemodewidget.cpp | 1 +
+ src/statistics/statisticsmainwindow.cpp | 1 +
+ 4 files changed, 4 insertions(+)
+
+diff --git a/src/dashboard/buttondelegate.cpp b/src/dashboard/buttondelegate.cpp
+index a99dcc3..315f069 100644
+--- a/src/dashboard/buttondelegate.cpp
b/src/dashboard/buttondelegate.cpp
+@@ -19,6 +19,7 @@
+ #include
+ #include
+ #include
++#include
+ #include
+ #include
+ #include
+diff --git a/src/editor/latexwidget.h b/src/editor/latexwidget.h
+index 0424e43..e3156b0 100644
+--- a/src/editor/latexwidget.h
b/src/editor/latexwidget.h
+@@ -16,6 +16,7 @@
+ #include "ui_latexwidget.h"
+
+ #include
++#include
+ #include
+
+ class QDataWidgetMapper;
+diff --git a/src/practice/multiplechoicemodewidget.cpp b/src/practice/multiplechoicemodewidget.cpp
+index a4eff53..67bd6b5 100644
+--- a/src/practice/multiplechoicemodewidget.cpp
b/src/practice/multiplechoicemodewidget.cpp
+@@ -18,6 +18,7 @@
+
+ #include "ui_practice_widget_multiplechoice.h"
+
++#include
+ #include
+ #include
+ #include
+diff --git a/src/statistics/statisticsmainwindow.cpp b/src/statistics/statisticsmainwindow.cpp
+index 834091c..fe59460 100644
+--- a/src/statistics/statisticsmainwindow.cpp
b/src/statistics/statisticsmainwindow.cpp
+@@ -16,6 +16,7 @@
+
+ #include "statisticsmainwindow.h"
+
++#include
+ #include
+
+ #include
+--
+cgit v0.11.2
+
diff -Nru parley-17.08.3/debian/patches/series parley-17.08.3/debian/patches/series
--- parley-17.08.3/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ parley-17.08.3/debian/patches/series 2018-12-01 00:38:28.0 +0100
@@ -0,0 +1 @@
+qt_5.11.patch
signature.asc
Description: Digital Signature
Processed: parley: diff for NMU version 4:17.08.3-1.1
Processing control commands:
> tags 906977 + pending
Bug #906977 [src:parley] parley: FTBFS in buster/sid ('QItemSelection' does not
name a type)
Added tag(s) pending.
--
906977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing of parley_17.08.3-1.1_sourceonly.changes
parley_17.08.3-1.1_sourceonly.changes uploaded successfully to localhost along with the files: parley_17.08.3-1.1.dsc parley_17.08.3-1.1.debian.tar.xz parley_17.08.3-1.1_sourceonly.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
kamoso is marked for autoremoval from testing
kamoso 18.04.0-3 is marked for autoremoval from testing on 2018-12-22 It is affected by these RC bugs: 914441: kamoso: no user interface is shown: qrc:/qml/Main.qml:7 module "org.kde.kirigami" is not installed
