unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Bengt Richter <bokr@bokr.com>
Cc: Alexandros Theodotou <alex@zrythm.org>, 38163@debbugs.gnu.org
Subject: bug#38163: GDK does not return the monitor's refresh rate
Date: Thu, 14 Nov 2019 22:00:30 +0100	[thread overview]
Message-ID: <87h836npg1.fsf@gnu.org> (raw)
In-Reply-To: <20191113205624.GA48517@PhantoNv4ArchGx.localdomain> (Bengt Richter's message of "Wed, 13 Nov 2019 12:56:24 -0800")

Hi Bengt,

Bengt Richter <bokr@bokr.com> skribis:

> On +2019-11-11 21:31:23 +0000, Alexandros Theodotou wrote:

[...]

>> > 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

[...]

> I'm wondering about a narrowly-X solution.
>
> Shouldn't this really come from udevd noticing display changes?
> What about a multi-display seat, with potentially different refresh rates?
>
> IIUC it seems like libdrm and KMS can get at all that, so a light-weight solution
> should be possible, ISTM, and accessible from console command line without X.

You’re right, but note that GDK has several backends (not just X11), and
this issue was about fixing the problem with the X11 backend.

Thanks,
Ludo’.

  reply	other threads:[~2019-11-14 21:01 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
2019-11-13 20:56     ` Bengt Richter
2019-11-14 21:00       ` Ludovic Courtès [this message]
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=87h836npg1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=38163@debbugs.gnu.org \
    --cc=alex@zrythm.org \
    --cc=bokr@bokr.com \
    /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).