Re: Screen energy saving turning on and off and (fixed)
So, I've discovered that kwin-x11 is now deprecated:
https://blog.martin-graesslin.com/blog/2018/01/kwinx11-is-feature-frozen/
So it is not a good idea to wait for fixings or improvements from there.
I've tried kwin-wayland, and it works.
But it is so broken, every single thing is broken.
Can't change font dpi without computer freezing, need to use power button.
It never ever remember the resolution of my screen: it always start in
resolution 1920x1080, what ever I do. (native resolution is 3840x2160)
Even re-loging lose the resolution.
When I've tried writing a mail: "kmail is not responding".
Rebooting fails 1 in 3 times.
anti aliasing is not very good, it is much more difficult to read text.
I usually use "reversed mouse wheel motion". You really can select that in
system settings, but it has no effect with wayland.
So, in a way, the initial issue is *fixed*: there won't be any improvement,
neither from X11, nor from dpms (which I've learn doesn't log things).
By the way, emacs was working too. So, if it wasn't for the fact that it is
crashing always. For the fact that you can't have your configuration right
however hard you try. And that it is ugly. It works. You can't do anything
with it, but in some way it does work. (And that 1 in 2 times you even have to
use power button to reboot; even, it starts rebooting, but it hangs in
halfway, and then you have to reach for the power button.)
I use: kwin-wayland-backend-drm
Because they say:
For X11 you need e.g. on Debian based systems the package kwin-wayland-
backend-x11. For the “real thing” you need: kwin-wayland-backend-drm
https://blog.martin-graesslin.com/blog/2016/07/why-does-kwin_wayland-not-start/
And I haven't been able to start kwin-wayland in another tty:
export $(dbus-launch)
kwin_wayland --xwayland --socket nested
=> failed
dbus-run-session startplasmacompositor
=> failed
But starting it from sddm worked right out of the box (though not really
usable for anything)
I've manually installed only one package: plasma-workspace-wayland,
and voila.
On Sunday, April 5, 2020 6:35:15 PM CEST you wrote:
> It is not the first time I describe the issue.
> Instead of remaining steadily turned off, the screen is turning on and off.
>
> The issue occurs randomly, and I can't find any trace of it in any log.
>
> Lately it did turn on and off for hours at intervals of about 10 min. And it
> did so before reboot and after reboot. (after reboot: user logged but no
> application specifically running)
>
> As you can understand it is really infuriating: flashing lights are usually
> not synonymous of quietness.
>
> As I already described, the setting is a 4K Dell monitor on display port, on
> a lid closed X230.
>
> And no, I can't just turn the screen off with the power button, because if I
> do so, kde freaks out and when I turn the screen back on the resolution for
> one thing, is so far away from initial settings, that I just can't see a
> thing; and also, it takes me hours to put back the settings right.
>
> I can't even keep the lid opened, because at that resolution, additional
> screen would be too much load for the gpu.
>
> That might be a little bit out of topic, because it is not specifically kde
> related. But I think Gnome is using Wayland. And I've found nothing about
> this sort of issues on the web. And it is not debian stable neither. irc
> seems a thing of the past... matrix.org debian-next is not working yet.
> xorg had never ever answered any question. I could make a bug report, but I
> don't know against what exactly.
>
> Only answer I've had, so far is "dpms and x11 are a crock of shit together,
> and web browsers are hilariously unpredictable actors in the x11 ecosystem"
> But I haven't found similar comments on the net. And it is not really
> hinting to any course of action.
>
> And again, I haven't been able to associate any traces of the malfunctioning
> with any logs: nothing specific seems to be recorded in the logs when the
> screen is flashing like a Christmas tree.
>
> I'm using rsyslogd and
> SYSTEMD_LESS=FRXMK journalctl -xa
> seems to show me everything there is.
> I haven't seen anything relevant in
> /var/log/Xorg.0.log
>
> Worth mentioning: I put the pc to sleep with: (the screen that is [*])
> xset dpms 10 10 10; sleep 10; xset dpms force off
> Then "C-l"
> Then after entering my password:
> xset dpms 1800 2700 3600
>
> But I don't thing it really influences the flashing effect; only the
> frequency of the flashing.
>
> Again, 9 times out of 10, it doesn't flash at all be behaves itself, like a
> good pc.
>
> [*] I cannot put the PC to sleep, nor suspend... I can, but it's
> complicated, and I don't think it works well.
> Because to restart the laptop, I'll have to make some event. But the lid is
> closed. So I'd have to manipulate the lid, but then kde will see that as a
> dual screen configuration, and it will freak out, and I will loose all my
> screen settings.
>
> When I restart the PC, I have to make a special dance:
> Open the lid; Press power button;
> Wait for grub screen...
> Then, at that moment, and that moment only,
> close the lid!
> Can you imagine the hassle.
>
> There must be much better solutions that I missed; only, I haven't found
> them yet.
Reply to: