public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alexandre Restovtsev" <tetromino@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-desktop/, gnome-base/gnome-desktop/files/
Date: Wed,  5 Oct 2011 08:00:43 +0000 (UTC)	[thread overview]
Message-ID: <e62c70681e4ce3215f79860befcc518e5df17046.tetromino@gentoo> (raw)

commit:     e62c70681e4ce3215f79860befcc518e5df17046
Author:     Alexandre Rostovtsev <tetromino <AT> gmail <DOT> com>
AuthorDate: Wed Oct  5 07:58:32 2011 +0000
Commit:     Alexandre Restovtsev <tetromino <AT> gmail <DOT> com>
CommitDate: Wed Oct  5 07:58:32 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=e62c7068

gnome-base/gnome-desktop: fix DPMS timeout and mode setting

This is required for clearing DPMS timeouts and setting DPMS modes to
work on some hardware. Fixes e.g. the problems with gnome-settings-daemon
refusing to turn off the screen.

Upstream bug filed at https://bugzilla.gnome.org/show_bug.cgi?id=660962

---
 ...esktop-3.2.0-dpmssettimeouts-return-value.patch |   91 ++++++++++++++++++++
 ...2.0-r1.ebuild => gnome-desktop-3.2.0-r2.ebuild} |    4 +
 2 files changed, 95 insertions(+), 0 deletions(-)

