(In reply to Karl Tomlinson (:karlt) from comment #68)
> Ah, yes.  That explains a lot.
> http://git.gnome.org/browse/gconf/log/gconf/gconf-client.c?h=gnome-2-20
> 
> I also wonder whether gconf_escape_key() should be used here.
> http://developer.gnome.org/gconf/stable/gconf-gconf.html#gconf-escape-key

Thanks for looking into this further guys - I was about to try in and
either install RHEL5 or compile GConf 2.16 to try and recreate this
other problem..

So we now have at least two distinct GNOME bugs which can trigger this 
behaviour.
1) For older versions of GVFS, the error handling is broken so it always uses 
the unreturned error handler (thus a popup)
2) When GIO is enabled, old versions of GIO still rely on GConf to get the URI 
Handlers and they pass NULL instead of a GError* so any errors will always 
cause a popup. 

It's pretty shameful really that RHEL5 is still delivering GConf 2.16 as
the error handling was actually fixed way back in 2007!

On the Ubuntu side of things - version 10.04LTS (Lucid Lynx) is about to reach 
the end of its support life (March 2013 I think), so I don't know whether we'd 
persuade them to change their Thunderbird build at this late stage. For this 
version of Ubuntu (which is based on Debian Squeeze), the popup issue will go 
away if Thunderbird is built with '--disable-gio'
This problem does not exist in Ubuntu 12.04LTS (precise pangolin) and hopefully 
the majority of users (including myself) will upgrade soon.

I suspect any other Debian-squeeze based distros which are hitting this
issue will probably have the same root cause as Ubuntu.

I suppose Thunderbird could detect gio and gconf versions in the
configure script and refuse to enable gio if it's older than a certain
version (perhaps just emit a warning and then continue with gio
disabled), and perhaps enable something similar to jhorak's patch if
gconf < 2.20 is detected??

-- 
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