gnome-settings-daemon issueshttps://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues2023-03-28T22:36:25Zhttps://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/737Brightness at minimum after disconnecting from docking station with LID closed2023-03-28T22:36:25ZFrédéric ParreninBrightness at minimum after disconnecting from docking station with LID closedI have a Dell XPS13-9370 laptop which I connect to a DS1000 docking station from Dell.\
When I connect/disconnect the laptop from the docking station, the LID is closed since I usually use only the external display.\
I noticed that when ...I have a Dell XPS13-9370 laptop which I connect to a DS1000 docking station from Dell.\
When I connect/disconnect the laptop from the docking station, the LID is closed since I usually use only the external display.\
I noticed that when I disconnect the laptop and re-open the LID after a while, the brightness is at minimum.\
So each time this happens, I have to increase the brightness, which is not terrible but I think it this is a bug which should be corrected.https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/699Enable auto-hide for battery notification2022-08-09T08:58:35Zsebastian387Enable auto-hide for battery notificationDescription of issue:
I have an ASUS ExpertBook B5 Flip which incorrectly reports any stylus pen as having 1% battery charge remaining, no matter what the actual charge of the battery is. The notification pops up and doesn't hide, but st...Description of issue:
I have an ASUS ExpertBook B5 Flip which incorrectly reports any stylus pen as having 1% battery charge remaining, no matter what the actual charge of the battery is. The notification pops up and doesn't hide, but stays on top of all other applications. I then have to manually click on the notification's close symbol ("x") which is very small, otherwise it opens GNOME Energy Settings. This behaviour is annoying to the user.
Recommendation / idea on how to progress:
Since we have to assume that there are a lot of such faulty devices out there, the most logical solution would be to:
1. Enable auto-hide for all mouse and keyboard battery notifications. (laptop battery shouldn't auto-hide though, since these report their battery percentage correctly & are too important for the user to miss them, so this is fine)
1. Create a "permanently dismiss" option. Or alternatively, a blacklist file where you can enter the upower devices that GNOME should ignore, manually on the terminal for such use cases.
I'd love for somebody to resolve this issue! Thank you very much in advance! Sebastianhttps://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/639power: Changes to power saver profile even when session is not active2021-10-28T08:08:07ZSebastian Kellerpower: Changes to power saver profile even when session is not activeI often have a jhbuild session running as a different user in the background and noticed several times now that power mode is being changed to power-saver when my battery is running low despite having `power-saver-profile-on-low-battery`...I often have a jhbuild session running as a different user in the background and noticed several times now that power mode is being changed to power-saver when my battery is running low despite having `power-saver-profile-on-low-battery` disabled in my main profile. So I'm assuming that the change is coming from my jhbuild session where I haven't changed that setting. From a quick glance at the code it doesn't seem to be checking if the current session is the active one before applying this (unless I missed it).https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/630Ignore screensaver inhibitors on lockscreen2021-12-14T10:47:39ZArtur RudenkoIgnore screensaver inhibitors on lockscreenScreensaver inhibitors don't need to work on lock screen because there is nothing to see. For example, if I open chromium with youtube video, then lock the screen, screen won't turn off because there's chrome inhibitor, but I can't see t...Screensaver inhibitors don't need to work on lock screen because there is nothing to see. For example, if I open chromium with youtube video, then lock the screen, screen won't turn off because there's chrome inhibitor, but I can't see the video so it's useless.https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/622Reconsider "idle-dim" feature2021-08-09T16:27:58ZBastien NoceraReconsider "idle-dim" featureFollowing the changes to idle-dim in GNOME 41, we should consider whether we want to:
- remove idle-dim and always dim when possible
- whether we should screensave harder instead of dimming
- whether dimming after half the timeout to scr...Following the changes to idle-dim in GNOME 41, we should consider whether we want to:
- remove idle-dim and always dim when possible
- whether we should screensave harder instead of dimming
- whether dimming after half the timeout to screensave is aggressive enough
- whether users expect the "power-saver" dimming to be something that should get disabled by the "idle-dim" option
CC @adayhttps://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/620Redesign device low battery notifications2021-07-22T15:32:23ZBastien NoceraRedesign device low battery notificationsThe low battery notifications are really pretty poor:
- they repeat information (the device type, the fact that the battery is low)
- they're tedious to translate and a fair few aren't translated (see https://gitlab.gnome.org/GNOME/gnome...The low battery notifications are really pretty poor:
- they repeat information (the device type, the fact that the battery is low)
- they're tedious to translate and a fair few aren't translated (see https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/607#note_1208764)
- they give "advice" that's not that helpful ("charge your device! why didn't I think of that!?", or "charge your device? it takes batteries)
- the device name isn't shown at all
- they have grammar that's not obvious to non-English speakers (non-British English speakers?): https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/107
Prior art
iOS:
![image](/uploads/0c872bcaf79698d6b86bad640ac357c3/image.png)
The iOS notification:
- doesn't repeat information
- shows rather than reads out the battery level through an icon
- shows the device type and name to make it recognisable
We should probably have some text though, so it can be read out by screen readers, like "Sony XYZ low battery (5%)" or "Keyboard low battery".
But we don't have a way to show 2 icons, or have the notification look good with only a title and no subtitle.https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/494Lock screen blanking timeout2022-07-24T22:40:39ZAnton AlexandrenokLock screen blanking timeout<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
<!--
Describe what you would like to be able to do with GNOME...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
<!--
Describe what you would like to be able to do with GNOME Shell
that you currently cannot do.
-->
I want to have a setting for a timeout of how long the lock screen is shown before turning off the screen.
### How would you like it to work
<!--
If you can think of a way GNOME Shell might be able to do this,
let us know here.
-->
If you lock your screen, it immediately goes blank and monitor switches to the stand-by mode. If I change my mind and want to unlock back, there will be a delay while my monitor is turning back (a couple of seconds). Also, sometimes it is useful to just have a glimpse on a clock/notification/battery. Having a configurable delay (5 sec by default) between showing the lock screen and switching it blank would help with both of those issues.
### Relevant links, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation,
code, mockups or a similar feature in another desktop environments,
please provide them here.
-->
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/472Dim screen when on battery (i.e. when AC is disconnected).2019-11-21T11:22:46ZChristian KellnerDim screen when on battery (i.e. when AC is disconnected).For most laptops and use-cases the screen-backlight is the number biggest consumer of energy. Therefore when switching from AC to battery, it makes sense to reduce the screen brightness. I personally keep repeating the following steps: w...For most laptops and use-cases the screen-backlight is the number biggest consumer of energy. Therefore when switching from AC to battery, it makes sense to reduce the screen brightness. I personally keep repeating the following steps: when undock (unplug) the computer, manually reduce the screen brightness; when docking (attach power), increase the screen brightness again.
Windows seems to be having two different "save points"/"settings" for the brightness, one for AC, one for battery. macOS only does dim the screen slightly and there is a settings to turn it of.
Had a chat with @aday about it and something like the latter is probably more what we want.https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/441Keyboard backlight level lost after suspend/resume on Thinkpad X1 Yoga2020-01-23T01:26:43ZCosimo CecchiKeyboard backlight level lost after suspend/resume on Thinkpad X1 YogaOn my Thinkpad X1 Yoga under Fedora 30 Silverblue (g-s-d 3.32.1), when I suspend and resume the laptop, the keyboard backlight level is lost and set to zero.
I'm not sure this is a g-s-d issue or a driver/firmware one, but perhaps there...On my Thinkpad X1 Yoga under Fedora 30 Silverblue (g-s-d 3.32.1), when I suspend and resume the laptop, the keyboard backlight level is lost and set to zero.
I'm not sure this is a g-s-d issue or a driver/firmware one, but perhaps there's something g-s-d could do to make sure the backlight level is restored upon resume...https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/434Don't automatically turn off monitor when music is being played through that ...2019-08-10T04:32:21ZNelson BenDon't automatically turn off monitor when music is being played through that same monitorI have a "turn off screen after 15 min." energy saving setting enabled, that's fine. But sometimes I left my system playing music from youtube or rhythmbox, my sound output device are the speakers on my monitor (I use an external monitor...I have a "turn off screen after 15 min." energy saving setting enabled, that's fine. But sometimes I left my system playing music from youtube or rhythmbox, my sound output device are the speakers on my monitor (I use an external monitor) so this means after 15 min. the monitor will turn off and music stops :disappointed: .
I request an enhancement where the "automatically turn off monitor" setting is ignored if **1)** the system sound output goes through the monitor itself and **2)** the system is currently playing music.
If you agree with this, and can give me some pointers where in the code this could be implemented, I can devote time to put up a MR.
Thanks,
PS. I think we are lacking a `sound` issue label.https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/420Display notification when computer was shutdown due to low battery2019-09-03T13:05:45ZGhost UserDisplay notification when computer was shutdown due to low batteryAfter a computer was shutdown due to critically low battery level a notification should be displayed that indicates the reason for the unexpected shutdown.
In general the user should be informed about the reason for any shutdown that wa...After a computer was shutdown due to critically low battery level a notification should be displayed that indicates the reason for the unexpected shutdown.
In general the user should be informed about the reason for any shutdown that was not initiated by the user.https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/376Do not unblank the screen when AC is plugged/unplugged2019-03-20T11:50:37ZBugzillaDo not unblank the screen when AC is plugged/unplugged## Submitted by Benjamin Berg `@bberg`
**[Link to original bug (#792213)](https://bugzilla.gnome.org/show_bug.cgi?id=792213)**
## Description
A patch to not unblank the screen in this case.
Note that the test depends on a helper fu...## Submitted by Benjamin Berg `@bberg`
**[Link to original bug (#792213)](https://bugzilla.gnome.org/show_bug.cgi?id=792213)**
## Description
A patch to not unblank the screen in this case.
Note that the test depends on a helper function added in bug #792209 (attachment #366310).https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/372Same action is forced for lid-close on AC and lid-close on battery2019-03-20T11:50:07ZBugzillaSame action is forced for lid-close on AC and lid-close on battery## Submitted by Kim Nguyen
**[Link to original bug (#790607)](https://bugzilla.gnome.org/show_bug.cgi?id=790607)**
## Description
Created attachment 364040
Custom Suspend action
Since the action to perform on lid-closed has been tr...## Submitted by Kim Nguyen
**[Link to original bug (#790607)](https://bugzilla.gnome.org/show_bug.cgi?id=790607)**
## Description
Created attachment 364040
Custom Suspend action
Since the action to perform on lid-closed has been transferred from gsd-power to logind, one has lost the ability to differentiate between the action to perform when on battery from the one to perform when on AC (admittedly because systemd-logind has no knowledge of ACPI events but gets the lid close/open from the input layer).
I only realised this recently when ubuntu switched to gnome-shell. Previously, ubuntu was using unity-settings-daemon by default (fork of an older version of gsd) which handled power policy itself.
This is a regression of a useful feature. For sure if you have a laptop you want to suspend when the lid is closed and on battery (and not plugged to external monitor or dock etc…).
But most of the time, when plugged on AC you don't want your background actions to stop when you close the lid (e.g. download, software update etc…).
The situation is a bit confusing because the corresponding gsettings still exist:
- org.gnome.settings-daemon.plugins.power lid-close-ac-action
- org.gnome.settings-daemon.plugins.power lid-close-battery-action
in but don't do anything.
As a reference, macos and windows 10 still allow the user to define a different lid close action for battery and AC (through their main UI none the less, it's not a hidden setting).
There is nothing that prevent the behaviour from being restored. I'm attaching a python script (lightly tested) to be launched with:
systemd-inhibit --who=me --why=because --mode=block --what=handle-lid-switch /path/to/custom_suspend.py
That take whatever is in the gsettings mentioned above and performs the action (through systemd).
It's just a proof of concept. I think there is now a proliferation of systemd inhibitors to handle various cases that obviously systemd-logind cannot handle:
- inhibit when fullscreen application running
- handle battery/ac differently
- inhibit and handle the doc/screen/external peripherials correctly
Maybe systemd is the right place to have the suspend primitive enabled but the power-policy seems higher level than logind and centralized in a component (systemd-powerd ?), or have logind gain real power management policy handling.
**Attachment 364040**, "Custom Suspend action":
[custom_suspend.py](/uploads/d6bca29d9769b4c03c06b3b1b715c328/custom_suspend.py)
Version: 3.26.xhttps://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/359Brightness control not working on laptop with Nvidia GPU2019-03-21T16:41:04ZBugzillaBrightness control not working on laptop with Nvidia GPU## Submitted by saf..@..il.com
**[Link to original bug (#788355)](https://bugzilla.gnome.org/show_bug.cgi?id=788355)**
## Description
The brightness control doesn't work when running GNOME 3.26 on a Dell Vostro 3300 with a Nvidia 31...## Submitted by saf..@..il.com
**[Link to original bug (#788355)](https://bugzilla.gnome.org/show_bug.cgi?id=788355)**
## Description
The brightness control doesn't work when running GNOME 3.26 on a Dell Vostro 3300 with a Nvidia 310M
The laptop keys Fn+Up/Down are what usually control the brightness and work fine on Unity 7 (for example).
Version: 3.26.xhttps://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/334add support for ConsoleKit22019-09-24T15:00:10ZBugzillaadd support for ConsoleKit2## Submitted by Eric Koegel
**[Link to original bug (#783335)](https://bugzilla.gnome.org/show_bug.cgi?id=783335)**
## Description
Created attachment 353039
add support for ConsoleKit2
ConsoleKit2 provides the same dbus methods as ...## Submitted by Eric Koegel
**[Link to original bug (#783335)](https://bugzilla.gnome.org/show_bug.cgi?id=783335)**
## Description
Created attachment 353039
add support for ConsoleKit2
ConsoleKit2 provides the same dbus methods as logind for PowerOff,
Suspend, Inhibit, etc so attempt to use it if connecting to logind
fails. This will help the BSDs have a smaller patch set to maintain to keep GNOME support.
I tried to make the changes as small as possible, i.e. I didn't rename the logind_proxy since it's doing the same thing anyway.
**Patch 353039**, "add support for ConsoleKit2":
[0001-Add-ConsoleKit2-Support.patch](/uploads/b2755c149c644c54b0dc07ab1d9a359a/0001-Add-ConsoleKit2-Support.patch)https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/326suspend notification does not go away when using mouse or keyboard2019-03-20T11:40:17ZBugzillasuspend notification does not go away when using mouse or keyboard## Submitted by Christian Stadelmann `@genodeftest`
**[Link to original bug (#780987)](https://bugzilla.gnome.org/show_bug.cgi?id=780987)**
## Description
Steps to reproduce:
1. In gnome-control-center, section "Power", make sure th...## Submitted by Christian Stadelmann `@genodeftest`
**[Link to original bug (#780987)](https://bugzilla.gnome.org/show_bug.cgi?id=780987)**
## Description
Steps to reproduce:
1. In gnome-control-center, section "Power", make sure the screen does not go blank before your computer suspends
2. wait for the suspend limit to be reached. You'll get a notification saying the computer is about to be suspended very soon.
3. use your mouse and/or keyboard
What happens:
The notification does not go away.
What should happen:
The moment I start using mouse or keyboard again, the notification should go away. This way the user will get feedback that the *suspend countdown* has been stopped and suspend won't happen any time soon.
Installed software versions:
gnome-shell-3.22.3-1.fc25.x86_64
libinput-1.6.3-3.fc25.x86_64
Version: 3.22.xhttps://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/325Remove GTK+ dependency2019-03-20T11:40:09ZBugzillaRemove GTK+ dependency## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#780604)](https://bugzilla.gnome.org/show_bug.cgi?id=780604)**
## Description
It's only used to play a couple of sounds.
Version: 3.24.x## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#780604)](https://bugzilla.gnome.org/show_bug.cgi?id=780604)**
## Description
It's only used to play a couple of sounds.
Version: 3.24.xhttps://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/319Screen doesn't blank when unused on boot2019-03-21T16:17:11ZBugzillaScreen doesn't blank when unused on boot## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#778462)](https://bugzilla.gnome.org/show_bug.cgi?id=778462)**
## Description
gnome-settings-daemon-3.23.3-1.fc26.x86_64
1. Boot computer
2. Stay on login screen and...## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#778462)](https://bugzilla.gnome.org/show_bug.cgi?id=778462)**
## Description
gnome-settings-daemon-3.23.3-1.fc26.x86_64
1. Boot computer
2. Stay on login screen and wait for screensaver
3. Screen goes black but no screen blank
Version: 3.23.xhttps://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/306Add support for 3 brightness levels for the keyboard backlight2021-11-25T15:07:05ZBugzillaAdd support for 3 brightness levels for the keyboard backlight## Submitted by Luca Mastromatteo `@Luky`
**[Link to original bug (#772517)](https://bugzilla.gnome.org/show_bug.cgi?id=772517)**
## Description
I own a dell XPS 15, which has a backlighted keyboard that only supports 0%, 50% and 10...## Submitted by Luca Mastromatteo `@Luky`
**[Link to original bug (#772517)](https://bugzilla.gnome.org/show_bug.cgi?id=772517)**
## Description
I own a dell XPS 15, which has a backlighted keyboard that only supports 0%, 50% and 100% brightness.
The brightness control, from the gnome control center, seems to be broken, since it doesn't move properly and does not detect that my PC supports only 3 levels.
In another desktop environment the control works flawlessly (the latest kde plasma build)https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/295Misleading wireless mouse power warning2019-03-20T11:33:04ZBugzillaMisleading wireless mouse power warning## Submitted by jgo..@..il.com
**[Link to original bug (#765069)](https://bugzilla.gnome.org/show_bug.cgi?id=765069)**
## Description
This has been a bug for 5-10 years or maybe longer. When my alkaline battery powered wireless USB ...## Submitted by jgo..@..il.com
**[Link to original bug (#765069)](https://bugzilla.gnome.org/show_bug.cgi?id=765069)**
## Description
This has been a bug for 5-10 years or maybe longer. When my alkaline battery powered wireless USB mouse runs low on power I get this warning:
"This device will soon stop functioning if not charged."
This error is clearly incorrect. Alkaline batteries are replaced, never charged. Manufacturers normally warn you that alkaline batteries could explode if recharged. I know that the GNOME team doesn't want to cause any explosions, so I propose this fix. Unfortunately, it will require 95 translations. I don't have that patch.
Incidentally, my wireless keyboard also runs on alkaline batteries, and the warning is also wrong.
--- gsd-power-manager.c.orig 2016-04-14 14:44:22.844962674 -0400
+++ gsd-power-manager.c 2016-04-14 14:50:11.475943592 -0400
@@ -457,7 +457,7 @@
g_free (remaining_text);
} else if (kind == UP_DEVICE_KIND_MOUSE) {
/* TRANSLATORS: mouse is getting a little low */
- title = _("Mouse battery low");
+ title = _("Mouse power low");
/* TRANSLATORS: tell user more details */
message = g_strdup_printf (_("Wireless mouse is low in power (%.0f%%)"), percentage);
@@ -591,11 +591,12 @@
g_free (remaining_text);
} else if (kind == UP_DEVICE_KIND_MOUSE) {
/* TRANSLATORS: the mouse battery is very low */
- title = _("Mouse battery low");
+ title = _("Mouse power low");
/* TRANSLATORS: the device is just going to stop working */
message = g_strdup_printf (_("Wireless mouse is very low in power (%.0f%%). "
- "This device will soon stop functioning if not charged."),
+ "This device will soon stop functioning if batteries " .
+ "are not replaced or recharged."),
percentage);
} else if (kind == UP_DEVICE_KIND_KEYBOARD) {
/* TRANSLATORS: the keyboard battery is very low */
Version: 3.20.x