Created attachment 357574 [details]
The "abonnements" subfolder is not visible in Fedora 11.
Description of problem:
Some subfolders are not visible within my Gmail account (IMAP access).
This is a new problem, it happened after upgrading RPM packages yesterday (August 15th). The problem was not visible before July 15th.
This problem is not reproduced under Windows with Thunderbird 3.0b3.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. View a Gmail account via IMAP.
2. Try to view subfolders.
Subfolders are not visible.
Subfolders are visible.
I've tried reproducing the problem with non Gmail accounts without success. The problem is not necessarily with Gmail though, it could be a problem with existing subfolders vs. new subfolders.
In any case I wasn't able to reproduce the problem with the same Gmail account on Windows.
Created attachment 357575 [details]
The "abonnements" subfolder is visible in Windows.
Cannot reproduce here ... could you reproduce with the latest upstream binary from ftp://ftp.mozilla.org/pub/thunderbird/nightly/latest-comm-1.9.1/ ?
Otherwise looks like a duplicate of bug 517813.
I'm unable to reproduce the problem with two non-Gmail accounts (Microsoft Exchange IMAP4 service) with lots of subfolders.
I'll try again with the Gmail account and the latest upstream binary ASAP.
I've tried the following versions of Thunderbird:
I can reproduce the problem with 3.0b3 and 3.0b4pre.
I cannot reproduce it with 3.0b2.
Note that the user interface has changed between 3.0b2 and 3.0b3: 3.0b2 uses a cross in a square in front of folders with subfolders, while 3.0b3 uses a triangle/arrow. This change might be related to the problem.
Is there something else you would like me to try?
Created attachment 357683 [details]
The "abonnements" subfolder is visible with 3.0b2.
Created attachment 357684 [details]
The "abonnements" subfolder is not visible with 3.0b3.
We filed this bug in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=511007) and believe that it is more appropriate to let it be resolved upstream.
We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.
Thank you for the bug report.
Please join the upstream bug, there is more information requested from you by the upstream developers.