diff --git a/gnome-base/gnome-desktop/files/gnome-desktop-3.2.0-dpmssettimeouts-return-value.patch b/gnome-base/gnome-desktop/files/gnome-desktop-3.2.0-dpmssettimeouts-return-value.patch
new file mode 100644
index 0000000..cd8b401
--- /dev/null
+++ b/gnome-base/gnome-desktop/files/gnome-desktop-3.2.0-dpmssettimeouts-return-value.patch
@@ -0,0 +1,91 @@
+From c33e020e4b6119b08c3748209360b7c826e0dfca Mon Sep 17 00:00:00 2001
+From: Alexandre Rostovtsev <tetromino@gmail.com>
+Date: Wed, 5 Oct 2011 02:27:48 -0400
+Subject: [PATCH] Ignore DPMSSetTimeouts() and DPMSForceLevel() return value
+
+At least with nvidia binary drivers, DPMSSetTimeouts() and DPMSForceLevel()
+always return BadRequest, even if they succeed. On a machine with intel
+graphics, DPMSForceLevel() was also observed to return BadRequest despite
+successfully changing the DPMS level. So we should just ignore the return
+value from these functions, like xset does.
+
+https://bugzilla.gnome.org/show_bug.cgi?id=660962
+---
+ libgnome-desktop/gnome-rr.c |   34 +++++++++++-----------------------
+ 1 files changed, 11 insertions(+), 23 deletions(-)
+
+diff --git a/libgnome-desktop/gnome-rr.c b/libgnome-desktop/gnome-rr.c
+index 465dee9..55ca03b 100644
+--- a/libgnome-desktop/gnome-rr.c
++++ b/libgnome-desktop/gnome-rr.c
+@@ -1240,24 +1240,17 @@ static gboolean
+ gnome_rr_screen_clear_dpms_timeouts (GnomeRRScreen *screen,
+                                      GError **error)
+ {
+-    gboolean ret = TRUE;
+-    gint rc;
+-
+     gdk_error_trap_push ();
+-    rc = DPMSSetTimeouts (screen->priv->xdisplay, 0, 0, 0);
+-    if (gdk_error_trap_pop ())
+-        ret = FALSE;
+-
+-    if (!ret || rc != Success) {
+-        ret = FALSE;
++    /* DPMSSetTimeouts() return value is often a lie, so ignore it */
++    DPMSSetTimeouts (screen->priv->xdisplay, 0, 0, 0);
++    if (gdk_error_trap_pop ()) {
+         g_set_error_literal (error,
+                              GNOME_RR_ERROR,
+                              GNOME_RR_ERROR_UNKNOWN,
+                              "Could not set DPMS timeouts");
+-        goto out;
++        return FALSE;
+     }
+-out:
+-    return ret;
++    return TRUE;
+ }
+ 
+ /**
+@@ -1272,7 +1265,6 @@ gnome_rr_screen_set_dpms_mode (GnomeRRScreen *screen,
+ {
+     CARD16 state = 0;
+     gboolean ret;
+-    gint rc;
+     GnomeRRDpmsMode current_mode;
+ 
+     g_return_val_if_fail (error == NULL || *error == NULL, FALSE);
+@@ -1305,11 +1297,9 @@ gnome_rr_screen_set_dpms_mode (GnomeRRScreen *screen,
+     }
+ 
+     gdk_error_trap_push ();
+-    rc = DPMSForceLevel (screen->priv->xdisplay, state);
+-    if (gdk_error_trap_pop ())
+-        ret = FALSE;
+-
+-    if (!ret || rc != Success) {
++    /* DPMSForceLevel() return value is often a lie, so ignore it */
++    DPMSForceLevel (screen->priv->xdisplay, state);
++    if (gdk_error_trap_pop ()) {
+         ret = FALSE;
+         g_set_error_literal (error,
+                              GNOME_RR_ERROR,
+@@ -1319,11 +1309,9 @@ gnome_rr_screen_set_dpms_mode (GnomeRRScreen *screen,
+     }
+ 
+     gdk_error_trap_push ();
+-    rc = DPMSSetTimeouts (screen->priv->xdisplay, 0, 0, 0);
+-    if (gdk_error_trap_pop ())
+-        ret = FALSE;
+-
+-    if (!ret || rc != Success) {
++    /* DPMSSetTimeouts() return value is often a lie, so ignore it */
++    DPMSSetTimeouts (screen->priv->xdisplay, 0, 0, 0);
++    if (gdk_error_trap_pop ()) {
+         ret = FALSE;
+         g_set_error_literal (error,
+                              GNOME_RR_ERROR,
+-- 
+1.7.7
+

diff --git a/gnome-base/gnome-desktop/gnome-desktop-3.2.0-r1.ebuild b/gnome-base/gnome-desktop/gnome-desktop-3.2.0-r2.ebuild
similarity index 93%
rename from gnome-base/gnome-desktop/gnome-desktop-3.2.0-r1.ebuild
rename to gnome-base/gnome-desktop/gnome-desktop-3.2.0-r2.ebuild
index ffbc212..3b01e21 100644
--- a/gnome-base/gnome-desktop/gnome-desktop-3.2.0-r1.ebuild
+++ b/gnome-base/gnome-desktop/gnome-desktop-3.2.0-r2.ebuild
@@ -93,5 +93,9 @@ src_prepare() {
 	# Fix GNomeWallClock fallback code
 	epatch "${FILESDIR}/${P}-GnomeWallClock-fallback.patch"
 
+	# Required for setting DPMS timeouts and modes to work on some hardware;
+	# https://bugzilla.gnome.org/show_bug.cgi?id=660962
+	epatch "${FILESDIR}/${P}-dpmssettimeouts-return-value.patch"
+
 	gnome2_src_prepare
 }



             reply	other threads:[~2011-10-05  8:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05  8:00 Alexandre Restovtsev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-14 21:00 [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-desktop/, gnome-base/gnome-desktop/files/ Sobhan Mohammadpour
2019-02-23 20:37 Mart Raudsepp
2018-11-16 17:25 Gilles Dartiguelongue
2012-11-21 22:27 Gilles Dartiguelongue
2012-10-28 16:42 Gilles Dartiguelongue
2011-10-18  7:37 Alexandre Restovtsev
2011-10-04  4:04 Alexandre Restovtsev
2011-05-30 17:11 Nirbheek Chauhan
2011-05-02 15:56 Nirbheek Chauhan

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=e62c70681e4ce3215f79860befcc518e5df17046.tetromino@gentoo \
    --to=tetromino@gmail.com \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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