[Bug 1507982] Re: [regression] OTA7 broke previously working app

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.20.0 ** Changed in: mir Status: Won't Fix => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1507982] Re: [regression] OTA7 broke previously working app

"Related branch", not a fix. ** Changed in: mir Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke previously working

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Hmm, actually bug 1498281 might be the cause here (even if libmirclient8 isn't actually in the click package). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke

[Bug 1507982] Re: [regression] OTA7 broke previously working app

We don't know how things will be done in the future, but I do know what Mir supports in the present. That is maintaining backward compatibility for the libmirclient9 client ABI. We have tests to ensure this. Mir does not support "bringing your own libmir*" on just the client side - you also have

[Bug 1507982] Re: [regression] OTA7 broke previously working app

1) talked to sturmflut, he's agreed to rebuild against libmirclient9 2) did a scan of store, so far only libmirclient9 is already being used by a couple of others -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1507982] Re: [regression] OTA7 broke previously working app

** Changed in: canonical-devices-system-image Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke previously working app To

[Bug 1507982] Re: [regression] OTA7 broke previously working app

** Changed in: mir Milestone: 0.18.0 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke previously working app To manage notifications about this bug

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Sorry. It appears in r2867 (which went into Mir 0.16.0) we broke the binary input event protocol (which is separate to protobuf). It's sufficiently broken that any Mir-0.15 or earlier client will reject and ignore all input messages it gets from v0.16 or newer servers.

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Annoyingly comment #9 may not work. If app developers rebuild with the latest Mir (0.17) then the slightly older Mir 0.16.0 in OTA7 will also reject their connections because they're now too new! This is again due to the overly strict protocol range checking introduced in r2893. -- You received

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Bisected and found the source of the input regression in 0.16.0. It came from: revno: 2867 [merge] author: Brandon Schaefer committer: Tarmac branch nick: development-branch timestamp: Thu 2015-08-20

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Comment #16 is misleading: There is only a "problem" if the app dynamically links against Mir-0.16 and attempts to run against a Mir-0.17 server. This should not happen as either: /1/ the matching server and client libraries are installed as part of the system (desktop, phone); or, /2/

[Bug 1507982] Re: [regression] OTA7 broke previously working app

In the pure snappy case there is no "system" Mir server. The Mir server needs to be included in the snap. @a - see comment #13 @b - we can't police every wrong way to do things[*]. [*] A (hypothetical) idiot could create a .deb that includes libmirclient.so.9 instead of depending on

[Bug 1507982] Re: [regression] OTA7 broke previously working app

The "matching" you mention may not happen in the snappy case. So there is a problem. In the pure snappy case, an app brings its own libmirclient and potentially its own libmirprotobuf and libmir*. So it is not a binary "match" for the server in question. And the app may be using Mir binaries that

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Please keep that tag. I use it for periodic quality analysis. ** Tags added: regression -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke previously working app

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Also bringing your own libmir* is not a mistake and not "foolish". It may be different to traditional Linux packaging, but it's the way snappy is designed for good reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Alan, I think it's likely in the future (if not already) that the Mir server/shell will be a separate snap to any app snaps. And certainly it's difficult to make anything completely foolproof, because fools are so ingenious. But we can build things that are more robust in the face of potential

[Bug 1507982] Re: [regression] OTA7 broke previously working app

** Branch linked: lp:~vanvugt/mir/improved-protocol-version-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke previously working app To manage

[Bug 1507982] Re: [regression] OTA7 broke previously working app

** Tags removed: regression ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke previously working app To manage notifications

[Bug 1507982] Re: [regression] OTA7 broke previously working app

the good news is, the promise of ABI compatibility will be maintained with libimrclient9, so a one time rebuild should fix it going fwd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title:

[Bug 1507982] Re: [regression] OTA7 broke previously working app

*not QML, I mean. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke previously working app To manage notifications about this bug go to:

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Hi Daniel o/ "Alternatively, we will need to ask all app developers to rebuild their packages with Mir 0.16.0 or later :(" i don't think there are many to ask, probably just sturmflut :>> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Digging further explains why this bug appears in OTA-7. It's because OTA-7 upgraded the Mir server from 0.15.1 to 0.16.0: https://wiki.ubuntu.com/Touch/ReleaseNotes/OTA-7 ** Changed in: mir Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mir Status: Triaged =>

[Bug 1507982] Re: [regression] OTA7 broke previously working app

** Also affects: mir/0.17 Importance: Undecided Status: New ** Also affects: mir/0.16 Importance: Undecided Status: New ** Changed in: mir/0.16 Importance: Undecided => High ** Changed in: mir/0.16 Status: New => Triaged ** Changed in: mir/0.17 Importance:

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Verified that removing the fix for bug 1486496 allows the client to start up and render. So that's the first hurdle. Unfortunately there's a second hurdle we may not be able to overcome -- that is with Mir 0.16.0 we broke input event/protocol compatibility. So 0.13.3 clients never receive input

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Perhaps if we want apps to keep working at least for the lifetime of UbuntuTouch-vivid, then we will need to wind back in OTA8 and keep Mir on the 0.15 series. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Actually comment #9 might be feasible. If we're only asking developers of native Mir apps (not Qt) to rebuild... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke

[Bug 1507982] Re: [regression] OTA7 broke previously working app

Alternatively, we will need to ask all app developers to rebuild their packages with Mir 0.16.0 or later :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke