How to Fix Ubuntu Automatic Suspend During a Long Download

You start a big download before bed, wake up, and find it stopped at forty percent. The screen shows a message about automatic suspend, and Ubuntu went to sleep right in the middle of the job. This is not a broken download manager or a faulty network. It is Ubuntu’s power saving doing exactly what it was told to do, because a download does not count as activity.

The good news is that this is easy to fix, and you have several levels of fix to choose from. You can turn automatic suspend off completely, keep the computer awake only while a download runs, or use a simple terminal tool that holds sleep away until a command finishes. This guide explains why it happens first, then walks through each method.

Quick Answer

Open Settings, go to Power, and set Automatic Suspend to Off, or set its delay longer than your download needs. For a temporary fix, run your download with gnome-session-inhibit or start it after running systemd-inhibit, which tells Ubuntu not to suspend while that command is running. A downloading program alone does not stop the automatic suspend timer, because Ubuntu only watches for keyboard, mouse, and certain media activity.

Why Ubuntu Suspends During Downloads

Ubuntu suspends based on inactivity, and its idea of inactivity is simple. If nobody presses keys, moves the mouse, or plays media through a player that reports itself properly, the idle timer keeps counting. When it reaches the limit you set, the system suspends to save power, especially on laptops.

A browser download, a torrent, or a large file copying over the network may keep the disk and network busy for hours, but most download tools do not tell the power manager to stay awake. So from Ubuntu’s point of view, the machine is idle even though it is clearly working hard.

This behaviour is deliberate and saves power when you genuinely walk away. The problem is the mismatch between a machine busy downloading and a system that sees nobody touching it. The official Ubuntu power management documentation explains these settings.

Method 1: Turn Off or Delay Automatic Suspend in Settings

This is the right fix if you regularly leave long jobs running and simply want the machine to stay on.

1. Open Settings from the top-right system menu or the applications list.
2. Select Power in the left sidebar.
3. Find the Automatic Suspend option. On many versions it appears as a row you click to open separate choices for when plugged in and when on battery.
4. Set Automatic Suspend to Off for plugged-in use. If you prefer a delay instead, choose a long option such as two hours or more.
5. Also check the Screen Blank setting above it. A blank screen is fine and saves power without stopping downloads, so you can leave that short.
6. Close Settings. The change applies immediately and there is nothing to save manually.

On a laptop, be more careful with the battery setting. Turning suspend off on battery can leave you with a flat battery and a lost download if the power cable comes out. A sensible setup for many people is Off when plugged in and a longer delay, not Off, when on battery.

Method 2: Change the Setting From the Terminal

If you prefer the terminal, or you are setting up several machines, the same options are available through gsettings. These commands change the same settings the Settings window controls.

1. Check the current suspend delay with gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type.
2. Disable automatic suspend while plugged in: gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'.
3. Do the same for battery only if you are sure you want it: gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing'.
4. To bring back suspend later, set the value back to 'suspend' in the same commands.
5. You can also control the idle delay in seconds with gsettings set org.gnome.session idle-delay 0, where zero means the session does not mark itself idle for screen blanking. Use this carefully, because it affects screen behaviour too.

Terminal changes take effect straight away. Open Settings afterwards and confirm the Power page shows what you expect, so there is no surprise later.

Method 3: Keep Ubuntu Awake Only While a Download Runs

Turning suspend off forever wastes power on all the nights you are not downloading anything. A smarter approach is to block sleep only for the length of one job. Ubuntu includes tools for exactly this.

Using systemd-inhibit

1. Start your download command through the inhibitor: systemd-inhibit --what=idle:sleep wget https://example.com/largefile.iso, using your real download command and address.
2. Leave that terminal open. While the command runs, Ubuntu will not idle-suspend or sleep.
3. When the download finishes, the inhibitor ends automatically and normal power saving returns.
4. To check what is currently blocking sleep, run systemd-inhibit --list in another terminal.

Using a graphical inhibitor tool

