[Touch-packages] [Bug 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

Ooops!! that's based on the wrong branch

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  New

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

It looks very much as though protobuf3 reverts this change:

  $ bzr log -c 295 lp:protobuf

I've not yet proved that's the whole problem, but it would explain it.

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

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

Here's the fix to +branch/ubuntu/wily-proposed/protobuf/ that fixes the
problem with reloading modules that depend on protobuf.

** Attachment added: "Forward port fix from protobuf 2.6"
   
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+attachment/4734807/+files/fix-protobuf

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  New

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

Patch for the correct branch

** Attachment added: "fix-protobuf"
   
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+attachment/4734930/+files/fix-protobuf

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  New

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

There was a hack put into Mir around the end of June 2015 as linked by
Daniel
(https://code.launchpad.net/~vanvugt/mir/fix-1391976/+merge/262678). As
the comment suggests this was pending "a proper fix will come from
libprotobuf itself but this way we don't need to wait for that".

This "hack" was removed at the end of July 2015. I don't see a
corresponding change to protobuf. So I suspect I have been chasing the
wrong fix. I found some differences that look related and tried patching
them locally. I still have to figure out why patching things seems to
work locally - especially with the typo in the patch file. Clearly I'm
doing something wrong. :(

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

I'm very suspicious of my laptop running yakkety - even with "proposed"
purged it is now crashing every few minutes (which makes keeping track
of things a PITA).

The root cause is probably a failure in protobuf to re-initalise static
data when clients call google::protobuf::ShutdownProtobufLibrary(). This
leads to a failure when if the whole .so isn't unloaded before the next
"GOOGLE_PROTOBUF_VERIFY_VERSION;"

Which is why the change I picked up looks relevant.

The "hack" mentioned above did appear to workaround the problem for Mir
(i.e. the test passes). (But it will probably recur with other Qt
plugins that use protobuf.)

So I'm going to reinstall and start over.

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

But I don't yet see how 2.6.1 avoided this issue.

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

A simpler fix that removes the assumption that the shared library will
be unloaded between uses

** Attachment added: "fix-protobuf"
   
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+attachment/4736108/+files/fix-protobuf

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

Oops. The patch in #18 is for google/protobuf/stubs/common.cc:

415d414
<   shutdown_functions = new vector;
425a425,426
>   if (internal::shutdown_functions == NULL)
> shutdown_functions = new vector;
446,447d446
<   delete internal::shutdown_functions_mutex;
<   internal::shutdown_functions_mutex = NULL;

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

OK, I have rebuild laptop and have a less flaky system. This (updated)
patch is only a proof-of-concept as it clearly leaks resources on
program exit in this form.

OTOH it does make the Mir test pass, so I have found the right problem.

** Attachment added: "fix-protobuf"
   
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+attachment/4736088/+files/fix-protobuf

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

Narrowing the problem: it isn't any of the Mir code, or the generated
code, or explicit calls into libprotobuf-lite.

The following program loads and unloads libprotobuf-lite.so from 2.6.1
successfully. With 3.0.0 it fails to unload.

#include 
#include 

int main(int argc, char** argv)
{
char const* libname = argc <= 1 ? "libprotobuf-lite.so" : argv[1];

void* dl = NULL;

dl = dlopen(libname, RTLD_NOW);
if (!dl)
{
printf("dlopen() error: (%s)\n", dlerror());
return 1;
}

printf("library loaded\n");
dlclose(dl);

dl = dlopen(libname, RTLD_NOW|RTLD_NOLOAD);

if (dl)
{
printf("library didn't unload: (%s)\n", libname);
dlclose(dl);
return 1;
}

printf("library unloaded\n");

return 0;
}

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

Same patch as mentioned in #18 and #20 formatted better

** Attachment added: "my least bad solution"
   
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+attachment/4736828/+files/fix-protobuf

** Changed in: mir
Milestone: 0.25.0 => None

** Changed in: mir (Ubuntu)
Milestone: ubuntu-16.09 => 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/1619616

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

  ~

  The reason this matters:

  The principle downstream from Mir (Unity8) loads Mir as one of a
  number of plugins, several of which use protobuf. That means that
  we're prone to being loaded, unloaded and reloaded and don't have
  control of this.

  We've encountered problems in this scenario before that have been
  traced to protobuf so we have a specific test. But other Unity8
  plugins may encounter the same issue.

  As seen in comment #25 the problem here is entirely down to a change
  in the behavior of libmirprotobuf-lite - it no longer unloads on
  dlclose().

  This is only a problem because there is code (see patch in comment
  #20) that assumes that the library will not be used after a call to
  google::protobuf::ShutdownProtobufLibrary() unless it is reloaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

Hmm the library publishes a load of symbols that seem unnecessary at
best:

$ readelf -Ws /usr/local/lib/libprotobuf-lite.so | grep -v " UND " | grep -v 
6google8protobuf | wc -l
123

2.6.1 seems far more reasonable:

$ readelf -Ws /usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.9 | grep -v " UND " 
| grep -v 6google8protobuf | wc -l
10

I'm especially suspicious of the following leading to entanglement with
libstdc++:

$ readelf -Ws /usr/local/lib/libprotobuf-lite.so.10 | grep -v " UND " | grep -v 
6google8protobuf | grep _ZNS 
   402: 00023080   474 FUNCWEAK   DEFAULT   12 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJS5_EEEvDpOT_
   552: 0001b2c0   220 FUNCWEAK   DEFAULT   12 
_ZNSt6vectorIPFvvESaIS1_EE19_M_emplace_back_auxIJRKS1_EEEvDpOT_
   700: 00023260   117 FUNCWEAK   DEFAULT   12 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_
39: 00023310   194 FUNCLOCAL  DEFAULT   12 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag.isra.25
40: 00023310   194 FUNCLOCAL  DEFAULT   12 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag.isra.20
46: 0001c4a0   194 FUNCLOCAL  DEFAULT   12 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag.isra.29
47: 0001c4a0   194 FUNCLOCAL  DEFAULT   12 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag.isra.23
72: 00019740   194 FUNCLOCAL  DEFAULT   12 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag.isra.42
73: 00019740   194 FUNCLOCAL  DEFAULT   12 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag.isra.36
78: 0001b3a0   194 FUNCLOCAL  DEFAULT   12 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag.isra.30
87: 0001e820   194 FUNCLOCAL  DEFAULT   12 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag.isra.45
88: 0001e820   194 FUNCLOCAL  DEFAULT   12 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag.isra.39
   115: 0002ea80   174 FUNCLOCAL  DEFAULT   12 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag.isra.21.constprop.32
   466: 00023260   117 FUNCWEAK   DEFAULT   12 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_
   776: 0001b2c0   220 FUNCWEAK   DEFAULT   12 
_ZNSt6vectorIPFvvESaIS1_EE19_M_emplace_back_auxIJRKS1_EEEvDpOT_
   777: 00023080   474 FUNCWEAK   DEFAULT   12 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJS5_EEEvDpOT_

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

** Description changed:

  builds with 3.0.0-7, then has one failing test:
  
  test 19
Start 19: Protobuf-can-be-reloaded
  
  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec
  
  95% tests passed, 1 tests failed out of 19
  
  Total Test time (real) = 125.73 sec
  
  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8
+ 
+ ~
+ 
+ The reason this matters:
+ 
+ The principle downstream from Mir (Unity8) loads Mir as one of a number
+ of plugins, several of which use protobuf. That means that we're prone
+ to being loaded, unloaded and reloaded and don't have control of this.
+ 
+ We've encountered problems in this scenario before that have been traced
+ to protobuf so we have a specific test. But other Unity8 plugins may
+ encounter the same issue.
+ 
+ As seen in comment #25 the problem here is entirely down to a change in
+ the behavior of libmirprotobuf-lite - it no longer unloads on dlclose().
+ 
+ This is only a problem because there is code (see patch in comment #20)
+ that assumes that the library will not be used after a call to
+ google::protobuf::ShutdownProtobufLibrary() unless it is reloaded.

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

  ~

  The reason this matters:

  The principle downstream from Mir (Unity8) loads Mir as one of a
  number of plugins, several of which use protobuf. That means that
  we're prone to being loaded, unloaded and reloaded and don't have
  control of this.

  We've encountered problems in this scenario before that have been
  traced to protobuf so we have a specific test. But other Unity8
  plugins may encounter the same issue.

  As seen in comment #25 the problem here is entirely down to a change
  in the behavior of libmirprotobuf-lite - it no longer unloads on
  dlclose().

  This is only a problem because there is code (see patch in comment
  #20) that assumes that the library will not be used after a call to
  google::protobuf::ShutdownProtobufLibrary() unless it is reloaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: mir fails to build with protobuf3

[Alan Griffiths]

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

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

Title:
  mir fails to build with protobuf3

Status in mir package in Ubuntu:
  Confirmed

Bug description:
  mir fails to build with protobuf3. build logs at
  https://launchpad.net/ubuntu/+source/mir/0.24.0+16.10.20160815.3-0ubuntu2

  
  In file included from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0:
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:
 In function ‘void mir::frontend::detail::invoke(Self*, Server*, void 
(ServerX::*)(const ParameterMessage*, ResultMessage*, 
google::protobuf::Closure*), const mir::frontend::detail::Invocation&)’:
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13:
 error: ‘NewPermanentCallback’ is not a member of ‘google::protobuf’
   google::protobuf::NewPermanentCallback<
   ^~
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13:
 note: suggested alternative:
  In file included from /usr/include/google/protobuf/stubs/common.h:48:0,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.h:9,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/common/mir/protobuf/display_server.h:22,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/display_server.h:22,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:19:
  /usr/include/google/protobuf/stubs/callback.h:524:36: note:   
‘google::protobuf::internal::NewPermanentCallback’
   inline ResultCallback2<R, A1, A2>* NewPermanentCallback(
  ^~~~
  In file included from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0:
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:69:21:
 error: expected primary-expression before ‘,’ token
   Self,
   ^
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:70:43:
 error: expected primary-expression before ‘,’ token
   ::google::protobuf::uint32,
 ^
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:71:59:
 error: expected ‘(’ before ‘>’ token
   typename result_ptr_t::type>(
 ^

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+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 1619616] Re: mir fails to build with protobuf3

[Alan Griffiths]

sensible

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

Title:
  mir fails to build with protobuf3

Status in mir package in Ubuntu:
  Confirmed

Bug description:
  mir fails to build with protobuf3. build logs at
  https://launchpad.net/ubuntu/+source/mir/0.24.0+16.10.20160815.3-0ubuntu2

  
  In file included from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0:
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:
 In function ‘void mir::frontend::detail::invoke(Self*, Server*, void 
(ServerX::*)(const ParameterMessage*, ResultMessage*, 
google::protobuf::Closure*), const mir::frontend::detail::Invocation&)’:
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13:
 error: ‘NewPermanentCallback’ is not a member of ‘google::protobuf’
   google::protobuf::NewPermanentCallback<
   ^~
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:68:13:
 note: suggested alternative:
  In file included from /usr/include/google/protobuf/stubs/common.h:48:0,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.h:9,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/common/mir/protobuf/display_server.h:22,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/display_server.h:22,
   from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:19:
  /usr/include/google/protobuf/stubs/callback.h:524:36: note:   
‘google::protobuf::internal::NewPermanentCallback’
   inline ResultCallback2* NewPermanentCallback(
  ^~~~
  In file included from 
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/server/frontend/protobuf_message_processor.cpp:24:0:
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:69:21:
 error: expected primary-expression before ‘,’ token
   Self,
   ^
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:70:43:
 error: expected primary-expression before ‘,’ token
   ::google::protobuf::uint32,
 ^
  
/«BUILDDIR»/mir-0.24.0+16.10.20160815.3/src/include/server/mir/frontend/template_protobuf_message_processor.h:71:59:
 error: expected ‘(’ before ‘>’ token
   typename result_ptr_t::type>(
 ^

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

The reason 2.6.1 works is that libprotobuf-lite-so.9 is unloaded each
iteration. But with the move to 3.0.0 that no longer happens.

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

This shows the problem, but not the underlying cause:

$ gdb bin/mir_test_reload_protobufGNU gdb (Ubuntu 7.11.90.20160906-0ubuntu1) 
7.11.90.20160906-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from bin/mir_test_reload_protobuf...done.
(gdb) b /home/alan/display_server/mir/tests/loader-tests/test_reload.c:36
No source file named 
/home/alan/display_server/mir/tests/loader-tests/test_reload.c.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 
(/home/alan/display_server/mir/tests/loader-tests/test_reload.c:36) pending.
(gdb) r
Starting program: 
/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/mir_test_reload_protobuf
 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
MIR_CLIENT_PLATFORM_PATH=/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/../lib/client-modules/
MIR_SERVER_PLATFORM_PATH=/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/../lib/server-modules/
LD_LIBRARY_PATH=/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/../lib
exec=/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/mir_test_reload_protobuf.bin
process 2335 is executing new program: 
/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/mir_test_reload_protobuf.bin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, main (argc=1, argv=0x7fffde58) at 
/home/alan/display_server/mir/tests/loader-tests/test_reload.c:36
36  dl = dlopen(libname, RTLD_NOW);
(gdb) info share
>FromTo  Syms Read   Shared Object Library
0x77dd8aa0  0x77df6130  Yes /lib64/ld-linux-x86-64.so.2
0x77bd4d80  0x77bd598e  Yes 
/lib/x86_64-linux-gnu/libdl.so.2
0x779bba60  0x779c8e01  Yes 
/lib/x86_64-linux-gnu/libpthread.so.0
0x7760e9c0  0x7775f0c3  Yes 
/lib/x86_64-linux-gnu/libc.so.6
(gdb) n
37  if (dl)
(gdb) info share
>FromTo  Syms Read   Shared Object Library
0x77dd8aa0  0x77df6130  Yes /lib64/ld-linux-x86-64.so.2
0x77bd4d80  0x77bd598e  Yes 
/lib/x86_64-linux-gnu/libdl.so.2
0x779bba60  0x779c8e01  Yes 
/lib/x86_64-linux-gnu/libpthread.so.0
0x7760e9c0  0x7775f0c3  Yes 
/lib/x86_64-linux-gnu/libc.so.6
0x77360c60  0x773c3e86  Yes 
/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/../lib/libmirprotobuf.so.3
0x7710ddd0  0x7712a3c6  Yes 
/usr/local/lib/libprotobuf-lite.so.10
0x76df8900  0x76ea7c79  Yes (*) 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
0x76b58a90  0x76b688e5  Yes (*) 
/lib/x86_64-linux-gnu/libgcc_s.so.1
0x76852710  0x768c3bfa  Yes 
/lib/x86_64-linux-gnu/libm.so.6
(*): Shared library is missing debugging information.
(gdb) c
Continuing.
[0] dlopen `libmirprotobuf.so.3' = 0x557564c0

Breakpoint 1, main (argc=1, argv=0x7fffde58) at 
/home/alan/display_server/mir/tests/loader-tests/test_reload.c:36
36  dl = dlopen(libname, RTLD_NOW);
(gdb) info share
>FromTo  Syms Read   Shared Object Library
0x77dd8aa0  0x77df6130  Yes /lib64/ld-linux-x86-64.so.2
0x77bd4d80  0x77bd598e  Yes 
/lib/x86_64-linux-gnu/libdl.so.2
0x779bba60  0x779c8e01  Yes 
/lib/x86_64-linux-gnu/libpthread.so.0
0x7760e9c0  0x7775f0c3  Yes 
/lib/x86_64-linux-gnu/libc.so.6
0x7710ddd0  0x7712a3c6  Yes 
/usr/local/lib/libprotobuf-lite.so.10
0x76df8900  0x76ea7c79  Yes (*) 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
0x76b58a90  0x76b688e5  Yes (*) 
/lib/x86_64-linux-gnu/libgcc_s.so.1
0x76852710  0x768c3bfa  Yes 
/lib/x86_64-linux-gnu/libm.so.6
(*): Shared library is missing debugging information.

With protobuf-2.6.1 the libprotobuf-lite library is unloaded at this

[Touch-packages] [Bug 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

In any case, if protobuf choses to remain resident it is only polite to
work when the startup/shutdown cycle is repeated. (And that's what the
patch achieves.)

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

[Alan Griffiths]

** Changed in: miral
Milestone: None => 0.2

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

Title:
  Need to support pointer confinement in Mir and toolkits using Mir

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in MirAL:
  Fix Committed
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590099/+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 1625853] Re: Mouse cursor disappears (or just never changes) when entering the windows of Qt apps

[Alan Griffiths]

** Changed in: miral
Milestone: None => 0.2

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

Title:
  Mouse cursor disappears (or just never changes) when entering the
  windows of Qt apps

Status in Canonical System Image:
  In Progress
Status in Mir:
  Triaged
Status in MirAL:
  Fix Committed
Status in qtubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  To reproduce:
  1) Open qtcreator in mir
  2) Move mouse around window

  Expect:
  Able to see cursor

  Result:
  Cursor goes away as if disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625853/+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 1629275] Re: Clients and server all crash

[Alan Griffiths]

** This bug is no longer a duplicate of bug 1607812
   When stressed by a load of clients starting at once: Failed to get PRIME fd 
from gbm bo

** Description changed:

  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)
  
  Start a Mir-on-X11 session:
  
- $ mir_demo_server_minimal &
- $ mirrun gnome-terminal
+ $ mir_demo_server_minimal &
+ $ mirrun gnome-terminal
  
  In the terminal:
  
- $ mir_demo_client_all&
+ $ mir_demo_client_all&
  
  (A script that launches all the Mir demo clients - attached)
  
  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open
+ 
+ The "frequent" server crash is lp:1607812, this bug is for the client
+ crash

** Branch unlinked: lp:~alan-griffiths/mir/fix-server-crash

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

  The "frequent" server crash is lp:1607812, this bug is for the client
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1629275/+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 1629275] Re: Clients all crash (and sometimes server too)

[Alan Griffiths]

** Changed in: miral
   Status: Triaged => Invalid

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

Title:
  Clients all crash (and sometimes server  too)

Status in Mir:
  Incomplete
Status in MirAL:
  Invalid
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

  The "frequent" server crash is lp:1607812, this bug is for the client
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1629275/+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 1629275] Re: Clients all crash (and sometimes server too)

[Alan Griffiths]

** Summary changed:

- Clients and server all crash
+ Clients all crash (and sometimes server  too)

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

Title:
  Clients all crash (and sometimes server  too)

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

  The "frequent" server crash is lp:1607812, this bug is for the client
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1629275/+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 1629275] Re: Clients all crash (and sometimes server too)

[Alan Griffiths]

Console log from gnome-terminal (with MIR_CLIENT_RPC_REPORT=log)

[2016-10-04 15:41:58.721290]  rpc: Invocation request: id: 52 
method_name: submit_buffer
[2016-10-04 15:41:58.721397]  rpc: Invocation succeeded: id: 52 
method_name: submit_buffer
[2016-10-04 15:41:58.727375]  rpc: Invocation request: id: 53 
method_name: submit_buffer
[2016-10-04 15:41:58.727437]  rpc: Invocation succeeded: id: 53 
method_name: submit_buffer
[2016-10-04 15:41:58.737226]  rpc: Result received: id: 52
[2016-10-04 15:41:58.737269]  rpc: Complete response: id: 52
[2016-10-04 15:41:58.739094]  rpc: Result received: id: 53
[2016-10-04 15:41:58.739187]  rpc: Complete response: id: 53
*** Error in `/usr/lib/gnome-terminal/gnome-terminal-server': double free or 
corruption (out): 0x7f90bcb0c010 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7911b)[0x7f90d96d311b]
/lib/x86_64-linux-gnu/libc.so.6(+0x827aa)[0x7f90d96dc7aa]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f90d96e01dc]


** Tags added: gtk-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/1629275

Title:
  Clients all crash (and sometimes server  too)

Status in Mir:
  Incomplete
Status in MirAL:
  Invalid
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

  The "frequent" server crash is lp:1607812, this bug is for the client
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1629275/+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 1626804] Re: Qt apps can't run under Mir [Gtk-WARNING **: cannot open display: ]

[Alan Griffiths]

Something like mirrun?

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

Title:
  Qt apps can't run under Mir [Gtk-WARNING **: cannot open display: ]

Status in Canonical System Image:
  Invalid
Status in platform-api:
  Invalid
Status in platform-api package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  Invalid

Bug description:
  Qt apps can't run under Mir - fail with a Gtk error trying to open an
  X display (!?)

  $ qterminal --desktop_file_hint=unity8
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'

  (qterminal:9053): Gtk-WARNING **: cannot open display:

  
  $ qtcreator --desktop_file_hint=unity8
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'

  (qtcreator:9083): Gtk-WARNING **: cannot open display:

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626804/+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 1626804] Re: Qt apps can't run under Mir [Gtk-WARNING **: cannot open display: ]

[Alan Griffiths]

Really, I've been running qt apps under mir_demo_server, miral-shell and
egmde for ages, there isn't a problem. You need:

sudo apt-get install qtubuntu-desktop mir-utils

And then:

mirrun qterminal


** Changed in: canonical-devices-system-image
   Status: New => Invalid

** Changed in: platform-api
   Status: New => Invalid

** Changed in: platform-api (Ubuntu)
   Status: New => Invalid

** Changed in: qtubuntu (Ubuntu)
   Status: New => Invalid

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

Title:
  Qt apps can't run under Mir [Gtk-WARNING **: cannot open display: ]

Status in Canonical System Image:
  Invalid
Status in platform-api:
  Invalid
Status in platform-api package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  Invalid

Bug description:
  Qt apps can't run under Mir - fail with a Gtk error trying to open an
  X display (!?)

  $ qterminal --desktop_file_hint=unity8
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'

  (qterminal:9053): Gtk-WARNING **: cannot open display:

  
  $ qtcreator --desktop_file_hint=unity8
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'

  (qtcreator:9083): Gtk-WARNING **: cannot open display:

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626804/+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 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

[Alan Griffiths]

** Changed in: miral
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Changed in: miral
   Status: Triaged => In Progress

** Branch linked: lp:~dandrader/miral/confine_pointer

** Changed in: miral
   Importance: Wishlist => Medium

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

Title:
  Need to support pointer confinement in Mir and toolkits using Mir

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590099/+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 1447886] Re: mir_demo_server(_minimal): Window movement/resizing stops responding when the cursor leaves the surface, and can lead to windows 1px wide and unrecoverable.

[Alan Griffiths]

** Changed in: miral
   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/1447886

Title:
  mir_demo_server(_minimal): Window movement/resizing stops responding
  when the cursor leaves the surface, and can lead to windows 1px wide
  and unrecoverable.

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

Bug description:
  mir_demo_server(_minimal) version 0.13 and later: Window
  movement/resizing stops responding when the cursor leaves the surface.

  If you move or resize a surface with Alt+(button1/button3) then it's
  very easy to get the shell into a state where the window stops
  responding to movement/resizing and even becomes unrecoverable (window
  1px wide).

  Essentially the problem is the shell is only looking at the current
  cursor position and doesn't do anything if it's outside of the
  surface. This is frustrating as waiving the mouse around a bit it's
  very easy to reach this situation.

  It should be looking at the gesture as a whole and only doing position
  checking at the start of the move/resize gesture (ie. mouse button
  down). Thereafter the gesture should be continuous until the button is
  released, regardless of whether the cursor is still inside the
  surface/titlebar. You will find this is how all real desktops work,
  and mir_proving_server tries to too. Surfaces should always "own"
  input regardless of cursor position, just so long as the gesture
  (mouse down) began on that surface.

  The "unrecoverable" bit: This happens if you resize a surface too
  small/thin and it becomes impossible to resize it bigger again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1447886/+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 1624407] Re: Closing an application doesn’t actually close it, it merely requests all its windows to be closed

[Alan Griffiths]

It is not out of place at all - just an enhancement request.

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

Title:
  Closing an application doesn’t actually close it, it merely requests
  all its windows to be closed

Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Currently in unity8, when requesting to "Quit" a running application
  from the launcher, what happens is that qtmir goes through all its
  associated windows/surfaces, and closes them one by one. Supposedly,
  when the last window is closed, the application terminates itself (but
  this is not necessarily the case, see
  https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed-
  prop).

  This prevents application authors from doing proper cleanup before the
  app is closed. For example in Qt, the QCoreApplication::aboutToQuit()
  signal is emitted only after all windows have been closed, so the
  application doesn’t get a chance to e.g. save the list of open windows
  (real use case for multi-window browser application which saves the
  current session).

  This is similar to unity7’s implementation by the way, but I think
  it’s wrong. Surely there must be a way (maybe toolkit-specific) to
  request an app to terminate itself (and fall back to closing all
  windows if not).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1624407/+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 1624407] Re: Closing an application doesn’t actually close it, it merely requests all its windows to be closed

[Alan Griffiths]

AFAIK Mir follows the same model as X11 (which has the WM_DELETE_WINDOW
message but no WM_QUIT). I guess you could kill(pid, SIGTERM)?

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

Title:
  Closing an application doesn’t actually close it, it merely requests
  all its windows to be closed

Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Currently in unity8, when requesting to "Quit" a running application
  from the launcher, what happens is that qtmir goes through all its
  associated windows/surfaces, and closes them one by one. Supposedly,
  when the last window is closed, the application terminates itself (but
  this is not necessarily the case, see
  https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed-
  prop).

  This prevents application authors from doing proper cleanup before the
  app is closed. For example in Qt, the QCoreApplication::aboutToQuit()
  signal is emitted only after all windows have been closed, so the
  application doesn’t get a chance to e.g. save the list of open windows
  (real use case for multi-window browser application which saves the
  current session).

  This is similar to unity7’s implementation by the way, but I think
  it’s wrong. Surely there must be a way (maybe toolkit-specific) to
  request an app to terminate itself (and fall back to closing all
  windows if not).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1624407/+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 1625853] Re: Mouse cursor disappears (or just never changes) when entering the windows of Qt apps

[Alan Griffiths]

** Changed in: miral
   Status: Invalid => In Progress

** Changed in: miral
   Importance: Undecided => Low

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

** Branch linked: lp:~alan-griffiths/miral/cursor-theme

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

Title:
  Mouse cursor disappears (or just never changes) when entering the
  windows of Qt apps

Status in Canonical System Image:
  In Progress
Status in MirAL:
  In Progress
Status in qtubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  To reproduce:
  1) Open qtcreator in mir
  2) Move mouse around window

  Expect:
  Able to see cursor

  Result:
  Cursor goes away as if disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625853/+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 1592932] Re: non-puritine Xapp causing unity8 using 100% of CPU

