[kdeconnect] [Bug 449534] KDEConnect crashes on startup
https://bugs.kde.org/show_bug.cgi?id=449534 qrest changed: What|Removed |Added CC||qr...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 449534] KDEConnect crashes on startup
https://bugs.kde.org/show_bug.cgi?id=449534 --- Comment #1 from qrest --- Created attachment 146700 --> https://bugs.kde.org/attachment.cgi?id=146700&action=edit New crash information added by DrKonqi kdeconnectd (21.12.2) using Qt 5.15.3 - What I was doing when the application crashed: KDEConnect Damon immediatly crashed after startup. This also happened pre plasma 5.24 -- Backtrace (Reduced): #4 0x7fa2e621adf4 in (anonymous namespace)::constData (d=...) at ../../include/QtCore/5.15.3/QtCore/private/../../../../../src/corelib/kernel/qmetatype_p.h:64 #5 qVariantToHelper > (handlerManager=..., d=...) at kernel/qvariant.cpp:2669 #6 QVariant::toMap (this=0x5608fe33ce48) at kernel/qvariant.cpp:2721 #7 0x7fa2d99bf681 in ConnectivityReportPlugin::receivePacket (this=0x5608fe2ff9a0, np=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:424 #8 0x7fa2e77f25e0 in Device::privateReceivedPacket (this=, np=...) at ./core/device.cpp:398 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 454197] New: Color formatting text left in firmware security view
https://bugs.kde.org/show_bug.cgi?id=454197 Bug ID: 454197 Summary: Color formatting text left in firmware security view Product: kinfocenter Version: 5.24.90 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Firmware Security Assignee: plasma-b...@kde.org Reporter: qr...@protonmail.com CC: sit...@kde.org Target Milestone: --- Created attachment 149100 --> https://bugs.kde.org/attachment.cgi?id=149100&action=edit color formatting text included in output SUMMARY If the UEFI firmware can not be updated the "Firmware Security" view in the Info Center shows some not-interpreted color formatting text. STEPS TO REPRODUCE 1. Open Info Center 2. Navigate to Devices -> Firmware Security 3. If firmware can not be updated it shows the text "WARNING: UEFI firmware can not be updated ..." including some color formatting text in front (see enclosed screenshot) OBSERVED RESULT Color formatting text included in output EXPECTED RESULT Text without the not-interpreted color formatting characters SOFTWARE/OS VERSIONS This is on the testing kde neon image (https://files.kde.org/neon/images/testing/20220520-1636/neon-testing-20220520-1636.iso) via a VirtualBox 6.1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443710] New: Small icons in Kickoff
https://bugs.kde.org/show_bug.cgi?id=443710 Bug ID: 443710 Summary: Small icons in Kickoff Product: plasmashell Version: 5.23.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: qr...@protonmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY With Wayland and 200% display scaling, the arrow icons of the application categories are very small. This is on a 3840x2400 pixel display. See enclosed screenshot STEPS TO REPRODUCE 1. Start Wayland session and set display scaling to 200% 2. Open Kickoff 3. Notice the tiny arrows OBSERVED RESULT tiny icons EXPECTED RESULT appropriate sized icons SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-37-generic (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443710] Small icons in Kickoff
https://bugs.kde.org/show_bug.cgi?id=443710 --- Comment #1 from qrest --- Created attachment 142427 --> https://bugs.kde.org/attachment.cgi?id=142427&action=edit small arrows in application categories -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443710] Small icons in Kickoff
https://bugs.kde.org/show_bug.cgi?id=443710 qrest changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from qrest --- nevermind, this was due to a custom plasma style -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431979] Firewall entry in System Settings crashes in KCMFirewall::KCMFirewall() when I change on/off in GUFW.
https://bugs.kde.org/show_bug.cgi?id=431979 --- Comment #6 from qrest --- Created attachment 135725 --> https://bugs.kde.org/attachment.cgi?id=135725&action=edit New crash information added by DrKonqi systemsettings5 (5.21.0) using Qt 5.15.2 Opened the firewall page in settings. After that switched to another non-firewall settings page -> crash -- Backtrace (Reduced): #4 0x7fcd60231e26 in FirewallClient::capabilities() const () at /usr/lib/x86_64-linux-gnu/libkcm_firewall_core.so [...] #7 0x7fcdd6f7c152 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) (this=this@entry=0x55cc5d8d1e90, iface=0x7fcdd846e0f0 "KQuickAddons::ConfigModule", parentWidget=parentWidget@entry=0x0, parent=parent@entry=0x0, args=..., keyword=...) at ./src/lib/plugin/kpluginfactory.cpp:180 #8 0x7fcdd858db48 in KPluginFactory::create(QObject*, QList const&) (args=..., parent=0x0, this=0x55cc5d8d1e90) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:257 #9 KCModuleLoader::loadModule(KCModuleInfo const&, KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) (mod=..., report=report@entry=KCModuleLoader::Inline, parent=0x55cc5df4fb60, args=...) at ./src/kcmoduleloader.cpp:94 #10 0x7fcdd85995aa in KCModuleProxyPrivate::loadModule() (this=this@entry=0x55cc5df105e0) at ./src/kcmoduleproxy.cpp:81 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431979] Firewall entry in System Settings crashes in KCMFirewall::KCMFirewall() when I change on/off in GUFW.
https://bugs.kde.org/show_bug.cgi?id=431979 qrest changed: What|Removed |Added CC||qr...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431375] Crash in ContainmentInterface::addContainmentActions() when right-clicking on desktop
https://bugs.kde.org/show_bug.cgi?id=431375 qrest changed: What|Removed |Added CC||qr...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433013] New System Monitor in 5.21 crashes on startup
https://bugs.kde.org/show_bug.cgi?id=433013 qrest changed: What|Removed |Added CC||qr...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 440999] New: Low resolution color filter icons
https://bugs.kde.org/show_bug.cgi?id=440999 Bug ID: 440999 Summary: Low resolution color filter icons Product: kdenlive Version: 21.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: qr...@protonmail.com Target Milestone: --- Created attachment 140738 --> https://bugs.kde.org/attachment.cgi?id=140738&action=edit Low resolution color filter icons SUMMARY The icons for the filter by color feature of the project bin have low resolution. STEPS TO REPRODUCE 1. Open Kdenlive 2. Locate the project bin view 3. Click on the filter button near the search menu 4. Notice the low resolution color icons compared to other icons OBSERVED RESULT Low resolution icons EXPECTED RESULT High resolution icons SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-25-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION see screenshot for example -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441007] New: Empty Page in Settings (PIM)
https://bugs.kde.org/show_bug.cgi?id=441007 Bug ID: 441007 Summary: Empty Page in Settings (PIM) Product: plasmashell Version: 5.22.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: qr...@protonmail.com Target Milestone: 1.0 Created attachment 140749 --> https://bugs.kde.org/attachment.cgi?id=140749&action=edit empty page in settings menu SUMMARY The settings window of the Digital Clock widget has an empty page. Under the "Calendar" tab there is also an empty option. I think that both the empty page and the empty option are related to the PIM settings STEPS TO REPRODUCE 1. Open the settings of Digital Clock 2. Notice that between the "Holidays" and "Keyboard Shortcuts" page there is a tab with no text and no icon 3. Click on empty tab 4. See nothing OBSERVED RESULT A empty page in the settings menu EXPECTED RESULT No empty page in the settings menu SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-25-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION see screenshots -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441007] Empty Page in Settings (PIM)
https://bugs.kde.org/show_bug.cgi?id=441007 --- Comment #1 from qrest --- Created attachment 140750 --> https://bugs.kde.org/attachment.cgi?id=140750&action=edit empty option in settings menu -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 440723] New: Latte Dock Crash when opening "Docks, Panels..."
https://bugs.kde.org/show_bug.cgi?id=440723 Bug ID: 440723 Summary: Latte Dock Crash when opening "Docks, Panels..." Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: qr...@protonmail.com Target Milestone: --- Application: latte-dock (0.10.0) Qt Version: 5.15.3 Frameworks Version: 5.84.0 Operating System: Linux 5.11.0-25-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: In the Latte Dock settings clicked on "Docks, Panels...", Latte crashed immediatly. This was done while having the "Edna" Dock selected. Latte restarted afterwards and I tried again, this time it did not crash. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #4 QString::QString(QString const&) (other=..., this=0x7fff14d8d370) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1093 #5 Latte::Data::Generic::Generic(Latte::Data::Generic const&) (this=0x7fff14d8d370, o=...) at ./app/data/genericdata.cpp:19 #6 0x5594a3375c65 in Latte::Data::Layout::Layout(Latte::Data::Layout const&) (this=0x7fff14d8d370, o=...) at ./app/data/layoutdata.cpp:42 #7 0x5594a33f6bc1 in Latte::Settings::Controller::Layouts::setLayoutCurrentErrorsWarnings(QString const&, int const&, int const&) (this=0x5594a7845930, layoutCurrentId=..., errors=@0x7fff14d8d588: 0, warnings=@0x7fff14d8d58c: 0) at ./app/settings/settingsdialog/layoutscontroller.cpp:730 #8 0x5594a342bedf in Latte::Settings::Controller::Views::messagesForErrorsWarnings(Latte::CentralLayout const*, bool const&) (this=this@entry=0x5594ac07ca80, centralLayout=centralLayout@entry=0x5594a8141060, showNoErrorsMessage=@0x7fff14d8d620: false) at ./app/settings/viewsdialog/viewscontroller.cpp:575 Possible duplicates by query: bug 82199, bug 429973, bug 424760, bug 410345, bug 409383. Reported using DrKonqi This report was filed against 'kde' because the product 'latte-dock' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 440723] Latte Dock Crash when opening "Docks, Panels..."
https://bugs.kde.org/show_bug.cgi?id=440723 --- Comment #1 from qrest --- Created attachment 140584 --> https://bugs.kde.org/attachment.cgi?id=140584&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 440770] New: Latte Dock crashes on startup
https://bugs.kde.org/show_bug.cgi?id=440770 Bug ID: 440770 Summary: Latte Dock crashes on startup Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: qr...@protonmail.com Target Milestone: --- Application: latte-dock (0.10.0) Qt Version: 5.15.3 Frameworks Version: 5.84.0 Operating System: Linux 5.11.0-25-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: Latte Dock crashes on auto startup (login). Starting Latte manually produces no crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [New LWP 4799] [New LWP 4805] [New LWP 4815] [New LWP 4816] [New LWP 4817] [New LWP 4818] [New LWP 4819] [New LWP 4820] [New LWP 4821] [New LWP 4822] [New LWP 4823] [New LWP 4824] [New LWP 4825] [New LWP 4826] [New LWP 4827] [New LWP 4828] [New LWP 4829] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f2c4dce8aff in __GI___poll (fds=0x7ffd83f25578, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f2c4a15a9c0 (LWP 4797))] Thread 18 (Thread 0x7f2c14ff9700 (LWP 4829)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55560c278a08) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55560c2789b8, cond=0x55560c2789e0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55560c2789e0, mutex=0x55560c2789b8) at pthread_cond_wait.c:647 #3 0x7f2c41e1c84b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f2c41e1c44b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f2c4d3dd609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f2c4dcf5293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f2c157fa700 (LWP 4828)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55560c278a08) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55560c2789b8, cond=0x55560c2789e0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55560c2789e0, mutex=0x55560c2789b8) at pthread_cond_wait.c:647 #3 0x7f2c41e1c84b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f2c41e1c44b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f2c4d3dd609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f2c4dcf5293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f2c15ffb700 (LWP 4827)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55560c278a08) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55560c2789b8, cond=0x55560c2789e0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55560c2789e0, mutex=0x55560c2789b8) at pthread_cond_wait.c:647 #3 0x7f2c41e1c84b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f2c41e1c44b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f2c4d3dd609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f2c4dcf5293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f2c167fc700 (LWP 4826)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55560c278a08) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55560c2789b8, cond=0x55560c2789e0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55560c2789e0, mutex=0x55560c2789b8) at pthread_cond_wait.c:647 #3 0x7f2c41e1c84b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f2c41e1c44b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f2c4d3dd609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f2c4dcf5293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f2c16ffd700 (LWP 4825)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55560c278300) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55560c2782b0, cond=0x55560c2782d8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55560c2782d8, mutex=0x55560c2782b0) at pthread_cond_wait.c:647 #3 0x7f2c41e1c84b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f2c41e1c44b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f2c4d3dd609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f
[plasmashell] [Bug 438296] ssh-agent not started on startup under wayland
https://bugs.kde.org/show_bug.cgi?id=438296 --- Comment #2 from qrest --- That is exactly the point. I should not have to start the ssh-agent manually. It should be started automatically without a script created by a user. This is how it works with X11. "xinit handles launching ssh-agent for plasma" - https://bugzilla.redhat.com/show_bug.cgi?id=1761817 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438296] ssh-agent systemd service not working under wayland
https://bugs.kde.org/show_bug.cgi?id=438296 --- Comment #4 from qrest --- Created attachment 139325 --> https://bugs.kde.org/attachment.cgi?id=139325&action=edit ssh-agent_process_tree -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438296] ssh-agent systemd service not working under wayland
https://bugs.kde.org/show_bug.cgi?id=438296 --- Comment #5 from qrest --- The ssh-agent systemd service is not present on my system (not on X11 and not on wayland). I use KDE neon. I only added the redhat links as potential solution for the problem. The attached screenshot shows that ssh-agent is started by startplasma-x11 on my system, the same is not true on wayland: startplasma-wayland does not start ssh-agent. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439087] New: Action button overflow
https://bugs.kde.org/show_bug.cgi?id=439087 Bug ID: 439087 Summary: Action button overflow Product: Discover Version: 5.22.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: qr...@protonmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 139624 --> https://bugs.kde.org/attachment.cgi?id=139624&action=edit button of first item in list view overflows SUMMARY The action buttons in discovers list view overflow STEPS TO REPRODUCE 1. open discover 2. search for something which is directly installable from the package manger (non-snap, non-flatpak) e.g. "v4l", and thus has a long button text 3. maximize the window 4. click on one of the items in the list view so the discover menu, the list view and the items detail view are visible 5. notice that the action button with the text "Install from KDE neon User Edition 5.22" in the list view overflows to the right. The attached image shows an example. OBSERVED RESULT action button is partially hidden EXPECTED RESULT action is fully visible Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-59-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439396] New: Crash on exit
https://bugs.kde.org/show_bug.cgi?id=439396 Bug ID: 439396 Summary: Crash on exit Product: Discover Version: 5.22.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: qr...@protonmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.22.2) Qt Version: 5.15.3 Frameworks Version: 5.83.0 Operating System: Linux 5.8.0-59-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.2 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: Started Discover and exited immediatly. Crash is reproducible for me. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [New LWP 27065] [New LWP 27089] [New LWP 27091] [New LWP 27095] [New LWP 27114] [New LWP 27125] [New LWP 27149] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fb35cba0aff in __GI___poll (fds=0x7ffd81636b78, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fb35856fe40 (LWP 27062))] Thread 8 (Thread 0x7fb2eb65a700 (LWP 27149)): #0 0x7fb35cba0aff in __GI___poll (fds=0x7fb2bc0ecca0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb35b52936e in g_main_context_poll (priority=, n_fds=1, fds=0x7fb2bc0ecca0, timeout=, context=0x7fb2be764200) at ../../../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7fb2be764200, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4042 #3 0x7fb35b5294a3 in g_main_context_iteration (context=0x7fb2be764200, may_block=1) at ../../../glib/gmain.c:4108 #4 0x7fb2c63ec99d in () at /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #5 0x7fb35b552ad1 in g_thread_proxy (data=0x7fb2b1ae26a0) at ../../../glib/gthread.c:807 #6 0x7fb35bf85609 in start_thread (arg=) at pthread_create.c:477 #7 0x7fb35cbad293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fb2a8ffb700 (LWP 27125)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fb35b576746 in g_cond_wait_until (cond=cond@entry=0x561b95e1bab8, mutex=mutex@entry=0x561b95e1bab0, end_time=end_time@entry=5745143791) at ../../../glib/gthread-posix.c:1588 #2 0x7fb35b4f9581 in g_async_queue_pop_intern_unlocked (queue=queue@entry=0x561b95e1bab0, wait=wait@entry=1, end_time=end_time@entry=5745143791) at ../../../glib/gasyncqueue.c:422 #3 0x7fb35b4f9ba6 in g_async_queue_timeout_pop (queue=0x561b95e1bab0, timeout=timeout@entry=1500) at ../../../glib/gasyncqueue.c:545 #4 0x7fb35b553419 in g_thread_pool_wait_for_new_pool () at ../../../glib/gthreadpool.c:183 #5 g_thread_pool_thread_proxy (data=) at ../../../glib/gthreadpool.c:411 #6 0x7fb35b552ad1 in g_thread_proxy (data=0x7fb270006b60) at ../../../glib/gthread.c:807 #7 0x7fb35bf85609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb35cbad293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fb2c58cf700 (LWP 27114)): #0 0x7fb35b52875b in g_main_context_prepare (context=context@entry=0x7fb288000c20, priority=priority@entry=0x7fb2c58ceae0) at ../../../glib/gmain.c:3547 #1 0x7fb35b52929b in g_main_context_iterate (context=context@entry=0x7fb288000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4027 #2 0x7fb35b5294a3 in g_main_context_iteration (context=0x7fb288000c20, may_block=may_block@entry=1) at ../../../glib/gmain.c:4108 #3 0x7fb35d16df5b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fb288000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fb35d1121eb in QEventLoop::exec(QFlags) (this=this@entry=0x7fb2c58cec20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7fb35cf2bbb2 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7fb35cf2cd4c in QThreadPrivate::start(void*) (arg=0x561b95adb210) at thread/qthread_unix.cpp:329 #7 0x7fb35bf85609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb35cbad293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fb2e90fa700 (LWP 27095)): #0 0x7fb35cba0aff in __GI___poll (fds=0x7fb2c8006f20, nfds=1, timeout=120640) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb35b52936e in g_main_context_poll (priority=, n_fds=1, fds=0x7fb2c8006f20, timeout=, context=0x7fb2c8000c20) at ../../../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7fb2c8000c20, block=block@entry=1, dispa
[kdeconnect] [Bug 427917] New: Crash on send tab notification from firefox
https://bugs.kde.org/show_bug.cgi?id=427917 Bug ID: 427917 Summary: Crash on send tab notification from firefox Product: kdeconnect Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: qr...@protonmail.com Target Milestone: --- Application: kdeconnectd (1.4.0) Qt Version: 5.15.0 Frameworks Version: 5.75.0 Operating System: Linux 5.4.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: Firefox received a tab via the Firefox Sync feature. This caused a desktop notification to appear, which in turn caused KDE Connect to crash. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [New LWP 3946] [New LWP 3969] [New LWP 3976] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f9cb7ac7aff in __GI___poll (fds=0x7ffd77bc12e8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f9cb4473800 (LWP 3939))] Thread 4 (Thread 0x7f9cabfff700 (LWP 3976)): #0 0x7f9cb66bc09d in g_source_ref () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9cb66bc168 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9cb66bd66b in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9cb66be0db in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9cb66be2e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9cb8091eab in QEventDispatcherGlib::processEvents (this=0x7f9cab60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f9cb80361bb in QEventLoop::exec (this=this@entry=0x7f9cabffeda0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7f9cb7e54082 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7f9cb7e5520c in QThreadPrivate::start (arg=0x55fb1caf2330) at thread/qthread_unix.cpp:342 #9 0x7f9cb7020609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f9cb7ad4293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f9cb1a02700 (LWP 3969)): #0 __GI___libc_read (nbytes=16, buf=0x7f9cb1a01b60, fd=7) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=7, buf=0x7f9cb1a01b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f9cb670689f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9cb66bdcfe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9cb66be152 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9cb66be2e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f9cb8091eab in QEventDispatcherGlib::processEvents (this=0x7f9ca4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f9cb80361bb in QEventLoop::exec (this=this@entry=0x7f9cb1a01d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7f9cb7e54082 in QThread::exec (this=this@entry=0x7f9cb83c1d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7f9cb833ef2b in QDBusConnectionManager::run (this=0x7f9cb83c1d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #10 0x7f9cb7e5520c in QThreadPrivate::start (arg=0x7f9cb83c1d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:342 #11 0x7f9cb7020609 in start_thread (arg=) at pthread_create.c:477 #12 0x7f9cb7ad4293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f9cb379e700 (LWP 3946)): #0 0x7f9cb7ac7aff in __GI___poll (fds=0x7f9cb379dca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9cb63dec1a in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f9cb63e090a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f9cb3d85978 in QXcbEventQueue::run (this=0x55fb1c940950) at qxcbeventqueue.cpp:228 #4 0x7f9cb7e5520c in QThreadPrivate::start (arg=0x55fb1c940950) at thread/qthread_unix.cpp:342 #5 0x7f9cb7020609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f9cb7ad4293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f9cb4473800 (LWP 3939)): [KCrash Handler] #4 0x7f9cb7ed9028 in QStringView::QStringView (str=..., this=) at ../../include/QtCore/../../src/corelib/text/qstringview.h:209 #5 operator< (s1=..
[plasmashell] [Bug 431375] New: Crash when right clicking on desktop
https://bugs.kde.org/show_bug.cgi?id=431375 Bug ID: 431375 Summary: Crash when right clicking on desktop Product: plasmashell Version: 5.20.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: qr...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.20.5) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.4.0-60-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: I wanted to change the desktop background so I right clicked on the desktop to bring up the context menu. As the context menu did not appear I continued to repeatedly right click on it until it went black (crashed?) and then reloaded the background picture. Afer that the context menu worked again as expected. - Additional information: In the same session, a few hours before, I change the background from "Slideshow" to "Image". -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 4073] [New LWP 4079] [New LWP 4156] [New LWP 4717] [New LWP 4718] [New LWP 4719] [New LWP 4720] [New LWP 4721] [New LWP 4722] [New LWP 4723] [New LWP 4724] [New LWP 4725] [New LWP 4726] [New LWP 4727] [New LWP 4728] [New LWP 4729] [New LWP 4730] [New LWP 4731] [New LWP 4875] [New LWP 4876] [New LWP 4877] [New LWP 4878] [New LWP 4879] [New LWP 12289] [New LWP 12290] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fd61f941aff in __GI___poll (fds=0x7ffd4eedc868, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fd61bba32c0 (LWP 4065))] Thread 26 (Thread 0x7fd5b0d56700 (LWP 12290)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x559d628afa64) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x559d628afa10, cond=0x559d628afa38) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x559d628afa38, mutex=0x559d628afa10) at pthread_cond_wait.c:638 #3 0x7fd61fcd4d1b in QWaitConditionPrivate::wait (deadline=..., this=0x559d628afa10) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=this@entry=0x559d62bbec58, mutex=mutex@entry=0x559d62bbec50, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fd621a6e814 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x559d62bbec48) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x559d62bbebb0) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7fd621a6ec89 in QSGRenderThread::run (this=0x559d62bbebb0) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7fd61fccebac in QThreadPrivate::start (arg=0x559d62bbebb0) at thread/qthread_unix.cpp:329 #9 0x7fd61ed33609 in start_thread (arg=) at pthread_create.c:477 #10 0x7fd61f94e293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7fd5b1557700 (LWP 12289)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x559d62bf9df0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x559d62bf9da0, cond=0x559d62bf9dc8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x559d62bf9dc8, mutex=0x559d62bf9da0) at pthread_cond_wait.c:638 #3 0x7fd60a4c261b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fd60a4c221b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fd61ed33609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fd61f94e293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fd5b37fe700 (LWP 4879)): #0 0x7fd61e272c74 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd61e273152 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd61e2732e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd61ff0efbb in QEventDispatcherGlib::processEvents (this=0x7fd5ab60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fd61feb31ab in QEventLoop::exec (this=this@entry=0x7fd5b37fdca0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7fd61fccda12 in QThread::exec (this=this@entry=0x559d629b3030) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7fd6219a938a in QQuickPixmapReader::run (this=0x559d629b3030) at util/qquickpixmapcache.cpp:1024 #7 0x7fd61fccebac in QThreadPrivate::start (arg=0x559d629b3030) at thread/qthread_unix.cpp:329 #8 0x7fd61ed3360
[plasma-systemmonitor] [Bug 438276] New: System Monitor crashes on exit
https://bugs.kde.org/show_bug.cgi?id=438276 Bug ID: 438276 Summary: System Monitor crashes on exit Product: plasma-systemmonitor Version: 5.22.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: qr...@protonmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- The new plasma system monitor crashes every time when I close it. Also happened with plasma 5.21. Btw, the crash handler does not support to report system monitor crashes directly, I get "This application is not supporetd in the KDE bug tracking system" Application: plasma-systemmonitor (5.22.0) Qt Version: 5.15.3 Frameworks Version: 5.82.0 Operating System: Linux 5.8.0-55-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.0 Distribution: KDE neon User Edition 5.22 -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [New LWP 7881] [New LWP 7882] [New LWP 7883] [New LWP 7884] [New LWP 7885] [New LWP 7886] [New LWP 7887] [New LWP 7888] [New LWP 7889] [New LWP 7890] [New LWP 7891] [New LWP 7892] [New LWP 7893] [New LWP 7894] [New LWP 7895] [New LWP 7896] [New LWP 7897] [New LWP 7905] [New LWP 11681] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f38540e0aff in __GI___poll (fds=0x7fff78e115a8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f384ffa38c0 (LWP 7879))] Thread 20 (Thread 0x7f37e8afa700 (LWP 11681)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f37e8af9c50, clockid=, expected=0, futex_word=0x55a36e8e6cb0) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f37e8af9c50, clockid=, mutex=0x55a36e8e6c60, cond=0x55a36e8e6c88) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x55a36e8e6c88, mutex=0x55a36e8e6c60, abstime=0x7f37e8af9c50) at pthread_cond_wait.c:665 #3 0x7f3854471e48 in QWaitConditionPrivate::wait_relative (this=0x55a36e8e6c60, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x55a36e8e6c60) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x55a36e9032c0, mutex=mutex@entry=0x55a36ce81cf8, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7f385446f351 in QThreadPoolThread::run (this=0x55a36e9032b0) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7f385446bd4c in QThreadPrivate::start (arg=0x55a36e9032b0) at thread/qthread_unix.cpp:329 #8 0x7f385362f609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f38540ed293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f37ebfff700 (LWP 7905)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f37ebffec50, clockid=, expected=0, futex_word=0x55a36cea65b0) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f37ebffec50, clockid=, mutex=0x55a36cea6560, cond=0x55a36cea6588) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x55a36cea6588, mutex=0x55a36cea6560, abstime=0x7f37ebffec50) at pthread_cond_wait.c:665 #3 0x7f3854471e48 in QWaitConditionPrivate::wait_relative (this=0x55a36cea6560, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x55a36cea6560) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x55a36ce806e0, mutex=mutex@entry=0x55a36ce81cf8, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7f385446f351 in QThreadPoolThread::run (this=0x55a36ce806d0) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7f385446bd4c in QThreadPrivate::start (arg=0x55a36ce806d0) at thread/qthread_unix.cpp:329 #8 0x7f385362f609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f38540ed293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f38197fa700 (LWP 7897)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55a36c5c83e8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a36c5c8398, cond=0x55a36c5c83c0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55a36c5c83c0, mutex=0x55a36c5c8398) at pthread_cond_wait.c:647 #3 0x7f38466215db in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f38466211db in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f385362f609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f38540ed293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f3819ffb700 (LWP 7896)): #0 futex
[Discover] [Bug 438278] New: Discover crashes when searching for Plasma Addons
https://bugs.kde.org/show_bug.cgi?id=438278 Bug ID: 438278 Summary: Discover crashes when searching for Plasma Addons Product: Discover Version: 5.22.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: qr...@protonmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.22.0) Qt Version: 5.15.3 Frameworks Version: 5.82.0 Operating System: Linux 5.8.0-55-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.0 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: Clicked on "Plasma Addons" -> "Aurorae Window Decorations". After a few seconds Discover crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [New LWP 16078] [New LWP 16079] [New LWP 16080] [New LWP 16081] [New LWP 16082] [New LWP 16083] [New LWP 16084] [New LWP 16085] [New LWP 16086] [New LWP 16087] [New LWP 16088] [New LWP 16089] [New LWP 16090] [New LWP 16091] [New LWP 16092] [New LWP 16093] [New LWP 16095] [New LWP 16102] [New LWP 16104] [New LWP 16106] [New LWP 16107] [New LWP 16117] [New LWP 16118] [New LWP 16121] [New LWP 16156] [New LWP 16178] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f1295fabaff in __GI___poll (fds=0x7ffd102b7a68, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f12919d8980 (LWP 16075))] Thread 27 (Thread 0x7f11fdbfb700 (LWP 16178)): #0 g_source_ref (source=0x7f11c8004100) at ../../../glib/gmain.c:2166 #1 0x7f1294873328 in g_source_iter_next (iter=iter@entry=0x7f11fdbfaa20, source=source@entry=0x7f11fdbfaa18) at ../../../glib/gmain.c:1046 #2 0x7f129487482b in g_main_context_prepare (context=context@entry=0x7f11c8005ca0, priority=priority@entry=0x7f11fdbfaaa0) at ../../../glib/gmain.c:3597 #3 0x7f129487529b in g_main_context_iterate (context=context@entry=0x7f11c8005ca0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4027 #4 0x7f12948754a3 in g_main_context_iteration (context=0x7f11c8005ca0, may_block=may_block@entry=1) at ../../../glib/gmain.c:4108 #5 0x7f1296577b3b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f11c8007720, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f129651bdcb in QEventLoop::exec(QFlags) (this=this@entry=0x7f11fdbfabe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7f1296335bb2 in QThread::exec() (this=this@entry=0x55ee4b557340) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7f129809d3ba in QQuickPixmapReader::run() (this=0x55ee4b557340) at util/qquickpixmapcache.cpp:1024 #9 0x7f1296336d4c in QThreadPrivate::start(void*) (arg=0x55ee4b557340) at thread/qthread_unix.cpp:329 #10 0x7f12952d1609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f1295fb8293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f11e9297700 (LWP 16156)): #0 g_main_context_iterate (context=context@entry=0x7f11d08b4200, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4016 #1 0x7f12948754a3 in g_main_context_iteration (context=0x7f11d08b4200, may_block=1) at ../../../glib/gmain.c:4108 #2 0x7f122662b99d in () at /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #3 0x7f129489ead1 in g_thread_proxy (data=0x7f11f5a8f700) at ../../../glib/gthread.c:807 #4 0x7f12952d1609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f1295fb8293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f11ea098700 (LWP 16121)): #0 0x7f1295fabaff in __GI___poll (fds=0x7f11d400dc90, nfds=1, timeout=42485) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f129487536e in g_main_context_poll (priority=, n_fds=1, fds=0x7f11d400dc90, timeout=, context=0x7f11d4000c20) at ../../../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7f11d4000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4042 #3 0x7f12948754a3 in g_main_context_iteration (context=0x7f11d4000c20, may_block=may_block@entry=1) at ../../../glib/gmain.c:4108 #4 0x7f1296577b3b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f11d4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f129651bdcb in QEventLoop::exec(QFlags) (this=this@entry=0x7f11ea097c20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f1296335bb2 in QThread::exec() (this=) at ../../include/QtCore/../../sr
[plasmashell] [Bug 438296] New: ssh-agent not started on startup under wayland
https://bugs.kde.org/show_bug.cgi?id=438296 Bug ID: 438296 Summary: ssh-agent not started on startup under wayland Product: plasmashell Version: 5.22.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: qr...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Under wayland, ssh-agent is not started automatically on startup. This works on X11. Potential solutions: - Fedora added a patch to openssh-client to create a systemd service: https://bugzilla.redhat.com/show_bug.cgi?id=1761817 - some startup scripts: https://forum.kde.org/viewtopic.php?f=309&t=153769 Older discussion: https://bugs.kde.org/show_bug.cgi?id=380311 https://bugs.kde.org/show_bug.cgi?id=44177 STEPS TO REPRODUCE 1. Start a wayland session 2. notice that $SSH_AUTH_SOCK is not set OBSERVED RESULT ssh-agent needs to be started manually. EXPECTED RESULT ssh-agent is running on startup by default without user interaction. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433025] System Settings crashes when firewall page opened second time.
https://bugs.kde.org/show_bug.cgi?id=433025 --- Comment #15 from qrest --- maybe change the status to "open" to avoid getting duplicate bug reports. The bug is clearly not fixed yet. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434659] New: Frequently used items become unusable
https://bugs.kde.org/show_bug.cgi?id=434659 Bug ID: 434659 Summary: Frequently used items become unusable Product: systemsettings Version: 5.21.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: qr...@protonmail.com Target Milestone: --- SUMMARY The items/links presented under "Frequently Used" on the initial page of the system settings can become unusable. STEPS TO REPRODUCE 1. Open system settings 2. Notice the "Frequently Used" section with items like "Global Theme" or "Audio" 3. Click on one of the items for example "Audio" 4. Now the audio page is loaded 5. Click on the "Home" button on the top left (near the search bar) so you get back to the previous screen where you can see the "Frequently Used" items. 5. Click the SAME item again, in this example "Audio" 6. Notice that nothing happens. Other items still work fine. OBSERVED RESULT The previously used item becomes unusable. EXPECTED RESULT I can use the same item multiple times. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.8.0-45-generic OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415114] Crash when selecting on desktop and wallpaper changes at the same time
https://bugs.kde.org/show_bug.cgi?id=415114 --- Comment #4 from qrest --- I tried to reproduce it again but could not. Seems to be fixed. Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.8.0-48-generic OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433025] System Settings crashes when firewall page opened second time.
https://bugs.kde.org/show_bug.cgi?id=433025 qrest changed: What|Removed |Added CC||qr...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 432843] Include the nextcloud-desktop package in the repo OR implement full support for the PPA version
https://bugs.kde.org/show_bug.cgi?id=432843 qrest changed: What|Removed |Added CC||qr...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 qrest changed: What|Removed |Added CC||qr...@protonmail.com --- Comment #8 from qrest --- I have the same problem with kdeconnect, isMounted and mountAndWait return both true. But I found that executing the command with getDirectories gives me the correct path all mounted directories of the devices (/run/user/1000//storage/emulated/0). I'm also able to access the directories and modify files in it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412977] New: Desktop Folder Settings crash after applying changes
https://bugs.kde.org/show_bug.cgi?id=412977 Bug ID: 412977 Summary: Desktop Folder Settings crash after applying changes Product: plasmashell Version: 5.17.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: qr...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: In "Desktop Folder Settings" changed the time period for the slideshow The crash can be reproduced sometimes. -- 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 0x7fbb72a7a800 (LWP 3374))] Thread 25 (Thread 0x7fbad5bdc700 (LWP 15018)): #0 0x7fbb697ed9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55bdc60445d4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55bdc6044580, cond=0x55bdc60445a8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55bdc60445a8, mutex=0x55bdc6044580) at pthread_cond_wait.c:655 #3 0x7fbb6c8bcb0b in QWaitConditionPrivate::wait (deadline=..., this=0x55bdc6044580) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x7fbad0029ef0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fbb6c8bce19 in QWaitCondition::wait (this=0x7fbad0029ef8, mutex=0x7fbad0029ef0, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7fbb708dbec8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fbb708dc2fa in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fbb6c8b5b72 in QThreadPrivate::start (arg=0x7fbad0029e70) at thread/qthread_unix.cpp:360 #9 0x7fbb697e76db in start_thread (arg=0x7fbad5bdc700) at pthread_create.c:463 #10 0x7fbb6c1b288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fbad65e1700 (LWP 15017)): #0 0x7fbb697ed9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55bdc5c7bf8c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55bdc5c7bf38, cond=0x55bdc5c7bf60) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55bdc5c7bf60, mutex=0x55bdc5c7bf38) at pthread_cond_wait.c:655 #3 0x7fbb4cf893bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fbb4cf88fc7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fbb697e76db in start_thread (arg=0x7fbad65e1700) at pthread_create.c:463 #6 0x7fbb6c1b288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fbaebeac700 (LWP 15014)): #0 0x7fbb660defec in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fbb660df570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbb660df6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbb6caf89db in QEventDispatcherGlib::processEvents (this=0x7fbaeb20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fbb6ca98eaa in QEventLoop::exec (this=this@entry=0x7fbaebeabd80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fbb6c8b43ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fbb70382cb5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fbb6c8b5b72 in QThreadPrivate::start (arg=0x55bdc59b5fa0) at thread/qthread_unix.cpp:360 #8 0x7fbb697e76db in start_thread (arg=0x7fbaebeac700) at pthread_create.c:463 #9 0x7fbb6c1b288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7fbae9f02700 (LWP 5560)): #0 0x7fbb697ed9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fbb5000c834) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fbb5000c7e0, cond=0x7fbb5000c808) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fbb5000c808, mutex=0x7fbb5000c7e0) at pthread_cond_wait.c:655 #3 0x7fbb6c8bcb0b in QWaitConditionPrivate::wait (deadline=..., this=0x7fbb5000c7e0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55bdc57afd60, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fbb6c8bce19 in QWaitCondition::wait (this=0x55bdc57afd68, mutex=0x55bdc57afd60, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7fbb708dbec8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fbb708dc2fa in ?? () from /usr/lib/x86_64-linux-gnu/
[systemsettings] [Bug 412132] New: Crash when switching global theme
https://bugs.kde.org/show_bug.cgi?id=412132 Bug ID: 412132 Summary: Crash when switching global theme Product: systemsettings Version: 5.16.90 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: qr...@protonmail.com Target Milestone: --- Application: systemsettings5 (5.16.90) Qt Version: 5.12.3 Frameworks Version: 5.63.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: KDE neon Testing Edition -- Information about the crash: When changing from the default global theme to "Breeze Dark" the System Settings crashed. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb61ed44800 (LWP 1215))] Thread 9 (Thread 0x7fb5ce737700 (LWP 1232)): #0 0x7fb61a294bf9 in __GI___poll (fds=0x7fb5c8004e00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb61371a5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb61371a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb61abd7dcb in QEventDispatcherGlib::processEvents (this=0x7fb5c8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fb61ab7903a in QEventLoop::exec (this=this@entry=0x7fb5ce736d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fb61a9a04ca in QThread::exec (this=this@entry=0x55b8c644c2f0) at thread/qthread.cpp:531 #6 0x7fb618759115 in QQmlThreadPrivate::run (this=0x55b8c644c2f0) at qml/ftw/qqmlthread.cpp:148 #7 0x7fb61a9a1c72 in QThreadPrivate::start (arg=0x55b8c644c2f0) at thread/qthread_unix.cpp:361 #8 0x7fb615ad96db in start_thread (arg=0x7fb5ce737700) at pthread_create.c:463 #9 0x7fb61a2a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fb5d68c7700 (LWP 1225)): #0 0x7fb61a2900b4 in __GI___libc_read (fd=13, buf=0x7fb5d68c6b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fb61375f2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb61371a0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb61371a570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb61371a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb61abd7dcb in QEventDispatcherGlib::processEvents (this=0x7fb5db20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fb61ab7903a in QEventLoop::exec (this=this@entry=0x7fb5d68c6d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fb61a9a04ca in QThread::exec (this=this@entry=0x55b8c4ed7460) at thread/qthread.cpp:531 #8 0x7fb618759115 in QQmlThreadPrivate::run (this=0x55b8c4ed7460) at qml/ftw/qqmlthread.cpp:148 #9 0x7fb61a9a1c72 in QThreadPrivate::start (arg=0x55b8c4ed7460) at thread/qthread_unix.cpp:361 #10 0x7fb615ad96db in start_thread (arg=0x7fb5d68c7700) at pthread_create.c:463 #11 0x7fb61a2a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fb5df325700 (LWP 1224)): #0 0x7fb61a2900b4 in __GI___libc_read (fd=12, buf=0x7fb5df324b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fb61375f2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb61371a0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb61371a570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb61371a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb61abd7dcb in QEventDispatcherGlib::processEvents (this=0x7fb5d8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fb61ab7903a in QEventLoop::exec (this=this@entry=0x7fb5df324d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fb61a9a04ca in QThread::exec (this=this@entry=0x55b8c4c61250) at thread/qthread.cpp:531 #8 0x7fb618759115 in QQmlThreadPrivate::run (this=0x55b8c4c61250) at qml/ftw/qqmlthread.cpp:148 #9 0x7fb61a9a1c72 in QThreadPrivate::start (arg=0x55b8c4c61250) at thread/qthread_unix.cpp:361 #10 0x7fb615ad96db in start_thread (arg=0x7fb5df325700) at pthread_create.c:463 #11 0x7fb61a2a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fb5f5421700 (LWP 1222)): #0 0x7fb615adf9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b8c4b37d5c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b8c4b37d08, cond=0x55b8c4b37d30) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b8c4b37d30, mutex=0x55b8c4b37d08) at pthre
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 qrest changed: What|Removed |Added CC||qr...@protonmail.com --- Comment #4 from qrest --- I have the same problem. For me it only occurs if 'Zoom on hover' is set. Without zoom the applications launch as they should. Happened after the KDE Frameworks update to 5.55.0. Today's update to latte-dock 0.8.6 did not fix the problem. Software versions are the same as from OP: Linux/KDE Plasma: KDE Neon KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Latte-Dock: 0.8.6 (also occurs on 0.8.5) -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #8 from qrest --- 1. For all applications 2. No 3. No -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428
--- Comment #13 from qrest ---
I am using the 'Dock And TopBar' layout: https://store.kde.org/p/1221421
[warning 15:54:29.234234] -- [warning 15:54:42.724724] happens when the upper
half of the icon is clicked (working). When the lower half is clicked I get no
output. The output after that was produced when latte-dock was closed (via
CTRL+C).
'latte-dock -d --graphics' output:
[warning 15:54:17.242242] - "spotify" doesn't have any WindowType, assuming as
NET::Normal
[debug 15:54:17.245245] - package is valid true
[debug 15:54:17.245245] - connector : "DisplayPort-1" - "10"
[debug 15:54:17.245245] - Known Screen - "DisplayPort-1" - 10
[debug 15:54:17.246246] - connector : "HDMI-0" - "11"
[debug 15:54:17.246246] - Known Screen - "HDMI-0" - 11
[debug 15:54:17.246246] - connector : "DisplayPort-2" - "12"
[debug 15:54:17.246246] - Known Screen - "DisplayPort-2" - 12
[debug 15:54:17.246246] - connector : "HDMI-A-0" - "13"
[debug 15:54:17.246246] - Known Screen - "HDMI-A-0" - 13
[debug 15:54:17.246246] - Latte::DockCorona the package
QJsonObject({"KPlugin":{"Authors":[{"Email":"mvourla...@gmail.com,
audo...@openmailbox.org","Name":"Michail Vourlakos, Smith
Ar"}],"Description":"Shell provided for the Latte
Dock","Description[ca@valencia]":"Intèrpret d'ordres proporcionat pel Latte
Dock","Description[ca]":"Intèrpret d'ordres proporcionat pel Latte
Dock","Description[da]":"Skal til Latte-dokken","Description[de]":"Shell für
Latte-Dock","Description[el]":"Κέλυφος που παρέχεται από την εφαρμογή
Latte","Description[en_GB]":"Shell provided for the Latte
Dock","Description[es]":"Shell proporcionada para Latte
Dock","Description[eu]":"Shell-a Latte
Dockentzat","Description[fi]":"Latte-telakalle tarjottu
käyttöliittymä","Description[gl]":"Intérprete de ordes fornecido para a doca
Latte.","Description[it]":"Shell fornita per Latte
Dock","Description[nl]":"Shell geleverd voor de Latte
Dock","Description[nn]":"Skal frå Latte-dokk","Description[pl]":"Powłoka dla
doku Latte","Description[pt]":"Consola oferecida para a área acoplável do
Latte","Description[pt_BR]":"Shell fornecido pelo Latte
Dock","Description[ru]":"Оболочка для Latte Dock","Description[sv]":"Skal
tillhandahållet för Latte dockningsfönster","Description[uk]":"Оболонка панелі
Латте","Description[x-test]":"xxShell provided for the Latte
Dockxx","Description[zh_CN]":"用于 Latte 停靠栏的 Shell","Description[zh_TW]":"由
Latte Dock 提供的
Shell","Id":"org.kde.latte.shell","License":"GPLv3+","Name":"Latte
Shell","Name[ca@valencia]":"Intèrpret d'ordres del Latte","Name[ca]":"Intèrpret
d'ordres del Latte","Name[cs]":"Shell
Latte","Name[da]":"Latte-skal","Name[de]":"Latte-Shell","Name[el]":"Κέλυφος
Latte","Name[en_GB]":"Latte Shell","Name[es]":"Consola de
Latte","Name[eu]":"Latte
Shell-a","Name[fi]":"Latte-käyttöliittymä","Name[gl]":"Intérprete de ordes de
Latte","Name[it]":"shell
Latte","Name[nl]":"Latte-shell","Name[nn]":"Latte-skal","Name[pl]":"Powłoka
Latte","Name[pt]":"Consola do Latte","Name[pt_BR]":"Latte
Shell","Name[ru]":"Оболочка Latte","Name[sv]":"Latte skal","Name[uk]":"Оболонка
Латте","Name[x-test]":"xxLatte Shellxx","Name[zh_CN]":"Latte
Shell","Name[zh_TW]":"Latte
Shell","ServiceTypes":["Plasma/Shell"],"Version":"0.8.6","Website":"https://github.com/psifidotos/Latte-Dock"},"Keywords":"shell","Keywords[ca@valencia]":"intèrpret
d'ordres","Keywords[ca]":"intèrpret
d'ordres","Keywords[da]":"skal","Keywords[de]":"Shell","Keywords[el]":"κέλυφος","Keywords[en_GB]":"shell","Keywords[es]":"consola
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #16 from qrest --- (In reply to Michail Vourlakos from comment #14) > nope.. I tested the layout works just fine with 0.8.6 in my Tumbleweed > system... > > 1. Please send me some of your "env" outputs > 2. Is this appearing to all Neon updated systems, has anyone any idea? > 3. Close Latte and try to clean its cache at: ~/.cache/lattedock Deleting cache did not help, btw. on KDE neon we currently have qt 5.12.0, which caused some problems in general. Maybe that is the cause. 'env' output: DEFAULTS_PATH=/usr/share/gconf//usr/share/xsessions/plasma.default.path DESKTOP_SESSION=/usr/share/xsessions/plasma DISPLAY=:0 GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1 GS_LIB=/home/dark/.fonts HOME=/home/dark KDED_STARTED_BY_KDEINIT=1 KDE_FULL_SESSION=true KDE_SESSION_UID=1000 KDE_SESSION_VERSION=5 KONSOLE_DBUS_SERVICE=:1.95 KONSOLE_DBUS_SESSION=/Sessions/1 KONSOLE_DBUS_WINDOW=/Windows/1 KONSOLE_PROFILE_NAME=Profile 5 KONSOLE_VERSION=181202 LANG=en_GB.UTF-8 LANGUAGE=en_GB LC_ADDRESS=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LOGNAME=dark MANDATORY_PATH=/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path OLDPWD=/home/dark PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/var/lib/snapd/desktop/applications:/snap/bin PROFILEHOME= PWD=/home/dark QT_ACCESSIBILITY=1 QT_AUTO_SCREEN_SCALE_FACTOR=0 SESSION_MANAGER=local/neon:@/tmp/.ICE-unix/2095,unix/neon:/tmp/.ICE-unix/2095 SHELL=/usr/bin/zsh SHELL_SESSION_ID=5a6576711edd44a388f586b72a54b6c3 SHLVL=1 SSH_AGENT_PID=2032 SSH_AUTH_SOCK=/tmp/ssh-3CitfeIY3Nhc/agent.1985 TERM=xterm-256color USER=dark WINDOWID=81788935 XAUTHORITY=/tmp/xauth-1000-_0 XCURSOR_THEME=breeze_cursors XDG_CONFIG_DIRS=/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg XDG_CURRENT_DESKTOP=KDE XDG_DATA_DIRS=/usr/share//usr/share/xsessions/plasma:/home/dark/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop XDG_RUNTIME_DIR=/run/user/1000 XDG_SEAT=seat0 XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 XDG_SESSION_CLASS=user XDG_SESSION_DESKTOP=KDE XDG_SESSION_ID=3 XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1 XDG_SESSION_TYPE=x11 XDG_VTNR=1 _=/usr/bin/env ZSH=/home/dark/.oh-my-zsh PAGER=less LESS=-R LSCOLORS=Gxfxcxdxbxegedabagacad LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36: LC_CTYPE=en_GB.UTF-8 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #18 from qrest --- If the location of the panel is set to anything other than 'bottom' then the problem does not occur. Creating a new panel does not solve the problem (as reported here: https://www.reddit.com/r/kde/comments/arvc30/lattedock_v086_bug_with_zoom_on_mouse_hover/egq5rtt). -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #21 from qrest --- Created attachment 118184 --> https://bugs.kde.org/attachment.cgi?id=118184&action=edit latte-dock properties on hover Properties of latte-dock on hover -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #22 from qrest --- Created attachment 118185 --> https://bugs.kde.org/attachment.cgi?id=118185&action=edit latte-dock properties at click Properties of latte-dock at click. Only difference I see is 'Contents Heights' and 'Task Hovered', last of which changes from 5 to -1. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #23 from qrest --- (In reply to Michail Vourlakos from comment #19) > 1. Tweaks page, disable the activation of KWin Edge does it help? problem still occurs -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #25 from qrest --- (In reply to Michail Vourlakos from comment #24) > (In reply to qrest from comment #21) > > Created attachment 118184 [details] > > latte-dock properties on hover > > > > Properties of latte-dock on hover > > 1. your screen resolution is 1920x1080 ? > > in general the debug window looks ok and valid, I dont see something strange > in it, it even identifies which task is hovered... so strange...(In reply to > qrest from comment #22) > > Created attachment 118185 [details] > > latte-dock properties at click > > > > Properties of latte-dock at click. > > Only difference I see is 'Contents Heights' and 'Task Hovered', last of > > which changes from 5 to -1. > > left click or right click? Screen resolution is 1920x1080 Left click So 'task hovered' changing to -1 is okay? This did not happen when I clicked the upper (working) half of the icon. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Applications is only launched when it is clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #27 from qrest --- (In reply to Michail Vourlakos from comment #26) > (In reply to qrest from comment #25) > > (In reply to Michail Vourlakos from comment #24) > > > (In reply to qrest from comment #21) > > Left click > > So 'task hovered' changing to -1 is okay? This did not happen when I clicked > > the upper (working) half of the icon. > > no this is NOT right, it should remain to the task index that was clicked... > very weird, having so different experiences between our systems... > > try also the following: > > 1. Add in your Latte Dock an Application Launcher widget > 2. Wait for 4-5 seconds after first add it > 3. Does the issue remains when you try to click the Application Launcher > widget in Latte ? The issue does not persist with the Application Launcher, also tried with Analogue Clock which also worked like it should. Seems like widgets in general seem to work. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Tasks are only launched when are clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #31 from qrest --- I also use the KDE neon user edition. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404428] Tasks are only launched when are clicked on the upper half part of the icon.
https://bugs.kde.org/show_bug.cgi?id=404428 --- Comment #32 from qrest --- Just got an update for some qt libraries (see below). After restarting latte-dock the problem seems to be resolved. I can now start and maximize/minimize applications as usual. Upgrade: libqt5gui5-dbgsym:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5test5:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), qt5-gtk-platformtheme:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5dbus5:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5sql5-sqlite:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5widgets5:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5xml5:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5printsupport5:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5concurrent5:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5gui5:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5core5a-dbgsym:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5core5a:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5opengl5:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5network5:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5widgets5-dbgsym:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5sql5:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54), libqt5sql5-mysql:amd64 (5.12.0+dfsg-0+xneon+18.04+bionic+build53, 5.12.0+dfsg-0+xneon+18.04+bionic+build54) End-Date: 2019-02-19 14:55:59 -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 416275] Activating Application Menu Bar Removes Windows Controls in Firefox
https://bugs.kde.org/show_bug.cgi?id=416275 qrest changed: What|Removed |Added CC||qr...@protonmail.com --- Comment #3 from qrest --- I have the same problem. The window control buttons are scrambled for me in Firefox only. Other GTK applications work fine. Note: This only happens if a custom GTK theme is used. The default Breeze theme works fine. Also using KDE neon testing. settings.ini [Settings] gtk-application-prefer-dark-theme=1 gtk-button-images=1 gtk-cursor-theme-name=breeze_cursors gtk-decoration-layout=icon:minimize,maximize,close gtk-enable-animations=0 gtk-fallback-icon-theme=gnome gtk-font-name=Noto Sans, 10 gtk-icon-theme-name=Papirus-Dark gtk-menu-images=1 gtk-primary-button-warps-slider=0 gtk-theme-name=Mojave-dark-solid gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 416275] Activating Application Menu Bar Removes Windows Controls in Firefox
https://bugs.kde.org/show_bug.cgi?id=416275 --- Comment #4 from qrest --- Created attachment 125548 --> https://bugs.kde.org/attachment.cgi?id=125548&action=edit Other GTK applications work fine -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 416275] Activating Application Menu Bar Removes Windows Controls in Firefox
https://bugs.kde.org/show_bug.cgi?id=416275 --- Comment #5 from qrest --- Updated my system today and the window controls appear now as they should. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 416354] button to close GHNS window without label
https://bugs.kde.org/show_bug.cgi?id=416354 qrest changed: What|Removed |Added CC||qr...@protonmail.com --- Comment #3 from qrest --- Created attachment 125633 --> https://bugs.kde.org/attachment.cgi?id=125633&action=edit Same on KDE neon testing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415114] New: Crash when selecting on desktop and wallpaper changes at the same time
https://bugs.kde.org/show_bug.cgi?id=415114 Bug ID: 415114 Summary: Crash when selecting on desktop and wallpaper changes at the same time Product: plasmashell Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: qr...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I dragged a selection rectangle on the desktop. While dragging the desktop wallpaper changed and the crash occured. Desktop Wallpaper settings are as follows: Layout: Folder View Wallpaper Type: Slideshow Order: Random -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6571acb800 (LWP ))] Thread 27 (Thread 0x7f64ce9bf700 (LWP 325)): #0 0x7f65688359f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b2469486c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f65688359f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55b246948670, cond=0x55b246948698) at pthread_cond_wait.c:502 #2 0x7f65688359f3 in __pthread_cond_wait (cond=0x55b246948698, mutex=0x55b246948670) at pthread_cond_wait.c:655 #3 0x7f656b904aeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55b246948670) at thread/qwaitcondition_unix.cpp:146 #4 0x7f656b904aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55b246671230, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f656b904df9 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55b246671238, mutex=mutex@entry=0x55b246671230, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f656f928ec8 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55b246671228) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 0x7f656f928ec8 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55b2466711b0) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7f656f9292fa in QSGRenderThread::run() (this=0x55b2466711b0) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7f656b8fdb52 in QThreadPrivate::start(void*) (arg=0x55b2466711b0) at thread/qthread_unix.cpp:360 #10 0x7f656882f6db in start_thread (arg=0x7f64ce9bf700) at pthread_create.c:463 #11 0x7f656b1fa88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f64dd717700 (LWP 324)): #0 0x7f65688359f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b2469f5458) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f65688359f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55b2469f5408, cond=0x55b2469f5430) at pthread_cond_wait.c:502 #2 0x7f65688359f3 in __pthread_cond_wait (cond=0x55b2469f5430, mutex=0x55b2469f5408) at pthread_cond_wait.c:655 #3 0x7f65470d32bb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f65470d2eb7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f656882f6db in start_thread (arg=0x7f64dd717700) at pthread_create.c:463 #6 0x7f656b1fa88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f64de54d700 (LWP 309)): #0 0x7f65688359f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b24677c290) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f65688359f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55b24677c240, cond=0x55b24677c268) at pthread_cond_wait.c:502 #2 0x7f65688359f3 in __pthread_cond_wait (cond=0x55b24677c268, mutex=0x55b24677c240) at pthread_cond_wait.c:655 #3 0x7f656b904aeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55b24677c240) at thread/qwaitcondition_unix.cpp:146 #4 0x7f656b904aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55b2466a2700, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f656b904df9 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55b2466a2708, mutex=mutex@entry=0x55b2466a2700, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f656f928ec8 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55b2466a26f8) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 0x7f656f928ec8 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55b2466a2680) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7f656f9292fa in QSGRenderThread::run() (this=0x55b2466a
