kio-gdrive_1.2.2-1_amd64.changes is NEW

[Debian FTP Masters]

binary:kio-gdrive is NEW.
binary:kio-gdrive is NEW.
source:kio-gdrive is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

Processing of kio-gdrive_1.2.2-1_amd64.changes

[Debian FTP Masters]

kio-gdrive_1.2.2-1_amd64.changes uploaded successfully to localhost
along with the files:
  kio-gdrive_1.2.2-1.dsc
  kio-gdrive_1.2.2.orig.tar.xz
  kio-gdrive_1.2.2-1.debian.tar.xz
  kio-gdrive-dbgsym_1.2.2-1_amd64.deb
  kio-gdrive_1.2.2-1_amd64.buildinfo
  kio-gdrive_1.2.2-1_amd64.deb

Greetings,

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

Re: Qt 5.10.1 transition just started

[Lisandro Damián Nicanor Pérez Meyer]

On 7 April 2018 at 21:07, Lisandro Damián Nicanor Pérez Meyer
 wrote:
> Beware when you upgrade! :-)

Update: all binNMUs have been scheduled. If everything goes well
tomorrow a normal update should just work.


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

Re: Qt 5.10.1 transition just started

[Diederik de Haas]

On zondag 8 april 2018 02:07:45 CEST Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Beware when you upgrade! 

This is a reminder that people should not use 'apt/aptitude full-upgrade' or 
'apt-get dist-upgrade'. You don't need it in 99.9% of the cases.
The 'apt upgrade' and 'aptitude safe-upgrade' commands contain sanity checks 
which prevent you from breaking packages (dependencies).

If you do 'aptitude safe-upgrade' and it then says 'and 83 not upgraded', that 
is fine. Usually it's 0 or equal to the number of packages I've put on hold 
myself, but especially during Qt transitions it tend to get (this) high.

The right response is to wait.

It can take a few days, but it'll sort itself out over time.
If I think it's taking too long (usually a week, but I give Qt transitions a 
bit more time), I do 'aptitude full-upgrade -s'. The '-s' stands for simulate 
and it will tell you what it will do without actually doing it (you can do 
this as normal user too).
It will then tell you which packages will break with a full-upgrade and why.

In most cases you can then conclude that apt/aptitude was indeed smart and you 
should just wait a bit more.

There is another case and that is when it needs to remove a package which is 
marked as *manually* installed. With 'aptitude safe-upgrade' it has no problem 
removing packages marked as automatically installed (as dependency from 
another package). But it will not touch packages marked as manually installed 
with the logic "Apparently you have your reasons and I'll respect that".

It could be that a package is marked as manually installed, but being marked 
as automatically installed would be more appropriate. Library packages in most 
cases should be marked as automatically installed for example.
You can change the state with 'aptitude markauto ' or 'aptitude 
unmarkauto ' and thereby improve the state of your package manager.

With 'aptitude search '~i!?automatic' or '~i!~M' (they do exactly the same) 
you'll get a list of installed packages which are marked as manually (=not 
automatic) installed.
See 'Search term reference' on https://aptitude.alioth.debian.org/doc/en/
ch02s04s05.html or in your preferred aptitude-doc package for all kinds of 
search terms you can use to tailor your search result.
You often can just place those next to each other ('~i' + '!~M' above) but if 
you're not getting results you expected, try combining them with '?
narrow(term1, term2)' like this:
aptitude search '?narrow(~i!~M~slibs,~n^lib)'

HTH,
  Diederik

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

Processed: tagging 874959

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 874959 + pending
Bug #874959 [src:kmouth] [kmouth] Future Qt4 removal from Buster
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
874959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: New QT Version - so again KDE problems

[Diederik de Haas]

On maandag 9 april 2018 12:59:27 CEST Wolfgang Schindler wrote:
> So if you now use discover or an 'apt full-upgrade'

