@Robin: the extra message is annoying indeed (only with openjdk), it's hardcoded in openjdk, writing those env variable on stderr. I agree that some written script can have some output expectation on stderr (even if I don't think it's the best and most reliable way of handling output from a script). I think this part will be redirected in another bug report (even if we disable jayatana, to keep a track on it and have that noise turned off on openjdk).
I was wondering if the crash that people here were seeing were due to openjdk 8 instead of 7. I didn't get any crash with it though with jayatana installed, (I checked that /usr/lib/jvm/java-8-openjdk-amd64/bin/java was executed) when starting android studio on my wily machine which was pointed as one of the crashy program. The menu is then correctly exported. Can somebody give a simple (with a program that is in ubuntu repository) step by step reproducer so that we all start from the same bases? That would probably help danjaredg to have a better start.
@Robin: the extra message is annoying indeed (only with openjdk), it's hardcoded in openjdk, writing those env variable on stderr. I agree that some written script can have some output expectation on stderr (even if I don't think it's the best and most reliable way of handling output from a script). I think this part will be redirected in another bug report (even if we disable jayatana, to keep a track on it and have that noise turned off on openjdk).
I was wondering if the crash that people here were seeing were due to openjdk 8 instead of 7. I didn't get any crash with it though with jayatana installed, (I checked that /usr/lib/ jvm/java- 8-openjdk- amd64/bin/ java was executed) when starting android studio on my wily machine which was pointed as one of the crashy program. The menu is then correctly exported. Can somebody give a simple (with a program that is in ubuntu repository) step by step reproducer so that we all start from the same bases? That would probably help danjaredg to have a better start.