Mozilla 도움말 검색

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

자세히 살펴보기

Updated to 39.5, now getting "Live bookmark feed failed to load"

  • 6 답장
  • 3 이 문제를 만남
  • 3 보기
  • 최종 답변자: Meatballs

more options

Updated to 39.0 Beta 5, and now in my Latest Headlines toolbar bookmark I get "Live bookmark feed failed to load". Right-clicking and clicking 'Reload Live Bookmark' does nothing. This has happened before after certain updates, and seems only to be put right after other, subsequent updates.

Updated to 39.0 Beta 5, and now in my Latest Headlines toolbar bookmark I get "Live bookmark feed failed to load". Right-clicking and clicking 'Reload Live Bookmark' does nothing. This has happened before after certain updates, and seems only to be put right after other, subsequent updates.

모든 댓글 (6)

more options

hi, could you try to replicate this behaviour when you launch firefox in safe mode once? (this is just for testing purposes and not a general solution)

Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems

more options

The problem does not occur when FF is launched in safe mode. I've just updated my extensions, restarted FF, and the problem remains. I should add, my 'Latest Headlines' bookmark was working fine with these same extensions prior to updating to 39.0 Beta 5.

글쓴이 Meatballs 수정일시

more options

could you try narrowing it down to the extension which is interfering here, by disabling them one-by-one/in batches depending on how many you have? afterwards it would probably be helpful to inform the addon developer about this...

more options

Right, having repeated the process several times, I can say that it's the HTTPS Everywhere extension causing the problem.

more options

ok thanks, so this probably isn't a general conflict with live bookmarks and https everywhere but only with this particular rss feed which gets "upgraded" to https but doesn't work for some reason. can you create an exception for that one page in the https-everywhere settings?

more options

I'm reading up on that at the homepage but it's not so easy, it seems to involve writing an XML file....

I suppose for the moment we can consider this issue settled- the problem has been isolated, though not fixed- and I'll report back if I come up with a solution.

Thank you so much for your time Phillipp, you've been most helpful.