I will give you one thing: discover is a dangerous package in Sid as it seems 
to miss the sanity logic that are available in apt or aptitude.
I *really* wish plasma-discover was at most a Suggest to plasma-desktop. It's 
annoying that I have to explicitly remove it after installing KDE.
I've brought this up before and got the response that discover is meant for 
stable (*). Sorry, but (imo) if your package is unfit for Sid, then it's unfit 
for Testing and thus should be unfit for Stable.

For the rest, I completely agree with what Stuart wrote.
I've written multiple times on the debian-kde ML that people should stop using 
full or dist-upgrade as you don't need in 99% of cases. The normal 
(safe-)upgrade is really all you need. I consider(ed) it condescending to post 
that to this ML.
If you'd done 'aptitude full-upgrade' it would've explicitly told you each and 
every package that would break and why. It then essentially asks "Do you want 
to break your system?" to which you can respond 'Y', but don't be surprised if 
it does exactly what you asked it to do ...

/me goes to write to write to debian-kde to say that again

(*) Since that response I uninstalled discover immediately and remove it 
immediately after installing KDE. It may have actually improved since, but 
I'll never know as I found that response unacceptable and 1000x more so as it 
is a package manager, potentially ruining your system. Which was exactly what 
it had done.

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

Bug#895303: libkf5pimcommon: autopkgtest fails with new release while succeeded in the past

[Paul Gevers]

Source: libkf5pimcommon
Version: 4:17.12.3-1
Severity: normal
User: ci-t...@tracker.debian.org
Usertags: regression

With the upload of version 17.12.3-1 of libkf5pimcommon, the
autopkgtest¹ started to fail.

Among others:

objdump: /usr/lib/x86_64-linux-gnu/libc++.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libc.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libm.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libpthread.so: File format not recognized
cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++
but not for C
dh_acc: abi-compliance-checker -q -l libkf5pimcommon-dev -v1 4:17.12.3-1
-dump debian/libkf5pimcommon-dev.acc -dump-path
debian/libkf5pimcommon-dev/usr/lib/x86_64-linux-gnu/dh-acc/libkf5pimcommon-dev_4:17.12.3-1.abi.tar.gz
returned exit code 5

Paul

¹ https://ci.debian.net/packages/libk/libkf5pimcommon/unstable/amd64/



signature.asc
Description: OpenPGP digital signature

Re: Request for cherry-picking konsole: Support for ECMA-48 REP

[Miguel A. Vallejo]

Frank Mehnert  wrote:

>>> Would it be possible to cherry-pick that change for the current konsole
>>> package in Sid? IMHO that would make sense as it fixes a bug which is now
>>> triggered with the ncurses update from 20170729.

That would be nice. gpsmon and wavemon are also affected.

Request for cherry-picking konsole: Support for ECMA-48 REP

[Frank Mehnert]

Dear Debian KDE maintainers,

since a few months ncurses screen output is kind of scrambled under certain 
conditions, for example when configuring the Linux kernel with 'make 
menuconfig'. The reason is missing support for ECMA-48 REP in konsole. See

  https://phabricator.kde.org/D10064

and corresponding

  commit b8a2f0cfd0d0f894687953c3f50f2fb163e8690d

in konsole.

Would it be possible to cherry-pick that change for the current konsole 
package in Sid? IMHO that would make sense as it fixes a bug which is now 
triggered with the ncurses update from 20170729.

Thanks for your great work!

Frank

Re: New QT Version - so again KDE problems

[Stuart Prescott]

Hi Wolfgang,

Wolfgang Schindler wrote:

> I reported this some time before (1 or 2  month), now the same happens
> again.
> 
> This is boring.
> 
> Thank you, may be now for last time, as i will change all my systems to an
> other DE. I have no time for again and again working on the same really
> dump mistakes.
> If these things from time to time happen on rather unused packages this is
> bad luck, but libkf5xmlgui5 is a central piece of software, that kills
> anything if there is a mistake in packaging.

