[Touch-packages] [Bug 1644189] Re: Shell doesn't know when base display config has changed

2017-08-11 Thread Alan Griffiths
** Changed in: miral
Milestone: 1.5 => None

-- 
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/1644189

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Won't Fix

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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 1644189] Re: Shell doesn't know when base display config has changed

2017-07-21 Thread Alan Griffiths
** Changed in: miral
Milestone: None => 1.5

** Changed in: qtmir (Ubuntu)
 Assignee: Alan Griffiths (alan-griffiths) => (unassigned)

** Changed in: qtmir (Ubuntu)
   Status: In Progress => Won't Fix

-- 
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/1644189

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Won't Fix

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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 1644189] Re: Shell doesn't know when base display config has changed

2017-06-05 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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/1644189

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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 1644189] Re: Shell doesn't know when base display config has changed

2017-06-05 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

-- 
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/1644189

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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 1644189] Re: Shell doesn't know when base display config has changed

2017-03-13 Thread Michał Sawicz
** Project changed: qtmir => qtmir (Ubuntu)

-- 
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/1644189

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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 1644189] Re: Shell doesn't know when base display config has changed

2017-02-01 Thread Daniel van Vugt
** 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/1644189

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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 1644189] Re: Shell doesn't know when base display config has changed

2017-02-01 Thread Launchpad Bug Tracker
This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1644189] Re: Shell doesn't know when base display config has changed

2017-01-25 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2369

-- 
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/1644189

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Committed
Status in MirAL:
  In Progress
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  New

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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 1644189] Re: Shell doesn't know when base display config has changed

2017-01-24 Thread Daniel van Vugt
** 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/1644189

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Committed
Status in MirAL:
  In Progress
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  New

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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