||<>|| = Testing has now completed, thank you for submitting your results! = = Mir Multimonitor Testing = Multimonitor testing will be conducted via a Call for Testing from 8/26/13 - 8/28/13 for Ubuntu 13.10. During this timeframe the feature will be provided via the Ubuntu 13.10 system-compositor-testing PPA and will be integrated into trunk/archive shortly after testing ends. Please be sure to read the setup & notes to be aware of known issues and expectations. The listed test cases can also be used for general regression testing for multimonitor functionality. We would like to know your success and failures with this feature. We are tracking results in the [[ http://packages.qa.ubuntu.com/qatracker/milestones/298/builds/51476/testcases/1572/results | QA Tracker ]] but also in the [[ /results | MultiMonitor test results ]] wiki. Feel free to add your findings to the place that is more convenient to you. /!\ '''Please be aware that there is a security sensitive bug in this Mir release (https://bugs.launchpad.net/xmir/+bug/1192843)'''. == Setup == Install the PPA that enables multi-monitor. This can be done by the following. $> sudo add-apt-repository ppa:mir-team/system-compositor-testing Then update your package list $> sudo apt-get update We have to make sure updates in main don’t overwrite packages from the Mir PPA. Please edit /etc/apt/preferences.d/50-pin-mir.pref with following content: `Package: *`<
> `Pin: origin "private-ppa.launchpad.net"`<
> `Pin-Priority: 1001`<
> `Package: *`<
> `Pin: release o=LP-PPA-mir-team-system-compositor-testing`<
> `Pin-Priority: 1002`<
> Last but not least, install all the relevant packages $> sudo apt-get dist-upgrade And either reboot or restart lightdm (via sudo service lightdm restart) Please ensure you are running Xmir by running $> top wait a moment watching the process list, if you see unity-system-compositor listed...you are running Xmir. In the event you are not running Xmir, you may need to install unity-system-compositor $> sudo apt-get install unity-system-compositor Reboot or restart lightdm (via sudo service lightdm restart). Re-verfiy you are running Xmir. In the event this PPA causes major problems for you or you simply wish to return to the standard archive. Purge the packages with the following steps $> sudo apt-get install ppa-purge $> sudo ppa-purge ppa:mir-team/system-compositor-testing Then unpin the PPA $> sudo rm /etc/apt/preferences.d/50-pin-mir.pref $> sudo apt-get update $> sudo apt-get dist-upgrade And either reboot or restart lightdm (via sudo service lightdm restart) == General Multimonitor Testing Notes == === Bugs and expectations === First you can find a list of all the bugs we've identified so far relevant to multimonitor here https://bugs.launchpad.net/xmir/+bugs?field.tag=multimonitor tagged with "multimonitor". High level summary of what to expect with Xmir multimonitor, we have bugs for these issues so no need to duplicate. * Supported HW * Intel working * Radeon not working (is working with Xmir) * Nouveau is not working (is working with Xmir) * Hotplug works for VGA, HDMI, DisplayPort * Mirror mode works * Extended desktop works * Resoltion changes not working * Rotating screens not working * Changing relative positions of built-in vs 2nd display is working * In multimonitor mode, one monitor can have frame lag (sometimes, but frequent), user feels typing delay * Sometimes turning of 2nd display through settings can hang X * DisplayPort will show on 2nd display activity even though turned off * XMir receives input from other VTs (https://bugs.launchpad.net/xmir/+bug/1192843). This has security implications === Double Check Setup === Second, if you experience issue it would be good to ensure the packages loaded match those listed in https://launchpad.net/~mir-team/+archive/system-compositor-testing/+packages you may do this by inspecting your packages installed indicated by $> apt-cache policy of which the most important are xserver-org-video-intel (or ati, nouveau), xserver-xorg-xmir & unity-system-compositor === Be Patient === Third, in some cases be patient both to ensure you are not witnessing a bug or to help elicit a bug by providing enough time between connect & disconnect of cables. X takes some moments to accommodate the display configuration change. Also it may be worthy to remind you that this is pre-beta software which has not been optimized. The goal is to discover functional issues. === Checking on Mir vs X Issues === Fourth, in the event you experience an issue such as a blackscreen or ui lockup, another good debug step is to run a mir_demo_client_xxx. Simply VT switch (e.g. ctl+alt+F1) login and type $> sudo chmod 777 /tmp/mir_socket $> sudo mir_demo_client_egltriangle switch back to mir server on VT (ctl+alt+F7), if mir is still operating you will see spinning triangle, this means X has had an issue. This is good to note if you author a bug. === What to Collect === Fifth, based on our preliminary testing, it is most useful to capture the /var/log/Xorg.0.log or Xorg.0.log.old in the instance of a catastrophic bug. Since you may be rebooting, its good to check the timestamps to be certain you are sharing the right log. Also, photos and videos of your experiences are welcome to be attached to any bug reports. And of course collect your graphics card information $> lspci | grep "VGA" and simply report that line to the bug. If you experience a crash, you may also check the /var/crash/ folder for new *.crash files. Check their dates. If relevant you may attach those to the bugs as well. === Reporting your results === Remember to report your results good or bad on the provided wiki results page or by using the packages tracker. We are tracking results in the [[ http://packages.qa.ubuntu.com/qatracker/milestones/298/builds/51476/testcases/1572/results | QA Tracker ]] but also in the [[ /results | MultiMonitor test results ]] wiki. Feel free to add your findings to the place that is more convenient to you. === If You Get Stuck === Lastly, in the event you experience any issue or problem, just ping on IRC freenode #ubuntu-mir == Tests == <> == Scenario 1 : clean boot at “built-in display”, post boot connect/disconnect of 2nd display == === Preparations === * Ensure preconditions * System Settings... -> Displays is in its default configuration * 2nd monitor is not connected on boot === Test 1.1 (Mandatory) === * boot to single screen * open System Settings... -> Displays * open some window (e.g. terminal) * connect switched on monitor * verify display is an extension of desktop in the expected orientation, e.g. drag terminal to the other screen === Test 1.2 (Mandatory) === * assumes expected outcome of Test 1.1 post condition * Disconnect the monitor * verify the display adjusts to return active windows to “built-in display” === Test 1.3 (Mandatory) === * assumes expected Test 1.2 post condition * Reconnect the monitor * verify that the windows return to their original layout === Test 1.4 (Mandatory) === * assumes Test 1.3 postcondition * On System Settings... -> Displays select “Mirror displays” on * verify the screens adjusted to mirrored mode === Test 1.5 (Mandatory) === * assumes expected outcome of Test 1.4 postcondition * Disconnect the monitor * Reconnect the monitor * verify that the screens return to mirror mode layout == Scenario 2 : clean boot 2nd display already connected == === Preparations === * Ensure preconditions * System Settings... -> Displays is in its default configuration, e.g. “Mirror displays” is off * 2nd monitor is already connected and on prior to boot === Test 2.1 (Mandatory) === * boot to multimonitor already connected * open window to drag * verify that desktop comes up in extended mode === Test 2.2 (Mandatory) === * assumes expected outcome of Test 2.1 post condition * open System Settings... -> Displays select “Mirror displays” on * verify system reconfigures to mirrored screens * reboot * verify that system reboots into mirrored screens === Test 2.3 (Mandatory) === * assumes expected Test 2.2 post condition * open System Settings... -> Displays select “Mirror displays” off * verify that the system reconfigures to extended desktop * reboot * verify that the system reboots into extended desktop == Scenario 3 : turning off “built-in display” == === Preparations === * Ensure preconditions * System Settings... -> Displays is in its default configuration * 2nd monitor is already connected and on prior to boot === Test 3.1 (Mandatory) === * boot to multimonitor already connected * open System Settings... -> Displays toggle on/off button for “built-in display” to OFF * verify the second display remains active as a single screen/desktop === Test 3.2 (Mandatory) === * assumes expected outcome of Test 3.1 post condition * Open some windows (e.g. terminal) * disconnect display * verify the desktop returns to the “built-in display” === Test 3.3 (Mandatory) === * assumes expected outcome of Test 3.2 post condition * reconnect the display * verify that the desktop now appears on the second display and the “built-in display” is dark === Test 3.4 (Mandatory) === * assumes expected Test 3.3 postcondition * reboot with the second display connected * after login, verify that the desktop appears on the second display & the “built-in display” remains dark === Test 3.5 (Mandatory) === * assumes expected Test 3.4 postcondition * open System Settings... -> Displays toggle on/off button for “built-in display” to ON * verify that the desktop appears extended on both the second display & the “built-in display” == Scenario 4 : resolution change for “built-in display” & second display == == THIS IS CURRENTLY NOT WORKING == === Preparations === * Ensure preconditions * System Settings... -> Displays is in its default configuration === Test 4.1 === * boot to multimonitor (or if booted to single screen, connect 2nd monitor) * open System Settings... -> Displays, note the current resolution (referred to as res1) * change resolution down for “built in display”, note it, refer to as res2 * open some windows (e.g. terminal & file browser), have windows on each screen open * disconnect switched on monitor * verify “built in monitor” returned to original resolution, res1 === Test 4.2 === * assumes expected outcome of Test 4.1 post condition * Reconnect the monitor * verify the “built-in display” adjusts resolution back to res2 === Test 4.3 === * assumes expected Test 4.2 post condition * Disconnect monitor, change resolution of “built in monitor” down (preferably to a 3rd resolution setting not yet used), refer to as res3 * Reconnect the monitor * verify that the “built in monitor” returned to resolution setting selected in res 2 * Disconnect the monitor * verify that the “built in monitor” returned to res3 === Test 4.4 === * Assumes expected outcome of Test 4.3 postcondition * Reconnect monitor * through System Settings... -> Displays, select the second monitor & change resolution down, note it, refer to as res4 * disconnect monitor, let it settle * reconnect monitor * verify the screens adjusted to res 2 for “built-in” & res 4 for second monitor == Scenario 5 : rotation changes for display orientations == == THIS IS CURRENTLY NOT WORKING == === Preparations === * Ensure preconditions * System Settings... -> Displays is in its default configuration === Test 5.1 === * boot to multimonitor (or if booted to single screen, connect 2nd monitor) * the system should be in extended desktop mode * open System Settings... -> Displays, change the “Rotation” for the “built-in display” to be clockwise * verify “built in monitor” turned 90 degrees clockwise === Test 5.2 === * assumes expected outcome of Test 5.1 post condition * open System Settings... -> Displays, change the “Rotation” for the “built-in display” to be normal * verify the “built-in display” adjusts resolution back to normal === Test 5.3 === * assumes expected Test 5.2 post condition * open System Settings... -> Displays, change the “Rotation” for the “built-in display” to be 180 degrees * verify that the “built in monitor” rotated 180 degrees === Test 5.4 === * assumes expected outcome of Test 5.3 postcondition * return the orientation of the primary screen to normal, via System Settings... -> Displays, change the “Rotation” for the “built-in display” to be normal * set mirror mode, via System Settings... -> Displays select tick box on “Mirror displays” * then rotate, System Settings... -> Displays, change the “Rotation” for the “built-in display” to be 180 degrees * verify the both “built-in display” and 2nd display rotate 180 === Test 5.5 === * assumes expected Test 5.4 postcondition * return rotation to normal, open System Settings... -> Displays, change the “Rotation” for mirrored displays to normal * un-mirror, System Settings... -> Displays, unselect tick box for “Mirror displays” * select the 2nd monitor in the System Settings... -> Displays and change the Rotation clockwise * verify that the “built in monitor” did not rotate, and the second display rotates 90 degrees == Scenario 6 : relative display position == === Preparations === * Ensure preconditions * System Settings... -> Displays is in its default configuration === Test 6.1 === * boot to multimonitor (or if booted to single screen, connect 2nd monitor) * open System Settings... -> Displays to see the reflected virtual relationship of the “built-in display” to the second display * verify with the mouse by exiting the relative side of “built-in display” the mouse appears/enters the second display as reflected in the Displays dialog box === Test 6.2 === * assumes expected Test 6.1 post condition * in System Settings... -> Displays, select & grab the secondary display to move its relative position to the “built-in” display (effectively swap their position left-right of each other) * verify with the mouse by exiting the relative side of “built-in display” the mouse appears/enters the second display as reflected in the Displays dialog box