Restoring a GNOME 3 Session: A Developer’s Guide

GNOME can automatically restore your session—reopening all applications and windows that were running when you last logged out. This differs from autostart scripts, which launch specific programs on every login regardless of what was running before.

Automatic Session Restoration

To enable automatic session restoration in GNOME:

1. Open Settings → General (or search “Session” in Activities)
2. Look for Automatic Problem Reporting or similar session options
3. Enable the option to automatically restore your session on login

Alternatively, use dconf from the command line:

dconf write /org/gnome/gnome-session/auto-save-session true

Verify the setting:

dconf read /org/gnome/gnome-session/auto-save-session

GNOME will now save your session state when you log out and restore it on the next login. This includes open windows, workspace layout, and application state—though individual apps may not preserve internal state (like file positions or unsaved documents).

Manual Session Management

For finer control, you can manage sessions through the Session and Startup application if available on your distribution. Some GNOME variants still provide gnome-session-properties, though this has been largely replaced by dconf settings in modern GNOME releases.

Limitations and Considerations

Session restoration doesn’t guarantee that:

• Unsaved work in applications will be preserved
• Network connections or temporary resources will remain active
• All application state will be restored exactly as it was

Some applications explicitly disable session restoration for stability reasons. If an app consistently fails to restore, check its preferences or file a bug report.

Using Autostart Instead

If you prefer more reliable control over what starts at login, create an autostart .desktop file instead:

mkdir -p ~/.config/autostart

Create ~/.config/autostart/myapp.desktop:

[Desktop Entry]
Type=Application
Name=My Application
Exec=/usr/bin/myapp
X-GNOME-Autostart-enabled=true

This approach is more predictable than session restoration and works across different login sessions.

Workspace Persistence

GNOME also attempts to remember workspace layouts. To ensure workspaces are restored correctly, use:

dconf write /org/gnome/shell/extensions/dash-to-dock/dock-fixed false

This allows the dock/taskbar to adapt to your restored layout rather than forcing a fixed configuration.

Quick Reference

This article covered the essential concepts and commands for the topic. For more information, consult the official documentation or manual pages. The key takeaway is to understand the fundamentals before applying advanced configurations.

Practice in a test environment before making changes on production systems. Keep notes of what works and what does not for future reference.

Additional Tips and Best Practices

When implementing the techniques described in this article, consider these best practices for production environments. Always test changes in a non-production environment first. Document your configuration changes so team members can understand what was modified and why.

Keep your system updated regularly to benefit from security patches and bug fixes. Use package managers rather than manual installations when possible, as they handle dependencies and updates automatically. For critical systems, maintain backups before making any significant changes.

Quick Verification

After applying the changes described above, verify that everything works as expected. Run the relevant commands to confirm the new configuration is active. Check system logs for any errors or warnings that might indicate problems. If something does not work as expected, review the steps carefully and consult the official documentation for your specific version.