unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexandros Theodotou <alex@zrythm.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 38163@debbugs.gnu.org
Subject: bug#38163: GDK does not return the monitor's refresh rate
Date: Mon, 11 Nov 2019 21:31:23 +0000	[thread overview]
Message-ID: <39ba9bcf7fc343bf9c7f173149f3009fe5df69b7.camel@zrythm.org> (raw)
In-Reply-To: <87v9rqm8y4.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]

Hi Ludo,

> Looking at GTK+, the ‘init_randr*’ functions in ‘gdkscreen-x11.c’
> appear
> to be those responsible for setting the ‘refresh_rate’ field.
> 
> However, AFAICS, our ‘gtk+’ package does not depend on ‘libxrandr’,
> and
> thus that functionality is simply compiled out (the function returns
> 0
> unconditionally).
> 
> Could you try adding that dependency on ‘libxrandr’ in ‘gtk+’?

Just tried that and it worked! It's returning the correct refresh rate
now:
** Message: 21:20:40.548: refresh rate returned by GDK: 60.0

> We won’t make this change in ‘master’ because it entails too many
> rebuilds, but it could go on the next branch for massive rebuilds. 

Makes sense. I will be using my local gtk+ version for a while then
until this change goes live.

Thanks for taking a look at this.

Alex

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-11-11 21:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 16:44 bug#38163: GDK does not return the monitor's refresh rate Alexandros Theodotou
2019-11-11 20:53 ` Ludovic Courtès
2019-11-11 21:31   ` Alexandros Theodotou [this message]
2019-11-13 20:56     ` Bengt Richter
2019-11-14 21:00       ` Ludovic Courtès
2019-11-15 18:24     ` Marius Bakke
2019-11-16 15:07       ` Ludovic Courtès
2020-05-27  0:10 ` Alexandros Theodotou

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39ba9bcf7fc343bf9c7f173149f3009fe5df69b7.camel@zrythm.org \
    --to=alex@zrythm.org \
    --cc=38163@debbugs.gnu.org \
    --cc=ludo@gnu.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).