Closed Bug 253527 Opened 22 years ago Closed 21 years ago

Import "Wizard" hangs while importing from Communicator 4.x (Migration works, It's _import_ that fails)

Categories

(Thunderbird :: Migration, defect)

Other
Other
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 266027
Thunderbird1.0

People

(Reporter: edgar.sterk, Assigned: mscott)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Build Identifier: When using: Tools->Import... Choosing "Mail" (Next >) Choosing "Communicator 4.x" (Next >) From here, the process does not do anything. I am able to cancel, so the application does not hang, but it doesn't actually do something. Reproducible: Always Steps to Reproduce: 1. Menu "Mail" 2. Sub "Import..." 3. "Mail" 4. "Next >" 5. "Communicator 4.x" 6. "Next >" Actual Results: Nothing Expected Results: Imported my Communicator mailbox (or at least giving me some sort of wizart to do that" Host OS is Solaris: SunOS $HOSTNAME 5.8 Generic_117350-02 sun4u sparc SUNW,Sun-Fire-V210
Component: General → Migration
*** Bug 254167 has been marked as a duplicate of this bug. ***
*** Bug 250047 has been marked as a duplicate of this bug. ***
I can confirm this problem with the latest 0.8 branch Thunderbird build on XP. Importing Communicator mail just hangs.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Import "Wizard" hangs while importing from Communicator 4.x → Import "Wizard" hangs while importing from Communicator 4.x (Migration works, It's _import_ that fails)
I think this is a dupe of a mozilla seamonkey bug. It doesn't have anything to do with the new profile migration code which is completely separate from importing.
Whiteboard: DUPEME
Scott, OK. (the only reason we were even testing this is because many of the people who came to our bugday weren't seamonkey users with the necessary seamonkey registry.dat file so they couldn't do any _migration_ at all. In absense of that, we tested import.) If this is indeed a missing feature then we should remove that UI. Users experience this as a hang (though technically, it's not a hang, it's "nothing happening") The SeaMonkey version of this perceived hang is bug 157477 (I think) and the actual bug for implementing the backend behind this useless UI is probably bug 63389. Is it the case that all of the import functionality is completely differnt code from the migration functionality? Based on my experience today, users certainly don't think of it like that.
I see the older Bug 250047 has been closed, it would be great if the import from netscape 4.x is addressed verus the 4.x netscape just taken off of the UI (User Interface). A lot of us have been still using 4.8 netscape since no mail program till Tbird has the features to be worth upgrading to. I hope this issue is taken into serious consideration to be fixed. Thanks for your time. Phil Diakun
*** Bug 260905 has been marked as a duplicate of this bug. ***
js console error when this occurs: Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIComm4xProfile.getProfileList]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/importDialog.js :: ImportMail :: line 675" data: no]
using what build sairuh? I fixed this last week.
I fixed this as Bug #266027
Target Milestone: --- → Thunderbird1.0
*** This bug has been marked as a duplicate of 266027 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.