Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Run firefox from cron

  • 1 trả lời
  • 3 gặp vấn đề này
  • 8 lượt xem
  • Trả lời mới nhất được viết bởi pj11

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 ?

Tất cả các câu trả lời (1)

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?