树莓派通过crontab开机启动GUI Jar程序失败问题求助

Got it, let's break down why your GUI Jar works manually and with scheduled cron jobs but fails on @reboot, then fix it step by step.

The Root Cause #

When cron runs @reboot, it executes before the X11 desktop environment (like Raspberry Pi OS's Pixel) has fully initialized. Even if you set DISPLAY=:0, cron doesn't have access to the MIT-MAGIC-COOKIE stored in your user's ~/.Xauthority file—this cookie is what authenticates your session to the X server, which is exactly why you're seeing that error. Non-GUI Jars work because they don't need to communicate with the X server at all.

Solution 1: Add a Delay to Wait for X to Start #

The simplest quick fix is to add a sleep command to give the desktop environment time to load before launching your Jar. Modify your crontab line to:

@reboot sleep 30 && DISPLAY=:0 XAUTHORITY=/home/pi/.Xauthority /usr/bin/java -jar /home/pi/Downloads/GUI1.jar > /home/pi/Downloads/cron.log 2>&1

• Adjust the sleep 30 value (try 20 or 40 if 30 doesn't work) based on how long your Pi takes to boot to the desktop.
• We're explicitly setting XAUTHORITY here to point to your user's cookie file, which cron doesn't pick up by default.

Solution 2: Explicitly Load the X Authority Cookie #

If delaying isn't reliable (some Pi's boot faster or slower), you can directly reference the cookie file to ensure cron uses the correct authentication token. Update your crontab entry to:

@reboot export DISPLAY=:0 && export XAUTHORITY=/home/pi/.Xauthority && /usr/bin/java -jar /home/pi/Downloads/GUI1.jar > /home/pi/Downloads/cron.log 2>&1

This removes guesswork about boot timing by explicitly passing the required authentication data to the Java command.

Solution 3: Use a Desktop Autostart Entry (Most Reliable for GUI Apps) #

Cron is designed for background tasks, but GUI apps are better managed through the desktop environment's autostart system. Here's how to set it up:

1. Create a new .desktop file in the autostart directory:

   nano ~/.config/autostart/gui1-jar.desktop
   

2. Paste this content into the file:

   [Desktop Entry]
   Type=Application
   Name=GUI1 Jar
   Exec=/usr/bin/java -jar /home/pi/Downloads/GUI1.jar
   Terminal=false
   Hidden=false
   Comment=Starts my GUI Jar on desktop login
   

3. Save and exit (Ctrl+O, Enter, Ctrl+X).

This method guarantees your app runs only after you've logged into the desktop, so all X server environment variables and authentication cookies are already available. No more timing issues or cookie errors.

Why Your Test Cases Worked #

• Manual execution: You're already logged into the desktop, so DISPLAY and XAUTHORITY are set correctly in your terminal session.
• Scheduled cron jobs: By the time the scheduled time rolls around, the desktop is fully loaded, so cron can access the X server with the DISPLAY=:0 flag.
• @reboot: Cron runs too early, before the X server is ready to accept authenticated connections.

内容的提问来源于stack exchange，提问作者Mandeep