The issue is gone after upgrading gnome-control-center.
---
Bionic: ubuntu-18.04.2-desktop-amd64.iso
Xenial: ubuntu-gnome-16.04.5-desktop-amd64.iso
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed-xenial
** Tags added:
The issue is gone after upgrading gnome-control-center to
1:3.32.2-0ubuntu1.
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
@Sebastien
Please check the diff for xenial as attached.
** Patch added: "xenial.diff"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261724/+files/xenial.diff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Patch added: "xenial.diff"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261103/+files/xenial.diff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Patch added: "disco.diff"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261105/+files/disco.diff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Patch added: "bionic.diff"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261104/+files/bionic.diff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
@Sebastien
The description has been updated.
** Description changed:
[Impact]
- Power: Fail to set delay time when the value is 90 minutes
+ Fail to set delay time when the value is 90 minutes.
+
+ In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400
+ (90*60). When
** Attachment added: "1_set-delay-to-90-mins.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5260822/+files/1_set-delay-to-90-mins.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The attached patch has been accepted by upstream.
Please help to backport it to bionic and xenial.
** Patch added: "0001-power-correct-the-value-of-90-minutes-to-5400.patch"
** Attachment added: "2_value-is-80-after-reopen-power-settings.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5260823/+files/2_value-is-80-after-reopen-power-settings.png
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
[Impact]
Power: Fail to set delay time when the value is 90 minutes
[Test Case]
1) Go to [All Settings][Power][Automatic suspend]
2) Set delay time to 90 minutes (On Battery Power or Plugged in)
3) Close [All Settings]
4) Reopen [All Settings][Power][Automatic suspend]
@Sebastien
Yes. I have one project using GNOME.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1827030
Title:
Keyboard brightness control not working
To manage
The issue can be fixed by the commit below.
Please help to backport it to xenial.
commit 2b28b00a7e9ef21d3b94277e517692896e46e58c
Author: Hans de Goede
Date: Fri Oct 14 18:25:35 2016 +0200
power: The Power.Keyboard.Brightness property is in percent
--
You received this bug notification
Public bug reported:
[Impact]
Keyboard brightness control not working
[Test Case]
1) Go to [All Settings][Power][Keyboard brightness]
2) Adjust keyboard brightness by sidebar
---
$ cat /sys/class/leds/dell::/kbd_backlight/max_brightness
2
The valid value for my machine is 0, 1, and 2.
The
@Brian
The issue is gone after upgrading gnome-settings-daemon to 3.28.1-0ubuntu1.1.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
@Sebastien
The patch has been merged. Could you help to land it to bionic? Thanks~
commit a5514ae097e5881df3ef26c63f4f4652b3f77811
Author: Ethan Hsieh
Date: Tue Oct 9 10:28:31 2018 +0800
rfkill: set encoding as NULL
The default encoding for GIOChannel is UTF-8, but rfkill event
Thanks for your reminder. Bug description has been updated.
** Description changed:
+ [Impact]
+
+ The default encoding for GIOChannel is UTF-8, but rfkill event is binary
+ data. gsd-rfkill-manager will fail to receive rfkill event if rfkill-idx
+ is larger than 127.
+
+ The solution is to
Public bug reported:
The default encoding for GIOChannel is UTF-8, but rfkill event is binary
data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to
receive rfkill event.
Steps: Run suspend/resume Test (> 127 times)
Failure Rate: 100%
In some platforms, bt will be re-probed after
Have sent a merge request to GitLab and wait for approval.
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/57
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Public bug reported:
1) The release of Ubuntu you are using
lsb_release: Ubuntu 16.04 LTS release 16.04
kernel: 4.4.0-36-generic
2) The version of the package you are using
gnome-screensaver: 3.6.1-7ubuntu4
unity-settings-daemon: 15.04.1+16.04.20160701-0ubuntu1
Graphic: nvidia (driver 370.23)
Log:
(unity-settings-daemon:1845): power-plugin-DEBUG:
==> system wakes up after pressing the key
Received session is active change: now inactive
Received session is active change: now active
Doing a state transition: normal
TESTSUITE: Unblanked screen
Adding suspend delay inhibitor
Received
21 matches
Mail list logo
