UNSUBSCRIBE
Il giorno mer 26 feb 2020 alle ore 17:18 inkbottle <
[email protected]>
ha scritto:
*Intro:*
My screen randomly wakes up from standby / energy saving mode and it's a
very
very very annoying issue which cause I unfortunately have not the faintest clue about.
It is not something I can reproduce, so the best I can do is a sort of
"case
report".
*What happened:*
The screen woke up from energy saving mode all by itself.
I just had done an upgrade, so the system was up to date.
I had rebooted twice.
The screen initially went in energy saving mode from sddm: there were no active session. I think there even have been no session between last
reboot
and screen-standby.
Nobody was near the computer, and there was no earthquake at that time,
nor
any source of vibrations (note that I did try with mouses unplugged and
that
it made no difference).
I took note of the time on my phone.
When later I looked into "journalctl -a", there was no recorded events
around
the time of the incident. Not a line has been written in journalctl at or around that time. (My journalctl is on keep everything forever mode.)
*The general setting:*
It is an external screen connected to a lid-closed laptop through display port
(Lenovo x230, intel integrated gpu; Monitor is 4K Dell; Connection is
Display
Port).
I don't see anything else specific about it. I try never to do anything
fancy
with admin.
*Why is it so annoying:*
It is a huge distraction when the screen is turning on all by itself randomly.
Due to the settings described above, I cannot turn the screen off using
the
physical button.
My primary screen is the external screen. The lid of the laptop being
closed,
the screen of the laptop is altogether deactivated.
This is the configuration recorded in settings and it works well.
Now if I turn the external display off with the physical button:
The above configuration is becoming unrealistic.
Consequently the system has to go to a default realistic configuration,
which
it does very well: The laptop's screen becomes the primary display...
But that changes all the settings.
And since there is no different settings for different screens configurations,
my settings are necessarily just ditched away.
It would be too long to describe all the settings that are lost during
this
phase.
With a 4K monitor on a 3rd generation i5, the gpu is already to the limit
of
what it can do. I "could" keep the lid of the laptop open, and the laptop screen not disabled, etc. But that would take more place on my desk, put additional strain on the system.
As a consequence of all that, all I can do is turn the computer off.
And with the lid closed and all that, the whole sequence is something very difficult to do.
<div dir="ltr">UNSUBSCRIBE<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno mer 26 feb 2020 alle ore 17:18 inkbottle <<a href="mailto:
[email protected]">
[email protected]</a>> ha scritto:<br></div><
blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">*Intro:*<br>
My screen randomly wakes up from standby / energy saving mode and it's a very <br>
very very annoying issue which cause I unfortunately have not the faintest <br> clue about.<br>
It is not something I can reproduce, so the best I can do is a sort of "case <br>
report".<br>
*What happened:*<br>
The screen woke up from energy saving mode all by itself.<br>
I just had done an upgrade, so the system was up to date.<br>
I had rebooted twice.<br>
The screen initially went in energy saving mode from sddm: there were no <br> active session. I think there even have been no session between last reboot <br>
and screen-standby.<br>
Nobody was near the computer, and there was no earthquake at that time, nor <br>
any source of vibrations (note that I did try with mouses unplugged and that <br>
it made no difference).<br>
I took note of the time on my phone.<br>
When later I looked into "journalctl -a", there was no recorded events around <br>
the time of the incident. Not a line has been written in journalctl at or <br> around that time. (My journalctl is on keep everything forever mode.)<br>
*The general setting:*<br>
It is an external screen connected to a lid-closed laptop through display port <br>
(Lenovo x230, intel integrated gpu; Monitor is 4K Dell; Connection is Display <br>
Port).<br>
I don't see anything else specific about it. I try never to do anything fancy <br>
with admin.<br>
*Why is it so annoying:*<br>
It is a huge distraction when the screen is turning on all by itself randomly.<br>
Due to the settings described above, I cannot turn the screen off using the <br>
physical button.<br>
My primary screen is the external screen. The lid of the laptop being closed, <br>
the screen of the laptop is altogether deactivated.<br>
This is the configuration recorded in settings and it works well.<br>
Now if I turn the external display off with the physical button:<br>
The above configuration is becoming unrealistic.<br>
Consequently the system has to go to a default realistic configuration, which <br>
it does very well: The laptop's screen becomes the primary display...<br> But that changes all the settings.<br>
And since there is no different settings for different screens configurations, <br>
my settings are necessarily just ditched away.<br>
It would be too long to describe all the settings that are lost during this <br>
phase.<br>
With a 4K monitor on a 3rd generation i5, the gpu is already to the limit of <br>
what it can do. I "could" keep the lid of the laptop open, and the laptop <br>
screen not disabled, etc. But that would take more place on my desk, put <br> additional strain on the system.<br>
As a consequence of all that, all I can do is turn the computer off.<br>
And with the lid closed and all that, the whole sequence is something very <br> difficult to do.<br>
</blockquote></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)