[monitor/1_hdmi_PCI_ID_0x????] The test case will be failed after connect HDMI port when initial display mode is external
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Provider - Base |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
Test image: sutton-
Test machine: P50s (Sazan2p-3)
CPU: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:1916] (rev 07)
+
06:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:137a] (rev a2)
Steps:
1. Install image sutton-
2. Log in and make sure system working under NVidia [10de:137a]
3. Connect HDMI cable.
4. Try to switch display mode internal to next mode (e.g. external mode)
5. Unplug HDMI cable, then plug the HDMI cable again.
6. Try to switch display mode external to next mode (e.g. extend mode)
7. Unplug HDMI cable, then plug the HDMI cable again.
8. Try to switch display mode extend to next mode (e.g. mirror mode)
9. Unplug HDMI cable, then plug the HDMI cable again.
10. Try to switch display mode mirror to internal.
Actual result:
Screen blink during the switching.
Expect result:
The modes switch smoothly.
Notes:
Trigger -- step1 -> setp2 -> setp3. When the HDMI cable conncet, if the initial display mode is external, the issue reproduces 100%; the rest of modes could make the issue occurred, but the rate is random.
The issue will lead to test case monitor/
summary: |
- [Sazan2p-3] Screen blink when switch display modes after connect HDMI - device. -- NVIDIA Corporation Device [10de:137a] + [monitor/1_hdmi_PCI_ID_0x????] The test case will be failed after + connect HDMI port. |
summary: |
[monitor/1_hdmi_PCI_ID_0x????] The test case will be failed after - connect HDMI port. + connect HDMI port when initial display mode is external |
Changed in plainbox-provider-checkbox: | |
status: | New → Confirmed |
importance: | High → Wishlist |
information type: | Public → Private |
information type: | Private → Public |
In the steps you describe, do you do everything manually, or is it during the execution of a Checkbox job? If so, which job are you running?
From the description and the video, it looks like this is a hardware issue and not a Checkbox issue.