[Akonadi] [Bug 361610] New: “Server failed the authenticity check” not cancelable
https://bugs.kde.org/show_bug.cgi?id=361610 Bug ID: 361610 Summary: “Server failed the authenticity check” not cancelable Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: cdauth+bugs.kde@cdauth.eu CC: kdepim-bugs@kde.org, vkra...@kde.org When connecting to an IMAP server whose certificate can not be authenticated, a popup comes up that contains the following message: “The server failed the authenticity check (testdomain.example.org). The certificate is not signed by any trusted certificate authority”. The message has the buttons “Details”, “Continue”, “Cancel”. When clicking Cancel, the message comes up immediately again. When ignoring the message, another message of the same type will come up every 30 seconds or so, stealing the focus, thus making the computer basically unusable without accepting the invalid certificate. When pressing Cancel, Akonadi should not attempt to reconnect to the server until restarted or until a connection is manually initiated (by clicking the “Check Mail” button in KMail for example). Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 361608] New: Akonadi Segault when trying to sync IMAP (intensive sync of many hundreds of emails)
https://bugs.kde.org/show_bug.cgi?id=361608 Bug ID: 361608 Summary: Akonadi Segault when trying to sync IMAP (intensive sync of many hundreds of emails) Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: mathieu.belivea...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.89.0) Qt Version: 5.5.1 Operating System: Linux 4.2.0-35-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I was syncing kmail with my work place's exchange server through IMAP via Davmail. Note: This happend during an initial sync covering two years worth of emails. May be related to bug: 353957 (the stack trace is awfully similar). Although the crash reporting assistant wouldn't let me link my bug report to this one. The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Resource (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f53fb8ce840 (LWP 10405))] Thread 4 (Thread 0x7f53f91cf700 (LWP 10413)): #0 0x7f5408c5088d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f54043f5bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f54043f774f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f53fb5277e9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f540955da6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f54046146aa in start_thread (arg=0x7f53f91cf700) at pthread_create.c:333 #6 0x7f5408c5be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f53f1e50700 (LWP 10558)): #0 0x7f5408c5088d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f54038971ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f54038972fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f540979550b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f540973c50a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5409558ac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f540955da6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f54046146aa in start_thread (arg=0x7f53f1e50700) at pthread_create.c:333 #8 0x7f5408c5be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f53f0a45700 (LWP 10585)): #0 0x7f54038db860 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5403896789 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f540389711b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f54038972fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f540979550b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f540973c50a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5409558ac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f540955da6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f54046146aa in start_thread (arg=0x7f53f0a45700) at pthread_create.c:333 #9 0x7f5408c5be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f53fb8ce840 (LWP 10405)): [KCrash Handler] #6 0x7f540c3a9693 in Akonadi::Entity::id (this=this@entry=0x7f54098123d8 ) at ../../../../akonadi/src/core/entity.cpp:72 #7 0x0045833e in ImapResourceBase::retrieveItems (this=this@entry=0xfeabb0, col=...) at ../../../resources/imap/imapresourcebase.cpp:435 #8 0x7f540c74e32d in Akonadi::ResourceBasePrivate::slotItemRetrievalCollectionFetchDone (this=, job=0x103d3c0) at ../../../../akonadi/src/agentbase/resourcebase.cpp:954 #9 0x7f540c750200 in Akonadi::ResourceBase::qt_static_metacall (_o=, _c=, _id=, _a=) at ./moc_resourcebase.cpp:294 #10 0x7f540976d8ea in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f540aac1752 in KJob::result (this=this@entry=0x103d3c0, _t1=_t1@entry=0x103d3c0) at ./moc_kjob.cpp:555 #12 0x7f540aac2311 in KJob::finishJob (this=0x103d3c0, emitResult=) at ../../../src/lib/jobs/kjob.cpp:109 #13 0x7f540aac232a in KJob::emitResult (this=) at ../../../src/lib/jobs/kjob.cpp:295 #14 0x7f540c43a3b3 in Akonadi::JobPrivate::delayedEmitResult (this=) at
[kontact] [Bug 361605] New: kmail crash on double click email
https://bugs.kde.org/show_bug.cgi?id=361605 Bug ID: 361605 Summary: kmail crash on double click email Product: kontact Version: unspecified Platform: Chakra OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: luc...@bluewin.ch Application: kontact (5.1.90 rc) Qt Version: 5.6.0 Frameworks Version: 5.21.0 Operating System: Linux 4.5.0-1-CHAKRA x86_64 Distribution: "Chakra" -- Information about the crash: kmail 16.03.90 How to reproduce: double click and email from the email list. (I tested with a nestled email, one from a list of replies) Results: kmail/contact crash. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9063055840 (LWP 9372))] Thread 23 (Thread 0x7f90603e3700 (LWP 9373)): #0 0x7f9076f3718d in poll () from /usr/lib/libc.so.6 #1 0x7f907149fae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f90714a1757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f9062d6a329 in QXcbEventReader::run (this=0xea5c70) at qxcbconnection.cpp:1313 #4 0x7f9077840238 in QThreadPrivate::start (arg=0xea5c70) at thread/qthread_unix.cpp:340 #5 0x7f9070e75464 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f9076f4012d in clone () from /usr/lib/libc.so.6 Thread 22 (Thread 0x7f9057fff700 (LWP 9374)): #0 0x7f906f353336 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f906f308b7f in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7f906f309183 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f906f309322 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f9077a691fb in QEventDispatcherGlib::processEvents (this=0x7f9058c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f9077a11c2a in QEventLoop::exec (this=this@entry=0x7f9057ffed50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f907783b434 in QThread::exec (this=this@entry=0x7f9079d5dd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:503 #7 0x7f9079cea495 in QDBusConnectionManager::run (this=0x7f9079d5dd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:181 #8 0x7f9077840238 in QThreadPrivate::start (arg=0x7f9079d5dd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:340 #9 0x7f9070e75464 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f9076f4012d in clone () from /usr/lib/libc.so.6 Thread 21 (Thread 0x7f9056dee700 (LWP 9376)): #0 0x7f9070e7b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9074f023fb in ?? () from /usr/lib/libQt5WebKit.so.5 #2 0x7f9074f02439 in ?? () from /usr/lib/libQt5WebKit.so.5 #3 0x7f9070e75464 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f9076f4012d in clone () from /usr/lib/libc.so.6 Thread 20 (Thread 0x7f900f8ae700 (LWP 9377)): #0 0x7f9076f4c707 in __libc_disable_asynccancel () from /usr/lib/libc.so.6 #1 0x7f9076f33179 in read () from /usr/lib/libc.so.6 #2 0x7f906f351b41 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f906f308ca4 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #4 0x7f906f309183 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0x7f906f309322 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #6 0x7f9077a691fb in QEventDispatcherGlib::processEvents (this=0x7f90080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #7 0x7f9077a11c2a in QEventLoop::exec (this=this@entry=0x7f900f8add80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7f907783b434 in QThread::exec (this=) at thread/qthread.cpp:503 #9 0x7f9077840238 in QThreadPrivate::start (arg=0xfe6150) at thread/qthread_unix.cpp:340 #10 0x7f9070e75464 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f9076f4012d in clone () from /usr/lib/libc.so.6 Thread 19 (Thread 0x7f9007fff700 (LWP 9378)): #0 0x7f9070e7b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9074c0f1c4 in ?? () from /usr/lib/libQt5WebKit.so.5 #2 0x7f9074f32291 in ?? () from /usr/lib/libQt5WebKit.so.5 #3 0x7f9070e75464 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f9076f4012d in clone () from /usr/lib/libc.so.6 Thread 18 (Thread 0x7f90077fe700 (LWP 9379)): #0 0x7f9070e7b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9074c101f3 in ?? () from /usr/lib/libQt5WebKit.so.5 #2 0x7f9074f32291 in ?? () from /usr/lib/libQt5WebKit.so.5 #3 0x7f9070e75464 in start_thread () from /usr/l
[akregator] [Bug 361590] navigation buttons missing in internal webbrowser
https://bugs.kde.org/show_bug.cgi?id=361590 --- Comment #1 from Martin Steigerwald --- Created attachment 98316 --> https://bugs.kde.org/attachment.cgi?id=98316&action=edit there are no navigation buttons next to the other three buttons in the toolbar In older Akregator versions there have been navigation buttons (well, it was broken there for some time as well, but before that…) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 361590] New: navigation buttons missing in internal webbrowser
https://bugs.kde.org/show_bug.cgi?id=361590 Bug ID: 361590 Summary: navigation buttons missing in internal webbrowser Product: akregator Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-bugs@kde.org Reporter: mar...@lichtvoll.de Currently using Applications/16.04, but also happens with git master. On web page article view back and forward navigation buttons are missing. Reproducible: Always Steps to Reproduce: 1. Add a feed. 2. Open an article. 3. View an article in internal webbrowser. 4. Click a link. Actual Results: No back button at all (see attached screenshot). I reported the extremely smal font size separately as bug 361588. Expected Results: Back button is there and is made active (instead of ghosted) when I press first link. This issue first came up when Laurent implemented the wonderful WebEngine support. I told Laurent then and he said would be looking into it, but issue is still there, so I report bug. It has been fixed in the meanwhile for some time, but since quite a while is present again. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 361588] Text of articles from certain websites displayed way too small
https://bugs.kde.org/show_bug.cgi?id=361588 --- Comment #1 from Martin Steigerwald --- Created attachment 98315 --> https://bugs.kde.org/attachment.cgi?id=98315&action=edit This is how Akregator displays text from pro-linux.de Also affected are Heise Open heise.de/open, as well as KDE Dot News https://dot.kde.org/ and many other sites. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 361588] New: Text of articles from certain websites displayed way too small
https://bugs.kde.org/show_bug.cgi?id=361588 Bug ID: 361588 Summary: Text of articles from certain websites displayed way too small Product: akregator Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-bugs@kde.org Reporter: mar...@lichtvoll.de Currently running git Applications/16.04, but also happens with master. Text of articles from feeds from certain websites is displayed way too small. I meanwhile habitually press Ctrl + several times to make it readable. Reproducible: Always Steps to Reproduce: 1. Add rss feed of pro-linux.de (just visit site with Konqueror and use RSS symbol) or use the URL http://www.pro-linux.de/backend/pro-linux.rdf 2. Let is receive some articles 3. View one article 4. Open article as webpage in internet browser Actual Results: See attached screenshot. Expected Results: Obviously way bigger text! This is on ThinkPad T520, currently using even 24 inch external display, on internal Full HD with 143 dpi display the text is really unreadable. This issue first came up when Laurent implemented the wonderful WebEngine support. I told Laurent then and he said would be looking into it, but issue is still there, so I report bug. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 323455] "Filter account is missing" after KMail startup
https://bugs.kde.org/show_bug.cgi?id=323455 --- Comment #15 from staka...@freenet.de --- I confirm this bug for Leap 42.1 and both, the KDE4 version of Kmail 4.14.10 (Akonadi 4.14.10) as for the available Plasma 5 version with Qt:5.5.1 Kontact 15.12.3 and Akonadi 15.12.4 Both versions show the very same bug, an empty pop-up window claiming that the account for some filter rule is not found, you can click OK by choosing an empty line, sometimes this holds the filter rule alive, sometimes it vanishes. If you choose cancel, generally the filer rule vanishes. Sometimes even multiple filter vanish. Filters generally vanish one by one in chronological order of the filter list. What I discovered else, this but can be easily triggered by choosing not to apply a filter to multiple accounts (pop) if you have them but only to "one specific account". Especially if other filters are applied to all accounts indiscriminately (like pop-filters or spam and clamav filters). It appears the problem lies there somewhere. This is a very tedious bug, because on one hand constant and also sometimes hidden (no popup and you find out that some filter over the time vanish). I once had lost 50 % of all rules without warning. So this is valid for me for POP filtering and for both KDE4 version and Plasma 5 version of this programme. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 323455] "Filter account is missing" after KMail startup
https://bugs.kde.org/show_bug.cgi?id=323455 Andrey changed: What|Removed |Added CC||kdeb...@openaliasbox.org --- Comment #14 from Andrey --- I also confirm this bug. Gentoo Linux amd64 Qt: 5.5.1 Kontact 5.1.3 (KDEPIM 15.12.3) Akonadi 15.12.3 What additional info you need? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 361575] New: Background operation cause crash of akonadi_imap (Akonadi::Protocol::HelloResponse::HelloResponse)
https://bugs.kde.org/show_bug.cgi?id=361575 Bug ID: 361575 Summary: Background operation cause crash of akonadi_imap (Akonadi::Protocol::HelloResponse::HelloResponse) Product: Akonadi Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libakonadi Assignee: kdepim-bugs@kde.org Reporter: lukas.ka...@centrum.cz akonadi_imap_resource crashed after computer resume from suspend. Reproducible: Couldn't Reproduce Steps to Reproduce: I have no idea Actual Results: Application: akonadi_imap_resource (akonadi_imap_resource), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f188227a940 (LWP 9986))] Thread 7 (Thread 0x7f1880164700 (LWP 10012)): #0 0x7f18918795ad in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f188d9c2c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f188d9c48d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f1881e8f4a9 in QXcbEventReader::run (this=0x157e6e0) at qxcbconnection.cpp:1253 #4 0x7f18921857fe in QThreadPrivate::start (arg=0x157e6e0) at thread/qthread_unix.cpp:331 #5 0x7f188e5df6fa in start_thread (arg=0x7f1880164700) at pthread_create.c:333 #6 0x7f18918852dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f187e9c5700 (LWP 10093)): #0 0x7f18918750ed in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f188d2df6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f188d29be14 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f188d29c2d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f188d29c43c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f18923bca7b in QEventDispatcherGlib::processEvents (this=0x7f1878c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f1892363d8a in QEventLoop::exec (this=this@entry=0x7f187e9c4c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f1892180854 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7f18921857fe in QThreadPrivate::start (arg=0x15e1210) at thread/qthread_unix.cpp:331 #9 0x7f188e5df6fa in start_thread (arg=0x7f187e9c5700) at pthread_create.c:333 #10 0x7f18918852dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f187e1c4700 (LWP 10106)): #0 0x7f18918750ed in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f188d2df6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f188d29be14 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f188d29c2d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f188d29c43c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f18923bca7b in QEventDispatcherGlib::processEvents (this=0x7f18740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f1892363d8a in QEventLoop::exec (this=this@entry=0x7f187e1c3c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f1892180854 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7f18921857fe in QThreadPrivate::start (arg=0x15fb9d0) at thread/qthread_unix.cpp:331 #9 0x7f188e5df6fa in start_thread (arg=0x7f187e1c4700) at pthread_create.c:333 #10 0x7f18918852dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f187cfb3700 (LWP 10212)): #0 0x7f18918750ed in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f188d2df6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f188d29be14 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f188d29c2d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f188d29c43c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f18923bca7b in QEventDispatcherGlib::processEvents (this=0x7f18680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f1892363d8a in QEventLoop::exec (this=this@entry=0x7f187cfb2c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f1892180854 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7f18921857fe in QThreadPrivate::start (arg=0x1684740) at thread/qthread_unix.cpp:331 #9 0x7f188e5df6fa in start_thread (arg=0x7f187cfb3700) at pthread_create.c:333 #10 0x7f18918852dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f186d598700 (LWP 10871)): #0 0x7f18918795ad in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f188d29c32c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f188d29c43c in g_main_context_iteration () from /
