[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
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: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
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 Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
@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, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** 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. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** 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. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** 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. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
@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 setting the delay time to 90 minutes, the UI will show "80 + minutes" after reopening "All Settings". (Please refer to the photo in + #1 and #2) [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] - 5) The value of delay time is 80 minutes + 5) Check if the value is 90 minutes. + + [Regression Potential] + + Low. The value of 90 minutes is wrong. Just correct the value to 5400. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** 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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
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" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5260824/+files/0001-power-correct-the-value-of-90-minutes-to-5400.patch ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** Changed in: oem-priority/bionic Importance: Undecided => High ** Changed in: oem-priority/xenial Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** 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 Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827346] [NEW] Power: Fail to set delay time when the value is 90 minutes
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] 5) The value of delay time is 80 minutes ** Affects: oem-priority Importance: High Status: New ** Affects: oem-priority/bionic Importance: High Status: New ** Affects: oem-priority/xenial Importance: High Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Changed in: oem-priority/bionic Importance: Undecided => High ** Changed in: oem-priority/xenial Importance: Undecided => High ** No longer affects: oem-priority ** No longer affects: oem-priority/bionic ** No longer affects: oem-priority/xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827030] Re: Keyboard brightness control not working
@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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827030] Re: Keyboard brightness control not working
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 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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827030] [NEW] Keyboard brightness control not working
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 Power.Keyboard.Brightness property should be in percent. ** Affects: oem-priority Importance: High Status: New ** Affects: oem-priority/xenial Importance: High Status: New ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Patch added: "0001-New-upstream-bug-fix-release.patch" https://bugs.launchpad.net/bugs/1827030/+attachment/5260251/+files/0001-New-upstream-bug-fix-release.patch ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** Changed in: oem-priority/xenial Importance: Undecided => High -- 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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
@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 gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1797322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
@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 is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. -- 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/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1797322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797322] Re: gsd-rfkill-manager fails to receive 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 set the encoding of GIOChannel as NULL (binary data). + + [Test Case] + + 1) Enable the -proposed repository, and install new "gnome-settings- + daemon-schemas" and "gnome-settings-daemon" + + 2) Reboot system + + 3) Run suspend/resume test more than 127 times and then check if BT + settings still works well. + + [Regression Potential] + + Low. The default encoding for GIOChannel is wrong. Just set correct + encoding to receive rfkill event. + + --- + 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 s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 ** 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. + + Settings will always shows Bluetooth is off after resume. The solution is to set the encoding of GIOChannel as NULL (binary data). [Test Case] 1) Enable the -proposed repository, and install new "gnome-settings- daemon-schemas" and "gnome-settings-daemon" 2) Reboot system 3) Run suspend/resume test more than 127 times and then check if BT settings still works well. [Regression Potential] Low. The default encoding for GIOChannel is wrong. Just set correct encoding to receive rfkill event. --- 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 s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 -- 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/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1797322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797322] [NEW] gsd-rfkill-manager fails to receive rfkill event
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 s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic ** Patch added: "0001-rfkill-set-encoding-as-NULL.patch" https://bugs.launchpad.net/bugs/1797322/+attachment/5199851/+files/0001-rfkill-set-encoding-as-NULL.patch -- 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/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1797322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
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. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1797322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1638495] [NEW] Blank screen after wakeup from suspend
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) 3) What you expected to happen screen is on after wakeup from suspend 4) What happened instead screen is blank although system wakes up 5) Failure rate: 1/5 6) How to reproduce this issue: a. [System Menu] => [Suspend] b. press the key to wake up system c. screen is blank although system wakes up ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1638495 Title: Blank screen after wakeup from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1638495/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1638495] Re: Blank screen after wakeup from suspend
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 screensaver ActiveChanged signal: 1 (old: 0) setting up blank callback for 15s setting up sleep callback 300s setting up sleep warning callback 240s Doing a state transition: blank TESTSUITE: Blanked screen keyboard toggle on Received screensaver ActiveChanged signal: 1 (old: 1) Received screensaver ActiveChanged signal: 0 (old: 1) setting up sleep callback 300s setting up sleep warning callback 240s Received screensaver ActiveChanged signal: 0 (old: 0) ==> screen is blank although system wakes up ==> have to press the key again to turn on the screen power-plugin-DEBUG: idletime reset power-plugin-DEBUG: Doing a state transition: normal power-plugin-DEBUG: TESTSUITE: Unblanked screen power-plugin-DEBUG: keyboard toggle off -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1638495 Title: Blank screen after wakeup from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1638495/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
