Closed
Bug 576350
Opened 15 years ago
Closed 10 years ago
Migration Assistant disk space screen has "required sync" and "low disk warning"
Categories
(Thunderbird :: Migration, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: Dan.Schwartz, Unassigned)
Details
Attachments
(1 file)
339.58 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.86 Safari/533.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1
when upgrading from thunderbird 2 to 3.1 one of the screens titled "Disk space" displays 3 options, the first "Syncrhronize required:" and then two others. Why does it say required? Also it warns that I'm low on disk space. In our configuration we've redirected TB profiles to a network share with a limit of 500MB of space/user. We have over 10000 accounts which use this share, and it doesn't make sense to present an option to "synchronize" when the profile space is limited, unless that synchronization can properly handle using a restricted space (say 10% of available)? I'll attach an image of the screen.
Reproducible: Always
Reporter | ||
Comment 1•15 years ago
|
||
Comment 2•15 years ago
|
||
The "Required:" text should have the amount of space required, e.g. "Required: 123 MB". Same for "Your current total email usage:" and "Free space:".
Is there anything in the error console?
Comment 3•15 years ago
|
||
our server doesn't supply quota info
Comment 4•15 years ago
|
||
That's probably the issue, since it looks like it might be querying quota info before it displays anything, and I bet it's throwing an exception. It should be getting logged somewhere, though.
Comment 5•10 years ago
|
||
MA no longer exists
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Summary: migration disk space screen has "required sync" and "low disk warning" → Migration Assistant disk space screen has "required sync" and "low disk warning"
You need to log in
before you can comment on or make changes to this bug.
Description
•