This bug was fixed in the package unity -
7.2.0+14.10.20140512.4-0ubuntu1
---------------
unity (7.2.0+14.10.20140512.4-0ubuntu1) utopic; urgency=low
[ Stephen M. Webb ]
* lockscreen/LockScreenAccelerators.h: added required header for
std:vector definition
* disabled precompiled headers on arm64 Ubuntu package builds (LP:
#1317276)
[ Brandon Schaefer ]
* Set the max width, so our static text wraps. So we don't end up
rendering text out of the view area. (LP: #1312749)
[ Marco Trevisan (Treviño) ]
* UnityScreen: toggle activation of all the unity compiz actions when
locking the screen Also, make sure that the lockscreen views are
treated as "always-on-front" windows by nux (and this applies to
both visibility and events).
* PanelService: emit an invalid EntryActivated signal if the menu
hasn't actually been shown In addition, if the menu is not visible
after the first popup call, try to show a menu without keyboard
focus. This will make possible to see menus also when there's a key-
grab (although they will be without keyboard support). Finally,
reset the menu state, if that failed.
* UnityScreen: always paint the lockscreen above, just add menu and
onboard as exceptions Some code cleanup, factorizing similar code.
(LP: #1313280)
* UnityScreen: don't try to show Dash/Hud if the screen is grabbed
Also move the dash opening out from LauncherController, and get rid
of UBus as first initialization source, as it can only slow things
down here. (LP: #741869)
* PluginAdapter: make sure we don't try to call an invalid
initiate/terminate callback function (LP: #1221673)
* DebugDBusInterface: match properties if they are in the AP array
form [<type>, <value>] (LP: #1307748)
[ William Hua ]
* Add proper support for modifier-only shortcuts on the lock screen.
(LP: #1291461)
[ Jinkyu Yi ]
* Dash: Fix problem at checking blacklisted unicode range (LP:
#1251193)
[ Andrea Azzarone ]
* Add a warning in the session dialog if other sessions are still
open. (LP: #1281058)
-- Ubuntu daily release <ps-jenk...@lists.canonical.com> Mon, 12 May 2014
22:03:27 +0000
** Changed in: unity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307748
Title:
xpathselect attribute matching doesn't match anything other than
object Ids
Status in Unity:
In Progress
Status in “unity” package in Ubuntu:
Fix Released
Bug description:
I came across this issue while testing an autopilot branch of mine.
The xpathselect server-side matching (as opposed to matching in the
autopilot python code) is not working as expected.
To reproduce:
- Save this code as test_selection_attributes.py -
http://paste.ubuntu.com/7252495/
- (with the unity-autopilot package installed) run: `autopilot run
test_selection_attributes`
This script contains 2 tests, one passes to prove that it can get a
Launcher that has the monitor attribute of 0, the 2nd test attempts to
select the Launcher object with attribute monitor=0 and fails.
We see in the unity logs:
- "Unable to match 'monitor' against property of unknown integer type."
A bit of digging suggests that GetPropertyValue is returning an array
of values (Probably: Object type id, Value?) which means that, in
MatchIntegerProperty for instance, the values GVariantClass will never
be one of the Integer types.
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1307748/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