This is precisely what sid is for and why there is a migration to testing 
after a few days once buildds, uploaders have caught up and packages are 
tested together. If you don't want to face installability problems, you 
should use the testing release. You'll cope with packages that are a whole 5 
days older. Further, you shouldn't be using full-upgrade blindly. When you 
do so, you are explicitly permitting apt to remove packages to optimise on 
upgrading over retaining packages; you shouldn't be surprised when it does 
what you ask it to do.

I'll also add that English is a rich language with many words that don't 
involve so much ranting and swearing. Please learn to use some of them and 
show some respect for your audience and for the volunteers who are making 
Debian for you. 

Stuart


-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

New QT Version - so again KDE problems

[Wolfgang Schindler]

Hi,

like with the last updates, there are again problems in Debian sid.

Package libkf5xmlgui5 again depends on libqt5core5a > 5.9.0-beta and (and this 
is what makes an upgrade impossible) on qt-base-abi-5-9-2 (which is 
libqt5core5a, But in fixed version 5.9.2).
So if you now use fucking discover or an 'apt full-upgrade', you are fucked up 
with a system, that is graphically unusable.
I reported this some time before (1 or 2  month), now the same happens again.

This is boring.

Thank you, may be now for last time, as i will change all my systems to an 
other DE. I have no time for again and again working on the same really dump 
mistakes.
If these things from time to time happen on rather unused packages this is bad 
luck, but libkf5xmlgui5 is a central piece of software, that kills anything if 
there is a mistake in packaging.

Bye
Wolf

Bug#895260: kde-cli-tools: Hard dependency on sudo, which weakens system security

[Maximiliano Curia]

Control: reassign -1 src:kdesu
Control: severity -1 wishlist
Control: retitle -1 Please use the su backend (instead of sudo) by default

On Monday, 9 April 2018 01:58:15 CEST Alex Hvostov wrote:
> Package: kde-cli-tools
> Version: 4:5.10.5-2

> kde-cli-tools 4:5.12.4-1 has a hard dependency on kdesu, which
> indirectly depends on sudo, making it impossible to upgrade KDE without
> creating a serious, unnecessary security risk.

We clearly disagree on considering sudo a security concern. At least, not from 
the kde packaging point of view. I'm downgrading the severity value to 
wishlist.

>From the packaging point of view, the kdesu links against libkf5su5, thus the 
hard dependency, that's not a bug in kde-cli-tools. And in turn libkf5su5 uses 
sudo by default [1]. So, I'm reassigning this bug to src:kdesu.

> Frankly, I consider it a bug that sudo is available in Debian at all.
> Others obviously disagree, but that's no reason to tie unrelated
> packages to it like this.

> Please move kdesu into its own package, and make it optional again.
 
The kdesu tool isn't optional, it's even used by kio to handle certain 
desktop files.

> In the mean time, others with my concern can mitigate this risk by
> neutralizing sudo before installing it. To do that, run the following
> command (as root) before installing sudo:
 
> # dpkg-statoverride --add root root 644 /usr/bin/sudo

Or replacing sudo with a locally equivs generated package, or rebuilding 
libkf5su5 without the sudo dependency and defaulting back to su.

Happy hacking,
[1]: https://salsa.debian.org/qt-kde-team/kde/kdesu/blob/master/debian/
rules#L10
-- 
"Brilliant opportunities are cleverly disguised as insolvable problems."
-- Gardener's Philosophy

