[Touch-packages] [Bug 1458680] Re: platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)

2015-05-26 Thread Robert Carr
https://code.launchpad.net/~mir-team/platform-api/delete-
deprecations/+merge/254170 needed to land

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1458680

Title:
  platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)

Status in platform-api package in Ubuntu:
  New

Bug description:
  sbuild -A --dist=wily --arch=i386 -c wily-proposed-i386-sbuild
  platform-api_2.9.0+15.04.20150326-0ubuntu1.dsc

  [ 26%] Building CXX object 
src/ubuntu/application/common/mircommon/CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o
  cd 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/src/ubuntu/application/common/mircommon
  /usr/bin/i686-linux-gnu-g++-4.9-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2  -fvisibility=hidden -fPIC 
--std=c++11 -I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/include 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/android/include 
-I/usr/include/mirclient -I/usr/include/mircommon 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/include 
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/../../bridge
 -I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common  
  -o CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o -c 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp
  
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:
 In function 'bool ubuntu::application::ui::mir::event_to_ubuntu_event(const 
MirEvent*, WindowEvent)':
  
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:28:22:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
   switch (mir_event-type)
^
  In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
  /usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward 
declaration of 'const MirEvent {aka const union MirEvent}'
   typedef union MirEvent MirEvent;
 ^
  
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:32:44:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
   ubuntu_ev.key.device_id = mir_event-key.device_id;
  ^
  In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
  /usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward 
declaration of 'const MirEvent {aka const union MirEvent}'
   typedef union MirEvent MirEvent;
 ^
  
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:33:44:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
   ubuntu_ev.key.source_id = mir_event-key.source_id;
  ^
  In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
  /usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward 
declaration of 'const MirEvent {aka const union MirEvent}'
   typedef union MirEvent MirEvent;
 ^
  
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:34:41:
 error: invalid use of incomplete type 'const MirEvent {aka const union 
MirEvent}'
   ubuntu_ev.key.action = mir_event-key.action;
   ^
  In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
   from 
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
  

[Touch-packages] [Bug 1353855] Re: Explicit g++ 4.9 dependency breaks cross-building

2015-05-21 Thread Robert Carr
** Changed in: mir
   Status: Confirmed = Fix Released

** Changed in: mir (Ubuntu)
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1353855

Title:
  Explicit g++ 4.9 dependency breaks cross-building

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity-api package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  With the new explicit g++ 4.9 dependency apt falls over when trying to
  install cross-dependencies for e.g. Mir:

  The following packages have unmet dependencies:
   g++-4.9:armhf : Depends: gcc-4.9:armhf (= 4.9.1-4ubuntu3) but it is not 
going to be installed
  E: Build-dependencies for sbuild-build-depends-mir-dummy could not be 
satisfied.

  This means cross-building doesn't work for any packages that have that
  dependency added. We were told it's going to be fine due to 4.9
  becoming default, but it is now, and the situation remains.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1353855/+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 1425307] Re: [regression] Exception when running phablet-screenshot [std::exception::what: Attempt to set swap interval on screencast is invalid]

2015-05-21 Thread Robert Carr
It's just a log now right?

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

Title:
  [regression] Exception when running phablet-screenshot
  [std::exception::what: Attempt to set swap interval on screencast is
  invalid]

Status in Mir:
  Confirmed
Status in Mir 0.12 series:
  Confirmed
Status in Mir 0.13 series:
  Confirmed
Status in Mir 0.14 series:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in phablet-tools package in Ubuntu:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 22:35:35
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png
  I: Dumping fb0 ...
  [1424817826.846470] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
  [1424817826.847569] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so
  [1424817826.848393] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so
  [1424817826.849583] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
  [1424817826.944654] ERROR mircommon: Caught exception at Mir/EGL driver 
boundary (in setSwapInterval): 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): 
Throw in function virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error
  std::exception::what: Attempt to set swap interval on screencast is invalid

  3004 KB/s (3932160 bytes in 1.278s)
  I: Done

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1425307/+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 1419048] Re: Mir emits a mir_motion_action_hover_exit event before of a mir_motion_action_pointer_down

2015-04-22 Thread Robert Carr
** Branch linked: lp:~mir-team/mir/new-input-dispatcher

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

