Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Error message: Unable to open the summary file for Inbox on cfogelman@gmail.com. Perhaps there was an error on disk, or the full path is too long.

  • 4 个回答
  • 0 人有此问题
  • 1 次查看
  • 最后回复者为 CFogelman

more options

I got this error message and don't know what to do with it. All the other subs under gmail (sent, all mail, etc) are fine. No current inbound gmail displays under "inbox," though it does in "all mail." While checking by using gmail app, everything seems fine. How can I reopen or repopulate my inbox? Thanks.

I got this error message and don't know what to do with it. All the other subs under gmail (sent, all mail, etc) are fine. No current inbound gmail displays under "inbox," though it does in "all mail." While checking by using gmail app, everything seems fine. How can I reopen or repopulate my inbox? Thanks.

所有回复 (4)

more options

If IMAP, just delete the inbox from within windows file explorer and it will repopulate.

more options

Thanks. Tried that, but the delete program (which was going for everything in the gmail folder, not just inbox) halted, messaging that the file was in use by another program, which seems implausible. I'd closed TB first, of course. Any ideas? I guess I got just delete the whole account and reinstall, but since I have a lot of marked and sorted gmail I'd rather not.

more options

I could delete, not I got just delete, in above message.

more options

Well, here's a bizarre followup. I had rebooted once, to no effect. I just rebooted again, and everything returned to normal, including the gmail inbox. So the problem, at least for now, has sorted itself. ("Go Figure", we used to say in the Bronx). Thanks for your help. Perhaps I'll be back again with the same problem or a variant, but for now at least it's solved.