Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

No folders are listed after moving profile

  • 2 답장
  • 1 이 문제를 만남
  • 2 보기
  • 최종 답변자: decibel

more options

After moving my profile Thunderbird shows all my accounts but no folders at all, even under "Local Folders" or an RSS feed I have. I can still see account settings.

This is the error I'm seeing in Error Console:

Timestamp: 1/18/17, 12:38:32 PM Error: [Exception... "Component returned failure code: 0x80550007 [nsIMsgFolder.getStringProperty]" nsresult: "0x80550007 (<unknown>)" location: "JS frame :: chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2780" data: no] Source File: chrome://messenger/content/folderPane.js Line: 2782

After moving my profile Thunderbird shows all my accounts but no folders at all, even under "Local Folders" or an RSS feed I have. I can still see account settings. This is the error I'm seeing in Error Console: Timestamp: 1/18/17, 12:38:32 PM Error: [Exception... "Component returned failure code: 0x80550007 [nsIMsgFolder.getStringProperty]" nsresult: "0x80550007 (<unknown>)" location: "JS frame :: chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2780" data: no] Source File: chrome://messenger/content/folderPane.js Line: 2782

선택된 해결법

I found the problem. The profile was originally symlinked from another location, but Thunderbird had resolved through the symlink, so the base path was stored in a bunch of places in prefs.js. After fixing the absolute paths and fixing a bunch of directory-rel entries things seem to be working again.

문맥에 따라 이 답변을 읽어주세요 👍 0

모든 댓글 (2)

more options

Most likely, you have not set some path correctly, skipped profiles.ini, or the profile locations or other path settings do not match. Did you use the instructions in the Moving Thunderbird Data to a New Computer and Profiles - Where Thunderbird stores your messages and other user data support articles?

more options

선택된 해결법

I found the problem. The profile was originally symlinked from another location, but Thunderbird had resolved through the symlink, so the base path was stored in a bunch of places in prefs.js. After fixing the absolute paths and fixing a bunch of directory-rel entries things seem to be working again.