New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected behaviour if MOZ_SERVICES_SYNC is disabled for firefox compile #2003
Comments
Can you check the error console? |
Before I go looking for something that I might have disabled... can you point me in the right direction of where I should be looking for that? I thought they disabled the Error Console years ago? (If it's the web developer console, nothing in that shown for this issue) |
I still call it that because "Browser Console" .. blech. Ctrl-Shift-J should do it. |
Ah-ha! that did it. This is the log from open firefox, click the GM dropdown button, click "manage user scripts" (which just opens the extentions page, because GM User Scripts has gone). I then clicked "preferences" for greasemonkey, and tried to click OK (which does nothing visibly) It doesn't look happy!
|
Now I have something to look for... |
From those, it looks like we need an error somewhere at initial launch time to know why the service object wasn't correctly created. (Most of those are just pointing to it missing.) |
I think |
I've still got my "sync-less" build if you want me to test anything out or provide more info |
Ventero@63d11de should fix this issue, if I'm not mistaken. I couldn't verify this myself though, as I seem to be hitting https://bugzilla.mozilla.org/show_bug.cgi?id=883679 (or a similar bug) with my sync-less build. |
One of the configure variables for firefox during build time is MOZ_SERVICES_SYNC. This prevents the Sync service from being compiled in. Greasemonkey is the only thing I could find a problem with - it still runs, still works, and still applies any userscripts that I had installed -- but the menu doesn't list any scripts, the options window just hangs (nothing happens clicking OK), and "Manage User Scripts" isn't there at all.
The text was updated successfully, but these errors were encountered: