I confirm the Python scopes are now, after having applied the pygobject
update, working on a Xenial 64-bit system and still working (= no
regression) on a 32-bit one. Thanks!
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
After having installed 2 identical VM (PXE + preseed), with the only
difference being the architecture (32-bit vs 64-bit), I can now confirm
that the Python scopes are working on a 32-bit install and crashing on a
64-bit install, with exactly the same requests made on both sides
(calc:1+1, man:calc
Not sure if this helps but it appears this problem only occurs on a
64-bit system. I did a Xenial 32-bit installation recently and the
Python scopes (I tested calc: and manpages:) worked properly. On a
Xenial 64-bit installation, even with the very last updates (especially
the recent libunity-core)
I forgot to mention: I rely on on the Python scopes infrastructure to
work as expected to endorse the deployment of this Xenial LTS over 400
computers in the NGO I'm working for… Since I love Ubuntu and advocate
for it at work, if you need any more tests, it will be my pleasure to
volunteer!
--
Y
On my side, the error only shows once per session, yes, but… my request
also never works as expected, ever.
I just want to use the unity-scope-calculator as usual — “Dashing” for
calc:1+2 — but it doesn't work, neither the first time nor the next
ones. Is this scope obsolete? Or is it supposed to
I confirm on my side that the gsetting suggestion from Ted Gould
(comment #8) is working for a user with his homedir over NFS. I have now
put it in my default Ubuntu deployment strategy.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicato
6 matches
Mail list logo