Title:
  Mir emits a mir_motion_action_hover_exit event before of a
  mir_motion_action_pointer_down

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  This breaks toolkits such as gtk and clutter as this causes the input
  widget to be reset and thus not to get the pointer-down event.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1419048/+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 1425307] Re: [regression] Exception when running phablet-screenshot (mako/vivid 110) [std::exception::what: Attempt to set swap interval on screencast is invalid]

2015-03-11 Thread Robert Carr
Should be fixed in r2307

revno: 2307 [merge]
author: Robert Carr robert.c...@canonical.com
committer: Tarmac
branch nick: development-branch
timestamp: Tue 2015-02-10 01:21:53 +
message:
  Catch exceptions at android driver boundary.
  
  Approved by PS Jenkins bot, Kevin DuBois.


** Changed in: mir
   Status: Triaged = Fix Committed

** Changed in: mir (Ubuntu)
   Status: Triaged = 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/1425307

Title:
  [regression] Exception when running phablet-screenshot (mako/vivid
  110) [std::exception::what: Attempt to set swap interval on screencast
  is invalid]

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 22:35:35
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png
  I: Dumping fb0 ...
  [1424817826.846470] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
  [1424817826.847569] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so
  [1424817826.848393] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so
  [1424817826.849583] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
  [1424817826.944654] ERROR mircommon: Caught exception at Mir/EGL driver 
boundary (in setSwapInterval): 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): 
Throw in function virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error
  std::exception::what: Attempt to set swap interval on screencast is invalid

  3004 KB/s (3932160 bytes in 1.278s)
  I: Done

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1425307/+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 1413748] Re: GLibMainLoopTest failure seen in CI

2015-02-05 Thread Robert Carr
** 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/1413748

Title:
  GLibMainLoopTest failure seen in CI

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  These three test runs:
  http://jenkins.qa.ubuntu.com/job/mir-mediumtests-vivid-touch/980/console
  http://jenkins.qa.ubuntu.com/job/mir-mediumtests-vivid-touch/978/console
  http://jenkins.qa.ubuntu.com/job/mir-mediumtests-vivid-touch/977/console

  have failed in GLibMainLoopAlarmTest and GLibMainLoopTest

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1413748/+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 1416317] Re: Clang builds fail in CI

2015-02-05 Thread Robert Carr
** 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/1416317

Title:
  Clang builds fail in CI

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  See https://jenkins.qa.ubuntu.com/job/mir-clang-vivid-
  amd64-build/1128/console and later.

  /mir/src/server/shell/default_shell.h:60:45: error: 'open_session' overrides 
a member function but is not marked 'override' 
[-Werror,-Winconsistent-missing-override]
  virtual std::shared_ptrscene::Session open_session(

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1416317/+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 1418081] Re: Compositing is triggered continously and needlessly when there are occluded surfaces with available buffers

2015-02-05 Thread Robert Carr
** 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/1418081

Title:
  Compositing is triggered continously and needlessly when there are
  occluded surfaces with available buffers

Status in Mir:
  In Progress
Status in Mir 0.11 series:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  Because of recent changes in the way the MultiThreadedCompositor is
  triggered (or rather retriggered) [1], when the
  DisplayBufferCompositor doesn't render (e.g. because it's occluded) a
  non-hidden surface that has available buffers, compositing is
  retriggered continuously at full rate, even when nothing else changes
  on screen.

  To test this, run the proving server:

  $ sudo bin/mir_proving_server --compositor-report log

  then start a client and drag the client offscreen. The compositor log
  should report that the compositor has a frame rate of max(client
  frame, FDP) (FDP=value related to our frame droping policy). However,
  you will see that it's instead rendering at 60FPS.

  As an extreme (but not unusual) example of how problematic this
  behavior can be, perform the following:

  1. Change an example client to render at ~1 FPS (e.g. add sleep(1) in it's 
main loop).
  2. Perform the previous experiment with that client

  When the client surface is visible, the compositor is triggered at a
  rate of 1FPS. The same should be true when the surface is dragged off
  screen, but instead we get a full compositing rate of 60FPS.

  [1] https://code.launchpad.net/~vanvugt/mir/fix-
  buffers_ready_for_compositor/+merge/247124

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1418081/+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 1274408] Re: Hardware cursor is always slightly ahead of the composited image

