[Touch-packages] [Bug 1502200] Re: Cursor becomes visible by itself when an external monitor is connected
This bug was fixed in the package mir - 0.17.0+15.10.20151008.2-0ubuntu1
---
mir (0.17.0+15.10.20151008.2-0ubuntu1) wily; urgency=medium
[ Alexandros Frantzis ]
* New upstream release 0.17.0 (https://launchpad.net/mir/+milestone/0.17.0)
- ABI summary: Only servers and graphics drivers need rebuilding;
. Mirclient ABI unchanged at 9
. Mirserver ABI bumped to 35
. Mircommon ABI unchanged at 5
. Mirplatform ABI bumped to 11
. Mirprotobuf ABI bumped to 3
. Mirplatformgraphics ABI bumped to 6
. Mirclientplatform ABI unchanged at 3
- Enhancements:
. Introduce libmircookie, a simple mechanism for a group of cooperating
processes to hand out and verify difficult-to-forge timestamps to
untrusted 3rd parties.
. More refactorings to support renderers other than GL.
. Add MirBlob to the client API - a tool for serializing and
deserializing data.
. Introduce a libinput based input platform, not yet used by default.
. Provide a mechanism for the shell to send events on surface
construction.
. Provide mir::shell::DisplayConfigurationController allowing shells
to correctly change the display configuration, notifying clients
as appropriate.
. New DSO versioning guide.
. Send events pertaining to the output a surface is currently on (dpi,
form factor, scale) to clients.
- Bug fixes:
. [enhancement] XMir specific documentation should live in its own
subsection (LP: #1200114)
. Nested servers need cursor support (LP: #1289072)
. Mir cursor is missing/invisible until the client sets it multiple
times (LP: #1308133)
. [regression] Fullscreen software surfaces (like Xmir -sw) can crash
the Mir server (LP: #1493721)
. [usc] Mir gives up and shuts down due to input with multimonitor qtmir
(std::exception::what: Failure sending input event) (LP: #1496069)
. Mouse cursor disappears upon entering the surface area of a nested
client (LP: #1496849)
. [android] input is not dispatched when attaching an external monitor
(LP: #1498045)
. [android] input coordinates are scaled incorrectly when an external
display is connected (LP: #1498540)
. [android] std::exception::what: error during hwc set() when unplugging
external monitor (LP: #1498550)
. tests do not compile without precompiled headers (LP: #1498829)
. [android] std::exception::what: Failed to monitor fd: Operation not
permitted when unplugging external display in a nested configuration
(LP: #1499042)
. Mir suddenly no longer builds since 'mesa (11.0.0-1ubuntu1) wily':
/usr/include/EGL/eglplatform.h:100:35: fatal error:
android/native_window.h: No such file or directory (LP: #1499134)
. [android] various crashes when unplugging external display on a
nested configuration (LP: #1501927)
. Cursor becomes visible by itself when an external monitor is connected
(LP: #1502200)
. mesa FTBFS due to missing Requires in mirclient (LP: #1503450)
[ CI Train Bot ]
* New rebuild forced.
-- Alexandros Frantzis Thu, 08 Oct
2015 16:12:19 +
** Changed in: mir (Ubuntu)
Status: New => 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/1502200
Title:
Cursor becomes visible by itself when an external monitor is connected
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
Fix Released
Bug description:
Steps to reproduce:
--
1 - Build and install the following branches on a laptop:
lp:~dandrader/unity-api/mousePointer
lp:~dandrader/qtmir/multimonitorNext
lp:~dandrader/unity8/externalMonitor
2 - In lightdm greeter, log into a unity8 session
3 - connect an external monitor
Expected outcome:
-
You see only one cursor (the one unity8 draws)
Actual outcome:
-
You see two cursors: the unity8 one and the mir one.
Comments:
--
In qtmir's mir::Server class, this is the snippet it uses to hide the
mir cursor:
"""
add_init_callback([this](){ the_cursor()->hide(); });
"""
The mir cursor remains visible also after you unplug the external
monitor.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1502200/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1502200] Re: Cursor becomes visible by itself when an external monitor is connected
** 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/1502200
Title:
Cursor becomes visible by itself when an external monitor is connected
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
New
Bug description:
Steps to reproduce:
--
1 - Build and install the following branches on a laptop:
lp:~dandrader/unity-api/mousePointer
lp:~dandrader/qtmir/multimonitorNext
lp:~dandrader/unity8/externalMonitor
2 - In lightdm greeter, log into a unity8 session
3 - connect an external monitor
Expected outcome:
-
You see only one cursor (the one unity8 draws)
Actual outcome:
-
You see two cursors: the unity8 one and the mir one.
Comments:
--
In qtmir's mir::Server class, this is the snippet it uses to hide the
mir cursor:
"""
add_init_callback([this](){ the_cursor()->hide(); });
"""
The mir cursor remains visible also after you unplug the external
monitor.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1502200/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1502200] Re: Cursor becomes visible by itself when an external monitor is connected
** 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/1502200
Title:
Cursor becomes visible by itself when an external monitor is connected
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
New
Bug description:
Steps to reproduce:
--
1 - Build and install the following branches on a laptop:
lp:~dandrader/unity-api/mousePointer
lp:~dandrader/qtmir/multimonitorNext
lp:~dandrader/unity8/externalMonitor
2 - In lightdm greeter, log into a unity8 session
3 - connect an external monitor
Expected outcome:
-
You see only one cursor (the one unity8 draws)
Actual outcome:
-
You see two cursors: the unity8 one and the mir one.
Comments:
--
In qtmir's mir::Server class, this is the snippet it uses to hide the
mir cursor:
"""
add_init_callback([this](){ the_cursor()->hide(); });
"""
The mir cursor remains visible also after you unplug the external
monitor.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1502200/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1502200] Re: Cursor becomes visible by itself when an external monitor is connected
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
--
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/1502200
Title:
Cursor becomes visible by itself when an external monitor is connected
Status in Mir:
Fix Committed
Status in mir package in Ubuntu:
New
Bug description:
Steps to reproduce:
--
1 - Build and install the following branches on a laptop:
lp:~dandrader/unity-api/mousePointer
lp:~dandrader/qtmir/multimonitorNext
lp:~dandrader/unity8/externalMonitor
2 - In lightdm greeter, log into a unity8 session
3 - connect an external monitor
Expected outcome:
-
You see only one cursor (the one unity8 draws)
Actual outcome:
-
You see two cursors: the unity8 one and the mir one.
Comments:
--
In qtmir's mir::Server class, this is the snippet it uses to hide the
mir cursor:
"""
add_init_callback([this](){ the_cursor()->hide(); });
"""
The mir cursor remains visible also after you unplug the external
monitor.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1502200/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
