360696 - Migration wizard doesn't appear

Status: RESOLVED FIXED

(Calendar :: Import and Export, defect)

Description

[Koen Hendrickx]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061114 Calendar/0.4a1

When i start sunbird with an empty profile, the migration wizard does not appear. 
error console:
Failed to load XPCOM component: /home/koen/Sunbird/sunbird/extensions/[e-mail]/components/talkback/XTalkback.ad
---
Failed to load XPCOM component: /home/koen/Sunbird/sunbird/extensions/[e-mail]/components/talkback/talkback.so
---
Failed to load XPCOM component: /home/koen/Sunbird/sunbird/extensions/[e-mail]/components/talkback/talkback
---
Failed to load XPCOM component: /home/koen/Sunbird/sunbird/extensions/[e-mail]/components/talkback/master.ini
---
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIBoxObject.getProperty]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://global/content/bindings/textbox.xml ::  :: line 102"  data: no]
---> this appears 4 times.
---
Error: Migrator error: ReferenceError: ffSpec is not defined
Source File: chrome://calendar/content/calendarManagement.js
Line: 283

Comment 1

[Stefan Sitter [:ssitter]]

Attachment: fix typo and warnings

This fixes the typo (appSpec instead of ffSpec) and the warning about idx being undeclared by using the existing variable truncate.

Comment 2

[Stefan Sitter [:ssitter]]

Attachment: fix typo and more warnings

Comment 3

[Matthew (lilmatt) Willis]

Comment on attachment 245589 [details] [diff] [review]
fix typo and more warnings

r1/r2=lilmatt
ok for me to do r2 from mvl via irc

Comment 4

[Matthew (lilmatt) Willis]

Patch checked in on MOZILLA_1_8_BRANCH and trunk

-> FIXED

Comment 5

[cmtalbert]

I have tried this fix and still encounter this error:
Error: Migrator error: [Exception... "Component returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) [nsILocalFile.directoryEntries]"  nsresult: "0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)"  location: "JS frame :: chrome://calendar/content/migration.js :: gdm_calold :: line 422"  data: no]
Source File: chrome://calendar/content/calendarManagement.js
Line: 283

I am attempting to import Evolution into Sunbird on RedHat Fedora Core 4.

Reopening bug.

Comment 6

[Joey Minta]

(In reply to comment #5)
http://lxr.mozilla.org/mozilla/source/calendar/base/content/migration.js#699 needs an if (localFile.exists()) around it like getNormalProfile has.

Comment 7

[Matthew (lilmatt) Willis]

(In reply to comment #6)
like this...

        if (localFile.exists()) {
            return localFile;
        }
        return null;
    },

Comment 8

[cmtalbert]

Attachment: Implements jminta's suggestion

Implements jminta's suggested fix.

Comment 9

[Matthew (lilmatt) Willis]

Attachment: jminta's fix

Comment 10

[Matthew (lilmatt) Willis]

Comment on attachment 245600 [details] [diff] [review]
Implements jminta's suggestion

r1/2=lilmatt

Comment 11

[Matthew (lilmatt) Willis]

Patch checked in on MOZILLA_1_8_BRANCH and trunk.

-> FIXED

Comment 12

[Simon Paquet [:sipaq]]

Even with this patch I still get the following error and the migration wizard doesn't show up:

Error: Migrator error: [Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsILocalFile.initWithPath]"  nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: "JS frame :: chrome://calendar/content/migration.js :: gdm_getNorm :: line 741"  data: no]
Source File: chrome://calendar/content/calendarManagement.js
Line: 283

The build is a one day old nightly, but since no related checkins occurred this will still be valid in today's build:

Mozilla/5.0 (Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061117 Calendar/0.4a1

Comment 13

[Stefan Sitter [:ssitter]]

(In reply to comment #12)
The win32 problem was already filed as Bug 360659. The linux bug should be set back to fixed unless it's still failing.

Comment 14

[Simon Paquet [:sipaq]]

(In reply to comment #13)
> The win32 problem was already filed as Bug 360659. The linux bug should be set
> back to fixed unless it's still failing.

You're right. Setting back to FIXED.