[Alan Griffiths]

*** This bug is a duplicate of bug 1625401 ***
https://bugs.launchpad.net/bugs/1625401

Possibly a result of lp:1625401?

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

Title:
  non-puritine Xapp causing unity8 using 100% of CPU

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  unity8 will freeze up from time to time during  operation of xterm or
  other x11 legacy apps. This freeze up was reported by htop running in
  an instance on tty1. It will show two sessions of unity8 running at
  100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.12+16.10.20160527-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 15 14:22:04 2016
  InstallationDate: Installed on 2015-05-16 (395 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150510)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity8-filewatcher.log:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1592932/+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 1629275] Re: Clients and server all crash

[Alan Griffiths]

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

** Package changed: ubuntu => mir (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/1629275

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1629275/+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 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

[Alan Griffiths]

** Changed in: miral
   Status: Fix Committed => Fix Released

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

Title:
  Need to support pointer confinement in Mir and toolkits using Mir

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in MirAL:
  Fix Released
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590099/+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 1629275] Re: Clients and server all crash

[Alan Griffiths]

The reason the server exits is:

Thread 1 "mir_demo_server" received signal SIGTERM, Terminated.
0x76ea6200 in __libc_sendmsg (fd=40, msg=0x7fffc3f0, flags=16384) 
at ../sysdeps/unix/sysv/linux/sendmsg.c:28
28  ../sysdeps/unix/sysv/linux/sendmsg.c: No such file or directory.
(gdb) info threads
  Id   Target Id Frame 
