[Touch-packages] [Bug 1506846] Re: [multimonitor] nested server surface positioning incorrect
** Branch unlinked: lp:mir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1506846 Title: [multimonitor] nested server surface positioning incorrect Status in Mir: Fix Released Status in Unity System Compositor: Confirmed Status in mir package in Ubuntu: Fix Released Bug description: Flo and Mir 0.17. For multimonitor, it appears USC often positions the 2 nested server surfaces on the same screen, as if noth surfaces are positioned at (0,0) in the virtual desktop space - and not side-by-side. This screenshot may not be the clearest: https://chinstrap.canonical.com/~gerboland/mm2.jpg but I got it through moving the egltriangle surface to the right, and it appeared on the left! Steps to repro: 1. SSH into device and do: sudo stop lightdm 2. You'll want your backllight back, mirbacklight didn't work for me, so I called this as root: echo 255 > /sys/devices/platform/msm_fb.591617/leds/lcd-backlight/brightness 3. Run sudo unity-system-compositor --debug-without-dm --disable-inactivity-policy true --enable-hardware-cursor=true --debug-active-session-name=Test sudo chmod 777 /tmp/mir_socket 4. Start nested server mir_demo_server --host /tmp/mir_socket --display-config sidebyside --launch-client /usr/bin/mir_demo_client_egltriangle You should see the spinny triangle. 5. Now plug in the slimport cable. The display will flicker while the external display is being incorporated. 6. Use 3 fingers, move the triangle surface to the right. Expected result: It should appear on the external display Actual result: It pops in on the left of the internal display. See screenshot above. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1506846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506846] Re: [multimonitor] nested server surface positioning incorrect
** Changed in: unity-system-compositor Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1506846 Title: [multimonitor] nested server surface positioning incorrect Status in Mir: Fix Released Status in Unity System Compositor: Confirmed Status in mir package in Ubuntu: Fix Released Bug description: Flo and Mir 0.17. For multimonitor, it appears USC often positions the 2 nested server surfaces on the same screen, as if noth surfaces are positioned at (0,0) in the virtual desktop space - and not side-by-side. This screenshot may not be the clearest: https://chinstrap.canonical.com/~gerboland/mm2.jpg but I got it through moving the egltriangle surface to the right, and it appeared on the left! Steps to repro: 1. SSH into device and do: sudo stop lightdm 2. You'll want your backllight back, mirbacklight didn't work for me, so I called this as root: echo 255 > /sys/devices/platform/msm_fb.591617/leds/lcd-backlight/brightness 3. Run sudo unity-system-compositor --debug-without-dm --disable-inactivity-policy true --enable-hardware-cursor=true --debug-active-session-name=Test sudo chmod 777 /tmp/mir_socket 4. Start nested server mir_demo_server --host /tmp/mir_socket --display-config sidebyside --launch-client /usr/bin/mir_demo_client_egltriangle You should see the spinny triangle. 5. Now plug in the slimport cable. The display will flicker while the external display is being incorporated. 6. Use 3 fingers, move the triangle surface to the right. Expected result: It should appear on the external display Actual result: It pops in on the left of the internal display. See screenshot above. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1506846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506846] Re: [multimonitor] nested server surface positioning incorrect
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1506846 Title: [multimonitor] nested server surface positioning incorrect Status in Mir: Fix Released Status in Unity System Compositor: New Status in mir package in Ubuntu: Fix Released Bug description: Flo and Mir 0.17. For multimonitor, it appears USC often positions the 2 nested server surfaces on the same screen, as if noth surfaces are positioned at (0,0) in the virtual desktop space - and not side-by-side. This screenshot may not be the clearest: https://chinstrap.canonical.com/~gerboland/mm2.jpg but I got it through moving the egltriangle surface to the right, and it appeared on the left! Steps to repro: 1. SSH into device and do: sudo stop lightdm 2. You'll want your backllight back, mirbacklight didn't work for me, so I called this as root: echo 255 > /sys/devices/platform/msm_fb.591617/leds/lcd-backlight/brightness 3. Run sudo unity-system-compositor --debug-without-dm --disable-inactivity-policy true --enable-hardware-cursor=true --debug-active-session-name=Test sudo chmod 777 /tmp/mir_socket 4. Start nested server mir_demo_server --host /tmp/mir_socket --display-config sidebyside --launch-client /usr/bin/mir_demo_client_egltriangle You should see the spinny triangle. 5. Now plug in the slimport cable. The display will flicker while the external display is being incorporated. 6. Use 3 fingers, move the triangle surface to the right. Expected result: It should appear on the external display Actual result: It pops in on the left of the internal display. See screenshot above. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1506846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506846] Re: [multimonitor] nested server surface positioning incorrect
This bug was fixed in the package mir - 0.18.0+16.04.20151216.1-0ubuntu1 --- mir (0.18.0+16.04.20151216.1-0ubuntu1) xenial; urgency=medium [ Kevin DuBois ] * New upstream release 0.18.0 (https://launchpad.net/mir/+milestone/0.18.0) - ABI summary: Only servers need rebuilding; . Mirclient ABI unchanged at 9 . Mirserver ABI bumped to 36 . Mircommon ABI unchanged at 5 . Mirplatform ABI unchanged at 11 . Mirprotobuf ABI unchanged at 3 . Mirplatformgraphics ABI bumped to 7 . Mirclientplatform ABI unchanged at 3 . Mirinputplatform ABI added. Current version is 4 - Enhancements: . Use libinput by default, and remove the android input stack . Add x11 input probing . Add alternative buffer swapping mechanism internally, available with --nbuffers 0 . Automatic searching and selection of input platforms . Better support for themed cursors . Add demo client that uses multiple buffer streams in one surface . Improve fingerpaint demo to use touch pressure . Allow for configuring cursor acceleration, scroll speed and left or right handed mice . Allow for setting a base display configuration via client api . Various nested server multimonitor fixes and stability improvements . Remove DepthId from the SurfaceStack - Bug fixes: . Unit test failures in Display.* on Android (LP: #1519276) . Build failure due to missing dependency of client rpc code on mir protobuf (LP: #1518372) . Test failure in NestedServer.display_configuration_reset_when_application_exits (LP: #1517990) . CI test failures in various NesterServer tests (LP: #1517781) . FTBFS with -DMIR_PLATFORM=android (LP: #1517532) . Nesting Mir servers with assorted display configs causes lockup (LP: #1516670) . [testsfail] RaiseSurfaces.motion_events_dont_prevent_raise (LP: #1515931) . CI test failures in GLMark2Test (LP: #1515660) . Shells that inject user input events need to agree with the system compositor on the clock to use (LP: #1515515) . mircookie-dev is missing nettle-dev dependency (LP: #1514391) . Segmentation fault on server shutdown with mesa-kms (LP: #1513901) . mircookie requires nettle but libmircookie-dev doesn't depend on it (LP: #1513792) . libmircookie1 package does not list libnettle as dependency (LP: #1513225) . display configuration not reset when application exits (LP: #1511798) . unplugging external monitor causes nested server to throttle client (LP: #1511723) . 1/2 screen on external monitor (LP: #1511538) . unity-system-compositor crash, no interaction on windowed mode (LP: #1511095) . [regression] arm64/powerpc cross compile doesn't build any more (LP: #1510778) . mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY (LP: #1510218) . [multimonitor] nested server surface positioning incorrect (LP: #1506846) . unity-system-compositor fails to build against lp:mir r3027 (LP: #1506537) . [regression] Resampled touch events are slightly less regular than they used to be (LP: #1506331) . [testsfail] Segmentation fault mir_demo_server --test-client /usr/bin/mir_demo_client_basic (LP: #1506137) . [regression] Can't move/resize windows any more using Alt+left/middle buttons (LP: #1505114) . CI failure on some 32-bit targets in ServerSignal.terminate_handler_is_called_for_SIGTERM and others (LP: #1504579) . multibufferstreams use surface size instead of stream size (LP: #1503317) . CI segfault in mir-mediumtests-runner-mako in client tests (LP: #1502896) . CI segfault in mir-mediumtests-runner-mako after AndroidHardwareSanity tests (LP: #1502782) . compositing never stops when external monitor is connected (LP: #1499039) . mir_demo_server crashes with ERROR: Dynamic exception type: std::out_of_range - std::exception::what: map::at when an Xmir rootless app is closed by its File menu. (LP: #1497128) . Nested servers don't apply their display configuration at startup (LP: #1492269) . mir fails to open the right mouse device in kvm/qemu (LP: #1489522) . nexus4 & nexus7 hotplug survival (LP: #1488863) . Android uses mir_display_output_invalid_id (0) as an output id value (LP: #1463873) . DemoRenderer: GL_BLEND is really always enabled even when not required (also causes RGBX discolouration in mir_proving_server) (LP: #1423462) . Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android (LP: #1406725) . [enhancement] Ubuntu needs a way to set mouse scrolling speed
[Touch-packages] [Bug 1506846] Re: [multimonitor] nested server surface positioning incorrect
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1506846 Title: [multimonitor] nested server surface positioning incorrect Status in Mir: Fix Committed Status in Unity System Compositor: New Status in mir package in Ubuntu: New Bug description: Flo and Mir 0.17. For multimonitor, it appears USC often positions the 2 nested server surfaces on the same screen, as if noth surfaces are positioned at (0,0) in the virtual desktop space - and not side-by-side. This screenshot may not be the clearest: https://chinstrap.canonical.com/~gerboland/mm2.jpg but I got it through moving the egltriangle surface to the right, and it appeared on the left! Steps to repro: 1. SSH into device and do: sudo stop lightdm 2. You'll want your backllight back, mirbacklight didn't work for me, so I called this as root: echo 255 > /sys/devices/platform/msm_fb.591617/leds/lcd-backlight/brightness 3. Run sudo unity-system-compositor --debug-without-dm --disable-inactivity-policy true --enable-hardware-cursor=true --debug-active-session-name=Test sudo chmod 777 /tmp/mir_socket 4. Start nested server mir_demo_server --host /tmp/mir_socket --display-config sidebyside --launch-client /usr/bin/mir_demo_client_egltriangle You should see the spinny triangle. 5. Now plug in the slimport cable. The display will flicker while the external display is being incorporated. 6. Use 3 fingers, move the triangle surface to the right. Expected result: It should appear on the external display Actual result: It pops in on the left of the internal display. See screenshot above. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1506846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
