Bug#924956: qt3d-opensource-src: Fractional HiDPI scaling causes serious artifacts in some QT applications
Source: qt3d-opensource-src Severity: important Tags: newcomer Dear Maintainer, QT has had a bug which caused major artifacts in QT applications, for example Kate, Kwrite, Konsole, and probably many others. It only is an issue when non-integer scaling factors for HiDPI are used. At least for me, this makes Kate very difficult to use. The bug was fixed on this page: https://bugreports.qt.io/browse/QTBUG-66036 Comment #6 contains the fix, which is quite small. You may have to click the "X older comments" link to get this comment to appear. It was too late to make it into QT 5.11, sadly, but there is (or was?) talk of cherry-picking the patch into 5.11: https://phabricator.kde.org/T9244 If this patch could make it into Buster's QT, that would be fantastic. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#923653: RE: plasma-discover: mousehover over sort options makes them disappear
On Sat, 16 Mar 2019 19:02:42 + Larus Contract wrote: > Some additional information: deactivating compositor doesn't help. > The options start disapperating on the second item, meaning the first is > selectable and works. > I've added images showing the problem. In the images, there is an update > ongoing, but they do not affect the package nor the bug, it persisted after > the update. Confirmed on my end as well. It is not the first item in the list that triggers this bug, but rather "any" item on the list that is highlighted. This bug is also present on Fedora as well (running Plasma 5.14.5 and KDE Frameworks 5.55). This may be an upstream bug, unsure if it was fixed in Plasma 5.15 or not. signature.asc Description: OpenPGP digital signature
Bug#917107: qtwayland-opensource-src: Check if CMake files for plugins need to be removed
On Sat, Dec 22, 2018 at 03:37:27PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> The correct fix for
> https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1806186
> might be removing/patching cmake file for plugins.
Just for the record, Qt’s mkspecs/features/data/cmake/Qt5BasicConfig.cmake.in
has this line:
file(GLOB pluginTargets
\"${CMAKE_CURRENT_LIST_DIR}/Qt5$${CMAKE_MODULE_NAME}_*Plugin.cmake\")
And it ends up in /usr/lib/*/cmake/Qt5Gui/Qt5GuiConfig.cmake which then has
this line:
file(GLOB pluginTargets "${CMAKE_CURRENT_LIST_DIR}/Qt5Gui_*Plugin.cmake")
So the file Qt5Gui_QWaylandEglPlatformIntegrationPlugin.cmake and similar
files match this glob.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#910494: Parallel bug report at KDE
Please refer to the bug report created at KDE https://bugs.kde.org/show_bug.cgi?id=405601
Processed: Re: Bug#923720: plasma-discover: Plasma-discover segfaults on Stretch
Processing commands for cont...@bugs.debian.org: > reassign 923720 libappstreamqt2 0.10.6-2 Bug #923720 [plasma-discover] plasma-discover: Plasma-discover segfaults on Stretch Bug reassigned from package 'plasma-discover' to 'libappstreamqt2'. No longer marked as found in versions plasma-discover/5.8.5-3. No longer marked as fixed in versions plasma-discover/5.10.5-1 and libappstreamqt2/0.11.3-1. Bug #923720 [libappstreamqt2] plasma-discover: Plasma-discover segfaults on Stretch Marked as found in versions appstream/0.10.6-2. > End of message, stopping processing here. Please contact me if you need assistance. -- 923720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923720: plasma-discover: Plasma-discover segfaults on Stretch
reassign 923720 libappstreamqt2 0.10.6-2
Processed (with 1 error): Re: Bug#923720: plasma-discover: Plasma-discover segfaults on Stretch
Processing control commands: > reassign 923720 libappstreamqt2/0.10.6-2 Unknown command or malformed arguments to command. > affects 923720 plasma-discover Bug #923720 [plasma-discover] plasma-discover: Plasma-discover segfaults on Stretch Added indication that 923720 affects plasma-discover > fixed 923720 libappstreamqt2/0.11.3-1 Bug #923720 [plasma-discover] plasma-discover: Plasma-discover segfaults on Stretch The source libappstreamqt2 and version 0.11.3-1 do not appear to match any binary packages Marked as fixed in versions libappstreamqt2/0.11.3-1. > fixed 923720 plasma-discover/5.10.5-1 Bug #923720 [plasma-discover] plasma-discover: Plasma-discover segfaults on Stretch Marked as fixed in versions plasma-discover/5.10.5-1. > tags 923720 + upstream fixed-upstream patch Bug #923720 [plasma-discover] plasma-discover: Plasma-discover segfaults on Stretch Added tag(s) upstream, patch, and fixed-upstream. -- 923720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923720: plasma-discover: Plasma-discover segfaults on Stretch
Control: reassign 923720 libappstreamqt2/0.10.6-2
Control: affects 923720 plasma-discover
Control: fixed 923720 libappstreamqt2/0.11.3-1
Control: fixed 923720 plasma-discover/5.10.5-1
Control: tags 923720 + upstream fixed-upstream patch
Hello Everyone,
tried to get some more information from the backtrace.
I could not reproduce it but I think in this case method
AppStream::Pool::load got called with strerror being a null
pointer and for some reason the pool could not be loaded,
therefore line 77 was reached, trying to dereference strerror.
(gdb) list AppStream::Pool::load(QString*)
71
72 bool Pool::load(QString* strerror)
73 {
74 g_autoptr(GError) error = nullptr;
75 bool ret = as_pool_load (d->m_pool, NULL, );
76 if (!ret && error) {
77 *strerror = QString::fromUtf8(error->message); <<<
78 }
79 return ret;
80 }
81
This led to upstream fix in package appstream, available since 0.11.3: [1] [2]
Another fix was done in discover before, available since v5.10.5: [3] [4]
Therefore I assume this just affects Stretch.
Kind regards,
Bernhard
[1] https://github.com/ximion/appstream/pull/126
[2]
https://github.com/ximion/appstream/commit/32f1445fd3f348598edd5e24e29ad3644c299639
[3] https://bugs.kde.org/show_bug.cgi?id=382916
[4]
https://cgit.kde.org/discover.git/commit/?id=3a718124d45d60c49bb586e14d348f233178b34b
# Stretch amd64 qemu VM
apt update
apt dist-upgrade
apt install devscripts dpkg-dev systemd-coredump gdb xserver-xorg sddm
plasma-desktop muon libappstreamqt2-dbgsym plasma-discover-dbgsym
libglib2.0-0-dbg
systemctl start sddm
mkdir /tmp/source/appstream/orig -p
cd/tmp/source/appstream/orig
apt source appstream
cd
###
export DISPLAY=:0
# plasma-discover
gdb -q --args plasma-discover
set width 0
set pagination off
directory /tmp/source/appstream/orig/appstream-0.10.6
display/i $pc
break AppStream::Pool::load
y
run
disa 1.1
disa 1.3
disa 1.4
cont
bt
benutzer@debian:~$ gdb -q --args plasma-discover
Reading symbols from plasma-discover...Reading symbols from
/usr/lib/debug/.build-id/8e/af6f71ec2d372a44c646c9eb0311f4bb45dd50.debug...done.
done.
(gdb) set width 0
(gdb) set pagination off
(gdb) directory /tmp/source/appstream/orig/appstream-0.10.6
Source directories searched:
/tmp/source/appstream/orig/appstream-0.10.6:$cdir:$cwd
(gdb) display/i $pc
1: x/i $pc
(gdb) break AppStream::Pool::load
Function "AppStream::Pool::load" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (AppStream::Pool::load) pending.
(gdb) run
Starting program: /usr/bin/plasma-discover
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe66c2700 (LWP 2475)]
[New Thread 0x7fffe5a39700 (LWP 2476)]
[New Thread 0x7fffe5238700 (LWP 2478)]
[New Thread 0x7fffd278d700 (LWP 2479)]
[New Thread 0x7fffd1f8c700 (LWP 2480)]
[New Thread 0x7fffd178b700 (LWP 2481)]
[New Thread 0x7fffd0f8a700 (LWP 2482)]
[New Thread 0x7fffd0789700 (LWP 2483)]
[New Thread 0x7fffcff88700 (LWP 2484)]
[New Thread 0x7fffcf787700 (LWP 2485)]
[New Thread 0x7fffcef86700 (LWP 2486)]
[New Thread 0x7fffce01e700 (LWP 2487)]
[New Thread 0x7fffcd81c700 (LWP 2488)]
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami/GlobalDrawer.qml:213:9:
QML Flickable: Binding loop detected for property "contentWidth"
invalid kns backend! "" because: "Couldn't find knsrc file: comic.knsrc"
Thread 1 "plasma-discover" hit Breakpoint 1, 0x7fffc77e3cd0 in
AppStream::Pool::load()@plt () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so
1: x/i $pc
=> 0x7fffc77e3cd0 <_ZN9AppStream4Pool4loadEv@plt>: jmpq *0x2305ca(%rip)
# 0x7fffc7a142a0
(gdb) disa 1.1
(gdb) disa 1.3
(gdb) disa 1.4
(gdb) cont
Continuing.
Thread 1 "plasma-discover" hit Breakpoint 1, AppStream::Pool::load
(this=this@entry=0x55dcd3c8, strerror=strerror@entry=0x0) at
./qt/pool.cpp:73
73 {
1: x/i $pc
=> 0x7fffc738d020 :push %r12
(gdb) next
75 bool ret = as_pool_load (d->m_pool, NULL, );
1: x/i $pc
=> 0x7fffc738d038 : mov0x10(%rdi),%rax
(gdb)
74 g_autoptr(GError) error = nullptr;
1: x/i $pc
=> 0x7fffc738d03c : movq $0x0,0x10(%rsp)
(gdb)
75 bool ret = as_pool_load (d->m_pool, NULL, );
1: x/i $pc
=> 0x7fffc738d045 : test %rax,%rax
(gdb)
76 if (!ret && error) {
1: x/i $pc
=> 0x7fffc738d065 : jne0x7fffc738d0b8
(gdb) bt
#0 0x7fffc738d065 in AppStream::Pool::load(QString*)
(this=this@entry=0x55dcd3c8, strerror=strerror@entry=0x0) at
./qt/pool.cpp:76
#1 0x7fffc738d147 in AppStream::Pool::load()
(this=this@entry=0x55dcd3c8) at ./qt/pool.cpp:69
#2 0x7fffc77ea7f3 in PackageKitBackend::PackageKitBackend(QObject*)
(this=0x55dcd3b0, parent=) at
Bug#924740: plasma-desktop: plasma activities preview fails with svg wallpapers
The same problem happens when the background is set to a solid colour or slideshow; it looks exactly like with an SVG. I would have expected to see the colour or a preview of the image which is currently set as background (meaning the current item of the slideshow) to be put into the preview. Obviously it's the same with Hunyango or Haenau, but I couldn't test image of the day, as there doesn't seem to be a provider available.
Bug#924799: qtspeech-opensource-src: FTBFS: dh_auto_test: make -j4 check -Ctests/auto QT_HASH_SEED=0 QT_QPA_PLATFORM=minimal returned exit code 2
El lun., 18 mar. 2019 07:33, Lucas Nussbaum escribió: > > AFAIK they don't, but that shouldn't be a requirement to build the > package? Not building, but tests might require them and we might haven't noticed it. Anyways that turned out not to be the issue. Something changed in between but I still can't find the reason. Thanks for the follow up!
Re: KDEPIM 18.08.3 for Buster
Am Freitag, 15. März 2019, 12:39:55 CET schrieb Christian Hilberg: > Hi, > > Am Freitag, 15. März 2019, 12:02:42 CET schrieb Andy G Wood: > > Hello, > > > > I have also been suffering from infrequent kmail crashes in recent weeks. > > It is not related to filtering, nor is it specific to nouveau (I use the > > NVIDIA proprietary display driver). > > I'm seeing the issue with both, nouveau and (legacy 390) nvidia blob. > Currently running Kontact inside a VM instead, let's see what that does. (1) KMail in a Buster VirtualBox VM did not show the issue (2) Using nouveau, it showed that the crash path led through Qt WebEngine, but ended in the nouveau DRI lib, which is a known issue [0], [1]. Got there through the bug I filed on bugs.kde.org [2]. (3) Using NVidia 390xx legacy blob with vblank_mode=0 __GL_SYNC_TO_VBLANK=0 relaxed the situation for me, the error does not seem to occur (at least after a few hours there's no crash yet) (4) disabling vblank did _not_ resolve the issue when using the nouveau driver (5) I've seen reports where building Qt against OpenGL ES instead of GLX resolved the issue (but made e.g. WebGL not working) Just 2 cents. [0] https://bugreports.qt.io/browse/QTBUG-41242 [1] https://bugreports.qt.io/browse/QTBUG-49243 [2] https://bugs.kde.org/show_bug.cgi?id=405491 > > Not currently reproducible ... and yes I need to install debug syms in > > order to provide more than a "me too". The impact may be wider than > > kmail because I have also had one okular crash too. > > Regarding wider impact, the traces I've seen so far point towards > QtWebEngine, so any app integrating this might be affected. > > > Andy. > > > > On Friday, 15 March 2019 09:55:10 GMT Christian Hilberg wrote: > > > Hi there, > > > > > > Am Donnerstag, 7. Februar 2019, 13:20:00 CET schrieb Martin Steigerwald: > > > > Sandro Knauß - 07.02.19, 00:33: > > > > > Hey, > > > > > > > > > > as Debian is already in freeze, the version of KDEPIM that will > > > > > shipped with the next stable is 18.08.3. That was uploaded same days > > > > > ago. There is no time to package 18.12.X sorry for that. > > > > > So please test this version in more depth and report issues. If you > > > > > also manage to point to existing bugfixes like done in #921535 it is > > > > > very likely we can ship a that bugfix also for Buster. > > > > > > > > The other issue I have since 18.08 packages is: > > > > > > > > Debian #921624: kmail: Crash during/after filtering inbox, probably > > > > related to Qt WebEngine integration > > > > https://bugs.debian.org/921624 > > > > > > > > Crash during/after filtering inbox, probably related to Qt WebEngine > > > > integration > > > > https://bugs.kde.org/404052 > > > > > > Filed another one (since 18.08): > > > > > > KMail (in Kontact) crashing upon start or shortly after > > > https://bugs.kde.org/405491 > > > > > > It might be related (or even duplicate) to #404052, > > > only that I do not need to have mails filtered for > > > KMail to crash. Looks like a QtWebEngine thing. > > > > > > Just like Martin, I missed out on debug syms. Got them > > > installed now and trying to get another backtrace. > > > > > > > I can add more backtraces to the upstream bug report. For some reason > > > > DrKonqi shortened the second backtrace I had it generate after fully > > > > upgrading to 18.08.3-1. > > > > > > > > At least this one produces a crash, instead of just stalling… for > > > > whatever reason. > > > > > > > > Thanks, (Bye)², Christian -- signature.asc Description: This is a digitally signed message part.
Re: Akonadi does not start Debian Buster
The issue was resolved after upgrade. I don't know what was the reason but now
everything works as desired
Thanks
On Friday, March 15, 2019 3:14:41 PM EET Dimitris Paraschou wrote:
> Hello everybody,
>
>
> After upgrading to akonadi 18.08.3-4 akonadi does not start anymore
>
>
> The log of akonadictl start
>
>
> org.kde.pim.akonadiserver: Found mysqlcheck: "/usr/bin/mysqlcheck"
> org.kde.pim.akonadiserver: Using mysqld: "/usr/sbin/mysqld-akonadi"
> org.kde.pim.akonadiserver: mysqld reports version 10.3.13 (MariaDB)
> org.kde.pim.akonadiserver: Executing: "/usr/sbin/mysqld-akonadi"
> "--defaults-file=/home/jim/.local/share/akonadi/mysql.conf
> --datadir=/home/jim/.local/share/akonadi/db_data/
> --socket=/tmp/akonadi-jim.5qGLAh/mysql.socket
> --pid-file=/tmp/akonadi-jim.5qGLAh/mysql.pid"
> org.kde.pim.akonadiserver: database server stopped unexpectedly
> org.kde.pim.akonadiserver: Database process exited unexpectedly during
> initial connection!
> org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld-akonadi"
> org.kde.pim.akonadiserver: arguments:
> ("--defaults-file=/home/jim/.local/share/akonadi/mysql.conf",
> "--datadir=/home/jim/.local/share/akonadi/db_data/",
> "--socket=/tmp/akonadi-jim.5qGLAh/mysql.socket",
> "--pid-file=/tmp/akonadi-jim.5qGLAh/mysql.pid")
> org.kde.pim.akonadiserver: stdout: ""
> org.kde.pim.akonadiserver: stderr: "Could not open required defaults
> file: /home/jim/.local/share/akonadi/mysql.conf\nFatal error in defaults
> handling. Program aborted\n"
> org.kde.pim.akonadiserver: exit code: 1
> org.kde.pim.akonadiserver: process error: "Unknown error"
> org.kde.pim.akonadiserver: terminating connection threads
> org.kde.pim.akonadiserver: terminating service threads
> org.kde.pim.akonadiserver: stopping db process
> /usr/bin/mysqladmin: connect to server at 'localhost' failed
> error: 'Can't connect to local MySQL server through socket
> '/tmp/akonadi-jim.5qGLAh/mysql.socket' (2)'
> Check that mysqld is running and that the socket:
> '/tmp/akonadi-jim.5qGLAh/mysql.socket' exists!
> org.kde.pim.akonadiserver: Failed to remove runtime connection config file
> org.kde.pim.akonadiserver: Shutting down AkonadiServer...
> org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally..
>
>
>
> Thank yoy
>
> Dimitris
Bug#924799: qtspeech-opensource-src: FTBFS: dh_auto_test: make -j4 check -Ctests/auto QT_HASH_SEED=0 QT_QPA_PLATFORM=minimal returned exit code 2
Hi, On 17/03/19 at 18:06 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > El domingo, 17 de marzo de 2019 17:54:39 -03 Lisandro Damián Nicanor Pérez > Meyer escribió: > > Hi Lucas! > > > > El domingo, 17 de marzo de 2019 15:20:23 -03 Lucas Nussbaum escribió: > > > Source: qtspeech-opensource-src > > > Version: 5.11.3-2 > > > Severity: serious > > > Tags: buster sid > > > User: debian...@lists.debian.org > > > Usertags: qa-ftbfs-20190315 qa-ftbfs > > > Justification: FTBFS in buster on amd64 > > > > > > Hi, > > > > > > During a rebuild of all packages in buster (in a buster chroot, not a > > > sid chroot), your package failed to build on amd64. > > > > [snip] > > > > This: > > > > "Failed to start audio output (error 1)" BFAIL : > > And then: > > > > FAIL! : tst_QTextToSpeech::volume() 'tts.volume() > 0.65' returned > > > > FALSE. > > > > Makes me think if the test is failing due to no audio setup in your VMs. > > Maybe we have hit an interesting bug which was never caught on the buildds? > > Should a buildd have audio setup? > > The problem seems to be different, as I can reproduce it on a porterbox > (except barriere also has no audio). > > Non the less I'm still interested in knowing if your VMs provide an audio > setup. AFAIK they don't, but that shouldn't be a requirement to build the package? Lucas signature.asc Description: PGP signature
qtscript-opensource-src_5.11.3+dfsg-3_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Mar 2019 11:22:13 +0300 Source: qtscript-opensource-src Architecture: source Version: 5.11.3+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Closes: 924846 Changes: qtscript-opensource-src (5.11.3+dfsg-3) unstable; urgency=medium . * Add upstream patch to fix build with GCC 8.3 (closes: #924846). Checksums-Sha1: 161d965af6c83f0c55f9f463aabec88a5e197bfb 2784 qtscript-opensource-src_5.11.3+dfsg-3.dsc 63dee4adf71c13a8d8b387ea0d27616dcd4304be 17596 qtscript-opensource-src_5.11.3+dfsg-3.debian.tar.xz 5d2e8623d62b51357fb715cf937c9613bf4f179f 11574 qtscript-opensource-src_5.11.3+dfsg-3_source.buildinfo Checksums-Sha256: 08179b68de62bc796387a09b3fa5743627ddfb5aa4f17663777a674548114857 2784 qtscript-opensource-src_5.11.3+dfsg-3.dsc 655921b98c9fd8cb82070227b7bc60061795344500baaa4cf267b7eb32c052b4 17596 qtscript-opensource-src_5.11.3+dfsg-3.debian.tar.xz e855587e10aeb8deefdd6ee6157de41a036fc7d394698fdaef8727d052814bb6 11574 qtscript-opensource-src_5.11.3+dfsg-3_source.buildinfo Files: 86859251f7a283284862cceaf86dbb95 2784 libs optional qtscript-opensource-src_5.11.3+dfsg-3.dsc e30400df8f7515807ee4df87b50c3a9f 17596 libs optional qtscript-opensource-src_5.11.3+dfsg-3.debian.tar.xz 1f66bf04ab8dcd2f8bd463d1e36dcc4a 11574 libs optional qtscript-opensource-src_5.11.3+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE8kKZ/xu8kBi5BqTLYCaTbS8ciuAFAlyPVi4THG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBgJpNtLxyK4AtpEACosphUb5kaDbC4CIUwNajX5JXjaFR4 hOfntXaA3HScw6hsQJDaKgHJLu7p3C5Y0ozTUsLEhHcD74kZGH1z+BoA5IsLf8H8 Gmxzsf6XO5JKF6B/cdSHX5SVRz1GJkG8JDwRPbDMHuizC6Z8yh5FYxyQ+bckIApJ HqNIGen82Me+qiKV9+gRQ3Po+ehlPd6X7RKfcD8gH/q/HRHYo4uGHrb5qH7R83xR qCl/cskuyE9uNQ8xjVn8k2Ayuri+dDPozWiNB7muFfHwdUiCkNIqdYT5tiDdAdsU uVPMKNTzRnu1RKWkceCMcM+95ALkKqn2FoclW4u9kvuUAlndwiUok06b8GHv5g+Q DBxr23kiAnvKciS2PxEdrsxgkT3ak9zITHKhc5KcBfkYDpZm+Mw+dPiMNiSAdN7A kEnLU7qBtoHGS1JvxXMtny0bDWMYNcnmxkayPKyjfiO98r7RickQCyLbqoSbEBps pGffPhCok/SDNahg/5WMuSwMNjhlOlNNXHmT5tauvMTk7ai4/sMnoOYodn/oHtbZ 9oCx1rkoIEybRVUv3UpAsyI+PtSAjaCaQOO/vBymVCcvPi1gBjCDuBb05u1O4Bqu JftB/Gya1pa7ZdfX4IWOtJg3S2jNXH+ZSUoJne5bX8XTnPKm/PWQssS0YmsRhUOm CLwDN3nRzZooAA== =Ukr5 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#924846: marked as done (qtscript-opensource-src: FTBFS: ../3rdparty/javascriptcore/JavaScriptCore/jit/JITStubs.cpp:483:5: error: expected '(' before 'volatile')
Your message dated Mon, 18 Mar 2019 08:54:13 +
with message-id
and subject line Bug#924846: fixed in qtscript-opensource-src 5.11.3+dfsg-3
has caused the Debian Bug report #924846,
regarding qtscript-opensource-src: FTBFS:
../3rdparty/javascriptcore/JavaScriptCore/jit/JITStubs.cpp:483:5: error:
expected '(' before 'volatile'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
924846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtscript-opensource-src
Version: 5.11.3+dfsg-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> g++ -c -include .pch/Qt5Script -g -O2 -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing
> -Wall -Wreturn-type -Wcast-align -Wchar-subscripts -Wformat-security
> -Wreturn-type -Wno-unused-parameter -Wno-sign-compare -Wno-switch
> -Wno-switch-enum -Wundef -Wmissing-noreturn -Winit-self -fno-stack-protector
> -g -O2 -fdebug-prefix-map=/<>/qtscript-opensource-src-5.11.3+dfsg=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++1y
> -fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions -D_REENTRANT
> -fPIC -DQT_NO_FOREACH -DJSC=QTJSC -Djscyyparse=qtjscyyparse
> -Djscyylex=qtjscyylex -Djscyyerror=qtjscyyerror -DWTF=QTWTF
> -DQT_NO_USING_NAMESPACE -DQLALR_NO_QSCRIPTGRAMMAR_DEBUG_INFO
> -DBUILDING_QT__=1 -DWTF_USE_ACCELERATED_COMPOSITING -DNDEBUG -DLOG_DISABLED=1
> -DBUILDING_QT__ -DBUILDING_JavaScriptCore -DBUILDING_WTF
> -DWTF_USE_JAVASCRIPTCORE_BINDINGS=1 -DWTF_CHANGES=1 -DJS_NO_EXPORT
> -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_BUILD_SCRIPT_LIB
> -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS
> -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS
> -DQT_DISABLE_DEPRECATED_BEFORE=0x05 -DQT_NO_EXCEPTIONS
> -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_CORE_LIB -I.
> -I../3rdparty/javascriptcore/JavaScriptCore -I../3rdparty/javascriptcore
> -I../3rdparty/javascriptcore/JavaScriptCore/assembler
> -I../3rdparty/javascriptcore/JavaScriptCore/bytecode
> -I../3rdparty/javascriptcore/JavaScriptCore/bytecompiler
> -I../3rdparty/javascriptcore/JavaScriptCore/debugger
> -I../3rdparty/javascriptcore/JavaScriptCore/interpreter
> -I../3rdparty/javascriptcore/JavaScriptCore/jit
> -I../3rdparty/javascriptcore/JavaScriptCore/parser
> -I../3rdparty/javascriptcore/JavaScriptCore/pcre
> -I../3rdparty/javascriptcore/JavaScriptCore/profiler
> -I../3rdparty/javascriptcore/JavaScriptCore/runtime
> -I../3rdparty/javascriptcore/JavaScriptCore/wrec
> -I../3rdparty/javascriptcore/JavaScriptCore/wtf
> -I../3rdparty/javascriptcore/JavaScriptCore/wtf/symbian
> -I../3rdparty/javascriptcore/JavaScriptCore/wtf/unicode
> -I../3rdparty/javascriptcore/JavaScriptCore/yarr
> -I../3rdparty/javascriptcore/JavaScriptCore/API
> -I../3rdparty/javascriptcore/JavaScriptCore/ForwardingHeaders
> -I../3rdparty/javascriptcore/JavaScriptCore/generated
> -I/<>/qtscript-opensource-src-5.11.3+dfsg/src/3rdparty/javascriptcore/WebKit/qt/Api
> -I../3rdparty/javascriptcore/JavaScriptCore/pcre
> -I/<>/qtscript-opensource-src-5.11.3+dfsg/src/3rdparty/javascriptcore/JavaScriptCore/tmp
> -I. -Iparser -I../../include -I../../include/QtScript
> -I../../include/QtScript/5.11.3 -I../../include/QtScript/5.11.3/QtScript
> -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore/5.11.3 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore/5.11.3/QtCore -isystem
> /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o obj/release/JITStubs.o
> ../3rdparty/javascriptcore/JavaScriptCore/jit/JITStubs.cpp
> In file included from
> ../3rdparty/javascriptcore/JavaScriptCore/runtime/ArgList.h:28,
> from
> ../3rdparty/javascriptcore/JavaScriptCore/runtime/JSObject.h:26,
> from
> ../3rdparty/javascriptcore/JavaScriptCore/runtime/InternalFunction.h:27,
> from
> ../3rdparty/javascriptcore/JavaScriptCore/runtime/JSFunction.h:27,
> from
> ../3rdparty/javascriptcore/JavaScriptCore/runtime/Executable.h:29,
> from
Processing of qtscript-opensource-src_5.11.3+dfsg-3_source.changes
qtscript-opensource-src_5.11.3+dfsg-3_source.changes uploaded successfully to localhost along with the files: qtscript-opensource-src_5.11.3+dfsg-3.dsc qtscript-opensource-src_5.11.3+dfsg-3.debian.tar.xz qtscript-opensource-src_5.11.3+dfsg-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed: Bug #924846 in qtscript-opensource-src marked as pending
Processing control commands:
> tag -1 pending
Bug #924846 [src:qtscript-opensource-src] qtscript-opensource-src: FTBFS:
../3rdparty/javascriptcore/JavaScriptCore/jit/JITStubs.cpp:483:5: error:
expected '(' before 'volatile'
Added tag(s) pending.
--
924846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
