Open Bug 1911467 Opened 1 year ago Updated 1 year ago

Synchronization & Storage, "Disk Space" settings are broken for EWS

Categories

(Thunderbird :: Account Manager, defect)

Product:
Thunderbird
Component:
Account Manager
Version:
Thunderbird 130
Type:
defect

Tracking

(Not tracked)

People

(Reporter: daniel, Unassigned)

References

(Blocks 1 open bug)

Details

Steps to reproduce:

  1. Setup an EWS account
  2. Go to Account Settings -> Disk Space
  3. Change a setting on the page (e.g., only download 30 days of emails)

Actual results:

The new setting is not applied, and if you navigate away from the page and then back then the setting resets.

Expected results:

The new setting is applied and saved

Blocks: tb-ms-exchange
No longer depends on: tb-ms-exchange

So this is Account Settings -> Synchronization & Storage > Disk Space

Do other settings pages not retain their changes?
Is there anything in Error Console upon opening the settings page(s)?

Component: Untriaged → Account Manager
Flags: needinfo?(vlucaci)
Summary: "Disk Space" settings are completely broken for EWS → Synchronization & Storage, "Disk Space" settings are broken for EWS

Hello,

Tried to reproduce this issue with macOS 14, macOS 15, Ubuntu 24 and Windows 11 on 135.0a1(20250110170549) and 136.0a1(20250114103321) but did not succeed. I did not manage to encounter anything in the Error Console as well.

@Daniel, are you still able to reproduce this issue with the same account, version and steps? If yes, would you be kind in helping us find the regressor for this issue?

If this issue is still reproducible for you, could you please help us with a regression range using the Mozregression GUI tool?

I will provide some steps to make it easier for you:

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-08-04 you find one that does not reproduce the issue) on the 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!

Flags: needinfo?(vlucaci) → needinfo?(daniel)

fwiw I'm not sure a regression range would be helpful here. If it still reproduces, it very likely means we haven't properly implemented support for this for EWS yet, in which case it has never worked.

Yep, still reproduces. Windows 11 Arm64, Thunderbird 136.0a1, 2025-01-14.

Error console shows:
Uncaught NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIMsgFolder.folderURL]
collectOfflineFolders chrome://messenger/content/am-offline.js:394
initOfflineSettings chrome://messenger/content/am-offline.js:37
onInit chrome://messenger/content/am-offline.js:24
restorePage chrome://messenger/content/AccountManager.js:1486
onPanelLoaded chrome://messenger/content/AccountManager.js:1245
<anonymous> chrome://messenger/content/am-offline.xhtml:26
EventListener.handleEvent* chrome://messenger/content/am-offline.xhtml:25
2 am-offline.js:394

Flags: needinfo?(daniel)

Thanks Daniel! I believe this is a side-effect of bug 1917597, which is indeed about a feature we haven't implemented yet.

Usually I would consider this bug a duplicate (as it's entirely a symptom of another known bug), but I think it can be helpful to keep it open since it describes a UI/UX issue, making it easier to find for other users experiencing the same problem. Wayne, if you disagree and think it is preferable to keep everything onto one bug, I'm happy to follow your lead and close this one as a duplicate.

Status: UNCONFIRMED → NEW
Depends on: 1917597
Ever confirmed: true

Hi Daniel, could you try again with the latest Daily version? Since bug 1917597 was (indirectly) resolved, this error should not be happening again.

Flags: needinfo?(daniel)

Still not working, 138.0a1 2025-03-08

I don't see any errors when using the settings, but I see these at startup:

UnknownCollectionError: Unknown Collection "thunderbird/url-parser-default-unknown-schemes-interventions"
    UnknownCollectionError resource://services-settings/RemoteSettingsClient.sys.mjs:189
    sync resource://services-settings/RemoteSettingsClient.sys.mjs:635
SimpleURIUnknownSchemesRemoteObserver.sys.mjs:114:15
services.settings: Remote Settings startup changesets bundle could not be extracted (TypeError: serverInfo.capabilities.attachments is undefined) remote-settings.sys.mjs:225
services.settings: UnknownCollectionError: Unknown Collection "thunderbird/moz-essential-domain-fallbacks"
    UnknownCollectionError resource://services-settings/RemoteSettingsClient.sys.mjs:189
    sync resource://services-settings/RemoteSettingsClient.sys.mjs:635
RemoteSettingsClient.sys.mjs:555
Flags: needinfo?(daniel)

Thanks for checking! I'll take another look a bit later.

I don't believe these errors are related to EWS specifically, and I can also see them in my IMAP-only profile, so let's classify those as a red herring.

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