Your message dated Tue, 6 Oct 2020 17:26:48 +0200 with message-id <19f6c669-9bd5-d653-1086-dfcdd367f...@t-online.de> and subject line Re: Bug#971737: lightning: all calendars disappeared (and throws errors when double-clicked) has caused the Debian Bug report #971737, regarding lightning: all calendars disappeared (and throws errors when double-clicked) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 971737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: lightning Version: 1:78.3.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, I'm using thunderbird/lightning to show a few of my online calendars (iCal, caldav,... you name it). i recently (2 weeks ago) wiped my harddisk and setup a brand new system. all the calendars showed up nicely (afaict, this was with thunderbird-1:68.12.0-1). when i did a routine upgrade a few days ago (now running thunderbird-1:78.3.1-1), i found none of my calendars are displaying any appointments any more (nice: nothing to do! ;-() when i double click the calendar, i get a tiny window (10x10px or so) which i can resize to normal. then it shows: ``` The file /usr/share/lightning/chrome/calendar/content/calendar/calendarCreation.xul cannot be found. Please check the location and try again. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. ``` indeed that file is not there. as such, the calendar functionality of thunderbird is severely broken. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lightning depends on: ii thunderbird 1:78.3.1-2 lightning recommends no packages. lightning suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1:78.3.1-2 Am 06.10.20 um 14:58 schrieb IOhannes m zmölnig (Debian GNU|Linux): >> Any Add-ons installed locally within the copied profile? Any Add-on not >> disabled while working on the profile? > > > turns out the "lightning" add-on was still active. > once i disabled it (and restarted thunderbird), the calendars are back > to normal. > > i'm *pretty sure* that i didn't install the lightning add-on outside of > Debian (that is: as a *local* add-on). > so i guess there's a problem with the upgrade path from the > Debian-packaged lightning (1:68.12.0-1) to the transitional package. Well, we can't do anything about Add-ons that are installed within the profile, and we don't want to of course. And there is no easy way to detect such local installed Add-ons. A local installed Add-on will always win while TB searches for installed Add-ons. So I don't see any possible issue with the upgrade patch. Over 90% of reported issues with TB are based on local installed Add-ons or some strange behavior due entries from previously installed Add-ons within the prefs.js. I've tested a lot while after Lightning got included into the main source of TB, as you might find it unsurprisingly I haven't found real issues here. > gmdsr > IOhannes > > PS: i'm leaving this open, in case you want to verify whether this is > indeed an upgrade problem; for me, the problem is fixed now. That's fine. But as tried to explain above, I don't see a upgrade problem. I need to be able to readjust a issue otherwise I can't really fix something. So I close this report now. -- Regards Carsten Schoenert
--- End Message ---
