Le 30/06/2010 12:52, Thilo Six a écrit :
There had been hope that the upcoming icedove update as of today (squeeze
3.0.5) would fix this, apparently not.
I did try the whole thing with a new user=new profile and viola icedove open
http[,s] links with the right application namely x-www-browser.
This newly created icedove profile didn´t fixed it for my mainuser.
After deleting any mime related file i could find w/o success, i created a
completely new kde profile.
Now icedove behaves right also with it´s original profile!
Here i use
$ apt-cache policy kdebase-bin
kdebase-bin:
Installed: 4:4.4.4-1
Candidate: 4:4.4.4-1
Apparently i am not able to trace that down to a specific setting/file but it
seems this bug here is caused by the DE and not by icedove.
Fabrice cc'ed can you try that also and [,not] confirm?
Hello Thilo,
I confirm that this pb is not fixed with icedove-3.0.5-1.
icedove is using /etc/alternatives/x-www-browser instead of using the
one pointed to in prefs.js.
My configuration is the following :
$ grep network.protocol-handler prefs.js
user_pref("network.protocol-handler.app.http", "iceweasel");
user_pref("network.protocol-handler.app.https", "iceweasel");
$ grep network.protocol-handler /etc/icedove/pref/icedove.js
pref("network.protocol-handler.app.http", "/usr/bin/iceweasel");
pref("network.protocol-handler.app.https", "/usr/bin/iceweasel");
@+,
Fab
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
