[kate] [Bug 448207] New: Windows 11 on 4K display after sleep
https://bugs.kde.org/show_bug.cgi?id=448207 Bug ID: 448207 Summary: Windows 11 on 4K display after sleep Product: kate Version: 21.12.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: kvranc...@abvvmetaal.be Target Milestone: --- Created attachment 145296 --> https://bugs.kde.org/attachment.cgi?id=145296&action=edit Printscreen of the duplicate shrinked editor inside Kate window after Windows 11 resumes from sleep. On Windows 11 and a 4K display: 1. the Kate editor is open on the 4K display 2. I go for a break 3. the PC goes to sleep 4. I come back an fire up the PC 5. Windows 11 resumes Then all open windows are still at their previous state when I left. The Kate window also still has its normal outer dimensions, but inside it there is a duplicate of the editor located in the upper left corner at only a quarter of its previous size and with very small letters. The menu also has shrinked. Nothing is clickable. The application is completely frozen and has to be restarted. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 Karel changed: What|Removed |Added CC||k...@ecn.cz --- Comment #27 from Karel --- Sms,contacts and history sms not visible in messages window. Doesn't seem to connect to local address book even after "contacts" in settings are un-ticked. O if it connects the contacts nor the sms are visible in the "messages" window which does open, but empty. Ubuntu 19.10, Android 9 on Samsung A6, Kdeconnect on android version 1.13.2., Gsconnect 28 (last version updated today). Great app btw, thank yo very much Andy! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #28 from Karel --- (In reply to Karel from comment #27) > Sms,contacts and history sms not visible in messages window. Doesn't seem to > connect to local address book even after "contacts" in settings are > un-ticked. O if it connects the contacts nor the sms are visible in the > "messages" window which does open, but empty. > Ubuntu 19.10, Android 9 on Samsung A6, Kdeconnect on android version > 1.13.2., Gsconnect 28 (last version updated today). > Great app btw, thank yo very much Andy! Correction: The application apparently does connect to contacts (to my local address book I assume as "contacts" are unticked in settings), because a pop-up alert on incoming message shows details about contact name. However, the "messages" window remains empty. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #30 from Karel --- Apologies for making so much noise, but yet another correction: With upgrading to Gsconnect 28, the contact list (local, I assume) actually does show when I compose a new message. I didn't notice that before writing my first report - sorry for that. So the only issue that remains is that the sms log doesn't load. Otherwise all works perfect. Thank you for this excellent appkication! (In reply to Karel from comment #28) > (In reply to Karel from comment #27) > > Sms,contacts and history sms not visible in messages window. Doesn't seem to > > connect to local address book even after "contacts" in settings are > > un-ticked. O if it connects the contacts nor the sms are visible in the > > "messages" window which does open, but empty. > > Ubuntu 19.10, Android 9 on Samsung A6, Kdeconnect on android version > > 1.13.2., Gsconnect 28 (last version updated today). > > Great app btw, thank yo very much Andy! > > Correction: The application apparently does connect to contacts (to my local > address book I assume as "contacts" are unticked in settings), because a > pop-up alert on incoming message shows details about contact name. However, > the "messages" window remains empty. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 472453] krfb asserts in PWFrameBuffer::cursorPosition
https://bugs.kde.org/show_bug.cgi?id=472453 Karel Matějovský changed: What|Removed |Added CC||kodzghl...@gmail.com --- Comment #6 from Karel Matějovský --- I can confirm that this is still happening even on my system. The result matches the mentioned observations -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 Karel Matějovský changed: What|Removed |Added CC||kodzghl...@gmail.com Version|23.08.3 |23.08.4 --- Comment #10 from Karel Matějovský --- I have tried the command above, even killing pipewire, the process didn't die to SEGFAULT, but still doesn't work the way it's supposed to. I'm getting all my screens black except the first one which shows a menu for new display. In system settings the only monitor that appears to be there is the virtual one, all the other ones are gone for some reason and there's plenty of gibberish text (probably labels for physical monitors) in the display field. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 --- Comment #11 from Karel Matějovský --- One more thing I've noticed. When I look at my displays, the resolution of the virtual display is 100 times more than it should be, I guess it has something to do with the scale factor. Changing the scale to 1 doesn't work, so I'm currently stuck only with resolutions that end up with 00, because you can't type in decimal resolution (also crashes). Don't have enough skills to dig through the code, so I'd appreciate any help regarding this issue. I will also try to VNC to the newly created display (what did work for me was 'krfb-virtualmonitor --scale 100 --resolution 12x8 --name test1 --password a --port 5900') and report on whether I'm really getting somewhere. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 --- Comment #12 from Karel Matějovský --- After connecting to the virtual display through AVNC on Android, I got this issue: new client request /usr/include/c++/13.2.1/optional:477: constexpr _Tp& std::_Optional_base_impl<_Tp, _Dp>::_M_get() [with _Tp = PipeWireCursor; _Dp = std::_Optional_base]: Assertion 'this->_M_is_engaged()' failed. zsh: IOT instruction (core dumped) krfb-virtualmonitor --scale 100 --resolution 12x8 --name test1 --password a -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 446859] New: The background of Yakuake stays white no matter the settings
https://bugs.kde.org/show_bug.cgi?id=446859 Bug ID: 446859 Summary: The background of Yakuake stays white no matter the settings Product: yakuake Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: kodzghl...@gmail.com Target Milestone: --- Created attachment 144468 --> https://bugs.kde.org/attachment.cgi?id=144468&action=edit Here is how it looks like with the white background. Yakuake cannot change background color *** After last update, I can no longer change Yakuake background color, it stays white, which is very annoying and makes the whole program useless at night. *** STEPS TO REPRODUCE 1. Get the latest version of Yakuake 2. The introduction pop up window will show letting you set the key bind for it 3. Press that key you have just binded and Yakuake will appear with the white background OBSERVED RESULT The background is white no matter the color scheme or background color set in settings. The transparency is not working either. EXPECTED RESULT The color should change anyhow, but it stays the same. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 446859] The background of Yakuake stays white no matter the settings
https://bugs.kde.org/show_bug.cgi?id=446859 --- Comment #1 from Karel Matějovský --- I have managed to change the background by editing the Breath color scheme for Manjaro, so it looks like it is more Manjaro oriented issue. -- You are receiving this mail because: You are watching all bug changes.
[plasma-redshift-control] [Bug 437600] New: Redshift applet control window
https://bugs.kde.org/show_bug.cgi?id=437600 Bug ID: 437600 Summary: Redshift applet control window Product: plasma-redshift-control Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: kodzghl...@gmail.com Target Milestone: --- I would be really grateful if it was possible for me to change the redshift value from the taskbar just from a small window like it is possible with the notifications or Wi-fi for example. Opening the window every time I want to change the value or just simply disable it is a bit annoying. Nothing I can not live without, but it would be an awesome feature. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 Karel Kozlík changed: What|Removed |Added CC|koz...@kufr.cz | -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 399299] New: Akregator crashes when middle click on a link
https://bugs.kde.org/show_bug.cgi?id=399299 Bug ID: 399299 Summary: Akregator crashes when middle click on a link Product: akregator Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: koz...@kufr.cz Target Milestone: --- Application: akregator (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: When I middle click on a link (open in external browser) then akregator crash. But if I right click and select 'open in external browser' in the submenu it works without the crash. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f86d07ef0c0 (LWP 5786))] Thread 24 (Thread 0x7f867bfff700 (LWP 5923)): #0 0x7f86c696fed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f867bffe7e0, expected=0, futex_word=0x7f8680004714) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f867bffe880, mutex=0x7f86800046c0, cond=0x7f86800046e8) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f86800046e8, mutex=0x7f86800046c0, abstime=0x7f867bffe880) at pthread_cond_wait.c:667 #3 0x7f86bcf78652 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f86bcf4e799 in base::PosixDynamicThreadPool::WaitForTask() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f86bcf4ecfb in base::(anonymous namespace)::WorkerThread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f86bcf475eb in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f86c69696db in start_thread (arg=0x7f867bfff700) at pthread_create.c:463 #8 0x7f86cc64788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f8592c5d700 (LWP 5829)): #0 0x7f86c696f9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x564ef2fb85c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x564ef2fb8578, cond=0x564ef2fb85a0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x564ef2fb85a0, mutex=0x564ef2fb8578) at pthread_cond_wait.c:655 #3 0x7f86bcf49c95 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f86bcf4a177 in base::SequencedWorkerPool::Worker::Run() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f86bcf4af11 in base::SimpleThread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f86bcf475eb in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f86c69696db in start_thread (arg=0x7f8592c5d700) at pthread_create.c:463 #8 0x7f86cc64788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f861942b700 (LWP 5819)): #0 0x7f86c696f9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f86b997dfb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f86b997df68, cond=0x7f86b997df90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f86b997df90, mutex=0x7f86b997df68) at pthread_cond_wait.c:655 #3 0x7f86b96875f4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f86b9687639 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f86c69696db in start_thread (arg=0x7f861942b700) at pthread_create.c:463 #6 0x7f86cc64788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f861b47c700 (LWP 5813)): #0 0x7f86c696f9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x564ef30bc1c0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x564ef30bc170, cond=0x564ef30bc198) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x564ef30bc198, mutex=0x564ef30bc170) at pthread_cond_wait.c:655 #3 0x7f86ccd4d59b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f86ccd45c0b in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f862054180c in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so #6 0x7f86ccd4c16d in ?? () from /usr/lib/x86_64
[akregator] [Bug 401638] Segmentation fault (version 5.9.3) when closing the full article
https://bugs.kde.org/show_bug.cgi?id=401638 Karel Kozlík changed: What|Removed |Added CC||koz...@kufr.cz -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 Karel Kozlík changed: What|Removed |Added CC||koz...@kufr.cz -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 377715] New: Krunner consumes a lot of CPU since I start typing
https://bugs.kde.org/show_bug.cgi?id=377715 Bug ID: 377715 Summary: Krunner consumes a lot of CPU since I start typing Product: krunner Version: 5.8.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: filesearch Assignee: pinak.ah...@gmail.com Reporter: koz...@kufr.cz Target Milestone: --- Once I hit ALT+F2 and start typing into krunner the krunner CPU usage is increased to 80-90%. It does not go low until I kill krunner. This is reproducible always. Once I have disabled all modules (in krunner settings) that search through files, emails and contacts the krunner start behaving normally. Note: I have disabled baloo some time ago in system setting -> search -> file search It seems the guy here experience the same issue: https://forum.kde.org/viewtopic.php?f=289&t=132775 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368017] New: system setting crashes when assigning same shorcut to two actions
https://bugs.kde.org/show_bug.cgi?id=368017 Bug ID: 368017 Summary: system setting crashes when assigning same shorcut to two actions Product: systemsettings Version: 5.6.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: koz...@kufr.cz Application: systemsettings5 (5.6.5) Qt Version: 5.5.1 Frameworks Version: 5.23.0 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I have assigned Meta+M key shortcut for window maximize action. Then I have assigned the same shorcut for window minimize action. I got a dialog asking me whether I want to reassign the shorcut to new action. I have confirmed it and the system settings has crashed. The crash can be reproduced every time. -- Backtrace: Application: Nastavení systému (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc52162e8c0 (LWP 10857))] Thread 2 (Thread 0x7fc50fe4f700 (LWP 10858)): #0 0x7fc51dd4ce8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc51b7fdc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fc51b7ff8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fc5121a1629 in QXcbEventReader::run (this=0x20244e0) at qxcbconnection.cpp:1253 #4 0x7fc51e44284e in QThreadPrivate::start (arg=0x20244e0) at thread/qthread_unix.cpp:331 #5 0x7fc51af876fa in start_thread (arg=0x7fc50fe4f700) at pthread_create.c:333 #6 0x7fc51dd58b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fc52162e8c0 (LWP 10857)): [KCrash Handler] #6 QString::QString (other=, this=0x7fff0d87c060) at ../../include/QtCore/../../src/corelib/tools/qstring.h:877 #7 QLabel::text (this=0x0) at widgets/qlabel.cpp:322 #8 0x7fc520f19701 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #9 0x7fc51e651e4f in QtPrivate::QSlotObjectBase::call (a=0x7fff0d87c1b0, r=0x7fc51c606580, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #10 QMetaObject::activate (sender=0x7fc51c606580, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3698 #11 0x7fc51c3ecc34 in KGlobalAccel::globalShortcutChanged(QAction*, QKeySequence const&) () from /usr/lib/x86_64-linux-gnu/libKF5GlobalAccel.so.5 #12 0x7fc51c3f06fe in ?? () from /usr/lib/x86_64-linux-gnu/libKF5GlobalAccel.so.5 #13 0x7fc51e651fca in QMetaObject::activate (sender=0x2651e80, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3713 #14 0x7fc51c3fb279 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5GlobalAccel.so.5 #15 0x7fc51c3fd385 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5GlobalAccel.so.5 #16 0x7fc52178f913 in QDBusConnectionPrivate::deliverCall (this=0x207fee0, object=0x2651e80, msg=..., metaTypes=..., slotIdx=6) at qdbusintegrator.cpp:978 #17 0x7fc51e652ea1 in QObject::event (this=0x2651e80, e=) at kernel/qobject.cpp:1239 #18 0x7fc51fafc05c in QApplicationPrivate::notify_helper (this=this@entry=0x200c5f0, receiver=receiver@entry=0x2651e80, e=e@entry=0x279a850) at kernel/qapplication.cpp:3716 #19 0x7fc51fb01516 in QApplication::notify (this=0x7fff0d87cc30, receiver=0x2651e80, e=0x279a850) at kernel/qapplication.cpp:3499 #20 0x7fc51e62362b in QCoreApplication::notifyInternal (this=0x7fff0d87cc30, receiver=0x2651e80, event=event@entry=0x279a850) at kernel/qcoreapplication.cpp:965 #21 0x7fc51e625a26 in QCoreApplication::sendEvent (event=0x279a850, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x200bc70) at kernel/qcoreapplication.cpp:1593 #23 0x7fc51e625f08 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #24 0x7fc51e679673 in postEventSourceDispatch (s=0x2052750) at kernel/qeventdispatcher_glib.cpp:271 #25 0x7fc51aa661a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7fc51aa66400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7fc51aa664ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7fc51e679a7f in QEventDispatcherGlib::processEvents (this=0x2068cb0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #29 0x7fc51e620dea in QEventLoop::exec (this=this@entry=0x7fff0d87cb10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #30 0x7fc51e628e8c in QCoreApplication::exec () at kernel/qcoreapplication.cp
[kwin] [Bug 368103] New: Kwin crashes while changing number of screens
https://bugs.kde.org/show_bug.cgi?id=368103 Bug ID: 368103 Summary: Kwin crashes while changing number of screens Product: kwin Version: 5.6.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: koz...@kufr.cz Application: kwin_x11 (5.6.5) Qt Version: 5.5.1 Frameworks Version: 5.23.0 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I have disabled the left most one of my monitors in screen settings dialog. When I have confirmed this change the kwin crashes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc58716d940 (LWP 16671))] Thread 7 (Thread 0x7fc5548e1700 (LWP 17318)): #0 0x7fc586c55d13 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc58544210f in qt_safe_select (nfds=17, fdread=fdread@entry=0x7fc548000a78, fdwrite=fdwrite@entry=0x7fc548000d08, fdexcept=fdexcept@entry=0x7fc548000f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7fc585443c0e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7fc548000f98, writefds=0x7fc548000d08, readfds=0x7fc548000a78, nfds=, this=0x7fc5480008c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fc5480008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7fc58544413e in QEventDispatcherUNIX::processEvents (this=0x7fc5480008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7fc5853eddea in QEventLoop::exec (this=this@entry=0x7fc5548e0c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fc58520a8a4 in QThread::exec (this=this@entry=0x5167040) at thread/qthread.cpp:503 #7 0x7fc57faca3c5 in QQmlThreadPrivate::run (this=0x5167040) at qml/ftw/qqmlthread.cpp:141 #8 0x7fc58520f84e in QThreadPrivate::start (arg=0x5167040) at thread/qthread_unix.cpp:331 #9 0x7fc58096e6fa in start_thread (arg=0x7fc5548e1700) at pthread_create.c:333 #10 0x7fc586c5fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fc567fff700 (LWP 16737)): #0 0x7fc586c6dfda in __GI___clock_gettime (clock_id=, tp=tp@entry=0x7fc567ffea20) at ../sysdeps/unix/clock_gettime.c:134 #1 0x7fc5852bfc16 in qt_clock_gettime (ts=0x7fc567ffea20, clock=) at tools/qelapsedtimer_unix.cpp:105 #2 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #4 0x7fc585444529 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fc560001118) at kernel/qtimerinfo_unix.cpp:84 #5 0x7fc58544390b in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fc568e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:171 #6 0x7fc58544413e in QEventDispatcherUNIX::processEvents (this=0x7fc568c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #7 0x7fc5853eddea in QEventLoop::exec (this=this@entry=0x7fc567ffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7fc58520a8a4 in QThread::exec (this=this@entry=0x3b64120) at thread/qthread.cpp:503 #9 0x7fc57faca3c5 in QQmlThreadPrivate::run (this=0x3b64120) at qml/ftw/qqmlthread.cpp:141 #10 0x7fc58520f84e in QThreadPrivate::start (arg=0x3b64120) at thread/qthread_unix.cpp:331 #11 0x7fc58096e6fa in start_thread (arg=0x7fc567fff700) at pthread_create.c:333 #12 0x7fc586c5fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fc54700 (LWP 16680)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc584393bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fc584393c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fc58096e6fa in start_thread (arg=0x7fc54700) at pthread_create.c:333 #4 0x7fc586c5fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fc556b18700 (LWP 16678)): #0 0x7fc586c55d13 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc58544210f in qt_safe_select (nfds=16, fdread=fdread@entry=0x7fc55a78, fdwrite=fdwrite@entry=0x7fc55d08, fdexcept=fdexcept@entry=0x7fc55f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7fc585443c0e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7fc55f98, writefds=0x7fc55d08, readfds=0x7fc55a78, nfds=, this=0x7fc558c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherU
