** 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 unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1580774
Title:
mouse is getting stuck on a
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-landing-036
--
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/1580774
Title:
mouse is getting stuck
** Changed in: mir/0.23
Status: Fix Committed => Fix Released
--
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/1580774
Title:
mouse is getting stuck
** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005
--
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/1580774
Title:
mouse is
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
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/1580774
Title:
mir (0.22.1+16.04.20160516.2-0ubuntu1) xenial; urgency=medium
[ Andreas Pokorny ]
* New upstream release 0.22.1 (https://launchpad.net/mir/+milestone/0.22.1)
- ABI summary:
. No ABI changes in any libraries. Bugfix release only.
- Bugs fixed:
. [regression] Cursor stops at
** Branch unlinked: lp:mir/0.23
--
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/1580774
Title:
mouse is getting stuck on a phantom edge
Status in
Upstream release of Mir 0.22.1 with this fix completed. The fix is also
in some PPAs but not yet Ubuntu distro.
** Changed in: mir/0.22
Status: Fix Committed => Fix Released
** Changed in: mir (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
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/1580774
Title:
** Changed in: mir
Importance: Critical => High
** Changed in: mir
Status: In Progress => Fix Committed
** Changed in: mir/0.22
Importance: Undecided => Medium
** Changed in: mir/0.22
Importance: Medium => High
** Changed in: mir/0.23
Status: New => Fix Committed
**
** Branch unlinked: lp:mir
--
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/1580774
Title:
mouse is getting stuck on a phantom edge
Status in Canonical
** Branch linked: lp:mir
--
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/1580774
Title:
mouse is getting stuck on a phantom edge
Status in Canonical
** Changed in: qtmir (Ubuntu)
Status: Incomplete => Invalid
** Changed in: unity-system-compositor (Ubuntu)
Status: Incomplete => Invalid
** Changed in: mir (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
** Changed in: mir
Milestone: 0.22.1 => 0.24.0
** Also affects: mir/0.22
Importance: Undecided
Status: New
** Also affects: mir/0.23
Importance: Undecided
Status: New
** Changed in: mir/0.22
Status: New => Fix Committed
** Changed in: mir/0.22
Milestone: None
** Branch linked: lp:mir/0.23
--
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/1580774
Title:
mouse is getting stuck on a phantom edge
Status in Canonical
** Branch linked: lp:~andreas-pokorny/mir/fix-1580774
--
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/1580774
Title:
mouse is getting stuck on a phantom
** Changed in: mir
Importance: Undecided => Critical
--
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/1580774
Title:
mouse is getting stuck on a phantom
** Branch linked: lp:mir/0.22
--
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/1580774
Title:
mouse is getting stuck on a phantom edge
Status in Canonical
** Changed in: mir
Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)
** Changed in: mir
Status: Confirmed => In Progress
** Changed in: mir
Milestone: None => 0.22.1
** Changed in: mir
Milestone: 0.22.1 => 0.23.0
** Changed in: mir
Milestone: 0.23.0 => 0.22.1
It possible QtMir mis-using the Mir DisplayConfiguration API. Here is
our implementation:
http://bazaar.launchpad.net/~mir-
team/qtmir/trunk/view/head:/src/platforms/mirserver/mirdisplayconfigurationpolicy.cpp#L51
Let me know if something obviously wrong
--
You received this bug notification
** Changed in: mir
Status: New => Confirmed
** Changed in: qtmir (Ubuntu)
Status: Triaged => Incomplete
** Changed in: canonical-devices-system-image
Status: Triaged => In Progress
** Changed in: unity-system-compositor (Ubuntu)
Status: Confirmed => Incomplete
--
There appears to be a problem with the DisplayConfiguration::power_mode
flag in Mir.
I've added debug logging inside
ms::MediatingDisplayChanger::update_input_rectangles to print the
display configuration state. At startup, once unity8 starts, I see this
output from USC:
mi::DisplayInputRegion::confine(geom::Point& point) is responsible for
confining the cursor position inside the display rectangles.
void
ms::MediatingDisplayChanger::update_input_rectangles(mg::DisplayConfiguration
const& config)
is that which configures DisplayInputRegion with the display
Looking at Mir's SurfaceInputDispatcher::deliver_pointer,
auto target = find_target_surface(event_x_y);
printf("input event target %p, pos: (%d,%d)\n", target.get(),
event_x_y.x.as_int(), event_x_y.y.as_int());
prints this when hitting the barrier:
input event target 0x562470,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mir (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-system-compositor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Reopening Mir as while unity8 is responsible for its own cursor, if it
stops receiving events, it can't do much.
** Changed in: mir (Ubuntu)
Status: Invalid => New
** Changed in: mir
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
The suspicion is that USC/Mir are getting confused with pointer position
when we start applying scale.
--
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/1580774
Some debugging output from qtmir:
http://pastebin.ubuntu.com/16387328/
qtmir.mir.input: Received
MirPointerEvent(x=1175,y=915,relative_x=145.75,relative_y=0)
qtmir.mir.input: Received
MirPointerEvent(x=1243,y=915,relative_x=68.75,relative_y=0)
qtmir.mir.input: Unrecognized pointer event
The offending MP:
https://code.launchpad.net/~unity-team/qtmir/set-display-
config/+merge/286363
--
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/1580774
Title:
mouse is
The problem is introduced in:
qtmir_0.4.8+15.04.20160429.1
That is - DGU support in qtmir:
https://bazaar.launchpad.net/~mir-team/qtmir/trunk/revision/483
** Changed in: qtmir (Ubuntu)
Status: New => Triaged
** Changed in: qtmir (Ubuntu)
Assignee: Daniel d'Andrada (dandrader) =>
** Tags added: lt-blocker
--
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/1580774
Title:
mouse is getting stuck on a phantom edge
Status in Canonical System Image:
Triaged
I would say it's not related to rotation per se, since the "edge" moves
around, you're not always stuck at the same vertical line.
** Changed in: canonical-devices-system-image
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Invalid for Mir. Unity8 does its own mouse movement and boundaries
without using Mir's logic for that.
On a related note -- I found probably a very similar problem with touch:
bug 1502805
** Changed in: mir (Ubuntu)
Status: New => Invalid
** Also affects: mir
Importance: Undecided
** Description changed:
frieza build 101/rc-proposed
Steps:
1. connect mouse & keyboard to M10
2. launch xchat
3. go full screen
4. mouse move around across the entirety of the screen (landscape)
expected: mouse can range over entire screen
actual: gets stuck moving right
@dandrader this looks really familiar to that bug last year in london
that you and anpok worked on
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Milestone: None => 11
** Changed in:
36 matches
Mail list logo
