Closed Bug 490479 Opened 15 years ago Closed 15 years ago

Exception when trying to view smart folders (chrome://messenger/content/folderPane.js Line 849)

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
Thunderbird 3.0b3

People

(Reporter: stef, Assigned: Bienvenu)

References

Details

(Keywords: intl)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; pl; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4
Build Identifier: 

When I'm trying to display smart folders in folder pane nothing happens (last mode is displayed under changed label) and I'm getting following error in error console:

Błąd: uncaught exception: [Exception... "Component returned failure code: 0x80550013 [nsIMsgFolder.addSubfolder]"  nsresult: "0x80550013 (<unknown>)"  location: "JS frame :: chrome://messenger/content/folderPane.js :: ftv_createVFFolder :: line 849"  data: no]


Reproducible: Always

Steps to Reproduce:
1. Download tb nightly
2. Add predefined gmail account
3. Switch folder pane to smart folders mode



Mozilla/5.0 (X11; U; Linux i686; pl; rv:1.9.1b5pre) Gecko/20090428 Shredder/3.0b3pre
BuildID=20090428030602
Blocks: 305340
I'll try this - was this a new profile with no accounts, or did you add the gmail account to an existing profile with existing accounts?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Bug 490749 is relevant to this bug?
Bug 490749 is for exception in folderPane.js upon File/New/Saved Search when no account/no folder is selected at folder pane.
(In reply to comment #1)
> I'll try this - was this a new profile with no accounts, or did you add the
> gmail account to an existing profile with existing accounts?

spotted with old profile (gmail imap, rss, nntp, ...) and rerpo with fresh one (only gmail imap)
> Steps to Reproduce:
>(snip)
> 2. Add predefined gmail account
> 3. Switch folder pane to smart folders mode

Did you access Gmail IMAP server(click Inbox of the new Gmail IMAP account) after step 2, before step 3?
Yes, after complete Inbox sync (and some other folders).
OK, it looks like more general, not gmail specific problem - I get the same with pop3 account, and/or pop3 + gmail imap... the smart inboxes folder exist on disk, I'm testing this with recent localized (pl, but I don't see any difference when testing en-US ones) nightlies under Fedora 11pre/rawhide (earlier F10).
Summary: Smart folders don't work with gmail imap → Exception when trying to view smart folders (chrome://messenger/content/folderPane.js Line 849)
do you have any extensions installed?
(In reply to comment #7)
> do you have any extensions installed?

Lightning only (but not on fresh profiles).
Component: General → Folder and Message Lists
QA Contact: general → folders-message-lists
Confirming this bug for old and new, clean profiles. Error occurs for POP + IMAP accounts.

Now I've been testing en-US builds from 20090428 - 20090507. They're all working for me?! Switching back to a localized (de) 20090507 build leads to the described bug?!

BTW: If Smart Folders is the first folder pane mode after starting Thunderbird, all other pane modes fail, too.
(In reply to comment #9)
So maybe a problem width special folder names in l10n builds?
(In reply to comment #10)
> (In reply to comment #9)
> So maybe a problem width special folder names in l10n builds?

That would explain it - Ludovic, do you see a similar issue running a non-English build?
Also affects Windows XP.
OS: Linux → All
(In reply to comment #11)
> (In reply to comment #10)
> > (In reply to comment #9)
> > So maybe a problem width special folder names in l10n builds?
> 
> That would explain it - Ludovic, do you see a similar issue running a
> non-English build?

French build does.
OS: All → Linux
OS: Linux → All
I've now changed the special folder names in messenger.properties to the original en-US strings. That doesn't resolve the problem.
Keywords: intl
> I've now changed the special folder names in messenger.properties to the
> original en-US strings. That doesn't resolve the problem.

Mhh, I've to correct this. Removing only the intl. characters (umlauts) in German Special folder names doesn't resolve the problem. But replacing the whole special folder names with the en-US ones does resolve the problem. 
So I've done some more replacing tests with these strings. It seems, only the inbox can use the localized string. All other special folder strings lead to the error, if they use another name than the en-US one, although they don't include special characters like umlauts.

Strange is one more thing. Although I can use the German "Posteingang" (inbox) string in messenger.properties for this test, the special folder inbox uses only in the normal folders tree the German string. In the Smart folders tree it uses still "Inbox".
Flags: blocking-thunderbird3?
Given this appears to be a l10n issue (comment 13) granting blocking. bienvenu - can you take a closer look at this?
Assignee: nobody → bienvenu
Flags: blocking-thunderbird3? → blocking-thunderbird3+
Target Milestone: --- → Thunderbird 3.0b3
that error is NS_MSG_FOLDER_EXISTS, so our find is failing, even though the folder does exist, which could be a mismatch between what we're looking for, and what we're trying to create.
Attached patch proposed fixSplinter Review
I haven't tried this with a localized build, but I think it will fix the problem. It doesn't break the English build.
Attachment #377056 - Flags: review?(philringnalda)
Comment on attachment 377056 [details] [diff] [review]
proposed fix

Dossiers virtuels looks just fine, nothing in console d'erreurs.
Attachment #377056 - Flags: review?(philringnalda) → review+
Confirming; patch is working without error in German build.
(In reply to comment #15)
> Strange is one more thing. Although I can use the German "Posteingang" (inbox)
> string in messenger.properties for this test, the special folder inbox uses
> only in the normal folders tree the German string. In the Smart folders tree it
> uses still "Inbox".

This is sill a bug. In all "normal" account/folder trees, the l10n string for "inbox" is used, but in the smart folders tree it still remains as "Inbox". All other special folders are (with the patch applied) using the correct l10n string in smart folders.
Ihrig, can you file a new bug for the non-localized Inbox name? Actually, that might be a bit of a dup, but maybe not.

Thx to folks for verifying the fix. Fix checked in.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
(In reply to comment #22)
> Ihrig, can you file a new bug for the non-localized Inbox name?

Done:
https://bugzilla.mozilla.org/show_bug.cgi?id=492739
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: