Message data not showing following last two updates
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(thunderbird_esr115 affected, thunderbird_esr128 affected)
People
(Reporter: planabuild, Unassigned)
Details
(Whiteboard: [closeme 2024-09-01])
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
Steps to reproduce:
N/A PERMANANT PROBLEM
REINDEXED LAST TIME - BUT DID NOT RESOLVE PROBLEM THIS TIME
Actual results:
ON PREVIOUS UPDATE INBOX MESSAGES FOR APPROX 2 YEARS WERE MISSING BUT HEADER WAS SHOWING FOR ALL
ON LAST BETA UPDATE THE SENT MESSAGES ARE NOW NOT SHOWING
Expected results:
MESSAGES PANE SHOULD SHOW
Comment 1•1 year ago
|
||
Try Help | Troubleshoot mode
Anything in the Error Console (Ctrl+Shift+J)
Updated•1 year ago
|
console-export-2024-7-1_7-41-5
This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”. Sent
Request to access cookie or storage on “<URL>” was blocked because we are blocking all storage access requests. 2
This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”. Inbox
tb.account.size_on_disk - Attempted to set the scalar to an incompatible value. 4
At the first update of version 128 only the Inbox messages between 27/06/2024 and 28/09/2021.
After last update Sent messages between 27/06/2024 and 16/10/2021 were also not not visible
The program can display all messages in local folders or those that I have saved in my Job directories held on my Computer.
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Hello,
I have tried to reproduce this issue using Windows 10, Windows 11 , Ubuntu 22&24 and macOS 14 on the affected build from 2024-06-28, 129.0b6(20240729174322), 128.1.0esr(20240730200333), 115.14.0(20240801155430) but did not succeed.
If you can still reproduce this issue with the same repro steps, it would very helpful if you could indicate the affected versions on which you are able to reproduce it(besides the affected build from 2024-06-28 on which you have encountered it) and if time allows, help us with a regression range for this issue.
I will provide the steps necessary.
You have to determine a build that reproduces the issue.
Then you should find one that does NOT reproduce it. Detailed steps:
a. Open Mozregression app;
b. Click "File" -> "Run a single build";
c. On the "Single Run Wizard" pop-up, "Basic configuration", select "Thunderbird" and click "Next".
d. On the "Profile selection" page, just click the "Next" button.
e. On the "Build selection" select a date (dates before 2024-06-28 to have a better chance finding one that does not reproduce the issue) from the drop-down on the left and click "Finish".
f. Now the mozregression app will open a thunderbird build of the selected date and you can use it, close it and open another. (make a note of the version that does not reproduce the issue)
You will use mozregression app to "bisect" builds that reproduce the issue by builds that do not reproduce it in search of the one build/changeset that introduced the issue, in the first place:
a. Open mozregression-gui.exe
b. Click "File" -> "Run a new bisection"
c. On "Basic configuration" screen, select "Thunderbird" and click "Next" button.
d. Skip "Profile selection" screen by the "Next" button.
e. On the Bisection wizard screen, you will need to select a build that reproduces the issue and one that does not:
e1. In the "Last known good build:" section, select "date" on the right drop-down and the date of the build you found NOT to reproduce the issue.
e2. In the "First known bad build:" section, select "date" on the right drop-down and the date of the build you found to reproduce the issue.
f. Click "Finish" to start the bisection process.
g. Builds will open one-by-one, you will need to test each one of them and see whether the issue reproduces. If it reproduces, then you need to select the "bad" button in the mozregression window and if not, you need to select the "good" button.
h. When bisection is done, you will have the information in the "Log View" section of the mozregression window; bisection may also fail due to not enough builds, but the logs can always be useful.
Copy the logs in a text file and attach it to this bug.
If there is still information you need regarding the regression process, please request information from me.
Thank you for your contribution!
Updated•1 year ago
|
Comment 4•1 year ago
|
||
(happened with releases prior to 128)
Updated•1 year ago
|
Comment 5•1 year ago
|
||
Not enough data to do anything.
Please try v128.1 or above. Then right click and in the folder properties use Repair Folder.
Description
•