| Summary: | KScreen turns my monitor back on after "xset dpms force off" | ||
|---|---|---|---|
| Product: | [Plasma] KScreen | Reporter: | Danilo Luvizotto <danilo.luvizotto> |
| Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | minor | CC: | alvaro.carroz, eugene.shalygin+bugzilla.kde, nate, qydwhotmail |
| Priority: | NOR | ||
| Version: | 5.24.4 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: |
Plasma KDED journal
Plasma KScreen journal |
||
|
Description
Danilo Luvizotto
2022-04-07 21:53:02 UTC
Created attachment 148036 [details]
Plasma KDED journal
Attaching output of:
journalctl --user -b -u plasma-kded | grep kscreen > plasma-kded-journal.txt
Created attachment 148037 [details]
Plasma KScreen journal
Output of:
journalctl --user -b -u plasma-kscreen > plasma-kscreen-journal.txt
Same problem on Gentoo with: Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.18.0-gentoo (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics Memory: 62.3 GiB of RAM Graphics Processor: AMD RENOIR (In reply to Eugene Shalygin from comment #4) > https://gitlab.freedesktop.org/drm/amd/-/issues/662 I'm running linux 5.18.1 and still experience the problem every time I suspend my external monitor. Also, please notice in the original description: the problem only occurs when "KScreen 2" is enabled in kcm's background services. It does not happen if KScreen 2 is disabled. Thus, it is probably not a kernel problem. I am on 5.18.1 as well and experienced the same problem. Disabling automatic input selection in my screen settings helped. You can check X log for the events screens produce. (In reply to Eugene Shalygin from comment #6) > I am on 5.18.1 as well and experienced the same problem. Disabling automatic > input selection in my screen settings helped. You can check X log for the > events screens produce. Thank you for your tip. How do I disable automatic input selection? Can't find it. (In reply to Danilo Luvizotto from comment #7) > Thank you for your tip. How do I disable automatic input selection? Can't > find it. Sorry, I don't know. Watched video [1] and saw no obvious option. My screens are much more primitive, they provide a straightforward option "Input auto switch". https://www.youtube.com/watch?v=TjhH1o1Ygms (In reply to Eugene Shalygin from comment #8) > (In reply to Danilo Luvizotto from comment #7) > > Thank you for your tip. How do I disable automatic input selection? Can't > > find it. > > Sorry, I don't know. Watched video [1] and saw no obvious option. My screens > are much more primitive, they provide a straightforward option "Input auto > switch". > > https://www.youtube.com/watch?v=TjhH1o1Ygms Oh, you mean in the monitor itself. Thank you for even searching for a video of my monitor model. I'm afraid my monitor doesn't have that option, so I'm helpless for now. I've run the following command to check if there were input events waking up my monitor, and I get an event from "Virtual core XTEST pointer" only when KScreen 2 is enabled:
sleep 3 && xinput test-xi2 --root
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech M720 Triathlon id=10 [slave pointer (2)]
⎜ ↳ MX Keys Mini Keyboard id=17 [slave pointer (2)]
⎜ ↳ MX Keys Mini Keyboard id=16 [slave pointer (2)]
⎜ ↳ UNIW0001:00 093A:0255 Touchpad id=14 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ Logitech Webcam C925e id=11 [slave keyboard (3)]
↳ HD Webcam: HD Webcam id=12 [slave keyboard (3)]
↳ HD Webcam: IR Camera id=13 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
↳ Logitech M720 Triathlon id=18 [slave keyboard (3)]
↳ MX Keys Mini Keyboard id=19 [slave keyboard (3)]
↳ MX Keys Mini Keyboard id=20 [slave keyboard (3)]
EVENT type 1 (DeviceChanged)
device: 2 (4)
reason: SlaveSwitch
Reporting 3 classes:
Class originated from: 4. Type: XIButtonClass
Buttons supported: 10
Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" None None None
Button state:
Class originated from: 4. Type: XIValuatorClass
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 4. Type: XIValuatorClass
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
EVENT type 6 (Motion)
device: 4 (4)
detail: 0
flags:
root: 1919.00/1079.00
event: 1919.00/1079.00
buttons:
modifiers: locked 0x10 latched 0 base 0 effective: 0x10
group: locked 0 latched 0 base 0 effective: 0
valuators:
0: 1919.00
1: 1079.00
windows: root 0x6d7 event 0x6d7 child 0x5e00022
Can reproduce In general, when using kscreen, the kscreen-doctor command line is the preferred way to manipulate screens. Ah actually this manifests elsewhere with supported workflows in powerdevil too. See Bug 413618. *** This bug has been marked as a duplicate of bug 413618 *** |