[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 Miroslav Spehar changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #14 from Miroslav Spehar --- Answered above -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #9 from Miroslav Spehar --- This exact problem is now manifesting only when lockscreen is shown and while lockscreen is showing controls. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #10 from Miroslav Spehar --- Created attachment 170508 --> https://bugs.kde.org/attachment.cgi?id=170508&action=edit screenlocker with controls -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #11 from Miroslav Spehar --- Created attachment 170509 --> https://bugs.kde.org/attachment.cgi?id=170509&action=edit top showing high cpu usage for screen locker -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #12 from Miroslav Spehar --- this is now using plasma 6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410652] New: Changing icons theme in settings does not change category icons in Kickoff
https://bugs.kde.org/show_bug.cgi?id=410652 Bug ID: 410652 Summary: Changing icons theme in settings does not change category icons in Kickoff Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: mspe...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Changing icons theme in settings does not change category icons in Kickoff. This gets changed only when look-and-feel is changed. STEPS TO REPRODUCE 1. Install papirus icon theme 2. Change icon theme 3. Start Kickoff and verify that icons Favorites, Applications, Computer... have not been updated OBSERVED RESULT After changing icon theme, category icons in Kickoff are not updated EXPECTED RESULT After changing icon theme, category icons in Kickoff are used from the newly selected theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: arch KDE Plasma Version: 5.16 ADDITIONAL INFORMATION Same happens with Kicker -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] New: wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 Bug ID: 410856 Summary: wayland: kwin uses 100% cpu when idle Product: kwin Version: 5.16.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- Created attachment 122090 --> https://bugs.kde.org/attachment.cgi?id=122090&action=edit htop showing cpu usage SUMMARY 100% cpu usage when left to be idle in VM. when screen is activated, cpu usage drops. STEPS TO REPRODUCE 1. install basic archlinux desktop with kde plasma 2. login into wayland session 3. disable baloo 4. leave the machine for a while OBSERVED RESULT 100% cpu usage in kwin EXPECTED RESULT minimal cpu usage for kwin SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION journal | grep kwin Aug 03 18:03:17 vm-arch kernel: kwin_wayland[450]: segfault at 128 ip 7f645d812e9c sp 7ffd89473ee0 error 4 in libkwin.so.5.16.4[7f645d66f000+1eb000] Aug 03 18:03:17 vm-arch kernel: audit: type=1701 audit(1564848197.113:57): auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 03 18:03:17 vm-arch audit[450]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 03 18:05:32 vm-arch kernel: audit: type=1701 audit(1564848332.356:38): auid=1000 uid=1000 gid=998 ses=2 pid=448 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 03 18:05:32 vm-arch audit[448]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=448 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 12:22:16 vm-arch audit[3307]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=3307 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 12:22:16 vm-arch kernel: audit: type=1701 audit(1565518936.686:44): auid=1000 uid=1000 gid=998 ses=2 pid=3307 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 12:36:50 vm-arch audit[450]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 12:36:50 vm-arch kernel: audit: type=1701 audit(1565519810.083:42): auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aug 11 12:49:23 vm-arch kdeinit5[750]: kio_smb: dirp->name kwin.txt "kwin.txt" ' "" ' 8 Aug 11 12:49:23 vm-arch kdeinit5[750]: kio_smb: updateCache "/red/kwin.txt" Aug 11 12:49:24 vm-arch kdeinit5[743]: kio_smb: dirp->name kwin.txt "kwin.txt" ' "" ' 8 Aug 11 12:49:24 vm-arch kdeinit5[743]: kio_smb: updateCache "/red/kwin.txt" Aug 11 12:51:10 vm-arch systemsettings5[758]: org.kde.kcoreaddons: Error loading plugin "kcm_kwindecoration" "The shared library was not found." Aug 11 12:51:10 vm-arch systemsettings5[758]: Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations. Aug 11 12:51:13 vm-arch systemsettings5[758]: KActivitiesStats( 0x55c343144b00 ) ResultModelPrivate::onResultScoreUpdated result added: "kcm:kwindecoration.desktop" score: 0 last: 1565520673 first: 1565520673 Aug 11 12:55:09 vm-arch audit[451]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=451 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 12:55:09 vm-arch kernel: audit: type=1701 audit(1565520909.576:44): auid=1000 uid=1000 gid=998 ses=2 pid=451 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 13:27:19 vm-arch audit[450]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 13:27:19 vm-arch kernel: audit: type=1701 audit(1565522839.420:45): auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 13:28:03 vm-arch audit[453]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=453 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 13:28:03 vm-arch kernel: audit: type=1701 audit(1565522883.836:42): auid=1000 uid=1000 gid=998 ses=2 pid=453 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aug 11 13:29:02 vm-arch systemsettings5[660]: org.kde.kcoreaddons: Error loading plugin "kcm_kwindecoration" "Th
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #1 from Miroslav Spehar --- Created attachment 122091 --> https://bugs.kde.org/attachment.cgi?id=122091&action=edit kubuntu htop showing cpu usage same thing happens on kubuntu with latest updates. i uninstalled plasma-discover and disabled ubuntu. cpu spike is triggered when kscreen locker kicks in -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #2 from Miroslav Spehar --- *disabled baloo -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #4 from Miroslav Spehar --- after reinstallation of virtual machine, same situation again. post installaton steps: - update all packages - remove plasma-discover - install openssh-server - apt autoremove - configure autologin to wayland session in plasma settings status after reinstall: - cpu is ~25% while lockscreen is on - after monitors are turned off, session cannot be recovered via gui if i kill one of the other processes, session crashes. fwiw, i do not start manually those kwin processes, they are started by sddm it seems. i added a screenshot of htop with hierarchy. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #5 from Miroslav Spehar --- Created attachment 122102 --> https://bugs.kde.org/attachment.cgi?id=122102&action=edit 25% cpu kwin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414452] New: plasma crashes with reference to libc
https://bugs.kde.org/show_bug.cgi?id=414452 Bug ID: 414452 Summary: plasma crashes with reference to libc Product: plasmashell Version: master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: 1.0 SUMMARY Plasma session crashes with no aparent bug trigger (left the pc alone). was using firefox before and once, just by using firefox it crashed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 31, kernel 5.3.11 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61 Qt Version: 5.12.5 ADDITIONAL INFORMATION systemd-journald dump relevant for the crash Nov 24 12:28:13 r7 systemd-coredump[15128]: Process 13812 (plasmashell) of user 1000 dumped core. Stack trace of thread 13812: #0 0x7fea78e95625 raise (libc.so.6) #1 0x7fea7a7e7481 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #2 0x7fea78e956b0 __restore_rt (libc.so.6) #3 0x7fea78e95625 raise (libc.so.6) #4 0x7fea78e7e8d9 abort (libc.so.6) #5 0x7fea792a3b1b _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5) #6 0x7fea752cb08b _ZNK15QtWaylandClient15QWaylandDisplay10checkErrorEv.cold (libQt5WaylandClient.so.5) #7 0x7fea752d6a4e _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5) #8 0x7fea794aadfb _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #9 0x7fea794b708c _ZN15QSocketNotifier9activatedEiNS_14QPrivateSignalE (libQt5Core.so.5) #10 0x7fea794b73f1 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5) #11 0x7fea79f71ad6 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #12 0x7fea79f7b150 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #13 0x7fea79480de8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #14 0x7fea794d6667 _ZL28socketNotifierSourceDispatchP8_GSourcePFiPvES1_ (libQt5Core.so.5) #15 0x7fea77bd84a0 g_main_context_dispatch (libglib-2.0.so.0) #16 0x7fea77bd8830 g_main_context_iterate.isra.0 (libglib-2.0.so.0) #17 0x7fea77bd88d3 g_main_context_iteration (libglib-2.0.so.0) #18 0x7fea794d5cb5 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #19 0x7fea7947fceb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #20 0x7fea79487a16 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #21 0x55c421ce57e4 main (plasmashell) #22 0x7fea78e801a3 __libc_start_main (libc.so.6) #23 0x55c421ce5c6e _start (plasmashell) Stack trace of thread 14047: #0 0x7fea7877ad45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7fea6d72cebb util_queue_thread_func (radeonsi_dri.so) #2 0x7fea6d72cacb impl_thrd_routine (radeonsi_dri.so) #3 0x7fea787744e2 start_thread (libpthread.so.0) #4 0x7fea78f5a693 __clone (libc.so.6) Stack trace of thread 14078: #0 0x7fea7877ad45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7fea6d72cebb util_queue_thread_func (radeonsi_dri.so) #2 0x7fea6d72cacb impl_thrd_routine (radeonsi_dri.so) #3 0x7fea787744e2 start_thread (libpthread.so.0) #4 0x7fea7
[plasmashell] [Bug 414452] plasma crashes with reference to libc
https://bugs.kde.org/show_bug.cgi?id=414452 --- Comment #1 from Miroslav Spehar --- actually, better view on the dump is here https://paste.fedoraproject.org/paste/iAubV2NI8FruUkRjppWE0g -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394899] System Settings crashes when selecting activities on wayland
https://bugs.kde.org/show_bug.cgi?id=394899 Miroslav Spehar changed: What|Removed |Added CC||mspe...@gmail.com --- Comment #4 from Miroslav Spehar --- Created attachment 124103 --> https://bugs.kde.org/attachment.cgi?id=124103&action=edit activities-kcm on fedora it does not crash, but shows as it is on the attached pic fedora 31 kf 5.61.0 qt 5.12.5 plasma 5.16.5 kernel 5.3.11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414452] plasma crashes with reference to libc
https://bugs.kde.org/show_bug.cgi?id=414452 Miroslav Spehar changed: What|Removed |Added Version|master |5.16.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414470] New: wayland: wrong window position on maximize
https://bugs.kde.org/show_bug.cgi?id=414470 Bug ID: 414470 Summary: wayland: wrong window position on maximize Product: kwin Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- SUMMARY in dual screen setup (with hidpi), maximizing windows on the screen without taskbar is maximized only until the size up to the line where taskbar would be. check screenshot https://i.imgur.com/lZTzmMk.png STEPS TO REPRODUCE 1. maximize window on the screen without taskbar (in dual screen setup) OBSERVED RESULT maximizes screen up to the position of taskbar leaving part of the screen empty EXPECTED RESULT maximize over full screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.3.11 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414471] New: wayland: wrong position for kickoff when taskbar is on the top of the screen (dual screen setup)
https://bugs.kde.org/show_bug.cgi?id=414471 Bug ID: 414471 Summary: wayland: wrong position for kickoff when taskbar is on the top of the screen (dual screen setup) Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: mspe...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY when taskbar is on the top, kickoff is shown on the wrong side of the screen https://i.imgur.com/lZTzmMk.png STEPS TO REPRODUCE 1. dual screen setup, move taskbar on the top left screen 2. start kickoff OBSERVED RESULT kickoff is top-right on the left screen EXPECTED RESULT kickoff is top-left on the left screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: fedora 31, kernel 5.3.11 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414471] wayland: wrong position for kickoff when taskbar is on the top of the screen (dual screen setup)
https://bugs.kde.org/show_bug.cgi?id=414471 Miroslav Spehar changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396237] wayland: changing from folder view to desktop view and vice versa crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396237 Miroslav Spehar changed: What|Removed |Added CC||mspe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396237] wayland: changing from folder view to desktop view and vice versa crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396237 Miroslav Spehar changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #4 from Miroslav Spehar --- Done. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396237] wayland: changing from folder view to desktop view and vice versa crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396237 Miroslav Spehar changed: What|Removed |Added Version|5.13.1 |5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396237] wayland: changing from folder view to desktop view and vice versa crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396237 --- Comment #5 from Miroslav Spehar --- Created attachment 113807 --> https://bugs.kde.org/attachment.cgi?id=113807&action=edit New crash information added by DrKonqi plasmashell (5.13.2) using Qt 5.11.1 - What I was doing when the application crashed: changing desktop configuration -> from folder to desktop view -- Backtrace (Reduced): #6 0x7f0b12d90a27 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () at kernel/qobject.cpp:2680 [...] #8 0x7f0a02339349 in Kirigami::PlatformTheme::qmlAttachedProperties(QObject*) () from /usr/lib64/libKF5Kirigami2.so.5 #9 0x7f0b165cd2ed in QtQml::qmlAttachedPropertiesObjectById (id=, object=0x556d7b5140b0, create=create@entry=true) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/qml/qml/qqmlengine.cpp:1576 #10 0x7f0b16665a93 in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/qml/qml/qqmlobjectcreator.cpp:799 #11 0x7f0b166679f4 in QQmlObjectCreator::setupBindings (this=this@entry=0x7ffc23d07b20, applyDeferredBindings=applyDeferredBindings@entry=false) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/qml/qml/qqmlobjectcreator.cpp:777 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396235] wayland: alt-tab or selecting help -> about on a maximized window resizes that window
https://bugs.kde.org/show_bug.cgi?id=396235 --- Comment #1 from Miroslav Spehar --- seems to happen also when active window gets changed with a mouse -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396258] New: wayland: using window decorations installed from store crashes plasma when any window is closed
https://bugs.kde.org/show_bug.cgi?id=396258 Bug ID: 396258 Summary: wayland: using window decorations installed from store crashes plasma when any window is closed Product: plasmashell Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: 1.0 when using window decoration theme from kde store, it crashes plasma whenever window is being closed. afterwards i cannot access terminal. reproduce: install window decorations like lindows, change theme to that one and try to close the window hint: might be connected to sddm since sddm hangs during reboot until timeout is reached (remotely triggered) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396258] wayland: using window decorations installed from store crashes plasma when any window is closed
https://bugs.kde.org/show_bug.cgi?id=396258 Miroslav Spehar changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396235] wayland: alt-tab or selecting help -> about on a maximized window resizes that window
https://bugs.kde.org/show_bug.cgi?id=396235 --- Comment #2 from Miroslav Spehar --- in further testing, it seems that it does this resize whenever some dialog gets shown. window doesn't even have to be maximized: reproduce: shift-del in dolphin will resize dolphin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396258] wayland: using window decorations installed from store crashes plasma when trying to close any window
https://bugs.kde.org/show_bug.cgi?id=396258 Miroslav Spehar changed: What|Removed |Added Summary|wayland: using window |wayland: using window |decorations installed from |decorations installed from |store crashes plasma when |store crashes plasma when |any window is closed|trying to close any window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396272] New: wayland: kwin crashes after energy saving turns monitors off and i try to wake them on with a mouse
https://bugs.kde.org/show_bug.cgi?id=396272 Bug ID: 396272 Summary: wayland: kwin crashes after energy saving turns monitors off and i try to wake them on with a mouse Product: kwin Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- Created attachment 113814 --> https://bugs.kde.org/attachment.cgi?id=113814&action=edit gdb backtrace - What I was doing when the application crashed: Every time after resume from screen energy saving mode, plasma is wither non-responsive or just turns on the backlight of monitors without picture showing. Reproducible: Always Steps to Reproduce: 1. From System settings-> power management, set the "Screen energy saving" to 10 mins 2. Leave the screen to go blank and wait around 10 more mins (sometimes more) 3. Move the mouse so screen gets back There are two related bugs reported https://bugs.kde.org/show_bug.cgi?id=364526 https://bugs.kde.org/show_bug.cgi?id=348487 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396272] wayland: kwin crashes after energy saving turns monitors off and i try to wake them on with a mouse
https://bugs.kde.org/show_bug.cgi?id=396272 Miroslav Spehar changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 Miroslav Spehar changed: What|Removed |Added Version|5.12.4 |5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395492] Crash when opening system settings > application style > window decorations
https://bugs.kde.org/show_bug.cgi?id=395492 --- Comment #3 from Miroslav Spehar --- Created attachment 113815 --> https://bugs.kde.org/attachment.cgi?id=113815&action=edit New crash information added by DrKonqi systemsettings5 (5.13.2) using Qt 5.11.1 - What I was doing when the application crashed: open systemsettings5 -> click on application style -> window decorations -- Backtrace (Reduced): #6 0x7fd1130d4024 in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x10011) at /usr/include/c++/8/bits/atomic_base.h:390 #7 QAtomicOps::load (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x10011) at /usr/include/qt5/QtCore/qbasicatomic.h:103 #9 QtPrivate::RefCount::isShared (this=0x10011) at /usr/include/qt5/QtCore/qrefcount.h:101 [...] #11 QHash::operator[] (akey=@0x7ffd0482d148: 0x5573de58f090, this=0x5573de57f7f8) at /usr/include/qt5/QtCore/qhash.h:753 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395492] Crash when opening system settings > application style > window decorations
https://bugs.kde.org/show_bug.cgi?id=395492 Miroslav Spehar changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|BACKTRACE |--- --- Comment #4 from Miroslav Spehar --- (In reply to Martin Flöser from comment #2) > Unfortunately the backtrace is lacking debug symbols. If you are able to > reproduce please install debug packages and attach a new backtrace. Would attached bt work? Drkonqi complained about some missing debuginfo packages, but when 'install dependencies' was clicked, it didnt install anything. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 396306] New: wayland: in dual screen, unlocking is possible only on one monitor
https://bugs.kde.org/show_bug.cgi?id=396306 Bug ID: 396306 Summary: wayland: in dual screen, unlocking is possible only on one monitor Product: kscreenlocker Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com CC: bhus...@gmail.com Target Milestone: --- in dual screen configuration, when screen is locked and i try to unclock it, it is possible only from one screen (in my case it's hidpi screen). other screen, even though it shows password field, clicking it or typing is automatically entered on the other screen. it is happening every time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396308] New: wayland: clearing clipboard history crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396308 Bug ID: 396308 Summary: wayland: clearing clipboard history crashes plasma Product: kwin Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- Created attachment 113830 --> https://bugs.kde.org/attachment.cgi?id=113830&action=edit gdb-backtrace clearing clipboard history on wayland crashes plasma steps to reproduce: 1. click in tray on clipboard contents 2. click clear history 3. confirming it on a popup dialog happens every time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396308] wayland: clearing clipboard history crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396308 Miroslav Spehar changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393649] Monitor reports no signal if turned off and back on with wayland session
https://bugs.kde.org/show_bug.cgi?id=393649 --- Comment #6 from Miroslav Spehar --- (In reply to Roman Gilg from comment #5) > Btw can you check from the virtual terminal if the KWin process is still > running and get a trace of the last calls it did. i opened a new bug since description when it happens is a bit different https://bugs.kde.org/show_bug.cgi?id=396272 backtrace is attached there -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396258] wayland: using window decorations installed from store crashes plasma when trying to close any window
https://bugs.kde.org/show_bug.cgi?id=396258 --- Comment #3 from Miroslav Spehar --- (In reply to David Edmundson from comment #2) > Crashes need backtraces unfortunatelly, now also going in that area of systemsettings5 also crashes, so i can't reach the problem with closing the window to get the backtrace. would it help if i provide backtrace of systemsettings5 crashing? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396258] wayland: using window decorations installed from store crashes plasma when trying to close any window
https://bugs.kde.org/show_bug.cgi?id=396258 Miroslav Spehar changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #5 from Miroslav Spehar --- bt added -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396258] wayland: using window decorations installed from store crashes plasma when trying to close any window
https://bugs.kde.org/show_bug.cgi?id=396258 --- Comment #4 from Miroslav Spehar --- Created attachment 113839 --> https://bugs.kde.org/attachment.cgi?id=113839&action=edit gdb backtrace actually i figure out how to get the backtrace, it's attached. explanation how did it work: 1. when i try to enter application style on standard dpi monitor, systemsettings5 crashes 2. when i try to enter application style on hidpi monitor, it works i'll open another bug with this issue(s) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396314] New: wayland: systemsettings5 crashes upon selecting window decorations when one monitor is scaled
https://bugs.kde.org/show_bug.cgi?id=396314 Bug ID: 396314 Summary: wayland: systemsettings5 crashes upon selecting window decorations when one monitor is scaled Product: systemsettings Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- Application: systemsettings5 (5.13.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.3-1-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: - What I was doing when the application crashed: enter systemsettings5 -> application style -> window decorations this happens in dual screen setup with one monitor being standard dpi and the other one is hidpi AND while systemsettings5 is currently on the standard dpi monitor - Unusual behavior I noticed: in dual screen setup, when one monitor is hidpi and scaled to 2, the other on is standard dpi with scale of 1, entering systemsettings5 -> application style -> window decoration crashes systemsettings5 this happens only when systemsettings5 is found on the standard dpi monitor. if systemsettings5 is found to be on the hidpi monitor, then it opens window decorations without crashing. additionally to this, apply button is disabled until the window is resized manually. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9e790cbcc0 (LWP 2017))] Thread 19 (Thread 0x7f9e06030700 (LWP 2038)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x562cbf5c1c54) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x562cbf5c1c00, cond=0x562cbf5c1c28) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x562cbf5c1c28, mutex=0x562cbf5c1c00) at pthread_cond_wait.c:655 #3 0x7f9e74e2afab in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x562cbf5c1c00) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait(QMutex*, unsigned long) () at thread/qwaitcondition_unix.cpp:215 #5 0x7f9e7301b2a9 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x562cbf658e98) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:245 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x562cbf658e20) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:709 #7 0x7f9e7301b4da in QSGRenderThread::run() () at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:738 #8 0x7f9e74e2a8ec in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #9 0x7f9e6fffc554 in start_thread (arg=) at pthread_create.c:463 #10 0x7f9e7470fccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f9e06831700 (LWP 2037)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x562cbf6c5a88) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x562cbf6c5a38, cond=0x562cbf6c5a60) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x562cbf6c5a60, mutex=0x562cbf6c5a38) at pthread_cond_wait.c:655 #3 0x7f9e5b40f69b in cnd_wait (mtx=0x562cbf6c5a38, cond=0x562cbf6c5a60) at ../../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x562cbf651040) at u_queue.c:255 #5 0x7f9e5b40f3c7 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #6 0x7f9e6fffc554 in start_thread (arg=) at pthread_create.c:463 #7 0x7f9e7470fccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f9e35c90700 (LWP 2036)): #0 0x7f9e747052c9 in __GI___poll (fds=0x7f9e0c004e00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9e6d9482c6 in g_main_context_poll (priority=, n_fds=1, fds=0x7f9e0c004e00, timeout=, context=0x7f9e0c000bf0) at gmain.c:4204 #2 g_main_context_iterate (context=context@entry=0x7f9e0c000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3898 #3 0x7f9e6d9483ec in g_main_context_iteration (context=0x7f9e0c000bf0, may_block=may_block@entry=1) at gmain.c:3964 #4 0x7f9e75012b3b in QEventDispatcherGlib::processEvents (this=0x7f9e0c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f9e74fc2b3b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f9e74e21326 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f9e72b14085 in QQmlThreadPri
[kwin] [Bug 396272] wayland: kwin crashes after energy saving turns monitors off and i try to wake them on with a mouse
https://bugs.kde.org/show_bug.cgi?id=396272 --- Comment #4 from Miroslav Spehar --- is this connected? https://bugs.kde.org/show_bug.cgi?id=385743 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396315] New: wayland: journal is filling up with kf5idletime_kwayland: This plugin does not support polling idle time
https://bugs.kde.org/show_bug.cgi?id=396315 Bug ID: 396315 Summary: wayland: journal is filling up with kf5idletime_kwayland: This plugin does not support polling idle time Product: plasmashell Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: 1.0 journal is filling up with the following error: kf5idletime_kwayland: This plugin does not support polling idle time -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396316] New: wayland: journal error on mouse over icons when using icons only task manager
https://bugs.kde.org/show_bug.cgi?id=396316 Bug ID: 396316 Summary: wayland: journal error on mouse over icons when using icons only task manager Product: plasmashell Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: mspe...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 on every mouseover event for icons pinned in icons only task manager, error is reported in system journal: plasmashell[1327]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:342: Unable to assign [undefined] to int reproducible: always -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 397136] New: wayland: after energy saving turns monitors off and i try to wake them on with a mouse, one monitor is unusable
https://bugs.kde.org/show_bug.cgi?id=397136 Bug ID: 397136 Summary: wayland: after energy saving turns monitors off and i try to wake them on with a mouse, one monitor is unusable Product: Powerdevil Version: 5.13.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- this happens on wayland: two monitors, both hidpi, one connected via hdmi (primary), the other one with displyport. after energy saving turns monitor off and i wake them on by interacting with mouse, one monitor (display port, secondary) gets turned off. Picture is only shown on the primary and this one has wrong scaling set. Mouse can be moved to the 'other' monitor, which is now in a wrong position (left side instead of right) and picture cannot be seen. Have to restart computer to get back proper setup. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 397136] wayland: after energy saving turns monitors off and i try to wake them on with a mouse, one monitor is unusable
https://bugs.kde.org/show_bug.cgi?id=397136 Miroslav Spehar changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
