Ok, it looks like the problem occurs in a newer release of Gmail. I've been doing some testing, and it looks like I've found how to determine the current version of Gmail. Just hit view > source and search for "GLOBALS" until you find something like the following::

var GLOBALS=[,,"14347794","gmail_fe_641_p7","...

I've got a few accounts so I was able to test the following. Could you all confirm my findings?

• gmail_fe_636_p8 - still works (thank god for my wife's unused account )
• gmail_fe_641_p7 - fails with fault *
• gmail_fe_642_p13 - fails with fault *

*CustomError: Service for "t" is not registered

You can see errors in the script by entering "about:config" into your address bar and searching for extension.bcGmailSigs.debug and changing its value to 'true'. This will enable messages in the Firefox console. Just hit CTRL+ALT+J and then select the "Messages" view. Errors will flash by pretty quickly, but you should be able to catch something.

Any thoughts?

Still looking into it. I'll probably have to wait for them to put out a fix.

Looking forward to a fix for this.  I am forced to use Gmail standard signature and it looks gross.  lol

...also looking fwd to fix...

Jerome

It'll be brilliant if can sort out a fix for this, thanks for the posting anyway as it's saved me pulling my hair out wondering what was wrong with gmail.

This is by far, my FAVORITE addon! I was very disappointed to find it not working this morning. Thanks for the explanation.

FYI, I have found (as I have many accounts in use (Google Apps & Gmail) with multiple signatures for each account, that sometimes the plugin was not loading properly when I had "Keep me signed in" checked. Work around seemed to be to make sure I signed out of the accounts (no big deal).

Anyone else seeing this behavior? Cookie issue maybe?

Thanks again for the great work here!

I show this in my source file too:

var GLOBALS=[,,"14347794","gmail_fe_641_p7","...

I'm using FF 3.5.7 on a Mac version 10.5.8

Good luck getting this resolved. I miss my email signatures. Once resolved do you think think we're going to
have to recreate our signatures will our preferences miraculously still be there?

Thanks.

According to this blog post, the GreasemMonkey API is fine. The script just needs a little update.

http://gmailblog.blogspot.com/2008/01/gmailgreasemonkey-api-issue.html

I un-installed BC Gmail signatures on Firefox 3.6 to try to see if it would help to get back the functionality if I re-install the extension.

I did this before I knew what the real problem was.

When I tried to re-install BC Gmail signatures I got the following error message:

Error: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIRDFService.GetLiteral]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: file:///C:/Program%20Files/Mozilla%20Firefox/components/nsExtensionManager.js :: EM_L :: line 236"  data: no]
Source File: file:///C:/Program%20Files/Mozilla%20Firefox/components/nsExtensionManager.js
Line: 236

I tried quite a few times, every time with the same result.

Any relationship at all  - or is this a different problem?

Hey Jerome,

I have a Gmail app thru GreaseMonkey for subfolders in my Gmail  - and it is working. Does this help you at all?

As described in the first post of this thread in the following link:

http://code.google.com/p/gmail-greasemonkey/issues/detail?id=39

Calling getActiveViewType() or getActiveViewElement() on the gmail object returned by gmonkey.load() throws an exception. Even the most basic script fails throwing the same fault:

CustomError: Service for "t" is not registered

// ==UserScript==

// @name           gmail test
// @namespace      gmailtest
// @include        *
// ==/UserScript==

window.addEventListener('load', function() {			 
	if(unsafeWindow.gmonkey) {
		unsafeWindow.gmonkey.load('1.0', function(gmail) {
			try { alert(gmail.getActiveViewType()); } catch(e) { alert(e); }
		});
	}
}, true);"

I believe the folders Greasemonkey script mentioned above (please provide a link in the future) is working because it uses the getNavPaneElement(), which accesses the left area of Gmail and seems to still be working.

Yes, you can go to gmail, confirm it's working, then click "view" > "page source" (or press CTRL+U) and search the page source for GLOBAL (as described above until you find a version number that looks something like 

var GLOBALS=[,,"14347794","gmail_fe_641_p7","...

and let me know what you find. I'm guessing your Gmail account hasn't been updated yet.

Hi Jerome,

First of all let me thank you for all your hard work and Blank Canvas is one of the most useful add ons I have seen. Well done !

As everybody's else, mine stop working a few days ago, presumably because of the changes to Google's libraries.

The first thing I did is uninstalled and tried to install again, but now I cannot even install it. When FF is installing I get the foilowing error:

Is this part of the same issue with Google's libraries ?

Thanks and regards,

Fernando

I recieve that same error code -203 and message and yes, I will donate! 

From the messages above it is clear that some other people also encountered the add-on installation bug that I ran into.

I reported the bug on Bugzilla Bug 543929

Those of you who also got the bug (adreamer, BKovac18, maybe some others?), please assist by going to

https://bugzilla.mozilla.org/show_bug.cgi?id=543929

and confirm the bug. Please add your own details as far as possible.

It may just help to get the Firefox developers to pay more serious attention to fixing it.


Thank you.

Another temporary fix is to create a sig in a message and save it as a canned response

Thanks Ventiman,

I'm becoming more and more determined to write my own Gmail access API. I tried last weekend and it was extremely frustrating, but the way things are going, it will be easier to spend some time initially and only have to update a line or two of code in the future than to wait for Google to fix their Greasemonkey API. I'll take another look tonight and through the weekend. With any luck we'll have something semi-workable next week.

Hello to all,

HERE'S A QUICK SOLUTION TO ADD SIGNATURES.

I have been a huge fan of Blank Canvas, and have posted a few times here before..... and like most of you, I cannot live without it!!

I gave a Gmail account where I use multiple @mydomain.com emails for my business, and every time I use a different email address to reply to messages, Blank Canvas would put the correct signature for that email. It is WONDERFUL!!!

So when it's not working..... It's a reason to PANIC!!!!!! I know....

But for the longest time, I have also been using another Firefox Addon which I love.... BUT.... I use it to paste template text into emails.... like when I need to respond the same thing over and over to people.... and don't want to keep writing the same thing again.

So because this Addon will paste text into an email (ANY text, even HTML formatted text).... I am now using it to paste my Signatures into my emails.... WHILE Jerome is working on a fix.

So don't get me wrong... this is NOT a replacement for Blank Canvas... it's a temporary solution!! And you'll see that you couldn't even consider using it to do what Blank Canvas does, because Blank Canvas does it automatically, which is why it's such a fantastic Addon.

This other Addon requires you to right-click on the body of an email, in order to insert the text/signature... so it's not too convenient (especially if you forget to do it), but it's better than nothing while we wait for the fix.

The Addon I am talking about is CLIPPINGS.

https://addons.mozilla.org/en-US/firefox/addon/1347

So I hope this helps those desperate people... like me!!! lol

PS.... Just for FYI.... I did NOT upgrade my Firefox... But when Blank Canvas upgraded itself... It stopped working. I even tried to go back to a previous version of BC, but it didn't work either.

My FF version is 3.0.5 (yeah I don't upgrade too often because of it breaking my Addons)

Take care all and thanks for everything Jerome,

Alexandra

It just struck me that this issue came to the fore at around the same time the Google Chrome browser began supporting Greasemonkey scripts:

http://download.cnet.com/8301-2007_4-10445538-12.html

I'm not suggesting their is a conspiracy, simply that Google may have made the changes they did with an eye toward future Chrome/Gmail developments.

Hi there,

From your Facebook page I learned you are doing well in the process of (re)writing the code for the marvelous add-on.  Just wanted to drop a line to let you know that we are all patiently wating for the update. Honostly, I am.

Ventiman.

Great job.

Well done jerome.