* 1Thread 0x77fa47c0 (LWP 23976) "mir_demo_server" 0x76ea6200 
in __libc_sendmsg (fd=40, msg=0x7fffc3f0, 
flags=16384) at ../sysdeps/unix/sysv/linux/sendmsg.c:28
  2Thread 0x7fffee814700 (LWP 23980) "Mir/Snapshot" 
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  3Thread 0x7fffee013700 (LWP 23981) "Mir/Comp" 
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  4Thread 0x7fffed812700 (LWP 23983) "Mir/Input Reade" 0x76e9910d 
in poll () at ../sysdeps/unix/syscall-template.S:84
  5Thread 0x7fffed011700 (LWP 23984) "Mir/IPC" 
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  6Thread 0x7fffec810700 (LWP 23985) "Mir/IPC" __lll_lock_wait () at 
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
(gdb) c
Continuing.
[Thread 0x7fffec810700 (LWP 23985) exited]
[Thread 0x7fffed011700 (LWP 23984) exited]
[Thread 0x7fffed812700 (LWP 23983) exited]
[Thread 0x7fffee013700 (LWP 23981) exited]
[Thread 0x7fffee814700 (LWP 23980) exited]
ERROR: 
/home/alan/display_server/mir/src/platforms/mesa/server/buffer_allocator.cpp(151):
 Throw in function virtual void 
{anonymous}::DMABufTextureBinder::ensure_egl_image()
Dynamic exception type: 
boost::exception_detail::clone_impl
std::exception::what: Failed to get PRIME fd from gbm bo: No such file or 
directory


Thread 1 "mir_demo_server" received signal SIGSEGV, Segmentation fault.
0x7038b62c in ?? ()
(gdb) bt
#0  0x7038b62c in ?? ()
#1  0x7740a141 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#2  0x76dd765a in __cxa_finalize (d=0x77dd60a0) at cxa_finalize.c:56
#3  0x77761d23 in __do_global_dtors_aux () from 
/usr/local/lib/libmirserver.so.42
#4  0x7fffe320 in ?? ()
#5  0x77de8efa in _dl_fini () at dl-fini.c:235
Backtrace stopped: frame did not save the PC

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1629275/+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 1625853] Re: Mouse cursor disappears (or just never changes) when entering the windows of Qt apps

[Alan Griffiths]

** Changed in: miral
   Status: Fix Committed => Fix Released

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

Title:
  Mouse cursor disappears (or just never changes) when entering the
  windows of Qt apps

Status in Canonical System Image:
  In Progress
Status in Mir:
  Triaged
Status in MirAL:
  Fix Released
Status in qtubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  To reproduce:
  1) Open qtcreator in mir
  2) Move mouse around window

  Expect:
  Able to see cursor

  Result:
  Cursor goes away as if disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625853/+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 1629275] Re: Clients and server all crash

[Alan Griffiths]

And this is where the "signal comes from:

