** No longer affects: qtmir
--
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/1488417
Title:
nexus4 window mode mouse motion bounded incorrectly with external
monitor
Status i
seems corrected in latest image
channel: ubuntu-touch/rc-proposed/ubuntu-pd
version version: 54
version ubuntu: 20151026
version device: 20150911
version custom: 20150929-2-vivid
** Changed in: canonical-pocket-desktop
Status: In Progress => Fix Released
** Changed in: mir (Ubuntu)
Actually input still gets in a pretty sorry state when an external monitor is
connected.
But waiting for silo 22 to land before raising the issue to mir guys. Will make
for easier debugging and communication.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
this is fixed in silo 22 which should land soon
** Branch linked: lp:~unity-team/unity8/mousePointer
** Changed in: qtmir (Ubuntu)
Status: Confirmed => In Progress
** Changed in: canonical-pocket-desktop
Status: New => In Progress
** Changed in: canonical-pocket-desktop
Assig
I've found the same kind of bug, but no external monitor required -->
bug 1502805.
--
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/1488417
Title:
nexus4 window mode mouse motio
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.
https://bugs.launchpad.net/bug
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 mir in Ubuntu.
https://bugs.launchpad.net/bugs/
I'm fairly sure this bug is invalid for Mir per comment #20. Although
pointer grabs in Mir would help to solve the problem, that's really an
enhancement for later. In comment #21 I was just being cautious in case
anyone can correct me.
--
You received this bug notification because you are a membe
Actually there might still be a related bug in Mir. Seems unlikely, but
not really sure yet.
** Changed in: mir
Status: Invalid => New
** Changed in: mir (Ubuntu)
Status: Invalid => New
** Also affects: qtmir
Importance: Undecided
Status: New
--
You received this bug no
Comment #18 kind of makes sense.
In trying to replicate the bug using just Mir demos I found one way to
do it: Have a client (which in our case is Unity8 itself) that fails to
resize to cover all displays. As it fails to resize to cover all
displays, the client (Unity8 shell) will fail to get moti
yep, like daniel said we'll lower priority on this since qtmir
multimonitor branch is getting cleaned up and landed.
** Changed in: canonical-pocket-desktop
Importance: Critical => Medium
** Changed in: mir
Importance: High => Medium
** Changed in: mir (Ubuntu)
Importance: High => Mediu
Now we know what the problem is, and it will be gone once qtmir+unity8
start using one surface per display instead of cloning displays as it's
currently happening.
** Changed in: mir (Ubuntu)
Status: In Progress => New
** Changed in: qtmir (Ubuntu)
Status: Invalid => New
--
You re
** Description changed:
when connecting a monitor to the Nexus4 during windowed mode, the device
is put into landscape mode. the mouse motion appears to not have
followed the orientation and is bounded by roughly portrait width
instead of landscape width
+
+
+ The problem is that when un
** Changed in: mir (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
** Changed in: mir (Ubuntu)
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
@duflu
There you go:
http://paste.ubuntu.com/12213056/
When you hit the invisible boundary on the external monitor nothing
comes up in the log. Neither from mir nor qtmir. Happy now? :)
** Changed in: mir (Ubuntu)
Status: Incomplete => New
** Changed in: mir
Status: Incomplete =>
Dropped back to High (https://wiki.ubuntu.com/Bugs/Importance)
** Summary changed:
- nexus4 window mode mouse motion bounded incorrectly
+ nexus4 window mode mouse motion bounded incorrectly with external monitor
** Tags added: android multimonitor
--
You received this bug notification because
Can you double check using the report in comment #10? It's still
theoretically a small possibility that the bug lies in unity8 till
that's confirmed.
** Changed in: mir
Status: New => Incomplete
** Changed in: mir (Ubuntu)
Status: New => Incomplete
** Changed in: mir
Importance:
To get the debug output you've to make sure your qtmir is at least lp
:~unity-team/qtmir/silo0 revision 369 ("QtEventFeeder: log the pointer
events it gets from Mir")
** Changed in: qtmir (Ubuntu)
Status: In Progress => Invalid
** Changed in: mir
Status: Incomplete => Confirmed
**
Mir keeps sending pointer events after it hits a boundary only if you're
using the primary display. If you connect and external monitor, it
doesn't work like that anymore.
Steps to reproduce:
- Flash an N7 and install silo0 in it.
- Add "initctl set-env --global QT_LOGGING_RULES=qtmir.mir.input.de
I will investigate the claim that qtmir is still receiving relative
mouse movement even when you see the cursor hitting an invisible
boundary
** No longer affects: unity8 (Ubuntu)
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtmir (Ubuntu)
Assig
Please try comment #10 as that should help us to identify if the problem
is on the Mir side or Unity8.
** Changed in: canonical-pocket-desktop
Status: New => Incomplete
** Changed in: unity8 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
** Changed in: canonical-pocket-desktop
Importance: Undecided => Critical
** Changed in: unity8 (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.laun
** Also affects: qtmir
Importance: Undecided
Status: New
** Changed in: qtmir
Status: New => Opinion
** Also affects: canonical-pocket-desktop
Importance: Undecided
Status: New
** No longer affects: qtmir
** No longer affects: qtmir (Ubuntu)
--
You received this bug
Please try this:
restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log
tail -f ~/.cache/upstart/unity8.log
and see if Unity8 actually is still receiving input events with relative
data (dx, dy) when the problem occurs.
--
You received this bug notification because you are a member of Ubuntu
My mistake. Not a Mir bug. I was looking at
MIR_CLIENT_INPUT_RECEIVER_REPORT=log and expecting the client to receive
motion events after the cursor had left the window, which was wrong.
Using a more correct test where the gesture starts in the app window
(click but don't release), then you can see
Aha! Confirmed on arale with a USB mouse and mir-demos.
Relative motion events usually work continuously, and come in even after
the cursor hits the screen boundary. However Mir stops sending relative
motion events if you've rotated the screen (touch+volume key in
mir_proving_server) and the curso
Oh... is there another Mir bug too? Is Mir failing to provide continuous
relative motion data without hitting invisible bounds?
** Changed in: mir (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
OK, I can see one problem already. While Unity8 does its own screen
rotation without notifying Mir, Mir cannot do anything to help it update
the cursor bounds. Because Unity8 is not telling Mir that the display
has rotated, Mir will keep the old cursor bounds...
Portrait:
$ mirout /var/run/mir_so
Yeah there may be some common things to fix with bug 1313610 but
possibly some things different 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/1488417
Title:
nexus4 wind
more information i should add - this is not seen on nexus7, which in windowed
mode is always in landscape and doesnt rotate
on nexus4, if a second monitor is not attached, this is not seen, even in
windowed mode (which rotates to landscape, e.g. just connect a bt mouse will
put into windowed mod
unduping for the moment, after some discussion with anpok, while this is
similar we're not totally convinced it's the same
@duflu also, your are welcome please try this - specifically notice that if you
move the mouse completely horizontal, the mouse will stick in a position that
is inconsistent
** This bug is no longer a duplicate of bug 1313610
Cursor gets stranded and can't move between non-contiguous monitors
(especially after rotation)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bug
*** This bug is a duplicate of bug 1313610 ***
https://bugs.launchpad.net/bugs/1313610
Yeah pretty sure it's the same as bug 1313610. We've never updated our
cursor bounds correctly on rotation...
** This bug has been marked a duplicate of bug 1313610
Cursor gets stranded and can't move be
Might be bug 1313610, or closely related.
** Tags added: cursor
--
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/1488417
Title:
nexus4 window mode mouse motion bounded incorrec
34 matches
Mail list logo
