[knotes] [Bug 406133] New: knotes 18.12.3 can't start after update
https://bugs.kde.org/show_bug.cgi?id=406133 Bug ID: 406133 Summary: knotes 18.12.3 can't start after update Product: knotes Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tomsk_interf...@vtomske.ru CC: myr...@kde.org Target Milestone: --- SUMMARY $ knotes knotes: symbol lookup error: /usr/lib/libknotesprivate.so.5: undefined symbol: _ZN7Akonadi10Collection21markAttributesChangedEv STEPS TO REPRODUCE 1. Update your Arch linux 2. Start knotes 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.0.5-arch1-1-ARCH / KDE Frameworks 5.56.0 (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: KDE Frameworks 5.56.0 Qt Version: Qt 5.12.2 (built against 5.12.1) ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 406117] New: kmail & akonadi crashes
https://bugs.kde.org/show_bug.cgi?id=406117 Bug ID: 406117 Summary: kmail & akonadi crashes Product: kmail2 Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 5.0.3-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: When I delete several mail or move several mail at once with multiple select and or keyboard shortcut m there's a hang (messages become greyed) but nothing change, and the interface freeze, you can click on other folders but nothing happend except akonadi or kmail crashes. This behaviour is increasing since the last few weeks, becoming more and more frequent. Database used PostgreSQL 10.7 (libpq is 11.2) baloo is disabled by balooctl disable as it doesn't work. Running akonadictl fsck or vacuum help sometime but not always. All email parts are stored inside the database. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa6e7be7a40 (LWP 3736))] Thread 35 (Thread 0x7fa597fff700 (LWP 30716)): #0 0x7fa6f65f4428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6f024a7e7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fa6f024b13a in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fa6f024b222 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fa6f0208bd1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fa6f020b516 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fa6f020b7d4 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fa6f024d341 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fa6f65edfab in start_thread () at /lib64/libpthread.so.0 #9 0x7fa6f8c486af in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7fa6b67fc700 (LWP 30715)): #0 0x7fa6f65f4428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6f024a7e7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fa6f024b13a in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fa6f024b222 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fa6f0208bd1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fa6f020b516 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fa6f020b7d4 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fa6f024d341 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fa6f65edfab in start_thread () at /lib64/libpthread.so.0 #9 0x7fa6f8c486af in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fa637bff700 (LWP 30714)): #0 0x7fa6f65f4428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6f024a7e7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fa6f024b13a in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fa6f024b222 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fa6f0208bd1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fa6f020b516 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fa6f020b7d4 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fa6f024d341 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fa6f65edfab in start_thread () at /lib64/libpthread.so.0 #9 0x7fa6f8c486af in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7fa595e0a700 (LWP 30713)): #0 0x7fa6f65f4428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6f024a7e7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fa6f024b13a in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fa6f024b222 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fa6f0208bd1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fa6f020b516 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fa6f020b7d4 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fa6f024d341 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fa6f65edfab in start_thread () at /lib64/libpthread.so.0 #9 0x7fa6f8c486af in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7fa596e0c700 (LWP 18470)): #0 0x7fa6f65f4428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6f024a7e7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fa6f024b13a in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fa6f024b222 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fa6f0208bd1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fa6f020b516 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fa6f020b7d4 in ()
[korganizer] [Bug 406108] add event => event add in akonadi and google calendar but not displayed in korganizer
https://bugs.kde.org/show_bug.cgi?id=406108 --- Comment #1 from Philippe ROUBACH --- if i relaunch korganizer then the event is displayed ! -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 406108] New: add event => event add in akonadi and google calendar but not displayed in korganizer
https://bugs.kde.org/show_bug.cgi?id=406108 Bug ID: 406108 Summary: add event => event add in akonadi and google calendar but not displayed in korganizer Product: korganizer Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: philippe.roub...@free.fr Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. add an event 2. it is recorded in akonadi db and google calendar 3. OBSERVED RESULT it is not displayed in korganizer EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION korganiser 5.10.3 i tried 4 times then i got 4 events recorded in akonadi db and google calendar here is the raw file in akonadi db BEGIN:VCALENDAR PRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN VERSION:2.0 X-KDE-ICAL-IMPLEMENTATION-VERSION:1.0 BEGIN:VEVENT DTSTAMP:20190401T093845Z CREATED:20190401T093337Z UID:hv9kg6qlvjf06o9dvmg859sna0 LAST-MODIFIED:20190401T093845Z SUMMARY:Etat des lieux STATUS:CONFIRMED DTSTART;TZID=Europe/Paris:20190417T18 DTEND;TZID=Europe/Paris:20190417T19 TRANSP:OPAQUE BEGIN:VALARM DESCRIPTION: ACTION:DISPLAY TRIGGER;VALUE=DURATION:-PT15M X-KDE-KCALCORE-ENABLED:TRUE END:VALARM END:VEVENT BEGIN:VTIMEZONE TZID:Europe/Paris BEGIN:DAYLIGHT TZNAME:CEST TZOFFSETFROM:+ TZOFFSETTO:+0200 DTSTART:19760328T00 RDATE;VALUE=DATE-TIME:19760328T00 END:DAYLIGHT BEGIN:STANDARD TZNAME:CET TZOFFSETFROM:+0200 TZOFFSETTO:+0100 DTSTART:19790930T03 RRULE:FREQ=YEARLY;UNTIL=19961027T03;COUNT=17;BYDAY=-1SU;BYMONTH=9 END:STANDARD BEGIN:STANDARD TZNAME:CET TZOFFSETFROM:+0200 TZOFFSETTO:+0100 DTSTART:19971026T03 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:STANDARD TZNAME:CET TZOFFSETFROM:+0200 TZOFFSETTO:+0100 DTSTART:19760926T01 RDATE;VALUE=DATE-TIME:19760926T01 RDATE;VALUE=DATE-TIME:19770925T03 RDATE;VALUE=DATE-TIME:19781001T03 RDATE;VALUE=DATE-TIME:19950924T03 END:STANDARD BEGIN:DAYLIGHT TZNAME:CEST TZOFFSETFROM:+0100 TZOFFSETTO:+0200 DTSTART:19810329T02 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3 END:DAYLIGHT BEGIN:DAYLIGHT TZNAME:CEST TZOFFSETFROM:+0100 TZOFFSETTO:+0200 DTSTART:19770403T02 RDATE;VALUE=DATE-TIME:19770403T02 RDATE;VALUE=DATE-TIME:19780402T02 RDATE;VALUE=DATE-TIME:19790401T02 RDATE;VALUE=DATE-TIME:19800406T02 END:DAYLIGHT END:VTIMEZONE END:VCALENDAR -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402229] Sqlite backend error with schema update 36 & 37 (5.10.0)
https://bugs.kde.org/show_bug.cgi?id=402229 Michael Palimaka changed: What|Removed |Added CC||kensing...@gentoo.org -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406106] RemoteID is too small MYSQL error
https://bugs.kde.org/show_bug.cgi?id=406106 ad1r...@hotmail.fr changed: What|Removed |Added CC||ad1r...@hotmail.fr -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406106] New: RemoteID is too small MYSQL error
https://bugs.kde.org/show_bug.cgi?id=406106
Bug ID: 406106
Summary: RemoteID is too small MYSQL error
Product: Akonadi
Version: 5.9.1
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: DAV Resource
Assignee: kdepim-bugs@kde.org
Reporter: ad1r...@hotmail.fr
Target Milestone: ---
SUMMARY
When i synchronise my calendar with nextcloud, the remoteID field can greather
than 255, in result of mysqlSQL error and crash
g.kde.pim.akonadiserver: Error during insertion into table "PimItemTable" "Data
too long for column 'remoteId' at row 1 QMYSQL3: Unable to execute statement"
g.kde.pim.akonadiserver: Query: "INSERT INTO PimItemTable (rev, remoteId,
remoteRevision, gid, collectionId, mimeTypeId, datetime, atime, dirty, size)
VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9)"
g.kde.pim.akonadiserver: Values: QMap((":0", QVariant(int, 0))(":1",
QVariant(QString,
"https://nextcloud.brain-networks.net/remote.php/dav/calendars/Adrien.Faveraux/personal_shared_by_Anselme.Josset/04008200E00074C5B7101A82E008000C070CA1EA9B1D40114865F8D8ECEAA47B9D3185D6F97F452.ics#04008200E00074C5B7101A82E008C070CA1EA9B1D40114865F8D8ECEAA47B9D3185D6F97F4522019-03-25T14:00:00+01:00;))(":2",
QVaria
g.kde.pim.akonadiserver: Error text: "Data too long for column 'remoteId' at
row 1 QMYSQL3: Unable to execute statement"
g.kde.pim.akonadiserver: DB error: "Data too long for column 'remoteId' at
row 1"
g.kde.pim.akonadiserver: Error code: "1406"
g.kde.pim.akonadiserver: DATABASE ERROR:
i have to edit the struct of mysql database of akonadi to set the limit more
huge.
mysql --socket=/tmp/akonadi-quartz.LHhNzx/mysql.socket
MariaDB [akonadi]> ALTER TABLE `PimItemTable` CHANGE `remoteId` `remoteId`
VARBINARY(512) NULL;
Can you set the limit more user friendly by default ?
STEPS TO REPRODUCE
1. Have an huge remoteID in ICS filename
2.
3.
OBSERVED RESULT
Crash
EXPECTED RESULT
Work :)
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Fedora 29
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.55
Qt Version: 5.11.3
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 406104] New: Kmail crashes when you try to run it
https://bugs.kde.org/show_bug.cgi?id=406104 Bug ID: 406104 Summary: Kmail crashes when you try to run it Product: kmail2 Version: 5.10.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: nick.craig@gmail.com Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.12.0 Frameworks Version: 5.55.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: Just clicked on the kmail icon, kmail crashed. Not sure if it makes any difference but I also use the kmail resource that allows you to link you gmail contacts to kde so that all my contacts are available to kmail. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f55a5cdcbc0 (LWP 26520))] Thread 24 (Thread 0x7f5583bd9700 (LWP 26625)): #0 0x7f55d91df0b4 in __GI___libc_read (fd=24, buf=0x7f5583bd87d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f55ccb15cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f55ccad1027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f55ccad14e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f55ccad164c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f55d9b2615b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f557c005290, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f55d9ac764a in QEventLoop::exec(QFlags) (this=this@entry=0x7f5583bd89e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f55d98ef41a in QThread::exec() (this=) at thread/qthread.cpp:531 #8 0x7f55d98f0bc2 in QThreadPrivate::start(void*) (arg=0x55fb89ebbe00) at thread/qthread_unix.cpp:361 #9 0x7f55d8eb76db in start_thread (arg=0x7f5583bd9700) at pthread_create.c:463 #10 0x7f55d91f088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f548700 (LWP 26586)): #0 0x7f55ccb17049 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f55ccad10c6 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f55ccad15c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f55ccad164c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f55d9b2615b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f5488000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f55d9ac764a in QEventLoop::exec(QFlags) (this=this@entry=0x7f548fffe9e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f55d98ef41a in QThread::exec() (this=) at thread/qthread.cpp:531 #7 0x7f55d98f0bc2 in QThreadPrivate::start(void*) (arg=0x55fb8d11b990) at thread/qthread_unix.cpp:361 #8 0x7f55d8eb76db in start_thread (arg=0x7f548700) at pthread_create.c:463 #9 0x7f55d91f088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f551a3ee700 (LWP 26585)): #0 0x7f55d8ebd9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f55bf0c8fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f55d8ebd9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f55bf0c8f68, cond=0x7f55bf0c8f90) at pthread_cond_wait.c:502 #2 0x7f55d8ebd9f3 in __pthread_cond_wait (cond=0x7f55bf0c8f90, mutex=0x7f55bf0c8f68) at pthread_cond_wait.c:655 #3 0x7f55bedd2844 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f55bedd2889 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f55d8eb76db in start_thread (arg=0x7f551a3ee700) at pthread_create.c:463 #6 0x7f55d91f088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f5521fe6700 (LWP 26572)): #0 0x7f55d8ebded9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f5521fe5710, expected=0, futex_word=0x7f5521fe58f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f55d8ebded9 in __pthread_cond_wait_common (abstime=0x7f5521fe57b0, mutex=0x7f5521fe58a8, cond=0x7f5521fe58d0) at pthread_cond_wait.c:533 #2 0x7f55d8ebded9 in __pthread_cond_timedwait (cond=0x7f5521fe58d0, mutex=0x7f5521fe58a8, abstime=0x7f5521fe57b0) at pthread_cond_wait.c:667 #3 0x7f55c3b10177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f55c3b10ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f55c3b10bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f55c3ace851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f55c3ad16b6 in () at
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 --- Comment #30 from Axel Braun --- (In reply to Martin Tlustos from comment #28) > Before I delete and re-add the account to kaddressbook: shouldn't a proper > fix work without this? If that is the goal, then I should wait to test > whether it works then, right? Make sure to check your distribution lists afterwards - mine got corrupted by removing/re-adding google contacts -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 406103] New: KMail won't display messages, crashes on Quit
https://bugs.kde.org/show_bug.cgi?id=406103 Bug ID: 406103 Summary: KMail won't display messages, crashes on Quit Product: kmail2 Version: 5.10.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: boven...@bovender.de Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: KMail stopped displaying messages; Akonadi logged database timeout errors. When I quit KMail in this situation (which happens very often) with CTRL+Q, I get this crash report. I also wrote about this problem here: https://forum.kde.org/viewtopic.php?f=215=159963 The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f202710bbc0 (LWP 32100))] Thread 26 (Thread 0x7f1fc2ec5700 (LWP 4924)): #0 0x7f2019909ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f1fc2ec4710, expected=0, futex_word=0x7f1fc2ec48f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f2019909ed9 in __pthread_cond_wait_common (abstime=0x7f1fc2ec47b0, mutex=0x7f1fc2ec48a8, cond=0x7f1fc2ec48d0) at pthread_cond_wait.c:533 #2 0x7f2019909ed9 in __pthread_cond_timedwait (cond=0x7f1fc2ec48d0, mutex=0x7f1fc2ec48a8, abstime=0x7f1fc2ec47b0) at pthread_cond_wait.c:667 #3 0x7f200e868177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f200e868ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f200e868bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f200e826851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f200e829387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f200e829974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f200e86acd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f20199036db in start_thread (arg=0x7f1fc2ec5700) at pthread_create.c:463 #11 0x7f202415788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f1f675f7700 (LWP 3744)): #0 0x7f2019909ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f1f675f6710, expected=0, futex_word=0x7f1f675f68f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f2019909ed9 in __pthread_cond_wait_common (abstime=0x7f1f675f67b0, mutex=0x7f1f675f68a8, cond=0x7f1f675f68d0) at pthread_cond_wait.c:533 #2 0x7f2019909ed9 in __pthread_cond_timedwait (cond=0x7f1f675f68d0, mutex=0x7f1f675f68a8, abstime=0x7f1f675f67b0) at pthread_cond_wait.c:667 #3 0x7f200e868177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f200e868ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f200e868bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f200e826851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f200e8296b6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f200e829974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f200e86acd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f20199036db in start_thread (arg=0x7f1f675f7700) at pthread_create.c:463 #11 0x7f202415788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f1ecd2ac700 (LWP 3655)): #0 0x7f2019909ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f1ecd2ab710, expected=0, futex_word=0x7f1ecd2ab8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f2019909ed9 in __pthread_cond_wait_common (abstime=0x7f1ecd2ab7b0, mutex=0x7f1ecd2ab8a8, cond=0x7f1ecd2ab8d0) at pthread_cond_wait.c:533 #2 0x7f2019909ed9 in __pthread_cond_timedwait (cond=0x7f1ecd2ab8d0, mutex=0x7f1ecd2ab8a8, abstime=0x7f1ecd2ab7b0) at pthread_cond_wait.c:667 #3 0x7f200e868177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f200e868ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f200e868bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f200e826851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f200e8296b6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f200e829974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f200e86acd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f20199036db in start_thread (arg=0x7f1ecd2ac700) at pthread_create.c:463
