Activity log for bug #1471708

Date Who What changed Old value New value Message
2015-07-06 09:11:58 Tim Chen bug added bug
2015-07-06 09:14:39 Tim Chen bug task added oem-priority
2015-07-06 09:14:54 Tim Chen nominated for series oem-priority/trusty
2015-07-06 09:14:54 Tim Chen bug task added oem-priority/trusty
2015-07-06 09:15:27 Tim Chen bug added subscriber OEM Priority Team
2015-07-06 09:17:21 Tim Chen oem-priority: importance Undecided Critical
2015-07-06 09:17:23 Tim Chen oem-priority/trusty: importance Undecided Critical
2015-07-06 09:28:49 Launchpad Janitor branch linked lp:~timchen119/unity-settings-daemon/unity-settings-daemon.1471708.trusty
2015-07-08 08:39:29 Alberto Milone unity-settings-daemon (Ubuntu): status New Triaged
2015-07-08 08:39:32 Alberto Milone unity-settings-daemon (Ubuntu): importance Undecided High
2015-07-08 08:39:34 Alberto Milone unity-settings-daemon (Ubuntu): assignee Alberto Milone (albertomilone)
2015-07-08 15:31:47 Alberto Milone unity-settings-daemon (Ubuntu): status Triaged In Progress
2015-07-08 15:33:56 Alberto Milone 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); } OEM LP private bug: https://bugs.launchpad.net/bugs/1466441 Title: Sometimes system turns a black screen when resume from S3 via Lid Close [Impact] 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 [Test Case] 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) [Regression Potential] Low. Delaying touchscreen mapping by 3 seconds should not affect any other input device. 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);          }
2015-07-08 15:34:04 Alberto Milone summary For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
2015-07-08 15:34:21 Alberto Milone bug added subscriber Ubuntu Stable Release Updates Team
2015-07-09 15:27:54 Alberto Milone 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 [Impact] 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 [Test Case] 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) [Regression Potential] Low. Delaying touchscreen mapping by 3 seconds should not affect any other input device. 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);          } OEM LP private bug: https://bugs.launchpad.net/bugs/1466441 Title: Sometimes system turns a black screen when resume from S3 via Lid Close [Impact] 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 [Test Case] 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) [Regression Potential] Low. Killing touchscreen mapping after 3 seconds should not affect any other input device. 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);          }
2015-07-24 14:01:53 Chen-Han Hsiao (Stanley) bug added subscriber Chen-Han Hsiao (Stanley)
2015-07-29 15:07:02 Alberto Milone branch linked lp:~albertomilone/unity-settings-daemon/non-blocking-touch-mapping-wily
2015-07-29 15:07:24 Alberto Milone branch linked lp:~albertomilone/unity-settings-daemon/non-blocking-touch-mapping-trusty
2015-08-13 14:33:31 Ara Pulido oem-priority: status New Triaged
2015-08-13 14:33:34 Ara Pulido oem-priority/trusty: status New Triaged
2015-08-13 14:34:17 Ara Pulido nominated for series Ubuntu Trusty
2015-08-13 14:34:17 Ara Pulido bug task added unity-settings-daemon (Ubuntu Trusty)
2015-08-13 14:34:28 Ara Pulido unity-settings-daemon (Ubuntu Trusty): status New In Progress
2015-08-25 12:28:54 Launchpad Janitor branch linked lp:ubuntu/wily-proposed/unity-settings-daemon
2015-08-26 14:46:30 Chris J Arges unity-settings-daemon (Ubuntu Trusty): status In Progress Fix Committed
2015-08-26 14:46:33 Chris J Arges bug added subscriber SRU Verification
2015-08-26 14:46:41 Chris J Arges tags verification-needed
2015-08-26 15:07:35 Launchpad Janitor branch linked lp:ubuntu/trusty-proposed/unity-settings-daemon
2015-08-27 14:19:14 Launchpad Janitor unity-settings-daemon (Ubuntu): status In Progress Fix Released
2015-08-29 21:12:28 Mathew Hodson unity-settings-daemon (Ubuntu Trusty): importance Undecided High
2015-09-11 17:42:46 Marc Deslauriers tags verification-needed verification-done
2015-09-16 08:19:15 Launchpad Janitor unity-settings-daemon (Ubuntu Trusty): status Fix Committed Fix Released
2015-09-16 08:19:19 Timo Aaltonen removed subscriber Ubuntu Stable Release Updates Team
2015-09-16 10:43:13 Ara Pulido oem-priority: status Triaged Fix Released
2015-09-16 10:43:17 Ara Pulido oem-priority/trusty: status Triaged Fix Released