Closed Bug 1548523 Opened 7 years ago Closed 7 years ago

Error message in console when starting thunderbird calendar widget

Categories

(Calendar :: General, defect)

Lightning 6.2.5.1
Desktop
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 758493

People

(Reporter: bugzilla, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

Start Thunderbird 60

Actual results:

Mutations-Ereignisse sollten nicht mehr verwendet werden. Verwenden Sie MutationObserver stattdessen. calendar-widgets.xml:512:20

Expected results:

Nothing I guess.

Does the calendar widget work even after the error?

Does it display any other errors after this one?

Yes, Calendar works here and I also have that error in my Error Console. It appears after every start of Thunderbird.

This message appears previous to it.

"While creating services from category 'profile-after-change', could not create service for entry 'calendar-backend-loader', contract ID 'service,@mozilla.org/calendar/backend-loader;1'"

Nothing related to Lightning that I can see after the calendar-widgets.xml:512.20 error

Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
Lightning 6.2.6.1 (Which isn't in the Tracking Version list)

I believe that error has been around for awhile.

Status: UNCONFIRMED → NEW
Component: Untriaged → General
Ever confirmed: true
OS: Unspecified → All
Product: Thunderbird → Calendar
Hardware: Unspecified → Desktop
Version: 60 → Lightning 6.2.5.1
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE

(In reply to Benjamin Flanagin from comment #1)

Does the calendar widget work even after the error?

Does it display any other errors after this one?

As stated above, same here, just that one error. Calendar widget works.

I also get some errors like this

Lightning:Couldn't find (GMT+01.00) Sarajevo/Warsaw/Zagreb calTimezoneService.js:194

But this seems to be another issue.

You need to log in before you can comment on or make changes to this bug.