"The reverse is also true." -- Corollary
 Saludos /\/\ /\ >< `/


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

Processed: Re: Bug#895260: kde-cli-tools: Hard dependency on sudo, which weakens system security

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:kdesu
Bug #895260 [kde-cli-tools] kde-cli-tools: Hard dependency on sudo, which 
weakens system security
Bug reassigned from package 'kde-cli-tools' to 'src:kdesu'.
No longer marked as found in versions kde-cli-tools/4:5.10.5-2.
Ignoring request to alter fixed versions of bug #895260 to the same values 
previously set
> severity -1 wishlist
Bug #895260 [src:kdesu] kde-cli-tools: Hard dependency on sudo, which weakens 
system security
Severity set to 'wishlist' from 'important'
> retitle -1 Please use the su backend (instead of sudo) by default
Bug #895260 [src:kdesu] kde-cli-tools: Hard dependency on sudo, which weakens 
system security
Changed Bug title to 'Please use the su backend (instead of sudo) by default' 
from 'kde-cli-tools: Hard dependency on sudo, which weakens system security'.

-- 
895260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

qbs_1.11.0+dfsg-1_amd64.changes ACCEPTED into unstable, unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 06 Apr 2018 17:36:51 +0300
Source: qbs
Binary: qbs qbs-common libqbscore1.11 libqbsqtprofilesetup1.11 qbs-dev 
qbs-examples qbs-doc qbs-doc-html
Architecture: source amd64 all
Version: 1.11.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Description:
 libqbscore1.11 - Qbs core library
 libqbsqtprofilesetup1.11 - Qbs profile setup library
 qbs- cross-platform build tool
 qbs-common - Qbs static files
 qbs-dev- Qbs development files
 qbs-doc- Qbs documentation
 qbs-doc-html - Qbs HTML documentation
 qbs-examples - examples for Qbs build tool
Changes:
 qbs (1.11.0+dfsg-1) unstable; urgency=medium
 .
   [ Alexander Volkov ]
   * New upstream release.
   * Drop fix_ftbfs_gcc6.diff, applied upstream.
   * Update QBS_LIBEXEC_DESTDIR for static.pro and fix DESTDIR for
 qbs_processlauncher (processlauncher_destdir.diff).
   * Set LD_LIBRARY_PATH for qbsres target so it could use built qbs
 to generate QML type descriptions (qml_type_descriptions.diff).
   * Fix the list of installed headers for qmake build (installed_headers.diff).
   * Update install files for the new release.
   * Rename the library packages according to upstream SONAME change.
   * Update symbols from build logs.
Checksums-Sha1:
 20668539221246cf45f48a7431b317035e496d82 2553 qbs_1.11.0+dfsg-1.dsc
 7e010cccd482dce7e9ecc76758e449171299d043 4276199 qbs_1.11.0+dfsg.orig.tar.gz
 28574cfa19329bb8c18cca7c4b0a84ae880fed30 27060 qbs_1.11.0+dfsg-1.debian.tar.xz
 5336767ef85b459b46677914760bd33fe8912f6a 27283188 
libqbscore1.11-dbgsym_1.11.0+dfsg-1_amd64.deb
 fe6595cac9407593b246b7b179052d344b6fb6e7 966272 
libqbscore1.11_1.11.0+dfsg-1_amd64.deb
 12ce1ef538795c319b305e292cb7faa16715bbd2 856432 
libqbsqtprofilesetup1.11-dbgsym_1.11.0+dfsg-1_amd64.deb
 7c5e300581f0878d98c33aa0d2b618507849c447 113600 
libqbsqtprofilesetup1.11_1.11.0+dfsg-1_amd64.deb
 3bd3c258eda83577a47421a901155fbf86218283 109168 
qbs-common_1.11.0+dfsg-1_all.deb
 a4dd187100d1e1fa9c3f41c3a5e7aa1838450e44 11308984 
qbs-dbgsym_1.11.0+dfsg-1_amd64.deb
 588b601a2ce42e81057553d730db3e65e844304b 24524 qbs-dev_1.11.0+dfsg-1_amd64.deb
 5477cae8e6cc54f5ea149fbb753342e589984698 270284 
qbs-doc-html_1.11.0+dfsg-1_all.deb
 66c39d0f8cc31206f19a1ebd802f6994604cbdb3 572592 qbs-doc_1.11.0+dfsg-1_all.deb
 d004325cc88b9bf5c2e903eadc398e607915f87b 410780 
qbs-examples_1.11.0+dfsg-1_all.deb
 bc63f5293be615358a9b7398cc58909bf2c263fd 14248 
qbs_1.11.0+dfsg-1_amd64.buildinfo
 6d36f6a5af94ce226e58b2965801b3c05954cf78 386168 qbs_1.11.0+dfsg-1_amd64.deb
Checksums-Sha256:
 3cada668f171a8fa777fc795d5446412b73d366881339c4a37fab644e2da8a34 2553 
qbs_1.11.0+dfsg-1.dsc
 0615a7f4206d7873a15280402d7f3e11fb77fdd58cf2382f70b1d65bfb3835f1 4276199 
qbs_1.11.0+dfsg.orig.tar.gz
 4b7cc31c9baafd574a01b1be5396d32f999feefc20651dc7bc6a245718d3aa93 27060 
qbs_1.11.0+dfsg-1.debian.tar.xz
 6cf27d3f38688cb5e65131dab1b0ebcc9ad19add67b33b7ffe6c0af74fcfa510 27283188 
libqbscore1.11-dbgsym_1.11.0+dfsg-1_amd64.deb
 891c93e2fe608bd975e52f0660287db555220638c6fdf1b4c5e70357db1d 966272 
libqbscore1.11_1.11.0+dfsg-1_amd64.deb
 a018a55273374c65f55cead7434c395ea6ee17b860f3f024b7195da13c949626 856432 
libqbsqtprofilesetup1.11-dbgsym_1.11.0+dfsg-1_amd64.deb
 bfe6612947942569982b86c6edb4e11cb26eb4391acb89e074ee6dfd13dc2964 113600 
libqbsqtprofilesetup1.11_1.11.0+dfsg-1_amd64.deb
 6ff7835114cbed85b294b0e581155acf0f9bece6eec7fa03e21ce972e5fae726 109168 
qbs-common_1.11.0+dfsg-1_all.deb
 89a6abcab46fe43b9710f18f9b07566b8f32c3259f655b645e2f01484e21d5d9 11308984 
qbs-dbgsym_1.11.0+dfsg-1_amd64.deb
 c4835fe77493fafa7ab271a6b476b80658c0d153714c9df05e79c8b15490d05d 24524 
qbs-dev_1.11.0+dfsg-1_amd64.deb
 341300161d53ed6a089fe098c6924ee832ce560c1518cdbd3a25b41fb2bbab9f 270284 
qbs-doc-html_1.11.0+dfsg-1_all.deb
 2862b1b396100f1770cad555bd00a9ce41f755d472750ec8b29d0ff688ecccb8 572592 
qbs-doc_1.11.0+dfsg-1_all.deb
 3511cb27f0760f156602da20add9d809518a531c204e0f1cbd94301a56840b66 410780 
qbs-examples_1.11.0+dfsg-1_all.deb
 e3c64c9b65b30692450ac44800bc37026f28c84940869c6b18cd8578b5949fa4 14248 
qbs_1.11.0+dfsg-1_amd64.buildinfo
 54ba886695e716697b7cb9a2e0df0ccbcb4c368c61394c86053b8d204b397d63 386168 
qbs_1.11.0+dfsg-1_amd64.deb
Files:
 ef8ec8b3d905c2214ed552b594a7019c 2553 devel optional qbs_1.11.0+dfsg-1.dsc
 5b57bfa196ff8697cb065c485f91591a 4276199 devel optional 
qbs_1.11.0+dfsg.orig.tar.gz
 e5563562569e54c1db24ecf8e9f51cdb 27060 devel optional 
qbs_1.11.0+dfsg-1.debian.tar.xz
 adb34b2ec10f87254585c7422ae04aba 27283188 debug optional 
libqbscore1.11-dbgsym_1.11.0+dfsg-1_amd64.deb
 b4ada1de8a0395424c740bcb850e2dfe 966272 libs optional 
libqbscore1.11_1.11.0+dfsg-1_amd64.deb
 f200cc11b77a8072855b49c816bf6a72 856432 debug optional 
libqbsqtprofilesetup1.11-dbgsym_1.11.0+dfsg-1_amd64.deb
 061322c06f79e5992673b6efae6c62ab 113600 libs 

Bug#895271: konqueror: crahses while running programms which try to start it

[Friedrich Dominicus]

Package: konqueror
Version: 4:17.08.3-2
Severity: critical
Tags: upstream
Justification: breaks unrelated software

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

trying to run
stack haddock --open lens

I get immediate a crash:

Application: Konqueror (kdeinit5), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0185b09780 (LWP 29858))]

Thread 18 (Thread 0x7f010700 (LWP 29877)):
#0  0x7f0176653273 in pa_mainloop_dispatch () at /usr/lib/x86_64-linux-
gnu/libpulse.so.0
#1  0x7f01766536ce in pa_mainloop_iterate () at /usr/lib/x86_64-linux-
gnu/libpulse.so.0
#2  0x7f0176653750 in pa_mainloop_run () at /usr/lib/x86_64-linux-
gnu/libpulse.so.0
#3  0x7f01766615b9 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f01761fbc78 in  () at /usr/lib/x86_64-linux-
gnu/pulseaudio/libpulsecommon-11.1.so
#5  0x7f018208e5aa in start_thread (arg=0x7f010700) at
pthread_create.c:463
#6  0x7f0183c0fcbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 17 (Thread 0x7f011cff9700 (LWP 29876)):
#0  0x7f018209481a in futex_reltimed_wait_cancelable (private=, reltime=0x7f011cff89d0, expected=0, futex_word=0x7f011cff8b58) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f018209481a in __pthread_cond_wait_common (abstime=0x7f011cff8a70,
mutex=0x7f011cff8b08, cond=0x7f011cff8b30) at pthread_cond_wait.c:533
#2  0x7f018209481a in __pthread_cond_timedwait (cond=0x7f011cff8b30,
mutex=0x7f011cff8b08, abstime=0x7f011cff8a70) at pthread_cond_wait.c:667
#3  0x7f0155318552 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#4  0x7f01552df82e in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#5  0x7f01552ba4bb in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#6  0x7f01552b6d38 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#7  0x7f01552d370b in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#8  0x7f01552eb3e6 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#9  0x7f01552e74fb in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#10 0x7f018208e5aa in start_thread (arg=0x7f011cff9700) at
pthread_create.c:463
#11 0x7f0183c0fcbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7f011d7fa700 (LWP 29875)):
#0  0x7f01820944ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x557ac74c25b8) at ../sysdeps/unix/sysv/linux/futex-
internal.h:88
#1  0x7f01820944ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x557ac74c24f8, cond=0x557ac74c2590) at pthread_cond_wait.c:502
#2  0x7f01820944ec in __pthread_cond_wait (cond=0x557ac74c2590,
mutex=0x557ac74c24f8) at pthread_cond_wait.c:655
#3  0x7f0155a6f8b0 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#4  0x7f01552eae21 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#5  0x7f01552e74fb in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#6  0x7f018208e5aa in start_thread (arg=0x7f011d7fa700) at
pthread_create.c:463
#7  0x7f0183c0fcbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7f011dffb700 (LWP 29874)):
#0  0x7f01820944ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f011dffab38) at ../sysdeps/unix/sysv/linux/futex-
internal.h:88
#1  0x7f01820944ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f011dffaae8, cond=0x7f011dffab10) at pthread_cond_wait.c:502
#2  0x7f01820944ec in __pthread_cond_wait (cond=0x7f011dffab10,
mutex=0x7f011dffaae8) at pthread_cond_wait.c:655
#3  0x7f01552df8a9 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#4  0x7f01552df8d7 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#5  0x7f01552ba46b in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#6  0x7f01552b6d38 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#7  0x7f01552d370b in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#8  0x7f01552eb3e6 in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#9  0x7f01552e74fb in  () at /usr/lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#10 0x7f018208e5aa in start_thread (arg=0x7f011dffb700) at
pthread_create.c:463
#11 0x7f0183c0fcbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7f011e7fc700 (LWP 29873)):
#0  0x7f01820944ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x557ac74b1328) at ../sysdeps/unix/sysv/linux/futex-
internal.h:88
#1  0x7f01820944ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x557ac74b12d8,