Closed Bug 1743167 Opened 3 years ago Closed 3 years ago

console errors when starting thunderbird 91

Categories

(Thunderbird :: General, defect)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1727509

People

(Reporter: sm1179844, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0

Steps to reproduce:

when run in console, it gives this

Actual results:

[calBackendLoader] Using Thunderbird's libical backend
[LDAPModuleLoader] Using LDAPDirectory.jsm
[MsgSendModuleLoader] Using MessageSend.jsm
[SmtpModuleLoader] Using SmtpService.jsm
console.warn: "[l10nregistry] Attempting to synchronously load file\n resource:///chrome/en-US/locale/en-US/calendar/messenger/otr/otrUI.ftl while it's being loaded asynchronously."
console.debug: "Trying to load /usr/lib64/thunderbird/libotr.so"
console.debug: "Trying to load libotr.so from system's standard library locations"
console.debug: "Successfully loaded OTR library libotr.so from system's standard library locations"
console.debug: "Successfully loaded OpenPGP library librnp.so version 0.15.2+git20210806.dd923a4e.MZLA from /usr/lib64/thunderbird/librnp.so"
console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0 unprotected)"
console.warn: services.settings: thunderbird/hijack-blocklists has signature disabled
IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

Are you encountering a specific problem?

Component: Untriaged → General
Flags: needinfo?(sm1179844)

(In reply to Wayne Mery (:wsmwk) from comment #1)

Are you encountering a specific problem?

There are no problems, but how to remove the console output.
If these are minor issues, how do you fix them?

Flags: needinfo?(sm1179844)

Duplicate of bug 1727509.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.