desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #127393
[Bug 1471708] [NEW] For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
Public bug reported:
OEM LP private bug: https://bugs.launchpad.net/bugs/1466441
Title: Sometimes system turns a black screen when resume from S3 via Lid
Close
Summary:
Sometimes system turns a black screen when resume from S3 via Lid Close
It only has cursor on screen but still can switch to tty1.
Failure rate ~ 1/5
Steps:
1. install Ubuntu 14.04.2 & 3.19+ kernel and boot to OS
2. Close the lid
3. Open the lid
4. check the display status
Expected results: System should resume to the log in screen when open
the lid
Actual results:
System sometimes fails to resume back to the log in screen but blackscreen instead.
(Failure rate~ 1/5)
Details:
unity-settings-deamon will call "xinput --map-to-output 11 eDP1" at background,
and it's being blocked so only cursor will show on screen.
1. Switch to tty1 when this happen
2. Login with user account on tty1.
3. Use "DISPLAY=:0 xrandr " on commandline you'll see it's being blocked.
Since xinput is being blocked for some unknown reason (in gdb it shows
polling on xcb_connect_to_fd() in XOpenDisplay() ),
a possible workaround is to set a timeout for xinput in u-s-d.
=== modified file 'plugins/xrandr/gsd-xrandr-manager.c'
--- plugins/xrandr/gsd-xrandr-manager.c 2014-06-05 11:56:15 +0000
+++ plugins/xrandr/gsd-xrandr-manager.c 2015-07-01 08:59:56 +0000
@@ -2199,7 +2199,7 @@
if (gnome_rr_output_info_is_active(output)) {
g_debug ("Mapping touchscreen %d onto output %s",
device_id, name);
- sprintf (command, "xinput --map-to-output %d %s",
+ sprintf (command, "timeout 3s xinput --map-to-output %d %s",
device_id, name);
status = system (command);
}
** Affects: oem-priority
Importance: Critical
Status: New
** Affects: oem-priority/trusty
Importance: Critical
Status: New
** Affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/trusty
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority/trusty
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1471708
Title:
For skylake system, u-s-d cause a black screen when resume from S3 via
Lid Close
Status in OEM Priority Project:
New
Status in OEM Priority Project trusty series:
New
Status in unity-settings-daemon package in Ubuntu:
New
Bug description:
OEM LP private bug: https://bugs.launchpad.net/bugs/1466441
Title: Sometimes system turns a black screen when resume from S3 via
Lid Close
Summary:
Sometimes system turns a black screen when resume from S3 via Lid Close
It only has cursor on screen but still can switch to tty1.
Failure rate ~ 1/5
Steps:
1. install Ubuntu 14.04.2 & 3.19+ kernel and boot to OS
2. Close the lid
3. Open the lid
4. check the display status
Expected results: System should resume to the log in screen when open
the lid
Actual results:
System sometimes fails to resume back to the log in screen but blackscreen instead.
(Failure rate~ 1/5)
Details:
unity-settings-deamon will call "xinput --map-to-output 11 eDP1" at background,
and it's being blocked so only cursor will show on screen.
1. Switch to tty1 when this happen
2. Login with user account on tty1.
3. Use "DISPLAY=:0 xrandr " on commandline you'll see it's being blocked.
Since xinput is being blocked for some unknown reason (in gdb it shows
polling on xcb_connect_to_fd() in XOpenDisplay() ),
a possible workaround is to set a timeout for xinput in u-s-d.
=== modified file 'plugins/xrandr/gsd-xrandr-manager.c'
--- plugins/xrandr/gsd-xrandr-manager.c 2014-06-05 11:56:15 +0000
+++ plugins/xrandr/gsd-xrandr-manager.c 2015-07-01 08:59:56 +0000
@@ -2199,7 +2199,7 @@
if (gnome_rr_output_info_is_active(output)) {
g_debug ("Mapping touchscreen %d onto output %s",
device_id, name);
- sprintf (command, "xinput --map-to-output %d %s",
+ sprintf (command, "timeout 3s xinput --map-to-output %d %s",
device_id, name);
status = system (command);
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1471708/+subscriptions
Follow ups
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Ara Pulido, 2015-09-16
-
[Bug 1471708] Update Released
From: Timo Aaltonen, 2015-09-16
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Launchpad Bug Tracker, 2015-09-16
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Marc Deslauriers, 2015-09-11
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Tammy Yang, 2015-08-31
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Mathew Hodson, 2015-08-29
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Launchpad Bug Tracker, 2015-08-27
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Launchpad Bug Tracker, 2015-08-26
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Chris J Arges, 2015-08-26
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Alberto Milone, 2015-08-26
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Launchpad Bug Tracker, 2015-08-25
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Alberto Milone, 2015-08-13
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Ara Pulido, 2015-08-13
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Alberto Milone, 2015-08-10
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Alberto Milone, 2015-07-29
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Alberto Milone, 2015-07-24
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Tim Chen, 2015-07-14
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Alberto Milone, 2015-07-10
-
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Alberto Milone, 2015-07-09
-
[Bug 1471708] Re: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Alberto Milone, 2015-07-08
-
[Bug 1471708] Re: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Alberto Milone, 2015-07-08
-
[Bug 1471708] Re: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Launchpad Bug Tracker, 2015-07-06
-
[Bug 1471708] [NEW] For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
From: Tim Chen, 2015-07-06
References