Avatar for Username

Mozilla 도움말 검색

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

Learn More

이 쓰레드는 보존되었습니다. 만약 도움이 필요하시면 새로운 질문을 올려주세요.

Run firefox from cron

  • 1 답장
  • 3 이 문제를 만남
  • 4 보기
  • 최종 답변자: pj11

ecornely
ecornely
more options

Hello,

I’m using firefox-dev under debian linux and since last updates my cron script that was supposed to open a certain url in firefox at a regular schedule stopped working.

I do export DISPLAY=:0 than run firefox $url and all was fine previously but now I always received a message : “Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile.”

You can easily reproduce by running : sudo -u $(whoami) /path/to/firefox-dev/firefox https://www.google.com

Can somebody explain what is checked by firefox and why it consider it is not responding instead of just open my url in a new tab ?

Hello, I’m using firefox-dev under debian linux and since last updates my cron script that was supposed to open a certain url in firefox at a regular schedule stopped working. I do export DISPLAY=:0 than run firefox $url and all was fine previously but now I always received a message : “Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile.” You can easily reproduce by running : sudo -u $(whoami) /path/to/firefox-dev/firefox https://www.google.com Can somebody explain what is checked by firefox and why it consider it is not responding instead of just open my url in a new tab ?

모든 댓글 (1)

pj11
pj11
more options

I have the same problem. Here is the line from my crontab: 

   0   5    *   *   *   DISPLAY=:0.0 /usr/bin/firefox -new-window https://apod.nasa.gov/apod/astropix.html

It started just a month or two ago. It's hard to search for since there is more than a decade of results with the same error message but some different cause. The key difference here is running it from cron (or sudo as shown above for easier reproducibility). Perhaps because it's a non-login shell?