** Changed in: canonical-devices-system-image
Milestone: 13 => backlog
--
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/1480654
Title:
[regression] Input focus delay
** Changed in: canonical-devices-system-image
Milestone: 12 => 13
--
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/1480654
Title:
[regression] Input focus delay after
I'm getting (b)
(https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1480654/comments/26)
as well on the
Nexus 4 (Mako)
particularly in the browser, which also leads to the fast scrolling bug:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1584965
--
You received this bug
I can confirm that (a) (b) and (c) in Oliver's comment [1] affects me.
I will add another:
d) unresponsive to power button press to wake up device. I sometimes
need to press a dozen or more times before the display will respond and
I'm presented with a login screen, or sometimes with the
well, it was never actually solved completely ... (as you can see by daniels
comment above)
i suspect there are still multipple bugs ...
there is:
a) the spread animation getting stuck a few pixels before the window
sits completely straight on the screen for a split second when you
switch apps
so shall we refine this bug or spawn a new one? sounds like this is now
beyond the original regression that was solved
--
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/1480654
FWIW, I can only reproduce this if either the resumed or the suspended
app is a webapp (or the browser). Perhaps this is related to the fact
that oxide runs in separate processes and we're sending sigstop/sigcont
to a chain of processes?
--
You received this bug notification because you are a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Milestone: None => 12
** Changed in: canonical-devices-system-image
Assignee:
Last time I tested this bug (and the Mir fix) the only remaining problem
for me was that one second tick of the Unity8 app switch animation
completing and then realigning the surface to fit the screen. Even that
delay doesn't happen reliably on demand for me...
I have just retested OTA-10.1 on
note that this behaviour is even more noticeable on turbo, seems the Mir
slowness is out of the way there, it takes between two and three seconds
for an app to accept input ... of which one second is a little "hang" of
the animation when flipping it into focus before it sits straight on the
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
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/1480654
Title:
[regression]
** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Tags added: performance
--
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/1480654
Title:
[regression] Input focus delay after switching app back into focus
since OTA5
** Changed in: mir
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/1480654
Title:
[regression] Input focus delay after switching
This bug was fixed in the package mir - 0.15.0+15.10.20150818-0ubuntu1
---
mir (0.15.0+15.10.20150818-0ubuntu1) wily; urgency=medium
[ Daniel van Vugt ]
* New upstream release 0.15.0 (https://launchpad.net/mir/+milestone/0.15.0)
- ABI summary: Only servers and graphics
** Branch linked: lp:ubuntu/wily-proposed/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/1480654
Title:
[regression] Input focus delay after switching app back into focus
Still not yet sure where the remaining delay is. Seems most likely in
Unity8 as that's where the spread animation happens.
Certainly the bug is fixed on the Mir side, but it's a very weird
coincidence that I found such similar regressions in Mir in the same
release, even if they're not the main
** Summary changed:
- [regression] Input focus delay after switching app back into focus since OTA5
(Mir 0.14)
+ [regression] Input focus delay after switching app back into focus since OTA5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Changed in: mir
Milestone: 0.16.0 = 0.15.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/1480654
Title:
[regression] Input focus delay after switching app back into
It also feels like the Unity8 window switcher is getting in the way.
Particularly when switching into the web browser, it takes half a second
or so to finish the app switch after the animation apparently completes.
You can notice this just slightly as a flicker of shadow (from the app
switcher)
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.16.0
** 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.
I'm somewhat confident the Mir fix does _not_ fix this bug entirely.
Just fixing all the related bugs on the Mir side so everything that's
left is not Mir :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
Tested the Mir fix on the full phone. The bug is not entirely solved, so
more work is indeed required looking to qtmir/unity8.
** Changed in: qtmir (Ubuntu)
Status: Opinion = New
** Changed in: unity8 (Ubuntu)
Status: Opinion = New
--
You received this bug notification because
It looks like QtMir/Unity8 is making the same mistake as Mir did. See
the Mir fix for a hint of what to 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/1480654
Title:
OK, the first bug 1481570 has a fix up for review. That's faulty end-of-
multifinger gesture detection. Probably doesn't apply to Unity, just the
Mir demo server..
The second bug (the Mir part of this one) seems to be a simple matter of
faulty end-of-gesture detection introduced in r2652. The
** Changed in: mir
Status: Triaged = In Progress
** Changed in: qtmir (Ubuntu)
Status: Invalid = Opinion
** Changed in: unity8 (Ubuntu)
Status: Invalid = Opinion
** Branch linked: lp:~vanvugt/mir/fix-1480654
--
You received this bug notification because you are a member
I need to point out that unity8 is not using much of Mir's input
dispatching focus logic, so please be certain the reported issue is
actually resolved with these mir fixes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir
marking as high.
also, @duflu - is it possible we can add an integration test in place to catch
future potential regression for this use case on ci ?
** Changed in: mir
Importance: Medium = High
** Changed in: mir (Ubuntu)
Importance: Medium = High
--
You received this bug notification
I disagree with High. Not only is the bug so minor that it went
unnoticed during the release of 0.14, but even now it took quite some
effort to discover. That's not High (which to me would imply it's a
potential release blocker). Not a major bug, IMHO.
--
You received this bug notification
Spoke too soon. It seems the bug reproducible using lp:mir is even worse
than the original bug seen with Unity. Using lp:mir you see all the
bugs...
1. Focus switch does not occur immediately. You need to start and finish a
new gesture before it takes effect (e.g. touch the screen).
2. When
Also made a minor mistake. Above where I mentioned r2590, that should be
r2591 where the first regression occurred. r2590 was actually the last
revision where everything worked properly...
revno: 2591 [merge]
author:
33 matches
Mail list logo
