Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#3111 - Enigmail trouble with packaged Thunderbird
Attached to Project:
Arch Linux
Opened by Peter Galiovsky (galiyosha) - Thursday, 25 August 2005, 18:51 GMT
Last edited by arjan timmerman (blaasvis) - Wednesday, 02 November 2005, 10:23 GMT
Opened by Peter Galiovsky (galiyosha) - Thursday, 25 August 2005, 18:51 GMT
Last edited by arjan timmerman (blaasvis) - Wednesday, 02 November 2005, 10:23 GMT
|
DetailsThe official build of Enigmail plugin doesn't work correctly with Thunderbird from testing package.
Although Enigmail installs and initializes correctly, when you actually try to decrypt a message, the decrypted content isn't displayed although it says decryption was succesful. And it indeed was as when you click Reply on the same message afterwards, the crypted text is replaced with the decrypted one. But only in the Reply window, not in Inbox. The problem seems to be in different build environment. In Enigmail troubleshooting FAQ, entry 18 reads: "On most platforms (excluding Windows), Enigmail works only if it is built on the same platform as Mozilla or Thunderbird was built. This means, if you use the official releases provided by mozilla.org you can use the official Enigmail releases. If you use some Mozilla or Thunderbird version coming from the provider of your distribution (e.g. RedHat, SuSE or Debian releases, reportedly this is also a problem on Sun Solaris), or if you built it yourself, you should either use an Enigmail built by the distribution vendor or build Enigmail yourself! For this, refer to the Source Code section. Please don't file any bug report concerning this problem, it is not solvable." (http://enigmail.mozdev.org/troubles.html) This really seems to be the problem. I tested Enigmail with official mozilla.org build and it worked flawlessly. The solution seems to be either to supply headers in Thunderbird package so users could compile Enigmail themselves without the need of compiling the whole Thunderbird (or at least headers) or, perhaps better, make an Arch Linux Enigmail package. Enigmail is a fairly useful and usable plugin so I think it deserves its place at least in the extra repository. |
This task depends upon
Closed by Dale Blount (dale)
Monday, 27 November 2006, 03:18 GMT
Reason for closing: Fixed
Additional comments about closing: fixed itself during version upgrades somewhere.
Monday, 27 November 2006, 03:18 GMT
Reason for closing: Fixed
Additional comments about closing: fixed itself during version upgrades somewhere.
But IIRC Enigmail is installed solely in the profile dir. Compiling Enigmail only produces an XPI package usable for user installation of the plugin, it doesn't change the Thunderbird build in any way.
So one possible solution is to bundle Enigmail XPI package into the Thunderbird one and just unpack it somewhere (/opt/mozilla-plugins/) during installation of Thunderbird, leaving the optional Enigmail installation to the user, informing him where could the XPI package be found.
Or, as the development cycle of Enigmail doesn't have to necessarily follow the one of Thunderbird, make a separate Enigmail package that would only unpack the compiled XPI somewhere and inform the user about it.
Also, just leaving the include headers in the Thunderbird package would do the trick. If they can be found in /opt/mozilla/include/thunderbird (like the Firefox one can) users can compile Enigmail -- and possibly other plugins that would have similar problems -- themselves without the need of compiling the headers or recompiling the whole application from ABS. If someone would be willing to create and maintain an Enigmail package, he/she can consequently put it into AUR and eventualy it can make it into some official repo.
I think I read a post from someone somewhere that was wondering why Arch Linux installation of Firefox is bigger than the official one. Headers came out to be the difference, as they take some 16 MB of space unpacked. If this is really a problem, the headers could be compressed before creating the package and left in the /opt/mozilla/include/ directory in an archive. They take only around 1,5 MB compressed with bzip2. Or, if the headers are really a thorn in someone's eye, putting them in a separate -headers packages would do.