2015-02-05 Thread Robert Carr
** 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/1274408

Title:
  Hardware cursor is always slightly ahead of the composited image

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  The hardware cursor is always slightly ahead of the composited image.
  This is a common problem you'll see on the Ubuntu desktop too.

  However in Mir we have the possibility of fixing it all in a single
  project... The issue is that we update the hardware cursor position
  immediately in the same thread as the Android input logic that
  controls it. But it takes several context switches and a buffer flip
  or two before a corresponding change in the client surface can appear
  on screen.

  Even worse, there still seems to be some (less) visible lag between
  the hardware cursor position and the shell (which is in the same
  process). I can see some lag when dragging windows around with Alt
  +left-button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1274408/+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 1417650] Re: Pointer motion and crossing events are missing

2015-02-04 Thread Robert Carr
Added handling of hover/enter exit in MirSurfaceItem...

** Also affects: qtmir (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mir (Ubuntu)
   Status: Triaged = In Progress

** Changed in: qtmir (Ubuntu)
   Status: New = In Progress

** Branch linked: lp:~mir-team/qtmir/port-to-event-2.0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1417650

Title:
  Pointer motion and crossing events are missing

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Unity 8 doesn't seem to emit events for when the pointer enters or
  leaves a window, or when the pointer moves around inside a window. It
  does seem to emit the needed motion events when the mouse is dragged
  though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1417650/+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 1417650] Re: Pointer motion and crossing events are missing

2015-02-03 Thread Robert Carr
qtmir/port-to-event-2.0 implements the pointer motion events ill add the
crossing events tomorrow.

** Changed in: mir (Ubuntu)
   Status: New = Fix Committed

** Branch linked: lp:~mir-team/mir/introduce-pointer-event

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Robert Carr (robertcarr)

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) = Robert Carr (robertcarr)

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

Title:
  Pointer motion and crossing events are missing

Status in mir package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Unity 8 doesn't seem to emit events for when the pointer enters or
  leaves a window, or when the pointer moves around inside a window. It
  does seem to emit the needed motion events when the mouse is dragged
  though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1417650/+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 1338612] Re: intermittent hang in TestClientInput

2014-09-23 Thread Robert Carr
** Changed in: mir
   Status: Fix Committed = Fix Released

** Changed in: mir (Ubuntu)
   Status: Triaged = 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/1338612

Title:
  intermittent hang in TestClientInput

Status in Mir:
  Fix Released
Status in “mir” package in Ubuntu:
  Fix Released

Bug description:
  Only see once and not reproduced since. I was testing issues with
  concurrent tests and so don't have complete information about this
  occurrence. I have a test instance hung  with the call stack:

  #0  0x7fc0ec75d66b in pthread_join (threadid=140466456983296, 
thread_return=0x0) at pthread_join.c:92
  #1  0x7fc0ebc729e7 in std::thread::join() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #2  0x006c5f24 in tear_down (this=0x14ace08) at 
/home/alan/display_server/mir1/tests/acceptance-tests/test_client_input.cpp:101
  #3  (anonymous namespace)::TestClientInput::TearDown (this=0x14ac7a0)
  at 
/home/alan/display_server/mir1/tests/acceptance-tests/test_client_input.cpp:145

  It looks like this is teardown from
  TestClientInput.multiple_clients_receive_motion_inside_windows as I
  see that start and not finish on the console.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1338612/+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 1194550] Re: [gallery] Gallery should not be fullscreen on thumbnail view

2014-09-23 Thread Robert Carr
Relevant platform API and QtUbuntu branches attached.

** Changed in: platform-api
   Status: Triaged = In Progress

** Changed in: platform-api
 Assignee: Ricardo Mendoza (ricmm) = Robert Carr (robertcarr)

** Changed in: qtubuntu
   Status: Triaged = In Progress

** Changed in: qtubuntu
 Assignee: Ricardo Mendoza (ricmm) = Robert Carr (robertcarr)

** Branch linked: lp:~mir-team/qtubuntu/support-state-changing

** Branch linked: lp:~mir-team/platform-api/support-state-changing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1194550

Title:
  [gallery] Gallery should not be fullscreen on thumbnail view

