From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: kodi-18.7.1: Fix DPMS behaviour
Date: Fri, 29 Jan 2021 03:46:35 +0100 [thread overview]
Message-ID: <20210129024635.Zt8_PeeENINvEZ_-tx8KwyjlOF5_BIl1-DIaY2z1_Iw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23040@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
There's a closed pull request on the void-packages repository
kodi-18.7.1: Fix DPMS behaviour
https://github.com/void-linux/void-packages/pull/23040
Description:
Change to only recreate window when dpms is being disabled due to it
not working when the window is recreated as it is going into powersaving
on the display.
without the patch if you wait for the screen to go into powersaving (takes 5mins) or if you use
```xset dpms force off``` it will turn back on every time after approximately 12secs, with the patch it behaves as expected and stays off
also verified that python2 is required, specifically python >= 2.7
after discussing the issue on the kodi freenode irc chatroom i was stuck listening to a 5minute rant on "ricer" distros like void/arch and that everyone should be using librelec as such i have not pushed this to upstream yet, however looking at the commit logs for this particular part of code it seems the intention was that the code should only be run when dpms is being disabled so this patch just changes it to the intended behaviour
prev parent reply other threads:[~2021-01-29 2:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23040@inbox.vuxu.org>
2020-09-30 17:27 ` Hoshpak
2020-10-09 19:24 ` ericonr
2021-01-29 2:46 ` ericonr
2021-01-29 2:46 ` ericonr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210129024635.Zt8_PeeENINvEZ_-tx8KwyjlOF5_BIl1-DIaY2z1_Iw@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).