[plasmashell] [Bug 482862] New: plasma desktop freezes on wayland
https://bugs.kde.org/show_bug.cgi?id=482862 Bug ID: 482862 Summary: plasma desktop freezes on wayland Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mak...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Plasma desktop session halts inmediately every time i move a window from one display to other drangging with the mouse cursor. input devicess renders iressponsive I use wayland session with 3 monitors, and fractional scaling set to 75% on 2 of them, and 100% on the center STEPS TO REPRODUCE 1. open plasma wayland desktop 2. drag a window from a display to another using mouse OBSERVED RESULT desktop inmeditately freezes, only choice is to reboot EXPECTED RESULT not to freeze SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kubuntu 24.04 beta (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 469352] New: kup-purger from wayland session
https://bugs.kde.org/show_bug.cgi?id=469352 Bug ID: 469352 Summary: kup-purger from wayland session Classification: Applications Product: kup Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: simon.pers...@mykolab.com Reporter: mak...@gmail.com Target Milestone: --- SUMMARY *** can´t launch kup prune utility from a wayland session, no problem launching it from a X11 session. launching from console results in: $ kup-purger QSocketNotifier: Can only be used with threads started with QThread *** STEPS TO REPRODUCE 1. start a plasma wayland session 2. try to launch purge old backups OBSERVED RESULT 3. wait forever :( EXPECTED RESULT launch prune backups utility SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 448460] discover 5.23.90 crashes with segfault on startup
https://bugs.kde.org/show_bug.cgi?id=448460
marco martinez changed:
What|Removed |Added
CC||mak...@gmail.com
--- Comment #12 from marco martinez ---
same error here, running kubuntu 22.04 and trying to open plasma-discover
throws the same result on wayland or x11:
marco@pc-kubuntu:~$ plasma-discover %F
org.kde.plasma.discover: Trying to open unexisting file
QUrl("file:///home/marco/%25F")
adding empty sources model QStandardItemModel(0x5627d6ee0a40)
org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
QML Binding: Binding loop detected for property "value"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:283:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:261:18:
QML QQuickItem*: Binding loop detected for property "implicitWidth"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:283:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
Violación de segmento (`core' generado)
--
You are receiving this mail because:
You are watching all bug changes.
[ksysguard] [Bug 432727] New: system logs flood regarding cpufreq
https://bugs.kde.org/show_bug.cgi?id=432727 Bug ID: 432727 Summary: system logs flood regarding cpufreq Product: ksysguard Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: mak...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY dmesg is flooded with messages like this: Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu2/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu3/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu4/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu5/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu6/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu7/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu8/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu9/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu10/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu11/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu12/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu13/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu14/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu15/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu2/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu3/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu4/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu5/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu6/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu7/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu8/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu9/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu10/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu11/cpufreq/cpuinfo_cur_freq"): device not open Feb 10 10:25:21 pc-kubuntu org.kde.ksystemstats[2782]: QIODevice::read (QFile, "/sys/devices/system/cpu/cpu12/cpufreq/cpuinfo_cur_freq"): device not open Feb 10
[plasmashell] [Bug 413223] Plasma Wayland session crashes immediately after login
https://bugs.kde.org/show_bug.cgi?id=413223 marco martinez changed: What|Removed |Added CC||mak...@gmail.com --- Comment #4 from marco martinez --- Created attachment 124167 --> https://bugs.kde.org/attachment.cgi?id=124167=edit wayland-session.log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #9 from marco martinez --- I think I'm facing the same issue. I'm running plasma 5.17 beta and have set the env variable and nvidia modeset. Running on an optimus laptop -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 marco martinez changed: What|Removed |Added CC||mak...@gmail.com --- Comment #8 from marco martinez --- Created attachment 122957 --> https://bugs.kde.org/attachment.cgi?id=122957=edit wayland-session.log -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=366156 marco martinez <mak...@gmail.com> changed: What|Removed |Added CC||mak...@gmail.com --- Comment #9 from marco martinez <mak...@gmail.com> --- same problem here, not only ksmserver-logout-greeter crashes, but also does konsole, apport and most of the kdeapps. As a temporary fix, I am currently using bumblebee for gpu offloading -- You are receiving this mail because: You are watching all bug changes.
