Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Run firefox from cron

  • 1 Antwort
  • 3 haben dieses Problem
  • 8 Aufrufe
  • Letzte Antwort von 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 ?

Alle Antworten (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?