That was the problem, something in there still pointed to firefox. I wonder why icedove didn't call x-www-browser as configured in prefs.js?
Thanks for the help, you should decide if this is a bug or not. Since it was an upgrade problem (worked with icedove 2.x) it probably is? Cheers, Bastian On 17.02.2010 16:02, Guido Günther wrote: > On Wed, Feb 17, 2010 at 03:26:25PM +0100, Bastian Venthur wrote: >> I found something in the error console: >> >> Error: uncaught exception: [Exception... "Component returned failure >> code: 0x80004005 (NS_ERROR_FAILURE) >> [nsIExternalProtocolService.loadUrl]" nsresult: "0x80004005 >> (NS_ERROR_FAILURE)" location: "JS frame :: >> chrome://communicator/content/contentAreaClick.js :: openLinkExternally >> :: line 188" data: no] >> >> A new message of this kind appears every time I try to open a link. > So there's an issue launching the link handler. Does: > > gconftool -g /desktop/gnome/url-handlers/http/command > gconftool -g /desktop/gnome/url-handlers/http/enabled > gconftool -g /desktop/gnome/url-handlers/https/command > gconftool -g /desktop/gnome/url-handlers/https/enabled > > return anything sensible? > -- Guido -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