Status in Platform API:
  In Progress
Status in QT Ubuntu:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “gallery-app” package in Ubuntu:
  Triaged
Status in “platform-api” package in Ubuntu:
  New
Status in “qtubuntu” package in Ubuntu:
  New

Bug description:
  As indicated in the design screenshots (http://design.ubuntu.com/apps
  /global-patterns/content-views#full-screen-view), the gallery app
  should only enter fullscreen mode (hiding the menu bar) when
  displaying an image, not when on the thumbnail overview.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1194550/+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 1328839] Re: The top panel is not restored after toggling full screen off

2014-09-22 Thread Robert Carr
The start of the problem is in platform API, where there is no way to
requestleaving fullscreen!

** Also affects: platform-api (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtmir
   Status: Confirmed = In Progress

** Changed in: platform-api (Ubuntu)
   Status: New = In Progress

** Changed in: unity8 (Ubuntu)
   Status: New = In Progress

** Also affects: qtubuntu (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtubuntu (Ubuntu)
   Status: New = In Progress

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) = Robert Carr (robertcarr)

** Changed in: platform-api (Ubuntu)
 Assignee: (unassigned) = Robert Carr (robertcarr)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1328839

Title:
  The top panel is not restored after toggling full screen off

Status in Qt integration with the Mir display server:
  In Progress
Status in “platform-api” package in Ubuntu:
  In Progress
Status in “qtubuntu” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “webbrowser-app” package in Ubuntu:
  Fix Released

Bug description:
  I’m implementing fullscreen mode for the browser application, and I’m
  seeing two issues, which can be reliably reproduced with the following
  piece of QML:

  import QtQuick 2.0
  import QtQuick.Window 2.1
  import Ubuntu.Components 0.1
  Window {
id: window
Button {
  anchors.centerIn: parent
  text: toggle fullscreen
  onClicked: window.visibility = (window.visibility == Window.FullScreen ? 
Window.AutomaticVisibility : Window.FullScreen)
}
  }

  Issue #1: when toggling fullscreen on, the top panel is hidden as
  expected, and consequently the coordinates of the window change on
  screen, but the contents of the window are not redrawn, so in the
  example above tapping the button has no effect (one needs to tap
  slightly above it to activate it)

  Issue #2: when toggling fullscreen off, the top panel is not restored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1328839/+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 1328839] Re: The top panel is not restored after toggling full screen off

2014-09-22 Thread Robert Carr
With https://code.launchpad.net/~mir-team/platform-api/support-state-
changing/+merge/235545 and https://code.launchpad.net/~mir-team/qtubuntu
/support-state-changing/+merge/235546

the example QML snippet functions correctly.

** Branch linked: lp:~mir-team/platform-api/support-state-changing

** Branch linked: lp:~mir-team/qtubuntu/support-state-changing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1328839

Title:
  The top panel is not restored after toggling full screen off

Status in Qt integration with the Mir display server:
  In Progress
Status in “platform-api” package in Ubuntu:
  In Progress
Status in “qtubuntu” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “webbrowser-app” package in Ubuntu:
  Fix Released

Bug description:
  I’m implementing fullscreen mode for the browser application, and I’m
  seeing two issues, which can be reliably reproduced with the following
  piece of QML:

  import QtQuick 2.0
  import QtQuick.Window 2.1
  import Ubuntu.Components 0.1
  Window {
id: window
Button {
  anchors.centerIn: parent
  text: toggle fullscreen
  onClicked: window.visibility = (window.visibility == Window.FullScreen ? 
Window.AutomaticVisibility : Window.FullScreen)
}
  }

  Issue #1: when toggling fullscreen on, the top panel is hidden as
  expected, and consequently the coordinates of the window change on
  screen, but the contents of the window are not redrawn, so in the
  example above tapping the button has no effect (one needs to tap
  slightly above it to activate it)

  Issue #2: when toggling fullscreen off, the top panel is not restored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1328839/+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 1292472] Re: unity8 crashed with what(): Requesting handle for an unregistered channel

2014-09-04 Thread Robert Carr
** This bug is no longer a duplicate of bug 1216727
   Mir server crashed: Requesting handle for an unregistered channel

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

Title:
  unity8 crashed with what():  Requesting handle for an unregistered
  channel

Status in Mir:
  Triaged
Status in Mir 0.6 series:
  Triaged
Status in “mir” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Every once in a while on current image + proposed (Qt 5.2 is in
  there), unity8 crashes on exit with:

  terminate called after throwing an instance of  
'boost::exception_detail::clone_implboost::exception_detail::error_info_injectorstd::logic_error
 '
what():  Requesting handle for an unregistered channel

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140307-0ubuntu1 [modified: 
usr/share/upstart/sessions/unity8.conf]
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Fri Mar 14 12:07:08 2014
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1394191081
  InstallationDate: Installed on 2014-03-14 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140314)
  ProcCmdline: unity8
  ProcCwd: /home/phablet
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6
   ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  Title: unity8 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty 
