Open GeorgeSchiro opened 10 years ago
I finally got the opportunity to install and test "armory_0.90.99.4-testing_64bit.deb". It was installed in a fresh "ubuntu-12.04.4-desktop-amd64.iso" virtual machine.
The above "Scenario 2" is resolved. But sadly, a new issue came to light. The "?" tool tips no longer cause "desktop winkout", but they also no longer display text either (they're just empty yellow pop-ups now).
The equivalent of "Scenario 1" in "armory_0.90.99.4-testing_64bit.deb" continues ("Scenario 1" was tested in "armory_0.90-beta_OfflineBundle_12.04-64bit.tar.gz"). After a wallet is restored the Unity desktop icons are gone.
All that said, I am happy to report that the problem with advanced encryption options detailed in issue 182 (now closed) has indeed been resolved.
Confirmed this on 12.04.X. I don't remember what X I used, but I do see it with 0.90.99.4-testing.
Apparently related: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/745996
Unfortunately, this is a unity bug. Quite possibly related to virtualbox, too. Not sure of a workaround yet... we're going to look into it.
Also we checked on the (?) things... it turns out that Ubuntu comes with almost-identical palette colors for those things (the text is there, it's just white on yellow). We are going to override the default colors for tooltips in 0.90.99.5+
I'm using VMware on Windows 7. Armory is installed in an Ubuntu virtual machine (from "ubuntu-12.04.4-desktop-amd64.iso" and "armory_0.90-beta_OfflineBundle_12.04-64bit.tar.gz").
What follows are steps which result in the Ubuntu Unity Desktop winking out (2 scenarios).
Scenario 1 (starting with a fresh install):
The Ubuntu Unity desktop will now be invisible (except the background image). The desktop icons are still there and can be clicked, but they can't be seen.
Scenario 2:
The Ubuntu Unity desktop will now be invisible (except the background image). The desktop icons are still there and can be clicked, but they can't be seen.
Note: I can work around this issue by maximizing and then restoring the virtual machine window. The same behavior occurs if I start with the VM window maximized.