Mozilla 도움말 검색

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

자세히 살펴보기

Restore previous session stopped working

  • 6 답장
  • 87 이 문제를 만남
  • 1 보기
  • 최종 답변자: Ross

more options

I have FF 7.01 and when starting up FF, always open the tabs I had been last using by clicking on the "Restore previous session" link on the FF start page. This has always worked fine but for the last two days has not worked at all. I have rebooted my PC and rebooted FF but the Restore function just will not work. I have not knowingly made any changes to FF.

Please could you help?!

Thank you.

I have FF 7.01 and when starting up FF, always open the tabs I had been last using by clicking on the "Restore previous session" link on the FF start page. This has always worked fine but for the last two days has not worked at all. I have rebooted my PC and rebooted FF but the Restore function just will not work. I have not knowingly made any changes to FF. Please could you help?! Thank you.

모든 댓글 (6)

more options

Same problem here. Already tried starting ff in safe mode with addons disabled, tried creating a new ff profile, nothing works :x.

more options

Same problem as well. So I tried restoring session using the history tab and it worked.

more options

The button that appears when I launch FF no longer (last few days) does anything, but I can go into the menu under History and it will restore.

more options

I am able to restore using the Restore link under the History tab so at least I am able to restore although obviously it would be better if the button worked on the FF start up page. I wonder why the button has suddenly stopped working for people?

more options

The Restore link under the History tab works for me but the button on the homepage does not work at all for me on two different computers. They both stopped working about the same time. I think with update 7.0.1.

글쓴이 thepriz 수정일시

more options

Well, I have now upgraded to FF 8.0 and the problem has not been resolved. Time to report it as a bug, methinks!