video

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1292472/+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 1292472] Re: unity8 crashed with what(): Requesting handle for an unregistered channel

2014-09-04 Thread Robert Carr
I propose that this was fixed in r157 onJuly 2nd.

Let's look at how the exception could occur, follow along with grep at
home for fun:

Starting with just the mir tree:

1. The exception can only occur in the InputRegistrar::handle_for_channel 
(android_input_registrar.cpp).
2. handle_for_channel is only invoked from the InputTargetEnumerator and the 
InputTargeter.

Let's break things down to find the cause of the exception

0. We can see QtMir does not directly use handle_for_channel
1. The InputTargetEnumerator, this is only used by the InputDispatcher. Of 
course, in qtmir the InputDispatcher is replaced with the QtEventFeeder, so it 
can not be Mir's usage of the InputTargetEnumerator triggering the exception. 
We can see the QtMir tree does not directly use the InputTargetEnumerator 
either, so we can rule it out as the cause of the exception.
2. The InputTargeter is the remaining culprit and its only used by the shell 
focus setter.

If we dig in to QtMir though we see
1. The InputTargeter is not used directly
2. The shell focus setter is overriden with a noop

By this logic we have shown that handle_for_channel is never called in
QtMir (and why would it be? It's purely used to translate between
InputDispatcher android types and MirSurfaces to avoid leaking the
android input window interface in to the Mir surface interface...as the
InputDispatcher is eliminated this code should be as well). However
clearly this exception was observed at one point so we must provide an
explanation:

bzr blame focussetter.cpp draws our attention to revision 157 (I suggest
skimming bzr diff 156..157 as the committ message is a little
misleading). We can see prior to r157 QtMir was not overriding the shell
focus setter and making use of the default mir impl, thusly making use
of the InputTargeter. We can also see application_manager.cpp making
direct use of the_focus_controller()-set_focus_to( thus invoking the
input targeter. One feasible explanation for the race is that depending
on the ordering of observer registration the application manager may be
notified surface removal after the input registrar has processed them.

None-the-less I am satisfied that this code path is no longer active and
thus closing the bug as fix released.


** Also affects: qtmir
   Importance: Undecided
   Status: New

** Changed in: mir
   Status: Triaged = Invalid

** Changed in: qtmir
   Status: New = Fix Released

** Changed in: mir/0.6
   Status: Triaged = Invalid

** Changed in: mir (Ubuntu)
   Status: New = Invalid

** Changed in: unity8 (Ubuntu)
   Status: New = Fix Released

** Changed in: qtmir
   Importance: Undecided = High

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

Title:
  unity8 crashed with what():  Requesting handle for an unregistered
  channel

Status in Mir:
  Invalid
Status in Mir 0.6 series:
  Invalid
Status in Qt integration with the Mir display server:
  Fix Released
Status in “mir” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  Every once in a while on current image + proposed (Qt 5.2 is in
  there), unity8 crashes on exit with:

  terminate called after throwing an instance of  
'boost::exception_detail::clone_implboost::exception_detail::error_info_injectorstd::logic_error
 '
what():  Requesting handle for an unregistered channel

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140307-0ubuntu1 [modified: 
usr/share/upstart/sessions/unity8.conf]
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Fri Mar 14 12:07:08 2014
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1394191081
  InstallationDate: Installed on 2014-03-14 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140314)
  ProcCmdline: unity8
  ProcCwd: /home/phablet
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6
   ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  Title: unity8 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty 
