After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 758535 - Can't change screen brightness without reloading plugin
Can't change screen brightness without reloading plugin
Product: gnome-settings-daemon
Classification: Core
Component: power
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
Depends on:
Reported: 2015-11-23 11:57 UTC by Mario Sánchez Prada
Modified: 2019-03-20 11:31 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Mario Sánchez Prada 2015-11-23 11:57:14 UTC
For some strange reason, since the last upgrade of my Fedora 23 box, I no longer can change screen brightness at all whenever I start a fresh GNOME session (I can still do it from GDM's screen, though), no matter it's for my regular user or for a different one (I've tried creating another user just to test, and did not work either).

The initial symptom was that using the special keys of my laptop would not work (not even the screen brightness overlay would show up), even though I could use the other special keys to change volume up and down. Then, after making sure that those keypresses were actually being recognized, I realized that not even changing the screen brightness from the top panel or gnome-control-center would work either.

After a bit of debugging, I found out that the problem is that the power plugin was early exiting here, in on_rr_screen_acquired():

    static void
    on_rr_screen_acquired (GObject      *object,
                           GAsyncResult *result,
                           gpointer      user_data)
            GsdPowerManager *manager = user_data;
            GError *error = NULL;
            gnome_settings_profile_start (NULL);
            manager->priv->rr_screen = gnome_rr_screen_new_finish (result, &error);
            if (error) {
                    g_warning ("Could not create GnomeRRScreen: %s\n", error->message);
                    g_error_free (error);
                    gnome_settings_profile_end (NULL);
            /* set up the screens */

Looking at the commit where that early return was introduced[1], reading the bug description at [2] and hten double-checking that gnome-settings-daemon's PID is actually lower than gnome-shell's, makes me think this might actually be another incarnation of bug 719974, perhaps in gnome-shell even, but reporting it here for now. I'm adding Carlos Garnacho to CC, just in case.

My current workaround for this is simply de-activating and re-activating the power plugin again from GSetting property, or simply killing the g-s-d process and let it restart again, but it would be nice to fix this upstream.

Last, some relevant bits describiing my current environment:

 - Fedora 23 64 bit with Kernel 4.2.6-300.fc23.x86_64
 - gnome-session-xsession-
 - gnome-shell-3.18.1-1.fc23.x86_64
 - gnome-settings-daemon-3.18.1-1.fc23.x86_64

Comment 1 Rui Matos 2015-11-24 15:07:13 UTC
What's the error message you get from that g_warning ?
Comment 2 Mario Sánchez Prada 2015-11-24 15:47:45 UTC
I can't remember clearly right now, but it was something like "timeout reached".

I will try to get it later today, though.
Comment 3 Mario Sánchez Prada 2015-11-24 15:50:17 UTC
Oh! I have it around, actually:

Nov 22 17:10:42 moucho gnome-settings-daemon.desktop[2297]: (gnome-settings-daemon:2297): power-plugin-WARNING **: Could not create GnomeRRScreen: Timeout was reached
Comment 4 GNOME Infrastructure Team 2019-03-20 11:31:36 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: