I can confirm this behavior and the fix on my system with Google Earth 5.0.11337.1968, but I'm not yet 100% sure that just removing the libcrypto.so.0.9.8 isn't going to break things in the future.
For example, a new Google Earth version and a new Debian version might break if the system libcrypto is used. (This is currently the case with a bunch of other libraries that Google Earth has it's own copy of.) Anyway, I just uploaded googleearth-package 0.5.5 which fixes just about every open bug except this one. If you (or anyone reading this) comes up with a fix that is less intrusive, let me know. In the meantime I'm going to think about if there is a better way to attack this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