#1  0x777672fa in mir::terminate_with_current_exception ()
at 
/home/alan/display_server/mir/src/server/terminate_with_current_exception.cpp:52
#2  0x778af4c2 in mir::compositor::CompositingFunctor::operator() 
(this=0x559fcae0)
at 
/home/alan/display_server/mir/src/server/compositor/multi_threaded_compositor.cpp:180
#3  0x778b2a7c in std::_Function_handler 
>::_M_invoke(std::_Any_data const&) (__functor=...) at 
/usr/include/c++/6/functional:1770
#4  0x77769846 in std::function::operator()() const 
(this=0x7fffee012d00) at /usr/include/c++/6/functional:2136
#5  0x779ea451 in (anonymous namespace)::Task::execute 
(this=0x7fffee012d00)
at /home/alan/display_server/mir/src/server/thread/basic_thread_pool.cpp:40
#6  0x779ea7ba in (anonymous namespace)::Worker::operator() 
(this=0x559fcbd0)
at /home/alan/display_server/mir/src/server/thread/basic_thread_pool.cpp:91
#7  0x779ed66c in std::__invoke_impl (__f=...) at /usr/include/c++/6/functional:218
#8  0x779ed62e in std::__invoke<(anonymous namespace)::Worker&> 
(__fn=...) at /usr/include/c++/6/functional:260
#9  0x779ed5d8 in std::reference_wrapper<(anonymous 
namespace)::Worker>::operator()<>(void) const (this=0x559fcf08)
at /usr/include/c++/6/functional:474
#10 0x779ed5b6 in std::_Bind_simple()>::_M_invoke<>(std::_Index_tuple<>) (this=0x559fcf08) 
at /usr/include/c++/6/functional:1400
#11 0x779ed540 in std::_Bind_simple()>::operator()(void) (
this=0x559fcf08) at /usr/include/c++/6/functional:1389
#12 0x779ed510 in 
std::thread::_State_impl()> >::_M_run(void) (this=0x559fcf00) at 
/usr/include/c++/6/thread:196
#13 0x7743650f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#14 0x7490170a in start_thread (arg=0x7fffee013700) at 
pthread_create.c:333
#15 0x76ea50ff in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

And that appears to be from failing to handle an exception from
DMABufTextureBinder::ensure_egl_image() ("ERROR:
/home/alan/display_server/mir/src/platforms/mesa/server/buffer_allocator.cpp(151):"
in comment #7)

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1629275/+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 1629275] Re: Clients and server all crash

[Alan Griffiths]

** Branch linked: lp:~alan-griffiths/mir/fix-server-crash

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1629275/+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 1629275] Re: Clients and server all crash

[Alan Griffiths]

Using qterminal in place of gnome-terminal works, so I think the server
crash may be the only Mir problem here.

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1629275/+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 1629275] Re: Clients and server all crash

[Alan Griffiths]

It is also worth noting that starting the mir clients outside the gnome-
terminal seems stable. So whatever weirdness is going on client-side is
associated with gnome-terminal.

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1629275/+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 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

[Alan Griffiths]

** Branch linked: lp:~alan-griffiths/miral/confine_pointer

** Changed in: miral
   Status: In Progress => Fix Committed

** Changed in: miral
 Assignee: Daniel d'Andrada (dandrader) => Alan Griffiths (alan-griffiths)

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

Title:
  Need to support pointer confinement in Mir and toolkits using Mir

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in MirAL:
  Fix Committed
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590099/+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 1625853] Re: Mouse cursor disappears (or just never changes) when entering the windows of Qt apps

[Alan Griffiths]

** Changed in: miral
   Status: In Progress => Fix Committed

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

Title:
  Mouse cursor disappears (or just never changes) when entering the
  windows of Qt apps

Status in Canonical System Image:
  In Progress
Status in MirAL:
  Fix Committed
Status in qtubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  To reproduce:
  1) Open qtcreator in mir
  2) Move mouse around window

  Expect:
  Able to see cursor

  Result:
  Cursor goes away as if disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625853/+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 1627697] Re: gnome-terminal crashes on resize

[Alan Griffiths]

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

** No longer affects: miral

** No longer affects: gtk+3.0 (Ubuntu)

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

** Changed in: miral
   Status: New => Fix Committed

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

Title:
  gnome-terminal crashes on resize

Status in GTK+:
  New
Status in MirAL:
  Fix Committed

Bug description:
  Yakkety, Mir-0.24, lp:miral

  Run gnome-terminal on a touchscreen laptop and resizing by three-
  finger pinch...

  $ miral-run gnome-terminal
  $ 
  (gnome-terminal-server:4817): Gtk-WARNING **: GtkSettings Cursor Theme: 
Unsupported GDK backend
  ...
  (gnome-terminal-server:4817): Gdk-WARNING **: unknown property 
gtk-fontconfig-timestamp

  (gnome-terminal-server:4817): Gdk-WARNING **: Ignoring unknown Mir
  event 11

  (gnome-terminal-server:4817): Gtk-WARNING **: Allocating size to GtkBox 
0x55eb906c6900 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  *** Error in `/usr/lib/gnome-terminal/gnome-terminal-server': double free or 
corruption (out): 0x7f2e70258010 ***

  (Can't reproduce with Mir-0.1, but that may be because resize was too
  broken.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1627697/+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 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

[Alan Griffiths]

Again:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2970/consoleFull

12:05:28 9: Actual function call count doesn't match EXPECT_CALL(first_client, 
handle_input(_))...
12:05:28 9: Expected: to be called between 20 and 180 times
12:05:28 9: Actual: called 18 times - unsatisfied and active
12:05:28 9: [2016-11-24 12:05:28.455825] mirserver: Stopping
12:05:28 9: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(124506 ms)

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

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

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

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570698/+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 1542029] Re: New windows have incorrect dimensions on launch (not the dimensions the app specifies)

[Alan Griffiths]

Can we have a specific example of the bug?

The size of the window requested is a hint to the window manager, not a
requirement. The requested size may legitimately be overridden (e.g. for
layout reasons).

I.e. There is no guarantee that size created matches the requested size.

** Changed in: miral (Ubuntu)
   Status: New => Incomplete

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

Title:
  New windows have incorrect dimensions on launch (not the dimensions
  the app specifies)

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in Ubuntu UX:
  Invalid
Status in miral package in Ubuntu:
  Incomplete
Status in puritine package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  currently, the shell is picking some random window size.
  They are about to change it to be close to what is on the phone - as this 
will match most apps.
  however the Xapps should have something "larger"

  shell is landing the ability to communicate to it, the desire default
  first launch window size

  it would also be good to have design input on this selection

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542029/+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 1648292] Re: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1]

[Alan Griffiths]

There are two problems being discussed:

/1/ mir doesn't work on the current Ubuntu snappy core kernel for Raspberry pi 
2; and,
/2/ Mir does not give good diagnostic information from our attempt at 
automaticity deciding on the right graphics stack.

IMO systems that try a series of options (in this case graphics modules)
and only report problems when the last one fails are a PITA, but that
has been discussed many times. I don't see an existing bug for this.
Maybe we should open one and leave this report for the former problem?

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

Title:
  Running Mir-Server snap, gives error! [Unknown command line options:
  --vt 1]

Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  I don't know, if this is right place!
  Trying to run mir-server gives error:

  Dec  8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Main process exited, code=exited, status=1/FAILURE
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Unit entered failed state.
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Failed with result 'exit-code'.
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Service hold-off time over, scheduling restart.

  Running on Raspberry pi 2, Ubuntu snappy core!

  runned lsb_release -rd

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

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

Re: [Touch-packages] [Bug 1649696]/usr/include/mirclient/mir_toolkit/events/event.h:24:32: fatal error: mir_toolkit/common.h: No such file or directory

[Alan Griffiths]

On Tuesday, 13 December 2016 21:29:23 GMT, kevin gunn 
<kevin.g...@canonical.com> wrote:
> ** Changed in: mir
>  Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)
> 
> ** Also affects: mir (Ubuntu)
>Importance: Undecided
>Status: New
> 
> ** Changed in: mir (Ubuntu)
>  Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)
> 

The header moved to mircore-dev, which is a dependency of miclient-dev and 
mirserver-dev. Reinstall one of them.


-- 
Alan Griffiths. +44 (0)798 9938 758
Octopull Limited. http://www.octopull.co.uk/

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

Title:
  /usr/include/mirclient/mir_toolkit/events/event.h:24:32: fatal error:
  mir_toolkit/common.h: No such file or directory

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

Bug description:
  A header from libmirclient-dev has an include for a file that used to
  be in libmircommon-dev, which seems to have been removed in
  0.25.0+16.04.20161203-0ubuntu1

  libmircommon-dev=0.24.1+16.04.20160928-0ubuntu1 did have
  mir_toolkit/common.h

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1649696/+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 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

[Alan Griffiths]

12:32:46 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
12:32:46 11: [2016-12-13 12:32:46.184830] mirserver: Starting
12:32:46 11: [2016-12-13 12:32:46.188127] mirserver: Selected driver: 
mir:stub-graphics (version 0.26.0)
12:32:46 11: [2016-12-13 12:32:46.501072] mirserver: Using software cursor
12:32:46 11: [2016-12-13 12:32:46.583720] mirserver: Selected input driver: 
mir:stub-input (version: 0.26.0)
12:32:46 11: [2016-12-13 12:32:46.586385] mirserver: Mir version 0.26.0
12:32:46 11: [2016-12-13 12:32:46.885544] mirserver: Initial display 
configuration:
12:32:46 11: [2016-12-13 12:32:46.885985] mirserver: Output 1: VGA connected, 
used
12:32:46 11: [2016-12-13 12:32:46.886267] mirserver: Physical size 0.0" 0x0mm
12:32:46 11: [2016-12-13 12:32:46.886495] mirserver: Power is on
12:32:47 11: [2016-12-13 12:32:46.886786] mirserver: Current mode 1000x800 
60.00Hz
12:32:47 11: [2016-12-13 12:32:46.887065] mirserver: Preferred mode 1000x800 
60.00Hz
12:32:47 11: [2016-12-13 12:32:46.887299] mirserver: Orientation normal
12:32:47 11: [2016-12-13 12:32:46.887551] mirserver: Logical size 1000x800
12:32:47 11: [2016-12-13 12:32:46.887795] mirserver: Logical position +0+0
12:32:51 11: 
/<>/mir-0.25.0+xenial3168bzr3882/tests/acceptance-tests/test_client_input.cpp:667:
 Failure
12:32:51 11: Mock function called more times than expected - returning directly.
12:32:51 11: Function call: handle_input(touch_event(when=3043267954730209 
(36.826310ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=11.7035, y=18.7256, pressure=1, major=8, minor=5, size=8}, modifiers=none))
12:32:51 11: Expected: to be called between 20 and 180 times
12:32:51 11: Actual: called 181 times - over-saturated and active
12:32:51 11: 
12:32:51 11: GMOCK WARNING:
12:32:51 11: Uninteresting mock function call - returning directly.
12:32:51 11: Function call: handle_input(touch_event(when=3043267976114041 
(162.322519ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=11.7339, y=18.7742, pressure=1, major=8, minor=5, size=8}, modifiers=none))
12:32:51 11: Stack trace:
12:32:51 11: [2016-12-13 12:32:51.256090] mirserver: Stopping
12:32:51 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(5183 ms)
12:32:51 11: [ RUN ] 

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial+overlay/3138/consoleFull

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

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

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

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 

[Touch-packages] [Bug 1627750] Re: gnome-terminal displays input in wrong window

[Alan Griffiths]

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gtk

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

Title:
  gnome-terminal displays input in wrong window

Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  $ miral-server --startup gnome-terminal

  Go "File=>Open Terminal" to create a second window

  Type in the new window.

  Expect: typing to appear in the new window
  Actual: typing appears in the original window

  Focus *is* on the new window as can be verified by Alt-F4, which
  correctly closes the new window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/miral/+bug/1627750/+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 1445542] Re: Using the Mir backend, secondary windows of GTK apps open behind the primary window

[Alan Griffiths]

[Testing on zesty]

I don't see the problem behaviour using miral-shell or mir_demo_server,
but maybe I'm just not trying the right apps? (remmina fails with a new
error: "GdkMirDisplay does not implement the monitor vfuncs".)

Marking "Incomplete" pending a way to reproduce with the current
codebase.

** Changed in: mir
   Status: New => Incomplete

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

Title:
  Using the Mir backend, secondary windows of GTK apps open behind the
  primary window

Status in Mir:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Using the Mir backend, secondary windows of GTK apps open behind the
  primary window. This is odd because Mir's default behaviour is to put
  any new surface on top.

  e.g. Remmina (after you apply the fix for bug 1444132)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1445542/+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 1445543] Re: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

[Alan Griffiths]

Seems to be working with gtk 3 on zesty - so not Mir.

** Changed in: mir
   Status: New => Invalid

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

Title:
  Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

Status in GTK+:
  New
Status in Mir:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  GTK apps on Mir: Input focus is unreliable and sporadic. Background
  windows ignore input and/or focus switches apparently randomly.

  Example:

  $ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg

  Show the "Scores" - you can switch focus between this and the main
  window with Alt+` but doesn't respond to input.

  Other dialogs (e.g. "About") work fine. From the Mir side there's no
  obvious difference between these windows.

  In this example, MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input
  events being correctly received on the client side. That shows most of
  the Mir stack is working correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1445543/+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 1625397] Re: [gtk] Focus is stuck on the save as window vs the main window

