calendar plugins are broken: when i receive a calendar entry per email, i cannot add it to the calendar. The message contains the info that there is a new entry, but the button to include it is empty (not working). same phenomenon occurs when i receive an update to an existing calendar-entry.
The calendar buttons are working (for me) if I view the invitation mail as "original HTML", the buttons are not there if I use "view as plain text". This is also reproducable with the "official" linux build (on a linux). I was assuming this was because of some addon-interaction...
The problem still exists for seamonkey, in thunderbird (FBSD 11.0) it seems to be resolved: In order to to narrow the search, I installed FreeBSD/amd64 11.0 on a DELL Desktop, added xorg kde seamonkey, firefox, thunderbird etc. For seamonkey there existed some unresolved dependencies (e.g. to package startup-notifikacion). Connecting to the mailserver (DELL PowerEdge R710 running FreeBSD/amd64 10.3-STABLE with dovecot) using TLS/SSL I observed the same phenomenon. The button to accept or update an event is empty and inactive. Using thunderbird on this machine, events are displayed as they should. Several buttons appear giving the choice to accept or decline the event and a combobox labeled more. At least thunderbird seems to work. Back to my workstation running FreeBSD/amd64 10.3-STABLE: seamonkey revealed the same symptoms and thunderbird showed neither buttons nor combobox. As the problem is reproducible please reopen this PR! I don't like to transfer all my calendar-entries from seamonkey to thunderbird...
Created attachment 183919 [details] Output of SeaMonkey's `make config' I actually had the Lightning functioning -- and even added a Google Calendar integration add-on to it locally -- until a rebuild recently... There is still $PREFIX/lib/seamonkey/distribution/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/calendar-js/ directory with lots of .js files, but the extension is not available at run-time. It is not listed in the "Add-On Manager" and the invites are rendered simply as text. My port-options for seamonkey haven't changed: ALSA CANBERRA DBUS DTRACE EXAMPLES FFMPEG GTK3 LDAP LIGHTNING NLS OPTIMIZED_CFLAGS PULSEAUDIO and --enable-calendar is still among MOZ_OPTIONS: --enable-application=suite --enable-ldap --enable-calendar --prefix="/opt" --enable-system-cairo --with-system-libevent --enable-system-ffi --with-system-graphite2 --with-system-harfbuzz --enable-system-hunspell --with-system-icu --with-intl-api --with-system-jpeg=/opt --with-system-nspr --with-system-nss --with-system-png=/opt --enable-system-pixman --enable-system-sqlite --with-system-libvpx --with-system-vorbis --with-system-ogg --enable-chrome-format=omni --enable-default-toolkit=cairo-gtk3 --enable-update-channel=release --enable-pie --with-pthreads --enable-extensions=default --enable-necko-protocols=default --with-system-zlib --with-system-bz2 --enable-optimize --enable-startup-notification --disable-gconf --disable-gnomeui --disable-libproxy --enable-alsa --enable-pulseaudio --disable-rust --disable-debug --disable-debug-symbols --enable-release --enable-dtrace --disable-gold --disable-profiling --disable-tests --disable-strip --disable-install-strip I'm attaching the output of the `make configure' for good measure.
Ok, it turns out, starting out with a new profile brings Calendar (Lightning) back -- so there is, probably, nothing wrong with the port on this account. Somehow the extension got disabled in my profile -- and there is no obvious way to undo that. For "normal" extensions, one can simply install them again, but Lightning has binary component(s) and there are no pre-build downloads for FreeBSD. I had to manually edit my profile's extensions.json and extensions.ini files to bring it back, but this has nothing to do with the port. Now that the extension is enabled again, the calendar e-mails in my mailboxes are, once again, rendered and processed properly. I suspect strongly, the submitter's problem is local as well, and there is nothing for the port's maintainers to do here.
I removed ~/.thunderbird, recreated my profile and the problems are gone. At least for thunderbird. I assume, removing ~/.mozilla/seamonkey should solve the problems for seamonkey. Thanks for your attention.
This really is an upstream's bug -- but, as far as FreeBSD is concerned, the "Works As Intended" is the only appropriate resolution...