touch-packages team mailing list archive

[kevin gunn <kevin.gunn@xxxxxxxxxxxxx>]

ok, i misunderstood - i thot you were running in windowed mode on
purpose or something.

After some further discussion:
understanding is that AP is emulating mouse events
unfortunately for convergence, mouse events is precisely the trigger for windowed mode
so need to find a solution for AP that can work in the presence of converged code base.

** Changed in: unity8 (Ubuntu)
   Importance: Low => Medium

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

** Changed in: autopilot (Ubuntu)
   Importance: Undecided => High

** Changed in: unity8 (Ubuntu)
   Importance: Medium => High

** Changed in: autopilot (Ubuntu)
       Status: New => Confirmed

** Summary changed:

- Autopilot tests on Krillin run in windowed mode 
+ Autopilot uses mouse events, puts device in windowed mode

** Description changed:

- The autopilot tests on Krillin run in windowed mode. I don't think this
- should ever happen on that form factor.
+ AP tests emulating mouse to run, which puts the device into windowed mode.
+ mouse presence is used to toggle the windowed mode on mobile devices.
+ 
+ ----orig bug ----
+ The autopilot tests on Krillin run in windowed mode. I don't think this should ever happen on that form factor.
  
  See also a bunch of dubious errors below.
  
  Tests running...
  terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<mir::socket_disconnected_error> >'
  what(): Failed to send message to server: Broken pipe
  Failed to connect to server. Error was :Failed to connect to server socket: Connection refused
  
  (process:5172): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
  g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  /bin/bash: line 1: 5172 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run ubuntuuitoolkit

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

Title:
  Autopilot uses mouse events, puts device in windowed mode

Status in autopilot package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  AP tests emulating mouse to run, which puts the device into windowed mode.
  mouse presence is used to toggle the windowed mode on mobile devices.

  ----orig bug ----
  The autopilot tests on Krillin run in windowed mode. I don't think this should ever happen on that form factor.

  See also a bunch of dubious errors below.

  Tests running...
  terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<mir::socket_disconnected_error> >'
  what(): Failed to send message to server: Broken pipe
  Failed to connect to server. Error was :Failed to connect to server socket: Connection refused

  (process:5172): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
  g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  /bin/bash: line 1: 5172 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run ubuntuuitoolkit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1471598/+subscriptions