[Alan Griffiths]

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gtk

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

Title:
  [gtk] Focus is stuck on the save as window vs the main window

Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  To reproduce:
  Open gedit in miral
  click save (the window should pop up)
  click back on the main window leaving the save window open
  type

  Expected:
  Text to appear in the main top most window

  Result:
  Text appears on the save as window behind the main window.

  I checked with mir_demo_server and same issue so this could be a gtk
  bug it self.

  Added by alan_g:

  As described in comment #5 this seems to be mostly a gtk-mir problem.
  (Where are they filed?) But there is a MirAL component (because even
  if gtk-mir was right, this problem would sill be seen).

  Added later by alan_g:
  The problem mentioned in lp:1626659 has been committed, everything left is a 
gtk-mir issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/miral/+bug/1625397/+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 1629275] Re: Clients all crash (and sometimes server too)

[Alan Griffiths]

Not reproducible on zesty - probably fixed by changes to gtk-3 (or
gnome-terminal). Marking invalid in Mir.

** Changed in: mir
   Status: Incomplete => Invalid

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

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

Title:
  Clients all crash (and sometimes server  too)

Status in Mir:
  Invalid
Status in MirAL:
  Invalid
Status in mir package in Ubuntu:
  Invalid

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

  The "frequent" server crash is lp:1607812, this bug is for the client
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1629275/+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 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

[Alan Griffiths]

** No longer affects: mir (Ubuntu)

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

Title:
  clients crash with "UbuntuClientIntegration: connection to Mir server
  failed."

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  According to
  https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
  it seems to be common-ish.

  This happens when unity8-dash can't find unity8 (mir server) and
  crashing (via QFatal) is our controlled way of exiting (not very
  clean, but it is how it is)[1].

  This will happen for example if you try to start unity8-dash directly (not 
through upstart) from a ssh shell in the phone, i.e
  phablet-shell
  stop unity8-dash
  unity8-dash

  And it may happen after a unity8 crash.

  In general we think that it's not a pressing issue users have since
  there seems to have not been any report of unity8-dash failing to
  start, but we're creating this bug to track it from time to time and
  make sure it doesn't get worse.

  [1] Qt platform plugins (also know as QPA) don't have a way to say
  they had a problem initiating themselves, Qt code is prepared for the
  QPlatformIntegrationPlugin::create() function to return, but all it
  does when that happens is call qFatal anyway [2]

  [2]
  
http://code.qt.io/cgit/qt/qtbase.git/tree/src/gui/kernel/qguiapplication.cpp#n1132

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1655936/+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 1655936] Re: clients crash with "UbuntuClientIntegration: connection to Mir server failed."

[Alan Griffiths]

I don't think anything can be done in Mir: The API [mir_connect_sync()]
returns an error if it can't connect. There's no requirement to crash as
a result - we have tests and examples that report the error and exit.

** Changed in: mir (Ubuntu)
   Status: New => Incomplete

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

Title:
  clients crash with "UbuntuClientIntegration: connection to Mir server
  failed."

Status in mir package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  According to
  https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
  it seems to be common-ish.

  This happens when unity8-dash can't find unity8 (mir server) and
  crashing (via QFatal) is our controlled way of exiting (not very
  clean, but it is how it is)[1].

  This will happen for example if you try to start unity8-dash directly (not 
through upstart) from a ssh shell in the phone, i.e
  phablet-shell
  stop unity8-dash
  unity8-dash

  And it may happen after a unity8 crash.

  In general we think that it's not a pressing issue users have since
  there seems to have not been any report of unity8-dash failing to
  start, but we're creating this bug to track it from time to time and
  make sure it doesn't get worse.

  [1] Qt platform plugins (also know as QPA) don't have a way to say
  they had a problem initiating themselves, Qt code is prepared for the
  QPlatformIntegrationPlugin::create() function to return, but all it
  does when that happens is call qFatal anyway [2]

  [2]
  
http://code.qt.io/cgit/qt/qtbase.git/tree/src/gui/kernel/qguiapplication.cpp#n1132

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1655936/+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 1627697] Re: gnome-terminal crashes on resize

[Alan Griffiths]

gtk seems to be fixed on 17.04

** Changed in: miral
   Status: Fix Committed => Fix Released

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

Title:
  gnome-terminal crashes on resize

Status in MirAL:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Yakkety, Mir-0.24, lp:miral

  Run gnome-terminal on a touchscreen laptop and resizing by three-
  finger pinch...

  $ miral-run gnome-terminal
  $ 
  (gnome-terminal-server:4817): Gtk-WARNING **: GtkSettings Cursor Theme: 
Unsupported GDK backend
  ...
  (gnome-terminal-server:4817): Gdk-WARNING **: unknown property 
gtk-fontconfig-timestamp

  (gnome-terminal-server:4817): Gdk-WARNING **: Ignoring unknown Mir
  event 11

  (gnome-terminal-server:4817): Gtk-WARNING **: Allocating size to GtkBox 
