Updated to v0.9.0 and then v0.9.1 of Greasemonkey and other than the loss of the handy Manage User Scripts interface (to selectively disable scripts and re-enable them later WITHOUT having to Restart Firefox to implement), did not at first notice any problems.
BUT, when I decided to install a few more scripts, I was totally unable to do so without reverting to GM v0.8.2...
I've checked with a few colleagues who are not having this problem (all PC users) and have colleagues running Mac OS who are suffering the same fate I did after updating Greasemonkey.
Mac OS 10.6.6 with Firefox 3.6.13 ... am not technically savvy about how Greasemonkey and user scripts work and have no clue why v0.9.x would break my ability to install scripts... here's a short list of the scripts (used on Flickr) I cannot install (or update) when running v0.9.x of GM:
Trailr: http://vispillo.org/trailr-1.2.1-fixed.user.js
ANY of Steeev's marvelous Flickr scripts found here: http://steeev.freehostia.com/flickr/
Flickr - Move comment form up: http://userscripts.org/scripts/show/82360
Since I really NEED the ability to install (and/or update scripts) and also MUCH prefer the older GM for selectively enabling and disabling scripts 'on the fly' using the Manage User Scripts interface, I have reverted my version of GM. However, I expect that I will eventually encounter problems of a different sort so am reporting this issue in case the folks working on GM haven't already heard about it.
This feature has not been removed, only moved. It is now the "User
Scripts" tab of the add-ons dialog. All the scripts are listed there,
and disable/enable changes take effect immediately.
> BUT, when I decided to install a few more scripts, I was totally unable to
> do so without reverting to GM v0.8.2...
>
> I've checked with a few colleagues who are not having this problem (all PC
> users) and have colleagues running Mac OS who are suffering the same fate I
> did after updating Greasemonkey.
On Mac OS 10.5.8, Firefox 3.6.13, I can install all of the scripts you
mentioned which I tried. Could you run through our Troubleshooting
steps and report the results?
As I pointed out (whoops, only) in the issue where we're tracking this,
making sure Growl is installed and working should work around this
issue. Long term, we should make it work either way.