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

Hi Alexandros,

Alexandros Theodotou <alex@zrythm.org> skribis:

> I have been developing and testing my GTK app (Zrythm) on many distros
> and Guix is the only case that the monitor's refresh rate is returned
> as 0.
>
> The API I am using is this:
> https://developer.gnome.org/gdk3/stable/GdkMonitor.html#gdk-monitor-get-refresh-rate

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+’?

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.

Thanks for your report,
Ludo’.

  reply	other threads:[~2019-11-11 20:54 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 [this message]
2019-11-11 21:31   ` Alexandros Theodotou
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=87v9rqm8y4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=38163@debbugs.gnu.org \
    --cc=alex@zrythm.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).