0x55eb906c6900 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  *** Error in `/usr/lib/gnome-terminal/gnome-terminal-server': double free or 
corruption (out): 0x7f2e70258010 ***

  (Can't reproduce with Mir-0.1, but that may be because resize was too
  broken.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/miral/+bug/1627697/+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 1639745] Re: Mir GL clients never appear at all on VirtualBox

[Alan Griffiths]

Also affects VM (qemu/kvm) lp:1646532

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

Title:
  Mir GL clients never appear at all on VirtualBox

Status in Mir:
  In Progress
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Mir GL clients never appear at all on VirtualBox.

  After digging for a while, it appears the issue is that vboxvideo does
  not support DRM_CAP_PRIME and so only supports GEM flink names. Sadly
  Mir is the opposite now: Mir only supports PRIME but not flink names.

  Internally some exceptions are being thrown in Mir at present, but we
  seem to catch and silence them all. So you never see any error
  messages at all. Just Mir GL clients never appear on screen in
  VirtualBox.

  For the record, Wayland supports falling back to flink names in the
  absence of PRIME. We should too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1639745/+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 1651735] [NEW] $ mir_demo_server --help fails with an exception

[Alan Griffiths]

Public bug reported:

$ mir_demo_server --help
[2016-12-21 11:49:00.068655] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.25.0)
[2016-12-21 11:49:00.069710] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.25.0)
[2016-12-21 11:49:00.069935] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.25.0)
[2016-12-21 11:49:00.069954] mirplatform: Found graphics driver: 
throw-on-creation (version 0.25.0)
ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
Dynamic exception type: 
boost::exception_detail::clone_impl
std::exception::what: character conversion failed

** Affects: mir
 Importance: Undecided
 Status: New

** Affects: mir (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: mir
   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/1651735

Title:
  $ mir_demo_server --help fails with an exception

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

Bug description:
  $ mir_demo_server --help
  [2016-12-21 11:49:00.068655] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.25.0)
  [2016-12-21 11:49:00.069710] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.25.0)
  [2016-12-21 11:49:00.069935] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.25.0)
  [2016-12-21 11:49:00.069954] mirplatform: Found graphics driver: 
throw-on-creation (version 0.25.0)
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: character conversion failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651735/+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 1651735] Re: $ mir_demo_server --help fails with an exception

[Alan Griffiths]

It isn't just the test platform:

$ sudo apt remove mir-test-tools
$ mir_demo_server --help
[2016-12-21 12:07:29.534586] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.25.0)
[2016-12-21 12:07:29.535346] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.25.0)
ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
Dynamic exception type: 
boost::exception_detail::clone_impl
std::exception::what: character conversion failed

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

Title:
  $ mir_demo_server --help fails with an exception

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

Bug description:
  $ mir_demo_server --help
  [2016-12-21 11:49:00.068655] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.25.0)
  [2016-12-21 11:49:00.069710] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.25.0)
  [2016-12-21 11:49:00.069935] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.25.0)
  [2016-12-21 11:49:00.069954] mirplatform: Found graphics driver: 
throw-on-creation (version 0.25.0)
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: character conversion failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651735/+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 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

[Alan Griffiths]

10:15:27 Expected: to be called between 20 and 180 times
10:15:27 Actual: called 181 times - over-saturated and active
10:15:27 
10:15:27 GMOCK WARNING:
10:15:27 Uninteresting mock function call - returning directly.
10:15:27 Function call: handle_input(touch_event(when=3725515999186980 
(164.850700ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=11.9781, y=19.165, pressure=1, major=8, minor=5, size=8}, modifiers=none))
10:15:27 Stack trace:
10:15:27 [2016-12-21 10:03:39.345580] mirserver: Stopping
10:15:27 [ FAILED ] TestClientInput.receives_one_touch_event_per_frame (5473 ms)

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial+overlay/3250/consoleFull

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

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

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

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570698/+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 1651391] Re: Package mirtest-dev is missing a dependency on mir-renderer-gl-dev

[Alan Griffiths]

** Branch linked: lp:~alan-griffiths/mir/fix-1651391

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

Title:
  Package mirtest-dev is missing a dependency on mir-renderer-gl-dev

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

Bug description:
  tests/mirtest.pc.in contains the line:

  Requires: mirserver mirplatform mirclient mir-renderer-gl-dev

  But debian/control doesn't have the corresponding dependency on mir-
  renderer-gl-dev

  (I also think that mir-renderer-gl-dev.pc ought to be renamed mir-
  renderer-gl.pc, but that's a secondary issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651391/+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 1651735] Re: $ mir_demo_server --help fails with an exception

[Alan Griffiths]

On further investigation I only see this on my desktop (not on VM or
laptop).

** Changed in: mir
   Status: Incomplete => Invalid

** Changed in: mir (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  $ mir_demo_server --help fails with an exception

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid

Bug description:
  $ mir_demo_server --help
  [2016-12-21 11:49:00.068655] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.25.0)
  [2016-12-21 11:49:00.069710] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.25.0)
  [2016-12-21 11:49:00.069935] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.25.0)
  [2016-12-21 11:49:00.069954] mirplatform: Found graphics driver: 
throw-on-creation (version 0.25.0)
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: character conversion failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651735/+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 1651391] [NEW] Package mirtest-dev is missing a dependency on mir-renderer-gl-dev

[Alan Griffiths]

Public bug reported:

tests/mirtest.pc.in contains the line:

Requires: mirserver mirplatform mirclient mir-renderer-gl-dev

But debian/control doesn't have the corresponding dependency on mir-
renderer-gl-dev

(I also think that mir-renderer-gl-dev.pc ought to be renamed mir-
renderer-gl.pc, but that's a secondary issue.)

** Affects: mir
 Importance: Medium
 Assignee: Alan Griffiths (alan-griffiths)
 Status: In Progress

** Affects: mir (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Changed in: mir
   Importance: Undecided => Medium

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

** Changed in: mir (Ubuntu)
   Status: New => Triaged

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

Title:
  Package mirtest-dev is missing a dependency on mir-renderer-gl-dev

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

Bug description:
  tests/mirtest.pc.in contains the line:

  Requires: mirserver mirplatform mirclient mir-renderer-gl-dev

  But debian/control doesn't have the corresponding dependency on mir-
  renderer-gl-dev

  (I also think that mir-renderer-gl-dev.pc ought to be renamed mir-
  renderer-gl.pc, but that's a secondary issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651391/+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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Alan Griffiths]

I think there are distinct cases here:

Case 1: (easy I hope)

The client initiating a user-drag/resize is analogous to the existing
input focus request. Vis:

void mir_window_request_user_move(MirWindow* window, MirCookie const* 
cookie);
void mir_window_request_user_resize(MirWindow* window, MirCookie const* 
cookie);

Should be passed to the server, validated and handled by the WM policy
exactly the same as:

void mir_window_raise(MirWindow* window, MirCookie const* cookie);

How the client decides on calling these (via a menu or not) isn't really
the issue.

This is addressed by lp:~alan-griffiths/mir/client-initiates-user-move-
and-resize/+merge/320917

Case 2:

"Always on top" would be a property of a window, the client could set
(or reset) this on the MirWindowSpec. The WM policy gets to decide
whether (and how) to respect this property.

There's currently no support for such a property in libmirserver's
SurfaceStack - so addressing that would be a pre-requisite to
introducing such a property.

Case 3: (comment #6)

If there were some generic "window manager menu" that toolkits could
request then that might be requested with a similar mechanism to case 1.
But I've not seen a requirement for this (yet).

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

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Alan Griffiths]

** Branch linked: lp:~alan-griffiths/mir/client-initiates-user-move-and-
resize

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

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+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 1665286] Re: [unity8] A ghost (shadow only) window opens with some app windows/menus

[Alan Griffiths]

** Changed in: mir
   Status: Incomplete => Invalid

** Changed in: miral
   Status: Incomplete => Invalid

** Changed in: mir (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: miral (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [unity8] A ghost (shadow only) window opens with some app
  windows/menus

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Invalid
Status in MirAL:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in miral package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  ubuntu 17.04 unity8

  - install tiled, apt install tiled
  - Add "X-Ubuntu-XMir-Enable=false" to /usr/share/applications/tiled.desktop 
so that it doesn't get launched inside an xmir wrapper
  - launch tiled

  you'll see a transparent window opened beneath the main window called
  "Object Types Editor"

  see attached screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1665286/+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 1625397] Re: [gtk] Focus is stuck on the save as window vs the main window

[Alan Griffiths]

** Changed in: miral
   Status: Incomplete => Invalid

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

Title:
  [gtk] Focus is stuck on the save as window vs the main window

Status in GTK+:
  Fix Released
Status in MirAL:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  To reproduce:
  Open gedit in miral
  click save (the window should pop up)
  click back on the main window leaving the save window open
  type

  Expected:
  Text to appear in the main top most window

  Result:
  Text appears on the save as window behind the main window.

  I checked with mir_demo_server and same issue so this could be a gtk
  bug it self.

  Added by alan_g:

  As described in comment #5 this seems to be mostly a gtk-mir problem.
  (Where are they filed?) But there is a MirAL component (because even
  if gtk-mir was right, this problem would sill be seen).

  Added later by alan_g:
  The problem mentioned in lp:1626659 has been committed, everything left is a 
gtk-mir issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1625397/+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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Alan Griffiths]

The branch that landed was only part of the solution to one of the
problems

** Changed in: mir
   Status: Fix Committed => In Progress

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

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Alan Griffiths]

** Branch linked: lp:~alan-griffiths/mir/server-support-for-client-
initiates-move

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

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+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 1675138] Re: Please transition to Boost 1.62

[Alan Griffiths]

Resolved on #ubuntu-mir...

 if you are fine with people uploading the package directly to the 
archive we can work it out, i.e. I upload a -2 as soon at 0.26.2-1 is uploaded, 
but then your next upload done through whatever CI should contain it.
 mapreri: that would work for me
 I have no idea how bileto (or whatever kind of CI/landing system) you 
are using work
 oh, great
 so, what would be the timing for 0.26.2 to land? :)
 mapreri: out of my hands, first QA need to approve and then someone 
needs to push to archive. But I'd guess the next day or two.
 that works just fine
 I'll arrange the -2 upload, will you please merge it in 0.26.3 in the 
meantime?
 AFAIK 0.26.3 doesn't exist (and likely won't). But I'll take care of 
it in that contingency.

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

Title:
  Please transition to Boost 1.62

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  New
Status in mir package in Ubuntu:
  Triaged

Bug description:
  There is an ongoing transition to Boost 1.62 and mir is one of the last 
affected packages:
  http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1675138/+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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Alan Griffiths]

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

** Changed in: mir
   Status: Triaged => In Progress

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

** Changed in: miral
   Status: New => Triaged

** Changed in: miral
   Importance: Undecided => High

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

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+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 1671072] Re: Child windows don't get focused

[Alan Griffiths]

Confirmed that miral-shell (both decorated and tiling) fail to set the
focus anywhere sane.

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

Title:
  Child windows don't get focused

Status in Canonical System Image:
  Triaged
Status in MirAL:
  In Progress
Status in miral package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671072/+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 1671072] Re: Child windows don't get focused

[Alan Griffiths]

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

** Changed in: miral
   Status: New => In Progress

** Changed in: miral
   Importance: Undecided => High

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

** Changed in: miral
Milestone: None => 1.3.1

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

Title:
  Child windows don't get focused

Status in Canonical System Image:
  Triaged
Status in MirAL:
  In Progress
Status in miral package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671072/+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 1671072] Re: Child windows don't get focused

[Alan Griffiths]

miral-shell gets to step 5 before there's a focus issue. Here's the
problem:

[2017-03-16 14:14:51.298369] miral::Window Management: info_for -> Open File
[2017-03-16 14:14:52.798261] miral::Window Management: handle_modify_window 
window_info={name=Open File, type=dialog, state=restored, parent=Untitled , 
children={}, min_width=325, min_height=178, max_width=16777215, 
max_height=16777215, preferred_orientation=0xf, confine_pointer=0, 
output_id=0}, modifications={state=hidden}
[2017-03-16 14:14:52.798423] miral::Window Management: modify_window 
window_info={name=Open File, type=dialog, state=restored, parent=Untitled , 
children={}, min_width=325, min_height=178, max_width=16777215, 
max_height=16777215, preferred_orientation=0xf, confine_pointer=0, 
output_id=0}, modifications={state=hidden}
[2017-03-16 14:14:52.798490] miral::Window Management: advise_state_change 
window_info={name=Open File, type=dialog, state=restored, parent=Untitled , 
children={}, min_width=325, min_height=178, max_width=16777215, 
max_height=16777215, preferred_orientation=0xf, confine_pointer=0, 
output_id=0}, state=hidden
[2017-03-16 14:14:52.798560] miral::Window Management: advise_focus_gained 
window_info={name=Open File, type=dialog, state=restored, parent=Untitled , 
children={}, min_width=325, min_height=178, max_width=16777215, 
max_height=16777215, preferred_orientation=0xf, confine_pointer=0, output_id=0}
[2017-03-16 14:14:52.798609] miral::Window Management: raise_tree root=Open File
[2017-03-16 14:14:52.798658] miral::Window Management: advise_raise 
window_info={Untitled , Open File}
[2017-03-16 14:14:52.798712] miral::Window Management: advise_raise 
window_info={Open File}
[2017-03-16 14:14:52.798833] miral::Window Management: advise_focus_lost 
window_info={name=Open File, type=dialog, state=restored, parent=Untitled , 
children={}, min_width=325, min_height=178, max_width=16777215, 
max_height=16777215, preferred_orientation=0xf, confine_pointer=0, output_id=0}

It looks as though miral is not handling the hiding of the child dialog
correctly.

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

Title:
  Child windows don't get focused

Status in Canonical System Image:
  Triaged
Status in MirAL:
  In Progress
Status in miral package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671072/+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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Alan Griffiths]

It *is* also possible to crash miral-shell this way - after numerous
runs where it "merely" hung on exit I have a crash.

** Changed in: miral
   Status: Incomplete => Confirmed

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in Mir 0.26 series:
  Incomplete
Status in MirAL:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+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 1640366] Re: [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA dropping_latency_is_closer_to_zero_than_one)

[Alan Griffiths]

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/4268/consoleFull

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

Title:
  [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one (AKA
  dropping_latency_is_closer_to_zero_than_one)

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

Bug description:
  20:35:16 10: [ RUN  ] ClientLatency.dropping_latency_is_limited_to_one
  20:35:16 10: [2016-11-08 20:35:16.713374] mirserver: Starting
  20:35:16 10: [2016-11-08 20:35:16.713544] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.714686] mirserver: Using software cursor
  20:35:16 10: [2016-11-08 20:35:16.733467] mirserver: Initial display 
configuration:
  20:35:16 10: [2016-11-08 20:35:16.734637] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.734766] mirserver: Mir version 0.25.0
  20:35:18 10: 
/<>/mir-0.25.0+yakkety2807bzr3804/tests/acceptance-tests/test_latency.cpp:341:
 Failure
  20:35:18 10: Value of: max_latency
  20:35:18 10: Expected: is <= 1
  20:35:18 10:   Actual: 2 (of type unsigned int)
  20:35:18 10: [  debug   ] 98 frames sampled, averaging 1.0 frames latency
  20:35:18 10: [  debug   ]  0:  1  1  1  1  1  1  1  2  1  1
  20:35:18 10: [  debug   ] 10:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 20:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 30:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 40:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 50:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 60:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 70:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 80:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 90:  1  1  1  1  1  1  1  1
  20:35:18 10: [2016-11-08 20:35:18.575646] mirserver: Stopping
  20:35:18 10: [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one 
(1879 ms)

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2781/consoleFull]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1640366/+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 1671072] Re: Child windows don't get focused

[Alan Griffiths]

** Changed in: miral
   Status: In Progress => Fix Committed

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

Title:
  Child windows don't get focused

Status in Canonical System Image:
  Triaged
Status in MirAL:
  Fix Committed
Status in miral package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671072/+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 1671072] Re: Child windows don't get focused

[Alan Griffiths]

** Branch linked: lp:~alan-griffiths/miral/fix-1671072

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

Title:
  Child windows don't get focused

Status in Canonical System Image:
  Triaged
Status in MirAL:
  In Progress
Status in miral package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671072/+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 1655997] Re: [gtk] Save as dialog: dropdown menu surface positioned wrong

[Alan Griffiths]

Not happening with the latest gtk to land in zesty

** Changed in: miral
   Status: Incomplete => Invalid

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

Title:
  [gtk] Save as dialog: dropdown menu surface positioned wrong

Status in GTK+:
  Fix Committed
Status in MirAL:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Running miral-shell and gedit:

  1. Burger-menu -> Save As
  2. Click the "Character encoding" or "Line ending" or "All files" dropdowns

  Bug: child surfaces are positioned incorrectly, should be under/over
  the widget that invoked them

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1655997/+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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Alan Griffiths]

Correction to #14 - the miral-shell crash (and the hang on exit) seems
to be entirely down to racy decorations code. Both the "tiling" window
manage and miral-kiosk are entirely stable.

I *think* this is QtMir.

** Changed in: miral
   Status: Confirmed => Incomplete

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in Mir 0.26 series:
  Incomplete
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Alan Griffiths]

I've split off the miral-shell "hang on exit" as lp:1673038  since it
looks entirely separate to the Unity8 crash.

** Changed in: miral
   Status: Triaged => Incomplete

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in Mir 0.26 series:
  Incomplete
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+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 1671072] Re: Child windows don't get focused

[Alan Griffiths]

** Changed in: miral
   Status: Fix Committed => Fix Released

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

Title:
  Child windows don't get focused

Status in Canonical System Image:
  Triaged
Status in MirAL:
  Fix Released
Status in miral package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671072/+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 1668053] Re: [unity8] kate, impossible to close "Print Preview" window

[Alan Griffiths]

>From my perspective it is incorrect to say 'impossible to close "Print
Preview" window' I can run kate in miral-shell, open the print-preview
and close it (Alt-F4) fine.

Now I do agree it seems daft that there's neither a "Close" button (or
equivalent) on the window, nor an "X" in the titlebar, but isn't that
down to a design issue?

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

Title:
  [unity8] kate, impossible to close "Print Preview" window

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in Ubuntu UX:
  New
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 Unity 8
  [unity8] kate, impossible to close "Print Preview" window

  see attached screenshot
  Print Preview window doesn't have windows controls or a close button

  Launch Kate, from the menu File > Print Preview
  try to close the window, you can't because doh

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668053/+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 1676879] Re: Broken stack of modal dialogs

[Alan Griffiths]

There's no clear steps to reproduce, so I may have missed something. But
I can't get these symptoms with miral-app.

** Changed in: miral
   Status: New => Incomplete

** Changed in: miral (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Broken stack of modal dialogs

Status in Canonical System Image:
  New
Status in MirAL:
  Incomplete
Status in miral package in Ubuntu:
  Incomplete
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When multiple modal dialogs are stacked on top of each other, the
  topmost one is missing the window decoration (see
  https://imgur.com/0kVtLUB). Furthermore, after closing it, the middle
  modal dialog is hidden, preventing input from the main window.
  Launcher pips and context menu suggests the dialog is still there,
  albeit hidden. Results in a crash of the app after a few seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676879/+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 1685186] Re: Mir needs to be updated in 16.04 and the dependency tree trimmed

[Alan Griffiths]

** Description changed:

  Snap development using Mir has been using the "stable phone overlay" PPA
  which is both inconvenient and a legacy of the cancelled Unity8 project.
  
  It would greatly simplify things if Mir were updated in the Xenial
  archive.
  
  Mir has two categories of dependent project:
  
-   1 packages related to Unity8 (and unity-system-compositor)
-   2 toolkits and other "clients" of Mir
+   1 packages related to Unity8 (and unity-system-compositor)
+   2 toolkits and other "clients" of Mir
  
  We should remove the first category as it is not helpful to carry these
  in the LTS.
  
  The second category is dependent only on libmirclient which is ABI
  stable
+ 
+ notes:
+ 
+ A recursive search or rdependencies identifies the following packages in
+ category 1:
+ 
+ camera-app-autopilot
+ gallery-app-autopilot
+ indicator-network-autopilot
+ indicators-client
+ python3-mir-perf-framework
+ qtdeclarative5-qtmir-plugin
+ qtmir-android
+ qtmir-desktop
+ qtmir-tests
+ ubuntu-desktop-mir
+ ubuntu-experience-tests
+ ubuntu-pocket-desktop
+ ubuntu-push-autopilot
+ ubuntu-touch
+ ubuntu-touch-session
+ unity8
+ unity8-autopilot
+ unity8-desktop-session-mir
+ unity-scope-click-autopilot
+ unity-system-compositor
+ unity-system-compositor-autopilot

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

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

Title:
  Mir needs to be updated in 16.04 and the dependency tree trimmed

Status in mir package in Ubuntu:
  New

Bug description:
  Snap development using Mir has been using the "stable phone overlay"
  PPA which is both inconvenient and a legacy of the cancelled Unity8
  project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  Mir has two categories of dependent project:

    1 packages related to Unity8 (and unity-system-compositor)
    2 toolkits and other "clients" of Mir

  We should remove the first category as it is not helpful to carry
  these in the LTS.

  The second category is dependent only on libmirclient which is ABI
  stable

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  python3-mir-perf-framework
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1685186] [NEW] Mir needs to be updated in 16.04 and the dependency tree trimmed

[Alan Griffiths]

Public bug reported:

Snap development using Mir has been using the "stable phone overlay" PPA
which is both inconvenient and a legacy of the cancelled Unity8 project.

It would greatly simplify things if Mir were updated in the Xenial
archive.

Mir has two categories of dependent project:

  1 packages related to Unity8 (and unity-system-compositor)
  2 toolkits and other "clients" of Mir

We should remove the first category as it is not helpful to carry these
in the LTS.

The second category is dependent only on libmirclient which is ABI
stable

** 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/1685186

Title:
  Mir needs to be updated in 16.04 and the dependency tree trimmed

Status in mir package in Ubuntu:
  New

Bug description:
  Snap development using Mir has been using the "stable phone overlay"
  PPA which is both inconvenient and a legacy of the cancelled Unity8
  project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  Mir has two categories of dependent project:

1 packages related to Unity8 (and unity-system-compositor)
2 toolkits and other "clients" of Mir

  We should remove the first category as it is not helpful to carry
  these in the LTS.

  The second category is dependent only on libmirclient which is ABI
  stable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1685186] Re: Mir needs to be updated in 16.04 and the dependency tree trimmed

[Alan Griffiths]

** Description changed:

  Snap development using Mir has been using the "stable phone overlay" PPA
  which is both inconvenient and a legacy of the cancelled Unity8 project.
  
  It would greatly simplify things if Mir were updated in the Xenial
  archive.
  
  Mir has two categories of dependent project:
  
    1 packages related to Unity8 (and unity-system-compositor)
    2 toolkits and other "clients" of Mir
  
  We should remove the first category as it is not helpful to carry these
  in the LTS.
  
  The second category is dependent only on libmirclient which is ABI
  stable
  
  notes:
  
  A recursive search or rdependencies identifies the following packages in
  category 1:
  
  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
- python3-mir-perf-framework
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

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

Title:
  Mir needs to be updated in 16.04 and the dependency tree trimmed

Status in mir package in Ubuntu:
  New

Bug description:
  Snap development using Mir has been using the "stable phone overlay"
  PPA which is both inconvenient and a legacy of the cancelled Unity8
  project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  Mir has two categories of dependent project:

    1 packages related to Unity8 (and unity-system-compositor)
    2 toolkits and other "clients" of Mir

  We should remove the first category as it is not helpful to carry
  these in the LTS.

  The second category is dependent only on libmirclient which is ABI
  stable

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1685186] Re: Mir needs to be updated in 16.04 and the dependency tree trimmed

[Alan Griffiths]

** Description changed:

- Snap development using Mir has been using the "stable phone overlay" PPA
- which is both inconvenient and a legacy of the cancelled Unity8 project.
+ [Impact]
+ Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.
  
  It would greatly simplify things if Mir were updated in the Xenial
  archive.
  
+ [Test Case]
+ 
+ Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
+ against "Primary Ubuntu Archive" and deploy as described in
+ https://developer.ubuntu.com/en/snappy/guides/mir-snaps/
+ 
+ Expected: the client apps start and are visible on screen
+ Actual: the client don't apps start and are not visible on screen
+ 
+ [Regression Potential]
  Mir has two categories of dependent project:
  
    1 packages related to Unity8 (and unity-system-compositor)
    2 toolkits and other "clients" of Mir
  
- We should remove the first category as it is not helpful to carry these
- in the LTS.
+ We should remove the first category to avoid regressions as it is not
+ helpful to carry these in the LTS.
  
  The second category is dependent only on libmirclient which is ABI
- stable
+ stable.
+ 
+ The principle type of regression would be FTBFS where APIs have been
+ deprecated.
  
  notes:
  
  A recursive search or rdependencies identifies the following packages in
  category 1:
  
  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

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

Title:
  Mir needs to be updated in 16.04 and the dependency tree trimmed

Status in mir package in Ubuntu:
  New

Bug description:
  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  [Test Case]

  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

  Expected: the client apps start and are visible on screen
  Actual: the client don't apps start and are not visible on screen

  [Regression Potential]
  Mir has two categories of dependent project:

    1 packages related to Unity8 (and unity-system-compositor)
    2 toolkits and other "clients" of Mir

  We should remove the first category to avoid regressions as it is not
  helpful to carry these in the LTS.

  The second category is dependent only on libmirclient which is ABI
  stable.

  The principle type of regression would be FTBFS where APIs have been
  deprecated.

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Alan Griffiths]

It would be good to get a log with MIR_SERVER_WINDOW_MANAGEMENT_TRACE=on
as that ought to log the operation that propagates the exception.

Investigating this with miral-app: the server doesn't crash and nor does
the client.

Which is suggestive of a QtMir issue. However, the server fails to shut
down after this experiment which clearly can't be QtMir.

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in Mir 0.26 series:
  New
Status in MirAL:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Alan Griffiths]

Finally, mir_demo_server doesn't crash and exits successfully. (The
menus don't display correctly, they disappear as soon as they get focus.
But that's another issue.)

** Changed in: mir/0.26
   Status: New => Incomplete

** Changed in: mir
   Status: New => Incomplete

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in Mir 0.26 series:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+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 1640366] Re: [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA dropping_latency_is_closer_to_zero_than_one)

[Alan Griffiths]

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4242/consoleFull

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

Title:
  [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one (AKA
  dropping_latency_is_closer_to_zero_than_one)

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

Bug description:
  20:35:16 10: [ RUN  ] ClientLatency.dropping_latency_is_limited_to_one
  20:35:16 10: [2016-11-08 20:35:16.713374] mirserver: Starting
  20:35:16 10: [2016-11-08 20:35:16.713544] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.714686] mirserver: Using software cursor
  20:35:16 10: [2016-11-08 20:35:16.733467] mirserver: Initial display 
configuration:
  20:35:16 10: [2016-11-08 20:35:16.734637] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.734766] mirserver: Mir version 0.25.0
  20:35:18 10: 
/<>/mir-0.25.0+yakkety2807bzr3804/tests/acceptance-tests/test_latency.cpp:341:
 Failure
  20:35:18 10: Value of: max_latency
  20:35:18 10: Expected: is <= 1
  20:35:18 10:   Actual: 2 (of type unsigned int)
  20:35:18 10: [  debug   ] 98 frames sampled, averaging 1.0 frames latency
  20:35:18 10: [  debug   ]  0:  1  1  1  1  1  1  1  2  1  1
  20:35:18 10: [  debug   ] 10:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 20:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 30:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 40:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 50:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 60:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 70:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 80:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 90:  1  1  1  1  1  1  1  1
  20:35:18 10: [2016-11-08 20:35:18.575646] mirserver: Stopping
  20:35:18 10: [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one 
(1879 ms)

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2781/consoleFull]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1640366/+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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Alan Griffiths]

Another /possible/ cause of "'std::out_of_range' what(): map::at]" is
bug 1667645. That would imply that vlc is crashing and the server dies
in closing the session.

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in Mir 0.26 series:
  New
Status in MirAL:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Alan Griffiths]

MIR_SERVER_WINDOW_MANAGEMENT_TRACE shows that miral-shell doesn't
provoke "'std::out_of_range' what(): map::at]" - but that doesn't
explain the failure to exit. We either have two problems or two symptoms
of one underlying issue.

** Changed in: miral
   Status: New => Triaged

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in Mir 0.26 series:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+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 1671849] Re: Probing backends doesn't seem to work

[Alan Griffiths]

** Description changed:

  $ sudo apt install miral-examples
  $ miral-app
  
  Then in the Mir-on-X session:
  
- $ unset DISPLAY
- $ unset GDK_BACKEND
- $ gedit
+ $ unset DISPLAY
+ $ unset GDK_BACKEND
+ $ gedit
  
  Expect: can't connect to X, but can connect to Mir, so starts up
- Actual: hangs
+ Actual: only after around 25s does it starts

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

Title:
  Probing backends doesn't seem to work

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  $ sudo apt install miral-examples
  $ miral-app

  Then in the Mir-on-X session:

  $ unset DISPLAY
  $ unset GDK_BACKEND
  $ gedit

  Expect: can't connect to X, but can connect to Mir, so starts up
  Actual: only after around 25s does it starts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1671849/+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 1671849] [NEW] Probing backends doesn't seem to work

[Alan Griffiths]

Public bug reported:

$ sudo apt install miral-examples
$ miral-app

Then in the Mir-on-X session:

$ unset DISPLAY
$ unset GDK_BACKEND
$ gedit

Expect: can't connect to X, but can connect to Mir, so starts up
Actual: hangs

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Probing backends doesn't seem to work

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  $ sudo apt install miral-examples
  $ miral-app

  Then in the Mir-on-X session:

  $ unset DISPLAY
  $ unset GDK_BACKEND
  $ gedit

  Expect: can't connect to X, but can connect to Mir, so starts up
  Actual: hangs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1671849/+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 1672030] Re: kmines unable to drag the toolbar outside the window

[Alan Griffiths]

*** This bug is a duplicate of bug 1420334 ***
https://bugs.launchpad.net/bugs/1420334

Trying this out in miral-desktop you seem to be able to drag outside to
the right and lower, but only so far as the windows are adjacent.

This looks like the relative placement rules being applied. The
placement rules are such that the final position will *always* overlap
or be be contiguous with the parent window.

That is, the app is trying heroically to fake client-initiated drag
(c.f. bug 1420334) by doing relative placement. This approach is, by
design, doomed to failure.

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

Title:
  kmines unable to drag the toolbar outside the window

Status in Canonical System Image:
  New
Status in MirAL:
  New
Status in miral package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  kmines unable to drag the toolbar outside the window (you can on unity7) see 
attachement

  launch kmines without Xmir, right click on the toolbar, unlock, then
  try to drag it outside the window, it just sticks to the border but
  you cant't drag it farther away.see screenshot2

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672030/+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 1672030] Re: kmines unable to drag the toolbar outside the window

[Alan Griffiths]

*** This bug is a duplicate of bug 1420334 ***
https://bugs.launchpad.net/bugs/1420334

In summary:

/1/ mostly a duplicate of lp:1420334
/2/ kmines (or whatever library is fake client-initiated drag) needs updating 
to match

** This bug has been marked a duplicate of bug 1420334
   [enhancement] Missing client API for relative surface movement (e.g. 
dragging client-decorated windows)

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

Title:
  kmines unable to drag the toolbar outside the window

Status in Canonical System Image:
  New
Status in MirAL:
  New
Status in miral package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  kmines unable to drag the toolbar outside the window (you can on unity7) see 
attachement

  launch kmines without Xmir, right click on the toolbar, unlock, then
  try to drag it outside the window, it just sticks to the border but
  you cant't drag it farther away.see screenshot2

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672030/+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 1671047] Re: Starting rsibreak aborts in mir_create_menu_window_spec

[Alan Griffiths]

The probable reason for an abort in mir_create_menu_window_spec() is
that the connection argument is invalid.

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

Title:
  Starting rsibreak aborts in mir_create_menu_window_spec

Status in mir package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New

Bug description:
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
  #1  0x73a6f3ea in __GI_abort () at abort.c:89
  #2  0x7fffe5ea1378 in mir_create_menu_window_spec ()
 from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fffe61515a1 in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #4  0x7fffe615279d in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #5  0x7fffe613fe1b in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #6  0x74be60c9 in QWindowPrivate::create (this=0x55aff260, 
  recursive=recursive@entry=false) at kernel/qwindow.cpp:406
  #7  0x74be64db in QWindow::create (this=this@entry=0x55aff200)
  at kernel/qwindow.cpp:584
  #8  0x753ab585 in QWidgetPrivate::create_sys 
(this=this@entry=0x55b8cb30, 
  window=window@entry=0, initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1480
  #9  0x753aad7d in QWidget::create (this=0x55b91a60, 
window=window@entry=0, 
  initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1342
  #10 0x753ab1ae in QWidgetPrivate::createWinId (this=)
  at kernel/qwidget.cpp:2579
  #11 0x753ab1e9 in QWidget::winId (this=0x55b91a60) at 
kernel/qwidget.cpp:2547
  #12 0x5557f68c in ?? ()
  #13 0x5557fb7d in ?? ()
  #14 0x55568ddf in ?? ()
  #15 0x5557010b in ?? ()
  #16 0x555709e6 in ?? ()
  #17 0x55566955 in ?? ()
  #18 0x73a583f1 in __libc_start_main (main=0x55566230, argc=3, 
  argv=0x7fffe718, init=, fini=, 
  rtld_fini=, stack_end=0x7fffe708) at 
../csu/libc-start.c:291
  #19 0x55566a2a in _start ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1671047/+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 1656727] Re: Unity8 crashes and restarts when clicking on a menu [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

[Alan Griffiths]

No, the exception was thrown by libmiral code
[miral::BasicWindowManager::info_for()] and caused by synchronisation
issues in QtMir code that have been worked around.

Neither the libmiral nor the QtMir code in question is involved in any
of the mir-demos.

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

Title:
  Unity8 crashes and restarts when clicking on a menu [terminate called
  after throwing an instance of 'std::out_of_range' what():  map::at]

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Invalid
Status in MirAL:
  Invalid
Status in QtMir:
  Fix Released
Status in miral package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Unity8 crashes and restarts when clicking on a menu:

  terminate called after throwing an instance of 'std::out_of_range'
    what():  map::at

  Test case:
    1. Launch AisleRiot
    2. Click on a menu

  Expected: Menu opens
  Observed: Unity8 crashes and restarts every time

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170110.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  Date: Mon Jan 16 10:29:08 2017
  InstallationDate: Installed on 2016-11-03 (74 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656727/+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