[Powerdevil] [Bug 482853] New: "When locked, turn off screen" needs a checkbox to disable/enable it
https://bugs.kde.org/show_bug.cgi?id=482853 Bug ID: 482853 Summary: "When locked, turn off screen" needs a checkbox to disable/enable it Classification: Plasma Product: Powerdevil Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rl...@hotmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY In the energy saving options the "When locked, turn off screen" option needs a checkbox to disable/enable the feature. In it's current state it doesn't make sense under certain situations. I have the auto screen locking on 5mins, and I want to have the monitor on for 30minutes. Which I can't do because the "When locked, turn off screen" will trigger earlier, even with max value which is 800sec (~13min). OBSERVED RESULT "When locked, turn off screen" has no checkbox and can't be disabled EXPECTED RESULT "When locked, turn off screen" has a checkbox and can be disabled SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481000] Kicker not highlighting selection, neither via keyboard nor hover
https://bugs.kde.org/show_bug.cgi?id=481000 rLy changed: What|Removed |Added CC||rl...@hotmail.com --- Comment #10 from rLy --- I have/had the same issue with the exception of the volume slider. Based on the comments, I created a new user and tested it there. Everything worked and after I switched back, it started to work again on my account as well. I'm also on Arch and using Breeze Dark. KDE Plasma: 5.27.10 KDE Framework: 5.115.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481000] Kicker not highlighting selection, neither via keyboard nor hover
https://bugs.kde.org/show_bug.cgi?id=481000 --- Comment #12 from rLy --- (In reply to Yao Mitachi from comment #11) > Why the LTS version of Qt, rLy? Does the problem come back if you install Qt > 6.7? I just choose not to go with the RC version and wait for the full rls. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482853] "When locked, turn off screen" needs a checkbox to disable/enable it
https://bugs.kde.org/show_bug.cgi?id=482853 --- Comment #2 from rLy --- (In reply to Jakob Petsovits from comment #1) > Would it help if you could configure values up to the duration of the > regular (unlocked) timeout in the line above? Adding extra checkbox is easy, > but also adds mental overhead that perhaps we can avoid. > > Another user brought up that exposing the "timeout when locked" is overkill > and shouldn't be shown by default. I'd like to tweak the UI both towards > "simple by default" and to fix your use case, not sure yet how to best go > about it. Would it solve my use case? Yes, but it would still mean that under certain situations (depending on timer settings), one or the other timer is useless and will never trigger, which might still be a bit confusing. I wouldn't say that it's overkill but in it's current state I would opt to disable it (as in I wouldn't use it, not that it shouldn't be shown by default). The way I would use a feature like this, if it would only apply to intentional locks (via hotkey, gui, etc) and not apply to idle locks. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 484143] New: clipboard contents pushed to phone when the screen locks/unlocks
https://bugs.kde.org/show_bug.cgi?id=484143 Bug ID: 484143 Summary: clipboard contents pushed to phone when the screen locks/unlocks Classification: Applications Product: kdeconnect Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: rl...@hotmail.com Target Milestone: --- SUMMARY Every time when the screen locks or unlocks on PC, the connected phone shows the shared clipboard popup. STEPS TO REPRODUCE 1. Have the clipboard shared between pc and phone and have something on clipboard on pc 2. Have both the phone and pc unlocked 3. Lock screen on the pc and notice how the clipboard popup appears on the phone. Clipboard contents hidden. 4. Unlock the screen on pc and notice that the clipboard popup again appears on the phone. Clipboard contents visible. OBSERVED RESULT PC clipboard pushed to phone every time the screen on pc is locked or unlocked. EXPECTED RESULT Not get the clipboard copied during screen lock/unlocks SOFTWARE/OS VERSIONS Archlinux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Phone: Sony Xperia 5 V, android 14 kdeconnect version on phone: 1.29.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482853] "When locked, turn off screen" needs a checkbox to disable/enable it
https://bugs.kde.org/show_bug.cgi?id=482853 --- Comment #5 from rLy --- (In reply to Jakob Petsovits from comment #3) > A relevant merge request gets halfway to implementing this bug report: > https://invent.kde.org/plasma/powerdevil/-/merge_requests/358 > > In addition to UI changes, this also does away with the upper limit on > locked-screen timeouts. I designed in in a way that it should be > straightforward to add a "When locked: Never" option to round out the > existing functionality. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433159] New: Changing audio output crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=433159 Bug ID: 433159 Summary: Changing audio output crashes plasmashell Product: plasma-pa Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: rl...@hotmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 135837 --> https://bugs.kde.org/attachment.cgi?id=135837&action=edit journal log with 3 crashes SUMMARY I have a few virtual sinks to record audio in a separate track, when I switched the audio of an application to the virtual sink it crashed plasmashell. The crash happens after selecting an output then switching back to the Devices tab. I'm able to reproduce it fairly reliably but there are some inconsistencies. Most of the time the crash only happens 1 time per application, after a crash on a given application it "fixes" and works as expected but then starting a new application and switching the output for that cause plasma to crash again. Inconsistencies: 1) after 4-5 crashes it seemed to "fix" itself but I didn't do a lot of testing for this, I just went through multiple applications to see if it crashes every time but it just stopped crashing after that. 2) even though most of the time it fixed itself for a given application after a crash, one time it kept crashing for the same app when switching the output back and forth multiple times. After it "fixes" itself for an application simply reloading plasmashell can reintroduce the issue. STEPS TO REPRODUCE 1. Have a secondary output 2. Have an application with sound output open then bring up the audio applet and go to Applications tab 3. Switch the output for the application to something else and go back to Devices tab OBSERVED RESULT plasmashell crashes when clicking to go back to the Devices tab EXPECTED RESULT not crashing SOFTWARE/OS VERSIONS Linux/KDE Plasma: up to date Archlinux (available in About System) KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433159] Changing audio output crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=433159 --- Comment #1 from rLy --- Created attachment 135838 --> https://bugs.kde.org/attachment.cgi?id=135838&action=edit journal log after a reboot and multiple crashes -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433159] Changing audio output crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=433159 --- Comment #2 from rLy --- Created attachment 135839 --> https://bugs.kde.org/attachment.cgi?id=135839&action=edit kcrash log after a crash -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433159] Changing audio output crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=433159 --- Comment #3 from rLy --- Created attachment 135840 --> https://bugs.kde.org/attachment.cgi?id=135840&action=edit 2nd kcrash log -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433159] Changing audio output crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=433159 rLy changed: What|Removed |Added CC||rl...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433159] Changing audio output crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=433159 --- Comment #6 from rLy --- (In reply to David Redondo from comment #5) > Looks like 432482 > > *** This bug has been marked as a duplicate of bug 432482 *** I'm not sure that my bug is the same as bug 432482. I can open and close plasma-pa with "plasmawindowed org.kde.plasma.volume" and that's not causing any crashes, however it does crash when I have plasma-pa open and I run arecord ./test.wav and ctrl-c as this also mentioned in that bug. But that produces a completely different kcrash log compared to switching the outputs. kcrash when running plasma-pa from plasmawindowed and arecord Application: plasmawindowed (plasmawindowed), signal: Segmentation fault [KCrash Handler] #4 0x7f321cef4620 in QQmlData::isSignalConnected(QAbstractDeclarativeData*, QObject const*, int) () at /usr/lib/libQt5Qml.so.5 #5 0x7f321bb458e3 in () at /usr/lib/libQt5Core.so.5 #6 0x7f31b8134d03 in () at /usr/lib/qt/qml/org/kde/plasma/private/volume/libplasma-volume-declarative.so #7 0x7f31b80c1cb2 in () at /usr/lib/libpulse.so.0 #8 0x7f31981fd4e6 in () at /usr/lib/pulseaudio/libpulsecommon-14.2.so #9 0x7f31981feb18 in () at /usr/lib/pulseaudio/libpulsecommon-14.2.so #10 0x7f31981fef07 in () at /usr/lib/pulseaudio/libpulsecommon-14.2.so #11 0x7f3198201a9a in () at /usr/lib/pulseaudio/libpulsecommon-14.2.so #12 0x7f31d800365e in () at /usr/lib/libpulse-mainloop-glib.so.0 #13 0x7f3219d03b84 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #14 0x7f3219d57c21 in () at /usr/lib/libglib-2.0.so.0 #15 0x7f3219d023b1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #16 0x7f321bb676ac in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #17 0x7f321bb0d3ac in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x7f321bb15844 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #19 0x556d22dc94a8 in () #20 0x7f321b4d6b25 in __libc_start_main () at /usr/lib/libc.so.6 #21 0x556d22dc954e in () [Inferior 1 (process 73245) detached] kcrash when switching audio outputs, running pulse-pa from plasawindowed Application: plasmawindowed (plasmawindowed), signal: Aborted [KCrash Handler] #4 0x7f0492919ef5 in raise () at /usr/lib/libc.so.6 #5 0x7f0492903862 in abort () at /usr/lib/libc.so.6 #6 0x7f0458035317 in pa_stream_set_read_callback () at /usr/lib/libpulse.so.0 #7 0x7f04580d1156 in () at /usr/lib/qt/qml/org/kde/plasma/private/volume/libplasma-volume-declarative.so #8 0x7f04943974b7 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f0494398ca6 in () at /usr/lib/libQt5Qml.so.5 #10 0x7f0494396914 in QQmlBinding::update(QFlags) () at /usr/lib/libQt5Qml.so.5 #11 0x7f049437300d in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #12 0x7f0492f73905 in () at /usr/lib/libQt5Core.so.5 #13 0x7f04947665ef in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #14 0x7f049476655e in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #15 0x7f049476655e in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #16 0x7f04947666c5 in QQuickItemPrivate::setVisible(bool) () at /usr/lib/libQt5Quick.so.5 #17 0x7f04943982af in () at /usr/lib/libQt5Qml.so.5 #18 0x7f0494398ca6 in () at /usr/lib/libQt5Qml.so.5 #19 0x7f0494396914 in QQmlBinding::update(QFlags) () at /usr/lib/libQt5Qml.so.5 #20 0x7f049437300d in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #21 0x7f0492f73905 in () at /usr/lib/libQt5Core.so.5 #22 0x7f049432052e in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () at /usr/lib/libQt5Qml.so.5 #23 0x7f04943312f5 in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags) () at /usr/lib/libQt5Qml.so.5 #24 0x7f049425c079 in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #25 0x7f049425caa9 in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #26 0x7f049425cc47 in QV4::QObjectWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib/libQt5Qml.so.5 #27 0x7f04941eca43 in QV4::Lookup::setterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value&, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #28 0x7f0494275809 in () at /usr/lib/libQt5Qml.so.5 #29 0x7f049427968f in () at /usr/lib/libQt5Qml.so.5 #30 0x7f0494213d2e in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*
[plasmashell] [Bug 427685] Notification window closes when going back if no other window is visible
https://bugs.kde.org/show_bug.cgi?id=427685 rLy changed: What|Removed |Added CC||rl...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427685] Notification window closes when going back if no other window is visible
https://bugs.kde.org/show_bug.cgi?id=427685 --- Comment #2 from rLy --- Created attachment 132435 --> https://bugs.kde.org/attachment.cgi?id=132435&action=edit video of bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427685] Notification window closes when going back if no other window is visible
https://bugs.kde.org/show_bug.cgi?id=427685 --- Comment #3 from rLy --- (In reply to Konrad Materka from comment #1) > Hi, can you add some screenshots? I do not understand the issue fully. > It is possible that we have a fix already, waiting for review, please check > description of: > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/350 I attached a recording of it. Looking at the description of that merge it might fix the original issue. But I also noticed one more which can be also seen on the video. Randomly a new window shows up in the task manager called Plasma when going back to the grid. Most of the times it goes away immediately but sometimes it sticks until the dialog is closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494804] With Qt 6.8, can't log in using external screen when using the Breeze SDDM theme
https://bugs.kde.org/show_bug.cgi?id=494804 rLy changed: What|Removed |Added CC||rl...@hotmail.com --- Comment #45 from rLy --- (In reply to Nate Graham from comment #31) > Can everyone affected answer these questions: > 1. If you log in using the laptop screen rather than the external screen, > does it work as expected? > 2. What GPU(s) are present on your system, and which one is used to show the > SDDM login screen? > 3. Is SDDM set up in native Wayland mode, or X11 mode? > 4. When you hit Enter or click the arrow button, does it *never* log in? Or > does it *eventually* log in after 30-60 seconds? > > Trying to get a sense of whether this is Bug 483163, Bug 494927, Bug 483094, > some combination of them, or some new mutant thing triggered by Qt 6.8. > > Thanks! 1. Desktop pc with 2 monitors. Primary is DP, the secondary is HDMI. Also my monitors are mirrored in SDDM so can't select the other one to login. 2. 7900xtx 3. wayland 4. Doesn't login at all, waited a couple of minutes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496886] Desktop widget size resets at restart
https://bugs.kde.org/show_bug.cgi?id=496886 rLy changed: What|Removed |Added CC||rl...@hotmail.com --- Comment #1 from rLy --- I also have the same issue. I have a couple of widgets for disk monitoring and 2 out of the 6 gets resized after a restart. It's been happening since 6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496886] Desktop widget size resets at restart
https://bugs.kde.org/show_bug.cgi?id=496886 --- Comment #10 from rLy --- Just updated on Arch and it still happens to me as well. Operating System: Arch Linux KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 9800X3D 8-Core Processor Memory: 62,4 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7E47 System Version: 1.1 -- You are receiving this mail because: You are watching all bug changes.
