1622431 - messages not shown - instead the empty start page and create account window appears

Status: RESOLVED DUPLICATE of bug 1578539

(Thunderbird :: Untriaged, defect)

Description

[tleutritz]

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

Steps to reproduce:

I guess it all happened with an update (<68.6).

Actual results:

Afterwards all messages diappeared. Even deleting invalidprefs.js and global-messages-db.sqlite did not help (after having the error message "gloda.ds.pch ERROR database error:[xpconnect wrapped mozIStorageError]"). The correct folder is accessed by Thunderbird each time. Following error message remained but disappeared as well: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMessenger.msgHdrFromURI]

Expected results:

messages should be displayed

Comment 1

[Wayne Mery (:wsmwk)]

You updated from what version?
Your profile directory data seems to be intact ?

Comment 2

[Matt]

I would guess this is another dup of Bug 1578539

Comment 3

[tleutritz]

@Wayne: automatic upgrade to 68.6.0 (x86) on a Windows 10 system (also a fresh install with 64bit version showed same behaviour).
How can I check if the directory is intact (despite that files have sizes > 0 b)?

@Matt: yes, seems to be the same as reported in Bug 1578539, but workaround does not work.

Comment 4

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 5

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 6

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 7

[Firefox Bug Husbandry Bot]

The severity of these bugs was changed, mistakenly, from normal to S3.

Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.