If your downloads happen in a browser, a caffeine-style indicator can hold the system awake with one click. Turn it on before the download and off afterwards.

Our overview of Ubuntu power management settings and how they work together explains how these inhibitors interact with the main Power settings.

Method 4: Check Your Download Tool’s Own Settings

Some download tools have a built-in option to prevent sleep or to shut down only after downloads complete, though the wording varies. Torrent clients often include a setting to inhibit sleep while transfers are active, and some download managers can run a command when finished.

• Look in your torrent or download program’s preferences for power, sleep, or inhibit options.
• Enable any option that keeps the system awake while transfers are active.
• If the tool can run a command on completion, you can pair that with a notification so you know the job finished.
• Remember that browser downloads usually have no such option, which is why Methods 1 and 3 matter most for browser users.

How to Confirm the Fix Worked

Do not wait for a real overnight download to find out. Test quickly:

1. Temporarily set a short suspend delay, such as five minutes, if you changed settings by delay.
2. Start a harmless long download or a long-running command through your chosen inhibitor.
3. Leave the machine untouched past the delay time.
4. Confirm the machine stayed awake and the job kept running, then restore your preferred long-term settings.

You can also review what happened last time with the system journal. Running journalctl -b -1 | grep -i suspend shows suspend-related entries from the previous boot, which helps confirm whether suspend, and not a network drop, stopped your download.

Common Mistakes and Useful Tips

• Confusing screen blank with suspend: A dark screen does not stop downloads. Only suspend and shutdown do. You do not need to keep the screen on.
• Changing only the battery setting: Most overnight downloads happen while plugged in, so check the plugged-in, or AC, setting first.
• Forgetting a second timer: Some laptops also have BIOS or firmware sleep timers. If Ubuntu settings look right but the machine still sleeps, check the firmware setup too.
• Leaving suspend off forever by accident: After a one-off big download, set your normal delay back so the machine saves power again.
• Blaming the network: If the download resumes fine and the journal shows a suspend at the right time, power settings were the cause, not your connection.
• Closing the laptop lid: Lid closing can trigger suspend separately from the idle timer. If you download with the lid shut, you need to handle lid behaviour as its own setting.

The GNOME settings documentation on what happens when you suspend your computer is also worth reading if you want to understand the difference between suspend, hibernate, and screen blank.

Conclusion

Ubuntu suspending during a download is normal power saving meeting a job the system cannot see. Fix it at the level that suits you: turn automatic suspend off or give it a longer delay for a permanent change, use systemd-inhibit to protect a single download, or enable your download tool’s own stay-awake option. Test the fix with a short delay before your next big overnight job, and you will wake up to a finished download instead of a half-done one.

Frequently Asked Questions

Why does Ubuntu say automatic suspend even though I was downloading?

Because the idle timer measures input and certain media activity, not network or disk activity. Most download tools do not register an inhibitor, so Ubuntu treats the machine as unused and suspends when the timer ends, even while data is still moving.

Will turning off automatic suspend harm my laptop?

No, the computer can run normally without suspending. The downsides are higher power use and, on battery, the risk of running the battery flat. For a plugged-in desktop or laptop, turning it off is safe. Just remember heat and fans will keep working while it stays on.

How do I keep Ubuntu awake for just one command?

Put systemd-inhibit --what=idle:sleep in front of the command in a terminal. The block lasts only while that command runs, and normal suspend behaviour returns as soon as it finishes. Use systemd-inhibit --list to see active blocks.

My download still stops, but the screen is only blank. What else could it be?

If the machine is truly only blanking the screen, the download should continue. Check whether the machine actually suspended by looking for a login prompt or checking the journal, and also test your network connection and the download server, which can drop long transfers for their own reasons.

Does closing the lid use the same setting?

No. Lid-close behaviour is handled separately from the idle suspend timer, mainly through logind settings. A laptop can have automatic suspend off and still sleep when you close the lid, so treat the two as separate fixes.