video

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1292472/+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 1353855] Re: Explicit g++ 4.9 dependency breaks cross-building

2014-09-04 Thread Robert Carr
I'm so tired of broken cross compile work flows I am going to figure it
out.

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) = Robert Carr (robertcarr)

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

Title:
  Explicit g++ 4.9 dependency breaks cross-building

Status in “mir” package in Ubuntu:
  Confirmed
Status in “qtmir” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  With the new explicit g++ 4.9 dependency apt falls over when trying to
  install cross-dependencies for e.g. Mir:

  The following packages have unmet dependencies:
   g++-4.9:armhf : Depends: gcc-4.9:armhf (= 4.9.1-4ubuntu3) but it is not 
going to be installed
  E: Build-dependencies for sbuild-build-depends-mir-dummy could not be 
satisfied.

  This means cross-building doesn't work for any packages that have that
  dependency added. We were told it's going to be fine due to 4.9
  becoming default, but it is now, and the situation remains.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1353855/+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 1351097] Re: [emulator] bottom edge swipe broken

2014-08-08 Thread Robert Carr
Applying http://pastebin.ubuntu.com/7991531/ as a patch against the
android device tree fixes things for me. It looks like the emulator
never supported resizing EGLWindowSurfaces. The WindowSurfaceon the host
side will still be the wrong size...the effects of this are hard to
predict. With 5-10 minute sof playing around with the emulator image
things seem to work fine...probably because we only resize
bigger-smaller atm...things could get broken as we support more.

Now that I am familiar with the codebase and have a workflow for
iterating on the device tree I think I will be able to provide a proper
fix earyl next week, not sure if people want to take this one in the
mean time.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1351097

Title:
  [emulator] bottom edge swipe broken

Status in “android” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  root@ubuntu-phablet:~# system-image-cli -i
  current build number: 166
  device name: generic_x86
  channel: ubuntu-touch/utopic-proposed
  last update: 2014-07-31 17:40:46
  version version: 166
  version ubuntu: 20140731.1
  version device: 20140728.1

  Can't use the bottom edge swipe anymore.

  Just open the browser and try using the bottom edge part of the
  screen. Same happens with dialler and messaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1351097/+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 1351097] Re: [emulator] bottom edge swipe broken

2014-08-06 Thread Robert Carr
The problem is some of the client surface size state fails to update
when the surface is resized to 770 pixels tall from 800 pixels tall on
start up (due to panel). In particular see qtubuntu glcontext.cpp l121.
These eglQuerySurface calls will continue to return 800 pixels tall even
after the mir client library reports seeing a buffer 770 pixels tall.  A
look in to goldfish device source shows that yes, the implemtnation of
eglQuerySurface WIDTH/HEIGHT will never change.

One fix may be querying the native window for width/height at buffer
swap time...but this seems incorrect and I need to think more and
understand the GL translation passthrough mechanism thingy a little
better.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1351097

Title:
  [emulator] bottom edge swipe broken

Status in “android” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  root@ubuntu-phablet:~# system-image-cli -i
  current build number: 166
  device name: generic_x86
  channel: ubuntu-touch/utopic-proposed
  last update: 2014-07-31 17:40:46
  version version: 166
  version ubuntu: 20140731.1
  version device: 20140728.1

  Can't use the bottom edge swipe anymore.

  Just open the browser and try using the bottom edge part of the
  screen. Same happens with dialler and messaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1351097/+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 1351097] Re: [emulator] bottom edge swipe broken

2014-08-06 Thread Robert Carr
In addition to querying the native window there has to be some sort of
detection that width/height changed, and some sort of pass through
message to the host process to resize the host surface

Does the emulator really not support resizing EGL surfaces?!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1351097

Title:
  [emulator] bottom edge swipe broken

Status in “android” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  root@ubuntu-phablet:~# system-image-cli -i
  current build number: 166
  device name: generic_x86
  channel: ubuntu-touch/utopic-proposed
  last update: 2014-07-31 17:40:46
  version version: 166
  version ubuntu: 20140731.1
  version device: 20140728.1

  Can't use the bottom edge swipe anymore.

  Just open the browser and try using the bottom edge part of the
  screen. Same happens with dialler and messaging.

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