(In reply to sienkiew from comment #45)
> I don't understand why anybody would care about svn+ssh URLs in the email.
Agreed. I can't imagine anyone caring much about svn+ssh URIs and they won't work in a GNOME environment anyway because of this very issue.
> That is, when using GConf for the lookup, first assume a string with '+' in
> it was not found.
No! This is where the bug gets confusing... When thunderbird implements a GConf client, is handles the error and returns it to stdout. The pop-up only occurs when support for GIO is compiled in.
Old versions of libgio call on GConf to lookup URIs and it's the old libgio code which causes the popup for the error.
Any change like your suggestion needs to be applied to Thunderbird's GIO client (and to completely remove the error, also to the GConf client)
(In reply to sienkiew from comment #45)
> I don't understand why anybody would care about svn+ssh URLs in the email.
Agreed. I can't imagine anyone caring much about svn+ssh URIs and they won't work in a GNOME environment anyway because of this very issue.
> That is, when using GConf for the lookup, first assume a string with '+' in
> it was not found.
No! This is where the bug gets confusing... When thunderbird implements a GConf client, is handles the error and returns it to stdout. The pop-up only occurs when support for GIO is compiled in.
Old versions of libgio call on GConf to lookup URIs and it's the old libgio code which causes the popup for the error.
Any change like your suggestion needs to be applied to Thunderbird's GIO client (and to completely remove the error, also to the GConf client)