I think this is all a bit dependent on the version of GNOME is in use. I
am running Ubuntu 10.04 LTS which still uses GNOME 2.30.2

Looking at the git master for GVFS the latest code no longer appears to have 
any reliance on gconf. I guess that the GIO implementation in GNOME 2.30.2 is 
somewhat transitional.
I've just installed Ubuntu 12.04 + GNOME3 (gnome-shell) in a virtual machine 
and can confirm that thunderbird (versions 11.0 and 14.0) does not encounter 
any GConf errors running under GNOME3.

This all poses a slightly tricky question... Who's fault is this and who should 
fix it? Honestly, I don't know enough about the history of Thunderbird and 
GNOME to be sure, but the GNOME team possibly shot themselves in the foot a bit 
by choosing GConf as the central URI -> Application mapping database when it 
cannot fully support RFC2396 URIs. But then this seems to have always been the 
case and so with this known limitation, there seems to be little point in 
querying potential URIs which will fail to resolve.
Using GConf natively does not really cause a problem as the messages only go to 
stdout. The annoying pop-ups only occur when GNOME 2.x versions of GIO are in 
use, but I don't know if there's any easy way for thunderbird to test which 
version of GIO being used and change its behaviour based on that.

In my opinion, the essence of the plain text URI parsing in Thunderbird
is primarily for making clickable links for http:, https:, ftp:,
mailto:, etc... For these purposes it seems unnecessary to check the
full extent of the scheme defined in RFC2395. As there are currently no
known URI Schemes which use any non alphanumeric characters  (see
http://en.wikipedia.org/wiki/URI_scheme ) I thinks there is an argument
to suggest that the regular expression used to determine what might be a
URI, could be changed so that '+' isn't considered valid.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/411358

Title:
  Thunderbird2 gconf gmt problem 'Bad key or directory name' because of
  plus symbol (+)

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in “thunderbird” package in Ubuntu:
  Confirmed

Bug description:
  Here is an error message for Thunderbird 2 in Jaunty

  gnubyexample@k8amd:~$ thunderbird
  GConf Error: Bad key or directory name: 
"/desktop/gnome/url-handlers/GMT+02/command": `+' is an invalid character in 
key/directory names
  gnubyexample@k8amd:~$ date;uname -a;cat /etc/*version*;dpkg -l | grep 
underbird
  Sun Aug  9 14:48:37 BST 2009                                                  
              
  Linux k8amd 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 00:28:35 UTC 2009 
i686 GNU/Linux    
  5.0                                                                           
              
  ii  enigmail                                   2:0.95.7-1ubuntu2              
                            Enigmail - GPG support for Thunderbird
  ii  thunderbird                                
2.0.0.22+build1+nobinonly-0ubuntu0.9.04.1                  mail/news client 
with RSS and integrated spam filter support                                     
                                                                                
                                             
  ii  thunderbird-locale-en-gb                   1:2.0.0.14+1-0ubuntu2          
                            Thunderbird English language/region package  

  From reading this extract ( 
http://osdir.com/ml/os.solaris.opensolaris.desktop/2008-03/msg00020.html ):
    Subject:    Re: GConf/Thunderbird error on Solaris Nevada

    "Hi Mats,I believe you download the contribute builds of Thunderbird 2, and 
run
  it on snv_70.

  For some reason, the fix is upstreamed to Thunderbird 3 alpha, but not
  community version of Thunderbird 2.
  Fixed in snv_68 means the fix was integrated to Thunderbird bundled
  with snv_68."

  
  ...it seems that the fix for this in thunderbird2 might require some manual 
intervention as although the problem is well know, the fix was only 
incorporated in the newer thunderbird3.

  Have just checked the Karmic version at:
    http://packages.ubuntu.com/karmic/thunderbird
  which currently shows that version 2 of thunderbird is planned for Karmic 
release.

  As thunderbird3 is at Beta 3 right now I can perhaps see why debian and 
ubuntu are sticking with Thunderbird2 just now.
    http://www.mozillamessaging.com/en-US/about/press/archive/2009-07-21-01

  However it does seem a shame to ship a new release with this known
  gconf issue unpatched.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/411358/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to