control: found -1 icedove/1:45.4.0-1.1
Hi,
I was also affected by this with my existing icedove profile, but
can't reproduce it in a fresh profile.
Turns out in some places my icedove config (mimeTypes.rdf) still
carried "iceweasel", but I already had uninstalled the "iceweasel"
transitional package.
So icedove has to take its own steps to complete the iceweasel ->
firefox transition. Otherwise existing profiles will lack an imo
important functionality, as soon as the iceweasel package gets
uninstalled.
I don't know if this affects all existing profiles, or only some of
them. (I use mine since about 10 years. I sometimes do configuration
changes, but I'm quite sure I didn't change this setting manually/
on purpose.)
A short term solution might be to depend on iceweasel, but in the
long run mimeTypes.rdf in /home needs to be updated/fixed. Since
(afaik) Debian maintainer scripts mustn't change data in /home, I
guess this would be a job for /usr/bin/icedove itself.
Possible workarounds (successfully tested):
===========================================
1. Create a new profile
2. Or reinstall the transitional package:
$ sudo apt install iceweasel
3. Or manually create a compatibility link:
$ sudo ln -s /usr/bin/x-www-browser /usr/bin/iceweasel
4. Or fix mimeTypes.rdf (replace all broken "/usr/bin/iceweasel"
occurrences (requires icedove restart):
$ for file in $(find .icedove/ -name mimeTypes.rdf); do sed -i
"s|/usr/bin/iceweasel|/usr/bin/x-www-browser|g" "$file" ; done
I went for #4, so this is fixed for me now.
System setup/diagnosis:
=======================
According to "about:config" the http(s) protocol handlers in
icedove have the default setting:
network.protocol-handler.app.https;x-www-browser
network.protocol-handler.app.http;x-www-browser
A search in about:config for "iceweasel" is empty.
But mimeTypes.rdf still references iceweasel:
$ for i in $(find .icedove/ -name mimeTypes.rdf); do echo $i; grep -B1
iceweasel $i; done
.icedove/91hlzsoh.default/US/mimeTypes.rdf
.icedove/91hlzsoh.default/mimeTypes.rdf
<RDF:Description RDF:about="urn:scheme:externalApplication:https"
NC:prettyName="iceweasel"
NC:path="/usr/bin/iceweasel" />
--
<RDF:Description RDF:about="urn:scheme:externalApplication:ftp"
NC:prettyName="iceweasel"
NC:path="/usr/bin/iceweasel" />
--
<RDF:Description RDF:about="urn:scheme:externalApplication:http"
NC:prettyName="iceweasel"
NC:path="/usr/bin/iceweasel" />
The alternatives system for x-www-browser is correctly setup and
works, also for opening links from every other application. Changing
it e.g. to chromium doesn't help.
$ ls -l $(readlink -f /usr/bin/x-www-browser)
-rwxr-xr-x 1 root root 126000 Sep 21 04:56 /usr/lib/firefox-esr/firefox-esr
If I try to open a link from icedove I get in the error console:
> Timestamp: 12.11.2016 15:17:05
> Error: NS_ERROR_FILE_NOT_FOUND: Component returned failure code: 0x80520012
> (NS_ERROR_FILE_NOT_FOUND) [nsIExternalProtocolService.loadUrl]
> Source File: chrome://communicator/content/contentAreaClick.js
> Line: 152
Greets
jre
