[frameworks-baloo] [Bug 433204] baloo_file SEGV
https://bugs.kde.org/show_bug.cgi?id=433204 Wouter Haffmans changed: What|Removed |Added CC||wou...@simply-life.net --- Comment #37 from Wouter Haffmans --- I'm getting the same issue still on ArchLinux (baloo 5.99.0-1) with an infinite loop at WriteTransaction::removeRecursively. Running "gdb /usr/lib/baloo_file", the crash seems to happen when the stack is full of identical frames: #16 0x77e0bfc5 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function const&) (this=0x7fbfdc004df0, parentId=36028801313933346, shouldDelete=...) at /usr/src/debug/baloo-5.99.0/src/engine/writetransaction.cpp:167 #17 0x77e0bfc5 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function const&) (this=0x7fbfdc004df0, parentId=36028801313933346, shouldDelete=...) at /usr/src/debug/baloo-5.99.0/src/engine/writetransaction.cpp:167 #18 0x77e0bfc5 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function const&) (this=0x7fbfdc004df0, parentId=36028801313933346, shouldDelete=...) at /usr/src/debug/baloo-5.99.0/src/engine/writetransaction.cpp:167 It looks like this entry in particular (parentId=36028801313933346) has a child with the same id. Gdb confirms this is the first entry in the list: (gdb) frame 1071 #1071 0x77e0bfc5 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function const&) (this=0x7fbfdc004df0, parentId=36028801313933346, shouldDelete=...) at /usr/src/debug/baloo-5.99.0/src/engine/writetransaction.cpp:167 (gdb) print parentId $1 = 36028801313933346 (gdb) print reinterpret_cast((reinterpret_cast(children.d)+children.d->offset))[0] $2 = 36028801313933346 Looks to me like a parent that has itself as a child (from "docUrlDb.getChildren(parentId)") causes the infinite recursion, resulting in a stack overflow (i.e. segfault). Software/OS versions: Operating System: Arch Linux KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.6-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 420090] Project Environment Profiles ignored
https://bugs.kde.org/show_bug.cgi?id=420090 Wouter Haffmans changed: What|Removed |Added CC||wou...@simply-life.net --- Comment #1 from Wouter Haffmans --- I think this is a dupe of #403769 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403769] Only the default environment profle is being used
https://bugs.kde.org/show_bug.cgi?id=403769 Wouter Haffmans changed: What|Removed |Added CC||wou...@simply-life.net --- Comment #1 from Wouter Haffmans --- Created attachment 136075 --> https://bugs.kde.org/attachment.cgi?id=136075&action=edit Minimal CMake example This bug is still present in KDevelop 5.6.2. I've attached a minimalist CMakeLists.txt file that shows the behavior. Building the project (the buildenv target) simply prints the environment variables. The output allows you to easily observe that the selected environment profile is not used. This bug only applies when using Ninja to run the build. Using Make it works as expected. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 398617] Project/Configure Selection does not take qmake extra arguments into account
https://bugs.kde.org/show_bug.cgi?id=398617 Wouter Haffmans changed: What|Removed |Added CC||wou...@simply-life.net --- Comment #4 from Wouter Haffmans --- This bug is still present in KDevelop 5.6.1. It looks like both the QMake Builder and QMake Manager plugins have a QMakeJob class in the code, but they differ quite a bit. The latter plugin adds the "Run QMake" context menu entry, which works correctly (see QMakeProjectManager::slotRunQMake where it adds the arguments to the job). It looks like part of that code should be added/moved to QMakeBuilder::configure to fix this. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 411399] New: KDEConnect slow when bluetooth service is not started
https://bugs.kde.org/show_bug.cgi?id=411399
Bug ID: 411399
Summary: KDEConnect slow when bluetooth service is not started
Product: kdeconnect
Version: 1.3.5
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: plasmoid
Assignee: albertv...@gmail.com
Reporter: wou...@simply-life.net
Target Milestone: ---
SUMMARY
On Arch Linux with Bluez installed but no Bluetooth device plugged in, the KDE
Connect applet seems to slow down the starting up of Plasma.
After plugging in a (USB) Bluetooth adapter, Plasma starts up quickly again.
STEPS TO REPRODUCE
1. Install Bluez, bluedevil, Plasma and KDE Connect
2. Unplug any Bluetooth adapters (such that /sys/class/bluetooth no longer
exists), or modify the dbus-org.bluez.service (bluetooth.service) file to have
a startup condition that's always false.
3. Login to Plasma
OBSERVED RESULT
Plasma takes a long time to start up. Relevant log lines from journalctl:
aug 28 21:36:15 mortimer dbus-daemon[941]: [system] Activating via systemd:
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.1266'
(uid=1000 pid=8188 comm="/usr/lib/kdeconnectd ")
aug 28 21:36:15 mortimer systemd[1]: Condition check resulted in Bluetooth
service being skipped.
-- Subject: A start job for unit bluetooth.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit bluetooth.service has finished successfully.
--
-- The job identifier is 2878.
aug 28 21:36:15 mortimer klauncher[8427]: Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
aug 28 21:36:17 mortimer kdeinit5[8430]: Installing the delayed initialization
callback.
aug 28 21:36:17 mortimer kdeinit5[8430]: org.kde.bluez: Cannot open /dev/rfkill
for reading!
aug 28 21:36:17 mortimer kdeinit5[8430]: bluedevil: Created
aug 28 21:36:17 mortimer kdeinit5[8430]: Delayed initialization.
aug 28 21:36:17 mortimer kdeinit5[8430]: Reloading the khotkeys configuration
aug 28 21:36:17 mortimer kdeinit5[8430]: Version 2 File!
aug 28 21:36:17 mortimer kdeinit5[8430]: true
aug 28 21:36:17 mortimer kdeinit5[8430]: Imported file
"/usr/share/khotkeys/defaults.khotkeys"
aug 28 21:36:17 mortimer kdeinit5[8430]: Imported file
"/usr/share/khotkeys/konqueror_gestures_kde321.khotkeys"
aug 28 21:36:17 mortimer kdeinit5[8430]: Imported file
"/usr/share/khotkeys/konsole.khotkeys"
aug 28 21:36:17 mortimer kdeinit5[8430]: Imported file
"/usr/share/khotkeys/kde32b1.khotkeys"
aug 28 21:36:17 mortimer kdeinit5[8430]: bluedevil: Bluetooth operational
changed false
aug 28 21:36:17 mortimer kdeinit5[8430]: bluedevil: ObexManager operational
changed true
aug 28 21:36:17 mortimer kdeinit5[8430]: bluedevil: ObexAgent registered
aug 28 21:36:40 mortimer dbus-daemon[941]: [system] Failed to activate service
'org.bluez': timed out (service_start_timeout=25000ms)
aug 28 21:36:40 mortimer pulseaudio[8974]: E: [pulseaudio] bluez5-util.c:
GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
aug 28 21:36:40 mortimer kdeconnectd[8188]: Cannot find a running Bluez. Please
check the Bluez installation.
aug 28 21:36:40 mortimer kdeinit5[8430]: org.kde.bluez: PendingCall Error:
"Failed to activate service 'org.bluez': timed out
(service_start_timeout=25000ms)"
aug 28 21:36:40 mortimer kdeconnectd[8188]: kdeconnect.core: onStart
aug 28 21:36:40 mortimer dbus-daemon[941]: [system] Activating via systemd:
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.1266'
(uid=1000 pid=8188 comm="/usr/lib/kdeconnectd ")
aug 28 21:36:40 mortimer systemd[1]: Condition check resulted in Bluetooth
service being skipped.
-- Subject: A start job for unit bluetooth.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit bluetooth.service has finished successfully.
--
-- The job identifier is 2987.
aug 28 21:36:42 mortimer plasmashell[8478]: error activating kdeconnectd:
QDBusError("", "")
aug 28 21:37:05 mortimer dbus-daemon[941]: [system] Failed to activate service
'org.bluez': timed out (service_start_timeout=25000ms)
aug 28 21:37:05 mortimer dbus-daemon[1725]: [session uid=1000 pid=1725]
Successfully activated service 'org.kde.kdeconnect'
aug 28 21:37:05 mortimer kdeconnectd[8188]: kdeconnect.core: No local bluetooth
adapter found
aug 28 21:37:05 mortimer kdeconnectd[8188]: kdeconnect.core: KdeConnect daemon
started
aug 28 21:37:05 mortimer plasmashell[8478]: kdeconnect.interfaces: dbus
interface not valid
aug 28 21:37:05 mortimer plasmashell[8478]: kdeconnect.interfaces: dbus
interface not valid
aug 28 21:37:05 mortimer kdeconnectd[8188]: kdeconnect.
[kdevelop] [Bug 398907] New: kdevelop! script can't load libraries (Ubuntu 16.04; AppImage; zsh)
https://bugs.kde.org/show_bug.cgi?id=398907
Bug ID: 398907
Summary: kdevelop! script can't load libraries (Ubuntu 16.04;
AppImage; zsh)
Product: kdevelop
Version: 5.2.4
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: wou...@simply-life.net
Target Milestone: ---
Using KDevelop 5.2.4 from the AppImage on Ubuntu 16.04 (running Plasma 5.8.9
from kubuntu-backports), trying to run the 'kdevelop!' script from within the
konsole plugin shows:
/tmp/.mount_cLADEQ/usr/bin/kdevelop: error while loading shared libraries:
libKDevPlatformShell.so.52: cannot open shared object file: No such file or
directory
Error: Failed retrieving a pid.
It seems that when running from the AppImage, the environment for the Konsole
plugin isn't set up correctly. Expected behavior is that the script would at
least run without complaining about missing libraries.
The work-around I currently use is to use the APPDIR environment variable to
determine if the script is running from an AppImage environment, then set up
the environment correctly at the start of the script:
if [ ! -z $APPDIR ]; then
export KDEV_BASEDIR=${APPDIR}/usr/bin
export QML2_IMPORT_PATH=$APPDIR/usr/lib/qml:$QML2_IMPORT_PATH
export LD_LIBRARY_PATH=$APPDIR/usr/lib/:$LD_LIBRARY_PATH
export QT_PLUGIN_PATH=$APPDIR/usr/lib/qt5/plugins/
export XDG_DATA_DIRS=$APPDIR/usr/share/:$XDG_DATA_DIRS
export PATH=$APPDIR/usr/bin:$PATH
export KDE_FORK_SLAVES=1
export PYTHONHOME=$APPDIR/usr/
else
export KDEV_BASEDIR=$(dirname $0)
fi
I also change KDEV_BASEDIR because in my case I've put a copy of the script in
a directory which is in my PATH (see also bug #393091) - this might not
actually be necessary if this change is integrated in the AppImage. This
work-around currently allows me to control the session from the terminal as
usual.
Note: I haven't tried the work-around version of this script on a regular
package installation, because it's simply not necessary in that case.
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723 --- Comment #19 from Wouter Haffmans --- I haven't seen this crash anymore since applying the fix. As far as I'm concerned I think this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723 --- Comment #17 from Wouter Haffmans --- I still experience this crash with the current (2017-03-21) source build. Digging through the code and the stack trace, it seems the problem is in libksieve's VacationCheckJob::getNextScript() method. This code does a range of mScriptPos check on a list mAvailableScripts (through isLastScript()), but then doesn't return. This causes "mAvailableScripts[mScriptPos]" (line 185 in vacationcheckjob.cpp) to be out of range and triggers the crash. It seems to me that adding a return statement if the last script is reached will solve the crash, but I haven't confirmed that yet. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376319] New: Projects base directory not saved
https://bugs.kde.org/show_bug.cgi?id=376319 Bug ID: 376319 Summary: Projects base directory not saved Product: kdevelop Version: 5.0.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: wou...@simply-life.net Target Milestone: --- The "Projects base directory" setting is not saved correctly. Every time KDevelop is restarted, it resets to $HOME/projects instead of whatever I picked before. To reproduce: - Go to Settings->Configure KDevelop->Projects - Change the "Projects base directory" setting - Quit and restart KDevelop Expected: Setting is remembered and used when creating a new/opening an existing project Actual: Setting is reset after restart. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723 --- Comment #14 from Wouter Haffmans --- I have a similar crash (Arch Linux, see bug 363987 - already marked as dupe). My setup has 4 different Kolab mailboxes and one GMail without Sieve support. Account 1: a "Filters" enabled script, and a disabled "roundcube" script Account 2: one disabled "Filters" script. NOTE: The syntax checker of KMail succeeds, but trying to enable this one from KMail results in an error: "Sieve operation failed. The server responded: script errors:" (no further details) Account 3: an enabled "Filters" script Account 4: an enabled "roundcube" script All scripts were edited through Roundcube. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723 Wouter Haffmans changed: What|Removed |Added CC||wou...@simply-life.net --- Comment #13 from Wouter Haffmans --- *** Bug 363987 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 363987] Kontact crashes on start-up
https://bugs.kde.org/show_bug.cgi?id=363987 Wouter Haffmans changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Wouter Haffmans --- *** This bug has been marked as a duplicate of bug 363723 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 363987] Kontact crashes on start-up
https://bugs.kde.org/show_bug.cgi?id=363987 Wouter Haffmans changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=363723 --- Comment #2 from Wouter Haffmans --- Found possible (likely) duplicate: 363723 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 363987] Kontact crashes on start-up
https://bugs.kde.org/show_bug.cgi?id=363987 --- Comment #1 from Wouter Haffmans --- Similar backtrace of another crash just now: Thread 1 (Thread 0x7f4a22e0a840 (LWP 31842)): [KCrash Handler] #5 0x7f4a203f3d3e in QString::append(QString const&) () from /usr/lib/libQt5Core.so.5 #6 0x7f49943117a3 in ?? () from /usr/lib/libKF5KSieveUi.so.5 #7 0x7f499431184e in ?? () from /usr/lib/libKF5KSieveUi.so.5 #8 0x7f4994311ffc in ?? () from /usr/lib/libKF5KSieveUi.so.5 #9 0x7f4a2056a77c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #10 0x7f499246d06b in KManageSieve::SieveJob::gotScript(KManageSieve::SieveJob*, bool, QString const&, bool) () from /usr/lib/libKF5KManageSieve.so.5 #11 0x7f499246b14d in KManageSieve::SieveJob::Private::handleResponse(KManageSieve::Response const&, QByteArray const&) () from /usr/lib/libKF5KManageSieve.so.5 #12 0x7f4992461d61 in ?? () from /usr/lib/libKF5KManageSieve.so.5 #13 0x7f4a2056b1d9 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #14 0x7f4a214b67bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x7f4a214bb95f in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f4a2053d2e0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #17 0x7f4a2053f25c in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #18 0x7f4a20593323 in ?? () from /usr/lib/libQt5Core.so.5 #19 0x7f4a1816cdd7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #20 0x7f4a1816d040 in ?? () from /usr/lib/libglib-2.0.so.0 #21 0x7f4a1816d0ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #22 0x7f4a2059372f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #23 0x7f4a2053b4ca in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #24 0x7f4a20543a6c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #25 0x0040434f in ?? () #26 0x7f4a1f99e741 in __libc_start_main () from /usr/lib/libc.so.6 #27 0x00404859 in _start () -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 363987] New: Kontact crashes on start-up
https://bugs.kde.org/show_bug.cgi?id=363987 Bug ID: 363987 Summary: Kontact crashes on start-up Product: kontact Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: wou...@simply-life.net Application: kontact (5.2.1) Qt Version: 5.6.0 Frameworks Version: 5.22.0 Operating System: Linux 4.5.4-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Launching Kontact (on Arch Linux, x64, Plasma) Usually it takes several attempts for Kontact to start up correctly, after which there aren't any further crashes. - Custom settings of the application: I have several Kolab agents set up, with Sieve scripts set up by Roundcube (see backtrace; it mentions Sieve in there). The server-side has "Kolab 16" installed on CentOS 7. A possibly related side-effect may be that Sieve scripts sometimes don't load correctly in KMail (i.e. I cannot configure them). The icon for some of the accounts keeps on spinning attempting to load the scripts, so it seems. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdf4942f840 (LWP 31581))] Thread 34 (Thread 0x7fdf2cbe8700 (LWP 31582)): #0 0x7fdf4608168d in poll () from /usr/lib/libc.so.6 #1 0x7fdf3f5e08e0 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fdf3f5e2679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fdf2f167bc9 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fdf4698c1d8 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fdf3efb4474 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fdf4608a69d in clone () from /usr/lib/libc.so.6 Thread 33 (Thread 0x7fdf24255700 (LWP 31583)): #0 0x7ffdbcf72c59 in clock_gettime () #1 0x7fdf46097356 in clock_gettime () from /usr/lib/libc.so.6 #2 0x7fdf46a37d96 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7fdf46bb62f9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/libQt5Core.so.5 #4 0x7fdf46bb68a5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/libQt5Core.so.5 #5 0x7fdf46bb7c3e in ?? () from /usr/lib/libQt5Core.so.5 #6 0x7fdf3e79150d in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #7 0x7fdf3e791efb in ?? () from /usr/lib/libglib-2.0.so.0 #8 0x7fdf3e7920ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #9 0x7fdf46bb874b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #10 0x7fdf46b604ca in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #11 0x7fdf469872f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #12 0x7fdf4525ba65 in ?? () from /usr/lib/libQt5DBus.so.5 #13 0x7fdf4698c1d8 in ?? () from /usr/lib/libQt5Core.so.5 #14 0x7fdf3efb4474 in start_thread () from /usr/lib/libpthread.so.0 #15 0x7fdf4608a69d in clone () from /usr/lib/libc.so.6 Thread 32 (Thread 0x7fdf22e3d700 (LWP 31584)): #0 0x7fdf3efba09f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fdf4392e7db in ?? () from /usr/lib/libQt5WebKit.so.5 #2 0x7fdf4392e819 in ?? () from /usr/lib/libQt5WebKit.so.5 #3 0x7fdf3efb4474 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fdf4608a69d in clone () from /usr/lib/libc.so.6 Thread 31 (Thread 0x7fded9df3700 (LWP 31585)): #0 0x7ffdbcf72c59 in clock_gettime () #1 0x7fdf46097356 in clock_gettime () from /usr/lib/libc.so.6 #2 0x7fdf46a37d96 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7fdf46bb62f9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/libQt5Core.so.5 #4 0x7fdf46bb8018 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fdf3e791a01 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #6 0x7fdf3e791f74 in ?? () from /usr/lib/libglib-2.0.so.0 #7 0x7fdf3e7920ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #8 0x7fdf46bb874b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #9 0x7fdf46b604ca in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #10 0x7fdf469872f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #11 0x7fdf4698c1d8 in ?? () from /usr/lib/libQt5Core.so.5 #12 0x7fdf3efb4474 in start_thread () from /usr/lib/libpthread.so.0 #13 0x7fdf4608a69d in clone () from /usr/lib/libc.so.6 Thread 30 (Thread 0x7fded22be700 (LWP 31586)): #0 0x7fdf3efba09f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fdf4362dd84 in ?? () from /usr/lib/libQt5WebKit.so.5 #2 0x7fdf4395e481 in ?? () from /usr/lib/libQt5WebKit.so.5 #3 0x7fdf3efb4474 in start_thread
