(In reply to Magnus Melin from comment #48)
> FWIW, after bug 794378 is fixed --enable-gio will be the default (bug
> 713802).
Hmm - Thanks for that info... If --enable-gio becomes the default then this bug may become much more prevalent.
From my findings, earlier versions of linux (e.g. running GNOME 2.x) have a limited implementation of GIO which actually implements its own internal call to GConf and does not catch any errors, hence the errors are 'uncaught' and get displayed in a popup.
Later linuxes running GNOME 3.x have their own GIO implementation which does not rely on GConf at all and doesn't hit this problem..
Sorry everyone that I've gone quiet about this for ages - I was on holiday for 3 weeks then my wife was ill and life's now taken over... It looks like I'd need a sponsor from the Mozilla Dev Team to be able to propose or commit any kind of fix for this, so unless someone is willing to sponsor me (and to do a code review of my changes), I'll have to let someone else actually fix this :-(
(In reply to Magnus Melin from comment #48)
> FWIW, after bug 794378 is fixed --enable-gio will be the default (bug
> 713802).
Hmm - Thanks for that info... If --enable-gio becomes the default then this bug may become much more prevalent.
From my findings, earlier versions of linux (e.g. running GNOME 2.x) have a limited implementation of GIO which actually implements its own internal call to GConf and does not catch any errors, hence the errors are 'uncaught' and get displayed in a popup.
Later linuxes running GNOME 3.x have their own GIO implementation which does not rely on GConf at all and doesn't hit this problem..
Sorry everyone that I've gone quiet about this for ages - I was on holiday for 3 weeks then my wife was ill and life's now taken over... It looks like I'd need a sponsor from the Mozilla Dev Team to be able to propose or commit any kind of fix for this, so unless someone is willing to sponsor me (and to do a code review of my changes), I'll have to let someone else actually fix this :-(