Mozilla 도움말 검색

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

자세히 살펴보기

Calendar subscribes to my Google Calendar, but doesn't show any events.

  • 1 답장
  • 1 이 문제를 만남
  • 27 보기
  • 최종 답변자: Kevin Carder

more options

Using TB in Windows 10. This has been happening for a couple of versions of TB, Lightning, and Provider. I choose "New Calendar" and subscribe to the particular Google calendar that I want to add, then click Next. I can see the events briefly show up in the monthly calendar pane, but they almost immediately disappear. I can still see them stack up in the "All Events" pane, until I click "Finish." Then all the events in the "All Events" pane also disappear, and I'm left with no events in my calendar. No amount of syncing, unsubscribing and resubscribing, or uninstalling and reinstalling Lightning and/or Provider seems to fix this.

I am happy to provide whatever information anyone might need to help me with this.

Using TB in Windows 10. This has been happening for a couple of versions of TB, Lightning, and Provider. I choose "New Calendar" and subscribe to the particular Google calendar that I want to add, then click Next. I can see the events briefly show up in the monthly calendar pane, but they almost immediately disappear. I can still see them stack up in the "All Events" pane, until I click "Finish." Then all the events in the "All Events" pane also disappear, and I'm left with no events in my calendar. No amount of syncing, unsubscribing and resubscribing, or uninstalling and reinstalling Lightning and/or Provider seems to fix this. I am happy to provide whatever information anyone might need to help me with this.

선택된 해결법

For anyone following along, I deleted all the files in my profile that Lightning might use. It seems that permissions.sqlite was the one that actually fixed my issue.

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

모든 댓글 (1)

more options

선택된 해결법

For anyone following along, I deleted all the files in my profile that Lightning might use. It seems that permissions.sqlite was the one that actually fixed my issue.