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

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.launchpa

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

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 membe

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

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 (SEGFAU

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

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_m

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

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

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

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 soft

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

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. htt

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

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

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

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 "

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

** 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 Te

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

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:

[Touch-packages] [Bug 1624407] Re: Closing an application doesn’t actually close it, it merely requests all its windows to be closed

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.ne

[Touch-packages] [Bug 1624407] Re: Closing an application doesn’t actually close it, it merely requests all its windows to be closed

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,

[Touch-packages] [Bug 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

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

[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.

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

[Touch-packages] [Bug 1626804] Re: Qt apps can't run under Mir [Gtk-WARNING **: cannot open display: ]

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 Canoni

[Touch-packages] [Bug 1626804] Re: Qt apps can't run under Mir [Gtk-WARNING **: cannot open display: ]

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: platf

[Touch-packages] [Bug 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

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

[Touch-packages] [Bug 1592932] Re: non-puritine Xapp causing unity8 using 100% of CPU

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

[Touch-packages] [Bug 1619616] Re: mir fails to build with protobuf3

** 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 bu

[Touch-packages] [Bug 1619616] Re: mir fails to build with protobuf3

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

[Touch-packages] [Bug 1619616] Re: mir fails to build with protobuf3

Only on powerpc64? I don't have one of those. -- 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:

[Touch-packages] [Bug 1619616] Re: mir fails to build with protobuf3

This is during the second dlopen(libmirprotobuf...) and in the initialization code. So it seems similar to the problems discussed in lp:1391976. But the workaround linked there is clearly no longer adequate. (gdb) bt #0 google::protobuf::internal::Mutex::Lock (this=this@entry=0x0) at google/prot

[Touch-packages] [Bug 1619616] Re: mir fails to build with protobuf3

't time to chase down the history. ** Changed in: mir (Ubuntu) Assignee: Alan Griffiths (alan-griffiths) => (unassigned) -- 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/b

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

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

[Touch-packages] [Bug 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

Again: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1476/consoleFull 10:15:01 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame 10:15:01 11: [2016-07-08 10:15:01.272873] mirserver: Starting 10:15:01 11: [2016-07-08 10:15:01

[Touch-packages] [Bug 1601810] Re: ftbfs in linking libmir-test-assist.a in xenial+overlay and yakkety+overlay

As we want to test libmir-test-assist.a for downstream use linking to the static library instead is not an acceptable solution. -- 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/160

[Touch-packages] [Bug 1601810] Re: ftbfs in linking libmir-test-assist.a in xenial+overlay and yakkety+overlay

That explanation sounds incomplete. libmirserver.so really shouldn't be mentioning gmock templates. And "target_link_libraries(mir_acceptance_tests" also mentions libmir- test-assist.a before libmirserver.so. But if the solution works... -- You received this bug notification because you are a m

[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.

** 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 mir in Ubuntu. https://bugs.launchpad.net/bugs/1447886 Title: mir_demo_server(_minimal): Window movement/resiz

[Touch-packages] [Bug 1592691] Re: mir fails to build in xenial

Looks like the missing "#include " was added in 0.23 -- 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/1592691 Title: mir fails to build in xenial Status in mir package in Ubunt

[Touch-packages] [Bug 1543594] Re: unity-system-compositor locked up in __libc_do_syscall()

the whole problem but needs to be eliminated. ** Branch linked: lp:~alan-griffiths/mir/fix- SystemCompositorWindowManager-remove_surface ** Also affects: mir Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages

[Touch-packages] [Bug 1543594] Re: unity-system-compositor locked up in __libc_do_syscall()

** Branch unlinked: lp:~alan-griffiths/mir/fix- SystemCompositorWindowManager-remove_surface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1543594 Title

[Touch-packages] [Bug 1240909] Re: [performance] Restore support for better-than-triple buffering by default.

** Changed in: mir Milestone: 0.20.0 => 0.21.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/1240909 Title: [performance] Restore support for better-than-triple buffering

[Touch-packages] [Bug 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working

** Changed in: mir Milestone: 0.20.0 => 0.21.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/1262116 Title: Nested servers prevent overlays or fullscreen bypass from work

[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)

** Changed in: mir Milestone: 0.20.0 => 0.21.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/1544878 Title: Mir servers crash if I press the side mouse button (thumb) St

[Touch-packages] [Bug 1536662] Re: [regression] Black screen: Mir hangs and then crashes on login due to reading from /dev/random

** Changed in: mir Milestone: 0.20.0 => 0.21.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/1536662 Title: [regression] Black screen: Mir hangs and then crashes on login

[Touch-packages] [Bug 1528384] Re: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_

Fix landed in 0.19.2 ** Changed in: mir Status: In Progress => Fix Committed -- 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/1528384 Title: unity-system-compositor cras

[Touch-packages] [Bug 1377774] Re: unity-system-compositor crashed with SIGABRT in ~InputReaderThread

Too old to care about ** Changed in: mir Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/134 Title: unity-system-compos

[Touch-packages] [Bug 1515558] Re: [regression] Nested servers on mesa-kms select wrong (dummy) guest platform

As discussed above, the nested server doesn't have enough information to select the correct drivers and more work is needed on supplying this from the host before this can be closed. ** Changed in: mir Status: Fix Committed => Triaged ** Changed in: mir/0.18 Status: Fix Released =>

[Touch-packages] [Bug 1515558] Re: [regression] Nested servers on mesa-kms select wrong (dummy) guest platform

** Changed in: mir/0.18 Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1515558 Title: [regression] Nested servers on mesa-kms select wrong

[Touch-packages] [Bug 1515558] Re: [regression] Nested servers on mesa-kms select wrong (dummy) guest platform

Having a (hopefully) temporary workaround that handles some common scenarios isn't a fix. Here (copied from the email discussion) are some notes about resolving this: as discussed following today's standup the problems we face involves a number of issues beyond the probing logic. There are three

[Touch-packages] [Bug 1515558] Re: [regression] Nested servers on mesa-kms select wrong (dummy) guest platform

** Changed in: mir Status: Triaged => In Progress ** Changed in: mir Assignee: Mir development team (mir-team) => Alan Griffiths (alan-griffiths) ** Summary changed: - [regression] Nested servers on mesa-kms select wrong (dummy) guest platform + [regression] Nested serve

[Touch-packages] [Bug 1488863] Re: nexus4 & nexus7 hotplug survival

** Changed in: mir Status: Incomplete => 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/1488863 Title: nexus4 & nexus7 hotplug survival Status in canonica

[Touch-packages] [Bug 1575192] Re: Mir-on-X11 breaks mir_proving_server resize logic

** This bug is no longer a duplicate of bug 1575765 Mir-on-X11 doesn't pass Alt+button drag to 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/1575192 Title: Mir-on-X11

[Touch-packages] [Bug 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1015/consoleFull ... 22:06:59 11: Expected: to be called between 50 and 150 times 22:06:59 11: Actual: called 167 times - over-saturated and active 22:06:59 11: /��BUILDDIR��/mir-0.23.0+xeni

[Touch-packages] [Bug 1571556] Re: Some GTK windows lose interaction

MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input events being correctly received on the client side. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: mir Status: New => Invalid ** Changed in: mir Status: Invalid => Triaged ** Descrip

[Touch-packages] [Bug 1445543] Re: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

** Description changed: 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 an

[Touch-packages] [Bug 1571556] Re: Some GTK windows lose interaction

*** This bug is a duplicate of bug 1445543 *** https://bugs.launchpad.net/bugs/1445543 ** This bug has been marked a duplicate of bug 1445543 Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze -- You received this bug notification because you are a member of Ubuntu Tou

[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.

I've not yet investigated to determine when this was fixed, but I can't reproduce an "unrecoverable" state using 0.21 (or the current trunk). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpa

[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.

Was also fixed in 0.18. ** Changed in: mir (Ubuntu) Status: Triaged => Fix Released ** Changed in: mir Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs

[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.

OK, I get what you're saying now. OTOH I do think there's been a significant improvement at some point in the past: in that there's no "unrecoverable state". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. http

[Touch-packages] [Bug 1575192] [NEW] Mir-on-X11 breaks mir_proving_server resize logic

Public bug reported: $ mir_proving_server& $ mir_demo_client_egltriangle Alt+drag with middle mouse button Expect: client is resized Actual: Nothing happens A bit of investigation shows that the mouse-button-down event isn't being received. (The movement event is received.) (The problem doesn'

[Touch-packages] [Bug 1535297] Re: Unity8 crashes on logout with "Error in `unity8': double free or corruption" called from libprotobuf.so.9, called from libprotobuf-lite.so.9

I suspect the right solution is to fix the approach taken in Mesa to detecting Mir: All the above modules should be loaded with RTLD_LOCAL. As far as I can tell they are so they shouldn't interact. However, Mir's mesa.so.X client platform module reloads itself with RTLD_GLOBAL so that Mesa can fi

[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.

** Also affects: miral Importance: Undecided Status: New ** Changed in: miral Status: New => Confirmed ** Changed in: miral Importance: Undecided => Medium ** Changed in: miral Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Branch linked:

[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.

** Branch linked: lp:~alan-griffiths/mir/fix-1447886 -- 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

[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.

** Changed in: mir Milestone: None => 0.23.0 ** Changed in: mir Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: mir Status: Triaged => In Progress ** Changed in: miral Status: Confirmed => In Progress -- You received this bug

[Touch-packages] [Bug 1575192] Re: Mir-on-X11 breaks mir_proving_server resize logic

The middle button is 2 (correctly mapped to mir_pointer_button_tertiary). -- 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/1575192 Title: Mir-on-X11 breaks mir_proving_server re

[Touch-packages] [Bug 1575192] Re: Mir-on-X11 breaks mir_proving_server resize logic

OK, it (sort of) makes sense that compiz takes the Alt-middle down event but passes on the drag. And that explains everything except it working for Cemil. (Is he using Unity7?) ** Branch linked: lp:~cemil-azizoglu/mir/fix-1575765 ** Changed in: mir Status: New => Confirmed ** Changed in:

[Touch-packages] [Bug 1576260] Re: Can't VT switch from mir_demo_server

I've not encountered this problem - VT switching works for me (on desktop and a couple of Thinkpad laptops). Is this specific to certain devices? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.lau

[Touch-packages] [Bug 1576260] Re: Can't VT switch from mir_demo_server

I've not encountered this problem - VT switching works for me (on desktop and a couple of Thinkpad laptops). Is this specific to certain devices? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.lau

[Touch-packages] [Bug 1511538] Re: 1/2 screen on external monitor

This sounds like the cumulative effect of a number of Mir bugs in the display configuration handling that resulted in the surfaces composited by a nested server appearing in the wrong place. It is plausible that the fixes landed up to -r3056 have resolved this (they certainly address Mir issues in

[Touch-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly

Can't reproduce on wily -- 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/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mi

[Touch-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly

Please clarify how to reproduce: If run from a terminal window we don't need any of the "sudo's" as we simply load up the Mir-on-X stack and connect via $DISPLAY. In any case, sudo should only be require for the host mir server when using kms (--arw-file will make the endpoint accessible to all).

[Touch-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly

Missing information to aid reproducing: 1. Are you running from a terminal, a VT or a ssh session? 1.1. AFAICS the commands as given in the instructions can only work from a terminal session, but Mir-on-X doesn't *need* "sudo", so what happens without "sudo"? 2. Are you running a local build?

[Touch-packages] [Bug 1488431] Re: Clients fail to create surfaces when using Mir server in compositor mode

The system-compositor window manager expects clients to create fullscreen windows associated with outputs. For example: VT1: sudo bin/mir_demo_server --window-manager system-compositor --arw-file VT2: bin/mir_demo_server --host /tmp/mir_socket VT3: bin/mir_demo_client_eglplasma Which works for m

[Touch-packages] [Bug 1488431] Re: Clients fail to create surfaces when using Mir server in compositor mode

Ah! MIR_CLIENT_PLATFORM_PATH=/home/alan/local/lib/mir/client-platform bin /unity-system-compositor-spinner -m /tmp/mir_socket works. (But spinner eats the helpful error message.) ** Changed in: mir (Ubuntu) Status: Confirmed => Invalid ** Changed in: mir (Ubuntu) Importance: Critical

[Touch-packages] [Bug 1535397] Re: Implement support for QWindow::visibility set to Automatic

There's slightly more involved than adding mir_surface_state_automatic as the surface state will change to maximized/restored etc. but there needs to be a persistent "automatic" attribute as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, whic

[Touch-packages] [Bug 1535397] Re: Implement support for QWindow::visibility set to Automatic

Adding qtmir as that needs to handle the Window Management metadata Saviq alludes to. ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: qtmir Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded pa

[Touch-packages] [Bug 1535397] Re: [enhancement] Implement support for QWindow::visibility set to Automatic

Having discussed this a few times I've reached the following conclusion: "automatic" is not a MirSurfaceState - if it were a MirSurfaceState, then it would be correct to return it from get_state() and for it to be implemented as "looking the same as fullscreen or restored". By comparison, "restor

[Touch-packages] [Bug 1535397] Re: [enhancement] Implement support for QWindow::visibility set to Automatic

To clarify, the desired behaviour /can/ be implemented client-side with the existing Mir API. This would require implementation code in each toolkit (or client). The limitation of this approach being that the shell isn't required to respect set_state() requests issued by the client. We /can/ also

[Touch-packages] [Bug 1535397] Re: [enhancement] Implement support for QWindow::visibility set to Automatic

As a note to Chris's comment #9: While what is being asked for is state associated with a surface, it isn't a distinct "surface state". If modelled as surface state it requires at least new two states mir_surface_state_automatic_restored and mir_surface_state_automatic_fullscreen (and possibly mi

[Touch-packages] [Bug 1535397] Re: [enhancement] Implement support for QWindow::visibility set to Automatic

My concerns are threefold: 1. there is no good name for this feature: "automatic" doesn't capture specific behaviour; 2. I don't understand why this specific use case needs any special support; and, 3. what advantage is expected from Mir being involved? As discussed above: Clients can implement

[Touch-packages] [Bug 1535397] Re: [enhancement] Implement support for QWindow::visibility set to Automatic

** Branch linked: lp:~alan-griffiths/mir/add- mir_surface_spec_set_shell_chrome -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1535397 Title: [enhancement] Implement

[Touch-packages] [Bug 1528384] Re: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_

I don't think MultiThreadedCompositor::start()/stop() locking is the real issue. They are only called by MirScreen's "*_l()" functions which (if I understand the convention correctly) should only be invoked under lock of its mutex. However, usc::MirScreen::power_off_alarm_notification() calls con

[Touch-packages] [Bug 1528384] Re: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_

Actually, I've misunderstood. power_off_alarm_notification() is only called from MirScreen::PowerOffLockableCallback - which acquires the lock. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launch

[Touch-packages] [Bug 1528384] Re: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_

Digging into the code (without being able to reproduce) the likeliest cause seems to be incorrect error handling in mir::compositor::CompositingFunctor::operator()(). In Mir 0.18 this function can plausibly terminate via an exception before setting the promise (on line 116) - it has a catch block,

[Touch-packages] [Bug 1532607] Re: Phone not usable while a call comes in - followed by "restart"

Agreed, this is the behaviour I'd expect lp:1528384 to exhibit. Occum's razor suggests we don't needlessly look for another explanation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https:

[Touch-packages] [Bug 1528384] Re: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_

** Branch linked: lp:~alan-griffiths/mir/better-error-reporting-in- MultiThreadedCompositor-start ** Changed in: mir Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: unity-system-compositor Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Chan

[Touch-packages] [Bug 1528384] Re: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_

** Branch linked: lp:~alan-griffiths/unity-system-compositor/report- warnings-instead-of-crashing -- 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/1528384 Title: unity-system

[Touch-packages] [Bug 1528384] Re: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_

Note: lp:~alan-griffiths/mir/better-error-reporting-in-MultiThreadedCompositor-start lp:~alan-griffiths/unity-system-compositor/report-warnings-instead-of-crashing These linked branches may not be a full solution but: 1. they log the underlying problem (which is "eaten" by

[Touch-packages] [Bug 1538659] Re: unity8-desktop-session-mir is missing mir-platform-* and mir-client-* dependencies

I would guess that the correct dependency would be mir-graphics-drivers- desktop. Mir itself doesn't depend on either mir-graphics-drivers-desktop nor mir-graphics-drivers-android to avoid pulling both. -- You received this bug notification because you are a member of Ubuntu Touch seeded package

[Touch-packages] [Bug 1526658] Re: Mir clients (including Unity8 itself) crash in XGetXCBConnection() if multiple versions of mir-client-platform-mesa are installed.

** Branch linked: lp:~alan-griffiths/mir/fix-1526658 -- 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/1526658 Title: Mir clients (including Unity8 itself) crash in

[Touch-packages] [Bug 1475994] Re: mir fails to build with GCC 5

** Changed in: mir 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/1475994 Title: mir fails to build with GC

[Touch-packages] [Bug 1475994] Re: mir fails to build with GCC 5

** Branch linked: lp:~alan-griffiths/mir/fix-1475994-g++-5 -- 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/1475994 Title: mir fails to build with GCC 5 Status in Mir: New

[Touch-packages] [Bug 1475994] Re: mir fails to build with GCC 5

** Branch linked: lp:~alan-griffiths/mir/fix-1475994-g++-5-backport -- 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/1475994 Title: mir fails to build with GCC 5 Status in Mir

[Touch-packages] [Bug 1475994] Re: mir fails to build with GCC 5

** Changed in: mir Status: New => In Progress -- 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/1475994 Title: mir fails to build with GCC 5 Status in Mir: In Progress

[Touch-packages] [Bug 1475994] Re: mir fails to build with GCC 5

** Changed in: mir/0.14 Status: In Progress => Fix Committed ** Changed in: mir/0.14 Milestone: 0.14.1 => 0.14.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/147599

[Touch-packages] [Bug 1376324] Re: /usr/sbin/unity-system-compositor:*** Error in `unity-system-compositor': free(): invalid pointer: ADDR ***

: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: mir Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1376324 Title: /us

[Touch-packages] [Bug 1376324] Re: /usr/sbin/unity-system-compositor:*** Error in `unity-system-compositor': free(): invalid pointer: ADDR ***

I've not been able to reproduce yet[1], but looking at the code I can't see anything that prevents a buffer stream being owned by the compositor (for composition) after the corresponding Surface and Session have been closed. If that then attempts to "complete" a buffer swap then we would see the ab

[Touch-packages] [Bug 1376324] Re: /usr/sbin/unity-system-compositor:*** Error in `unity-system-compositor': free(): invalid pointer: ADDR ***

Our experience clearly differs. I find that it is often the second free of a block that triggers the error. As the occasions when the free list has previously been corrupted take disproportionately more time to solve I'm hoping this is an "easy" one. ;) -- You received this bug notification beca

[Touch-packages] [Bug 1376324] Re: /usr/sbin/unity-system-compositor:*** Error in `unity-system-compositor': free(): invalid pointer: ADDR ***

** Branch linked: lp:~alan-griffiths/mir/fix-1376324 ** Changed in: mir Status: Incomplete => In Progress -- 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/1376324 Ti

[Touch-packages] [Bug 1398088] Re: ClientLibraryErrorsDeathTest is dumping core, causing spurious problem reports (like this one)

The abort in this (and related) tests is correct: it is the behaviour being tested for. The error is in such tests being reported by Ubuntu Error Tracker - is there any way to flag executables as "do not error track"? -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1342694] Re: qmlscene crashed with SIGSEGV in _M_release() on quit

In Progress ** 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/1342694 Title: qm

[Touch-packages] [Bug 1342694] Re: qmlscene crashed with SIGSEGV in _M_release() on quit

** Branch linked: lp:~mir-team/mir/enable-late-release-0.5-backport -- 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/1342694 Title: qmlscene crashed with SIGSEGV in _M_release()

[Touch-packages] [Bug 1297100] Re: Installing mir-demos also unexpectedly installs *-dev packages

Oops - is the cause the "Recommends: mir-doc"? If that is installed then so are the -dev packages. -- 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/1297100 Title: Installing mir

[Touch-packages] [Bug 1297100] Re: Installing mir-demos also unexpectedly installs *-dev packages

This looks like a likely cause: $ cat libmirclient-dev.install usr/include/mirclient usr/lib/*/pkgconfig/mirclient.pc usr/lib/*/libmirclient.so -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launc

[Touch-packages] [Bug 1297100] Re: Installing mir-demos also unexpectedly installs *-dev packages

** Changed in: mir Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: mir Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu.

<    1   2   3   4