[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 crc changed: What|Removed |Added Version|6.0.3 |6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 crc changed: What|Removed |Added Platform|Debian unstable |Manjaro CC||crc2...@126.com Version|5.19.3 |6.0.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465619] New: plasma crashes while editing widgets
https://bugs.kde.org/show_bug.cgi?id=465619 Bug ID: 465619 Summary: plasma crashes while editing widgets Classification: Plasma Product: plasmashell Version: 5.24.7 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nepenthesbapho...@outlook.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.7) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-60-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.1 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: copying and pasting (ctrl+v) hex code while editing system monitor sensor colors - Custom settings of the application: sensor detail is applicatoin memory percentage The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f698748cb5e in QMetaObject::cast(QObject const*) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6981769eb6 in QQuickShortcutContext::matcher(QObject*, Qt::ShortcutContext) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #7 0x7f6987897480 in QShortcutMap::hasShortcutForKeySequence(QKeySequence const&) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x7f69882ca651 in QLineEdit::createStandardContextMenu() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f69882cb5a2 in QLineEdit::contextMenuEvent(QContextMenuEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f69881bd4ee in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f698817a713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f6988181ca4 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f6987483e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f69881d74a4 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f69881d9fd5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f698817a713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f6987483e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f698786c307 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #19 0x7f6987841a2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #20 0x7f6982353d6e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #21 0x7f6985860d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f69858b56c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f698585e3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f69874dd0b8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f698748275b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f698748acf4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x560bf2f47dce in ?? () #28 0x7f6986da1d90 in __libc_start_call_main (main=main@entry=0x560bf2f46f70, argc=argc@entry=1, argv=argv@entry=0x7fff1a89d7b8) at ../sysdeps/nptl/libc_start_call_main.h:58 #29 0x7f6986da1e40 in __libc_start_main_impl (main=0x560bf2f46f70, argc=1, argv=0x7fff1a89d7b8, init=, fini=, rtld_fini=, stack_end=0x7fff1a89d7a8) at ../csu/libc-start.c:392 #30 0x560bf2f47ef5 in ?? () [Inferior 1 (process 1520) detached] Possible duplicates by query: bug 449377, bug 449204, bug 443934, bug 443520, bug 438133. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 407139] kglobalaccel fails with QDBusObjectPath: invalid path "/component/vlc_bébé_desktop"
https://bugs.kde.org/show_bug.cgi?id=407139 --- Comment #14 from crc --- (In reply to Nate Graham from comment #13) > Good catch. Since you've already done some investigation, would you be > interested in submitting a merge request to fix it? Many thanks for your appreciate! But unfortunately I'm not a professional developer, so I don't know how to correctly submit a merge request. Besides, the original code solving the problem seems primal, even a bit ugly now. So I suggest the current code changing may have its own reason, and simply restore the old one,which is the only workaround I found, may not be a good choice for a long term solution. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 407139] kglobalaccel fails with QDBusObjectPath: invalid path "/component/vlc_bébé_desktop"
https://bugs.kde.org/show_bug.cgi?id=407139 --- Comment #12 from crc --- Hi there! I reopened this bug report because the very same problem reappeared since version 5.98. I've noticed that the code in Kglobalaccel's dBus components handler to transform all non-ascii characters in a path to ''_" has been changed to use "replace" function in C++, probably brought the bug back. For example, in my system a desktop file named "网易云音乐.desktop" (the file has long been deleted and I don't know why the path remains there) was wrongly transformed to "网___乐_desktop", causing "invalid path" error report in dbus, and made it impossible to access kglobalaccel via systemsettings5 anymore. I tried to restore the old script that once saved the problem (see comment 9) in kglobalaccel's source code and recompile it, then the bug was all gone. So I think the current code of kglobalaccel may need rechecking. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 407139] kglobalaccel fails with QDBusObjectPath: invalid path "/component/vlc_bébé_desktop"
https://bugs.kde.org/show_bug.cgi?id=407139 --- Comment #11 from crc --- Hi there! I reopend this bug report -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 407139] kglobalaccel fails with QDBusObjectPath: invalid path "/component/vlc_bébé_desktop"
https://bugs.kde.org/show_bug.cgi?id=407139 crc changed: What|Removed |Added Status|RESOLVED|REOPENED Version|5.70.0 |5.99.0 Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455738] KScreenLocker with black screen after some minutes in sleep
https://bugs.kde.org/show_bug.cgi?id=455738 crc changed: What|Removed |Added CC||crc2...@126.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446405] Wrong icon size of plasma applet "Trashcan" in latte-dock button panel
https://bugs.kde.org/show_bug.cgi?id=446405 --- Comment #1 from crc --- Created attachment 144165 --> https://bugs.kde.org/attachment.cgi?id=144165&action=edit My latte-dock layout file -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446405] New: Wrong icon size of plasma applet "Trashcan" in latte-dock button panel
https://bugs.kde.org/show_bug.cgi?id=446405 Bug ID: 446405 Summary: Wrong icon size of plasma applet "Trashcan" in latte-dock button panel Product: lattedock Version: git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: crc2...@126.com Target Milestone: --- Created attachment 144164 --> https://bugs.kde.org/attachment.cgi?id=144164&action=edit Screenshot that shown the abnormally small size of trashcan at the end of dock panel SUMMARY This problem has existed for quite a long time, perhaps ever since the update of Plasma5.21. When the applet "Trashcan" is added to latte-dock button panel its icon size is obviously smaller than other apps (as shown in the screenshot). Changing the absolute size of dock items does not make any difference. I'm not sure whether it is a specific problem for latte-dock or a general problem of KDE Plasma, so I temporarily post the bug here. STEPS TO REPRODUCE Add the "Trashcan" applet to latte dock button panel and observe its icon size. OBSERVED RESULT The icon of "Trashcan" shall be as same size as other apps in button panel. EXPECTED RESULT The icon size of "Trashcan" appears smaller than other apps in button panel. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro 21.2.0 Qonos (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION In the attachment is a screenshot proof along with my latte-dock layout file -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443536] Latte-dock wrongly appears before fullscreen window
https://bugs.kde.org/show_bug.cgi?id=443536 crc changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443536] Latte-dock wrongly appears before fullscreen window
https://bugs.kde.org/show_bug.cgi?id=443536 --- Comment #8 from crc --- Created attachment 142639 --> https://bugs.kde.org/attachment.cgi?id=142639&action=edit latte layout file Sorry, I thought I'v sent my latte layout file to your personal email but maybe you didn't receive it, so I post the file here again. My latte-dock has a top-panel, a sidebar and a dock at the bottom. The bug only belongs to the bottom dock. The top-panel never show above any fullscreen windows, and my former plasma panel (disabled after using latte top-panel) also behaved quite normally. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443536] Latte-dock wrongly appears before fullscreen window
https://bugs.kde.org/show_bug.cgi?id=443536 --- Comment #4 from crc --- Created attachment 142523 --> https://bugs.kde.org/attachment.cgi?id=142523&action=edit The option 'Can be above fullscreen windows' is already disabled but the bug remains -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443536] Latte-dock wrongly appears before fullscreen window
https://bugs.kde.org/show_bug.cgi?id=443536 crc changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #3 from crc --- (In reply to Michail Vourlakos from comment #2) > Disable from Behavior (advanced settings) - Can be above fullscreen windows Sorry I didn't give a clear description about the problem. I'm using the Chinese translated version and don't know the orginal English name of the option is 'Can be above fullscreen windows', so I wrongly discribed it as 'appear before full-screen window'. Anyway, the option 'Can be above fullscreen windows' is already disabled, but problem remains, latte-dock panel still appears before ksmserver-logout-greeter and Parachute. The bug occurs ONLY in these two fullscreen windows. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443536] Latte-dock wrongly appears before fullscreen window
https://bugs.kde.org/show_bug.cgi?id=443536 crc changed: What|Removed |Added CC||crc2...@126.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443536] Latte-dock wrongly appears before fullscreen window
https://bugs.kde.org/show_bug.cgi?id=443536 --- Comment #1 from crc --- Created attachment 142292 --> https://bugs.kde.org/attachment.cgi?id=142292&action=edit latte-dock panel appears before Parachute window -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443536] New: Latte-dock wrongly appears before fullscreen window
https://bugs.kde.org/show_bug.cgi?id=443536 Bug ID: 443536 Summary: Latte-dock wrongly appears before fullscreen window Product: lattedock Version: git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: crc2...@126.com Target Milestone: --- Created attachment 142291 --> https://bugs.kde.org/attachment.cgi?id=142291&action=edit latte-dock panel appears before ksmserver-logout-greeter window SUMMARY The dock panel of Latte-dock wrongly appears before certain full-screen windows in KDE Plasma, including the full-screen ksmserver-logout-greeter window and the virtual desktop interface of KWinScript Parachute, even though the "appear before full-screen window" option is disabled in latte-dock configuration. The problem seemingly occured right after plasma5.22 update. STEPS TO REPRODUCE 1. Check and confirm the "appear before full-screen window" option is disabled in latte-dock panel configuration. 2. Activate ksmserver-logout-greeter or Parachute. OBSERVED RESULT The dock panel of Latte-dock wrongly appears before the above two full-screen windows EXPECTED RESULT The dock panel should hide behind full-screen windows. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux Pahvo 21.1.5 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426112] Virtual Keyboard problems with lock screen
https://bugs.kde.org/show_bug.cgi?id=426112 crc changed: What|Removed |Added CC||crc2...@126.com Platform|Other |Manjaro --- Comment #4 from crc --- I encountered just the same problem after recent updates. Besides, the login button in the screenlocker UI is much smaller than before, almost thin as a line. My OS is also Manjaro Linux, with screen resolution 1920*1200. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 407139] kglobalaccel fails with QDBusObjectPath: invalid path "/component/vlc_bébé_desktop"
https://bugs.kde.org/show_bug.cgi?id=407139
--- Comment #9 from crc ---
(In reply to José Renan from comment #8)
> (In reply to crc from comment #7)
> > (In reply to crc from comment #6)
> > > (In reply to Christoph Feck from comment #4)
> > > > "é" is a Latin-1 character, but not ASCII. It needs an additional
> > > > ch.unicode() < 0x7F check.
> > >
> > > Having just the same problem in Kglobalaccel after adding a shortcut to a
> > > desktop file with chinese characters. Adding this additional check may
> > > solve
> > > it,but how can this be done?
> >
> > I finally solved the problem by adding the additonal check to the soucecode
> > of Kglobalaccel cloning from https://anongit.kde.org/kglobalaccel.git and
> > compiling it in my system, then created a soft link from the compiled
> > Kglobalaccel5 file to /usr/bin, it just worked fine. So this is certainly
> > proved to be at least a temporary solution for the problem, many thanks!!!
>
> Could you send a snippet with what exactly you added?
Sorry for replying late. I just modified Kglobalaccel source code in
src/runtime/component.cpp following your and Michael Pyne's suggestions. The
modification of component.cpp:203 is as follows:
QDBusObjectPath Component::dbusPath() const
{
QString dbusPath = _uniqueName;
const int len = dbusPath.length();
for ( int i = 0; i < len; ++i )
{
if ( !dbusPath[i].isLetterOrNumber()
|| dbusPath[i].unicode() >= 0x7F)
dbusPath[i] = QLatin1Char('_');
}
return QDBusObjectPath( _registry->dbusPath().path() + "component/" +
dbusPath);
}
I just add "dbusPath[i].unicode() >= 0x7F" check after the original
".isLetterOrNumber()" check, which will translate all international characters
to "_". I have to admit that I'm no program developer and only learned some
basic c++ during college time, so I'm not quit sure whether this adding is all
correct. But after this modification the compile progress went smoothly and the
complied Kglobalaccel5 run all fine on my Manjaro system, the bug never
appeared again, so I think this can prove that the check adding just works.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 407139] kglobalaccel fails with QDBusObjectPath: invalid path "/component/vlc_bébé_desktop"
https://bugs.kde.org/show_bug.cgi?id=407139 --- Comment #7 from crc --- (In reply to crc from comment #6) > (In reply to Christoph Feck from comment #4) > > "é" is a Latin-1 character, but not ASCII. It needs an additional > > ch.unicode() < 0x7F check. > > Having just the same problem in Kglobalaccel after adding a shortcut to a > desktop file with chinese characters. Adding this additional check may solve > it,but how can this be done? I finally solved the problem by adding the additonal check to the soucecode of Kglobalaccel cloning from https://anongit.kde.org/kglobalaccel.git and compiling it in my system, then created a soft link from the compiled Kglobalaccel5 file to /usr/bin, it just worked fine. So this is certainly proved to be at least a temporary solution for the problem, many thanks!!! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 407139] kglobalaccel fails with QDBusObjectPath: invalid path "/component/vlc_bébé_desktop"
https://bugs.kde.org/show_bug.cgi?id=407139 crc changed: What|Removed |Added CC||crc2...@126.com Version|5.57.0 |5.70.0 Status|REOPENED|CONFIRMED Platform|Other |Manjaro --- Comment #6 from crc --- (In reply to Christoph Feck from comment #4) > "é" is a Latin-1 character, but not ASCII. It needs an additional > ch.unicode() < 0x7F check. Having just the same problem in Kglobalaccel after adding a shortcut to a desktop file with chinese characters. Adding this additional check may solve it,but how can this be done? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 418465] New: latte-dock settings don't work after recent system update
https://bugs.kde.org/show_bug.cgi?id=418465 Bug ID: 418465 Summary: latte-dock settings don't work after recent system update Product: lattedock Version: 0.9.9 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: crc2...@126.com Target Milestone: --- Created attachment 126592 --> https://bugs.kde.org/attachment.cgi?id=126592&action=edit screenshot showing the abnormal right-click menu on dock SUMMARY After I run system and kernel update today, the configuration interface of latte-dock no longer works at all.The setting options just vanish in the right-click menus on the docked application icons, with the application options still there. And the option menu cannot be triggered directly by right-click on the docked icons, but have to press ctrl at the same time. Details can be seen on the attached screen-shot. STEPS TO REPRODUCE 1. press ctrl and right-click on the docked icons to trigger option menu 2. 3. OBSERVED RESULT latte-dock options cannot display on the right-click menu, and cannot call out configuration interface of the dock EXPECTED RESULT normal latte-dock option display on right-click menu, and normally run the dock configurations SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro 19.0.2 Kyria,linux kernel 5.5.7-1-manjaro (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION wayland is updated to version 1.18.0-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415662] New: Dismissing Pop-Up Notification Crashed Plasma
https://bugs.kde.org/show_bug.cgi?id=415662 Bug ID: 415662 Summary: Dismissing Pop-Up Notification Crashed Plasma Product: plasmashell Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cameron.r...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-24-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: Playing with panels. Added a blank panel on left of screen, and removed it. Panel was made transparent with 'Panel Transparency Button.' Panel was removed with GUI "Remove option." No issues. Plasma crashed when I dismissed the "Panel Removed: Undo?" notification by clicking on the 'X' dismiss button. Notification was displayed longer than the 5 second set time-out. No other foreground programs running. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa3b4fba880 (LWP 2179))] Thread 33 (Thread 0x7fa2f1578700 (LWP 10917)): #0 0x7fa3b7cdf2c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x5634448f31b4) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fa3b7cdf2c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5634448f3160, cond=0x5634448f3188) at pthread_cond_wait.c:508 #2 0x7fa3b7cdf2c6 in __pthread_cond_wait (cond=0x5634448f3188, mutex=0x5634448f3160) at pthread_cond_wait.c:638 #3 0x7fa3b885bdef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa3b885bee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa3ba6747b9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fa3ba674a1a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fa3b8855cc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa3b7cd8669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fa3b84da323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7fa2fa3c0700 (LWP 10876)): #0 0x7fa3b7cdf2c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x5634400f7b84) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fa3b7cdf2c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5634400f7b30, cond=0x5634400f7b58) at pthread_cond_wait.c:508 #2 0x7fa3b7cdf2c6 in __pthread_cond_wait (cond=0x5634400f7b58, mutex=0x5634400f7b30) at pthread_cond_wait.c:638 #3 0x7fa3b885bdef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa3b885bee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa3ba6747b9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fa3ba674a1a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fa3b8855cc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa3b7cd8669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fa3b84da323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7fa2f98c0700 (LWP 10272)): #0 0x7fa3b7cdf2c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x56343a161b84) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fa3b7cdf2c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56343a161b30, cond=0x56343a161b58) at pthread_cond_wait.c:508 #2 0x7fa3b7cdf2c6 in __pthread_cond_wait (cond=0x56343a161b58, mutex=0x56343a161b30) at pthread_cond_wait.c:638 #3 0x7fa3b885bdef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa3b885bee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa3ba6747b9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fa3ba674a1a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fa3b8855cc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa3b7cd8669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fa3b84da323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7fa355767700 (LWP 10268)): #0 0x7fa3b7cdf2c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x56343835dd90) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fa3b7cdf2c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56343835dd40, cond=0x56343835dd68) at pthread_cond_wait.c:508 #2 0x7fa3b7cdf2c6 in __pthread_cond_wait (cond=0x56343835dd68,
