Skip to main content

greyline

CI PyPI Live demo License: GPL v2+

[!NOTE] Greyline is in Beta. It works and I run it daily on my linux machine, but expect bugs or breaking changes before 1.0. It was built with AI help, but with heavy guardrails and adherence to performance, battery life and industry best practices.

A live world-time desktop wallpaper for Wayland/X11 — a world map with clocks for your cities, your home city highlighted, and a day/night terminator that tracks the sun. A modern recreation of the classic IBM/ThinkPad "World Time" Active Desktop.

greyline — dark theme

Shown with the optional ThinkPad wordmark (a user-supplied logo, see Credits). The bundled default logo is Tux.

Try the live demo: greyline running in your browser (your timezone highlighted), no install needed.

greyline doesn't run a browser or a background daemon. A small Python program renders a PNG once a minute and hands it to your existing wallpaper mechanism, then exits.

Table of Contents

Features

  • Multi-timezone clocks at each city's real location, with accurate DST via the OS IANA database (zoneinfo). 12h or 24h.
  • Home city accented (dot + bold label + optional timezone-column highlight), auto-detected from your system timezone or pinned in config.
  • Day/night terminator that's seasonally correct, with discrete civil / nautical / astronomical twilight bands.
  • Vector map from public-domain Natural Earth data: crisp at any resolution, fully themeable (dark, blue, or custom), with honest zig-zag timezone boundaries, a green GMT column, and a red International Date Line.
  • Any resolution, multi-monitor, HiDPI. Each output rendered at native pixels.
  • Swappable corner logo: ships with Tux; point logo_path at your own PNG.
  • Works on any desktop, with native backends for sway, swww, hyprpaper, x11 (feh/xwallpaper), plus a generic command backend for GNOME / KDE / XFCE and anything else.
  • One-command setup: greyline init detects your desktop, writes a config, and schedules updates.
blue theme home city accented minimal, no logo, 12h
blue theme home city highlighted minimal, 12-hour

Requirements

  • OS: Linux, Wayland or X11 (the supported, tested target). Architectures: x86_64 and aarch64. Windows and macOS have beta, untested support — see Windows & macOS (beta).
  • Python ≥ 3.11, only when installing via pip/pipx/uv (the Nix package bundles its own).
  • Runtime dependencies: Pillow and tomlkit, installed automatically; plus fontconfig (fc-match) for font resolution.
  • A wallpaper mechanism for your desktop: one of the tools in the table below.
  • Scheduling: a systemd user timer (most distros) or any session autostart running greyline watch (Runit/OpenRC/s6/… — no systemd required).

greyline is distro-agnostic: install it with pipx/uv on any distribution, or via the Nix flake on NixOS. Supported desktops and what each needs:

Desktop / compositor Backend Needs
sway / SwayFX sway swaymsg
Hyprland, river, Wayfire, other wlroots swww or hyprpaper swww / hyprpaper daemon
X11 window managers x11 feh or xwallpaper
GNOME command gsettings
KDE Plasma command plasma-apply-wallpaperimage
XFCE command xfconf-query
anything else with a CLI wallpaper-setter command your own command

greyline init detects your desktop and picks the backend for you; the command-backend rows are community-verified (see Contributing).

Installation

pipx / uv (any distro, any desktop)

pipx install greyline    # or: uv tool install greyline
greyline init            # detect your desktop, write a config, schedule updates

greyline init writes a starter ~/.config/greyline/config.toml, auto-detects your compositor/desktop and picks the backend (on GNOME / KDE / XFCE it fills in the right wallpaper command for you), and (where systemd is present) installs and enables the once-a-minute user timer. No git clone, no hand-copied units.

Nix (flake + home-manager) — recommended on NixOS

# flake.nix
inputs.greyline.url = "github:cothinking-dev/greyline";

# home-manager
imports = [ inputs.greyline.homeManagerModules.default ];

services.greyline = {
  enable = true;
  backend = "sway";              # auto | sway | swww | hyprpaper | x11 | command
  fontFamily = "Aporetic Sans";  # resolved via fontconfig
  settings = {
    theme = "dark";
    format = "24h";
    twilight = { bands = true; darkness = "subtle"; };
    home = { tz = "auto"; column_highlight = true; };  # "auto" = system tz
    city = [
      { name = "Kuala Lumpur"; lat = 3.14;  lon = 101.69; tz = "Asia/Kuala_Lumpur"; }
      { name = "London";       lat = 51.51; lon = -0.13;  tz = "Europe/London"; }
      { name = "New York";     lat = 40.71; lon = -74.01; tz = "America/New_York"; }
      { name = "Tokyo";        lat = 35.68; lon = 139.69; tz = "Asia/Tokyo"; }
    ];
  };
};

Run without installing

nix run github:cothinking-dev/greyline -- --out wt.png --res 2560x1440   # writes a PNG
uvx greyline --out wt.png --res 2560x1440                                # same, via PyPI

Windows & macOS (beta)

[!WARNING] Beta and untested on real hardware. greyline is developed and tested on Linux. The Windows and macOS backends are written against each platform's documented wallpaper API but have not been run on an actual Windows or Mac desktop — only in CI (which renders the image and exercises the code, but cannot verify the wallpaper visibly changes, since CI runners are headless). The rendering itself is the same well-tested pure-Python/Pillow code as on Linux. Please open an issue to report whether it works — success or failure both help.

Known limitations: single combined desktop only (no per-monitor wallpapers yet), and no automatic scheduling — you run the update loop yourself (see below).

Install (Python ≥ 3.11; Pillow ships wheels for both OSes):

pipx install greyline      # or: pip install greyline

Run — greyline auto-detects the windows / macos backend. Update once, or loop:

greyline --list-outputs    # sanity-check detection
greyline                   # render + set the wallpaper once
greyline watch             # keep it updating (foreground; Ctrl-C to stop)

You can also force the backend explicitly with --backend windows / --backend macos, or set backend = "windows" / "macos" in the config file.

Keep it running in the background — there's no native service installer on these platforms yet, so wrap greyline watch in the OS scheduler:

  • Windows — Task Scheduler → Create Task → trigger At log on → action Start a program: greyline with argument watch. (Or drop a shortcut to greyline watch in shell:startup.)
  • macOS — a ~/Library/LaunchAgents/ing.cothink.greyline.plist launchd agent whose ProgramArguments are the path to greyline and watch, with RunAtLoad set; load it with launchctl load ~/Library/LaunchAgents/ing.cothink.greyline.plist.

Fonts: greyline uses fontconfig (fc-match) on Linux; on Windows/macOS Pillow resolves a system font automatically (Segoe UI / Helvetica), falling back to a built-in font — so labels always render, though exact typography may differ from Linux.

Usage

After greyline init, the wallpaper updates on its own. Everything else is subcommands:

greyline                          # render all outputs and apply (what the timer runs)
greyline init                     # first-time setup: config + backend + scheduling
greyline watch [--interval SEC]   # render+apply on a loop (any init system / WM)
greyline config set <key> <val>   # also: get [key] / unset <key>   (edits the config file)
greyline city add "<name>" <lat> <lon> <tz> [--home]   # also: list / remove "<name>"
greyline enable | disable | status   # manage the systemd user timer
greyline doctor                   # detected backend, outputs, session, timer
greyline --list-outputs           # show detected backend + outputs
greyline --out wt.png --res WxH   # render a PNG, no backend needed

Scheduling. On systemd, greyline init/greyline enable install a user timer that runs every minute. No systemd? Any init system or WM works; skip the timer and add greyline to your session autostart:

greyline watch    # renders + applies every minute in the foreground

Configuration

Edit config from the CLI (comments in the file are preserved) or edit the file directly:

greyline city add "London" 51.51 -0.13 Europe/London --home
greyline config set theme blue
greyline config set twilight.darkness dramatic

The shipped worldtime/default-config.toml is the documented template. Keys:

Key Values
backend auto / sway / swww / hyprpaper / x11 / command
command, resolution for the command backend (see below)
map_style vector (default) / raster (bring your own art)
theme, format dark/blue · 24h/12h
logo, logo_path, logo_invert corner logo (default: Tux)
[twilight] bands, darkness (subtle/medium/dramatic)
[home] tz (auto or IANA), column_highlight, color
[[city]] name, lat, lon, tz, optional label_side

Desktop environments (GNOME / KDE / XFCE)

On desktops that manage their own wallpaper, greyline init configures the generic command backend automatically: greyline renders a PNG and runs a command to set it as your wallpaper, with {path} (the PNG) and {output} substituted.

greyline is not a live-wallpaper engine, so you don't need swww/awww or any wallpaper daemon on GNOME — it sets a static image through the desktop's own tool (gsettings on GNOME).

Note: this replaces your desktop wallpaper; it is not an overlay. greyline re-renders and re-sets it each minute; the last image stays after greyline stops.

To set the command by hand (greyline config set command '…', or in the config file):

backend = "command"
# resolution = "2560x1440"   # optional; else largest xrandr output, else 1920x1080
# GNOME (empty-then-set defeats GNOME's same-URI cache; sets light + dark):
command = 'gsettings set org.gnome.desktop.background picture-uri "" && gsettings set org.gnome.desktop.background picture-uri "file://{path}" && gsettings set org.gnome.desktop.background picture-uri-dark "file://{path}"'
# KDE Plasma:
command = 'plasma-apply-wallpaperimage {path}'
# XFCE (the monitor segment varies — see: xfconf-query -c xfce4-desktop -l | grep last-image):
command = 'xfconf-query -c xfce4-desktop -p /backdrop/screen0/monitor0/workspace0/last-image -s {path}'

These recipes are best-effort / community-verified; the maintainers run sway and can't test them directly. If yours needs a tweak, please report it.

How it works

A scheduler runs greyline once a minute; it renders a PNG per output and hands each to the detected backend, then exits.

flowchart LR
    T["systemd timer<br/>or greyline watch"] --> G(greyline)
    CFG["config.toml<br/>cities · theme · home"] --> G
    G --> S["sun.py<br/>subsolar point<br/>+ terminator"]
    G --> V["vectormap.py<br/>Natural Earth GeoJSON"]
    S --> R["render.py<br/>compose map, clocks,<br/>terminator, labels"]
    V --> R
    R --> P["PNG per output"]
    P --> B["backend<br/>sway · swww · hyprpaper<br/>x11 · command"]
    B --> W(["desktop wallpaper"])
  • sun.py — subsolar point + terminator/twilight boundary latitudes (pure astronomy math).
  • geo.py / vectormap.py — lon/lat → pixel projection; the vector map is drawn from Natural Earth GeoJSON (supersampled for smooth coastlines).
  • render.py — composites map + overlays, then draws clocks at native resolution with smart label placement (labels pick a side to avoid overlapping each other and the edges).
  • backends/ — the only platform-specific code; everything else is portable.

Contributing

greyline is a personal passion project, built and maintained in spare time and released as free and open-source software (GPL-2.0-or-later). It's a labour of love, not a product. Issues, desktop-compatibility recipes, and pull requests are all welcome.

  • Found a bug, or a command recipe that needs tweaking on your desktop? Open an issue; there's a dedicated desktop-compatibility report template for GNOME/KDE/XFCE.
  • Run the tests with nix flake check, or pytest in the dev shell.

Credits

Code is GPL-2.0-or-later. It descends from Maxim Proskurnya's GPL "World Time Wallpaper" tribute; the concept and original artwork are © IBM/Lenovo.

The default vector map uses public-domain Natural Earth data, and the default logo is Tux (Larry Ewing / GIMP); both are cleanly redistributable. The original IBM/Lenovo ThinkPad raster art and wordmark are not bundled; map_style = "raster" and the ThinkPad logo require you to supply those files yourself (see NOTICE and docs/CREDITS.md).

Built with the assistance of AI coding tools.

Release files for greyline 0.5.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for greyline 0.5.1
File Size Uploaded
greyline-0.5.1.tar.gz 1.7 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for greyline 0.5.1
File Interpreter ABI Platform
greyline-0.5.1-py3-none-any.whl Python 3 none any Details

Total release size: 3.5 MB

Release files / greyline-0.5.1.tar.gz

Download URL greyline-0.5.1.tar.gz
Size 1.7 MB
Tags Source
SHA-256 checksum
How to use checksums
9ca7740d80004a71574bf0bf9dae53b67627784c2c9dfc836015cd18769ef890
BLAKE2b-256 checksum
How to use checksums
6870cd8f6b7ac42fa33877ee2b1bb24c383d55a4fa731dc917256826140188af
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 22, 2026.

Transparency log

Release files / greyline-0.5.1-py3-none-any.whl

Download URL greyline-0.5.1-py3-none-any.whl
Size 1.7 MB
Tags Python 3
SHA-256 checksum
How to use checksums
9ca08593b6c4934bc787743763b7d77edda0ccdfe6efc7c80986fc8d41d4162b
BLAKE2b-256 checksum
How to use checksums
e82ab244737bc8367e7c6a66b53a96231a1bbca46f48d73d083d76fc6dd5ffd7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 22, 2026.

Transparency log

Release history Release notifications | RSS feed

0.8.6

2 release files

0.8.5

2 release files

0.8.4

2 release files

0.8.3

2 release files

0.8.2

2 release files

0.8.1

2 release files

0.8.0

2 release files

0.7.3

2 release files

0.7.1

2 release files

0.7.0

2 release files

0.6.0

2 release files

0.5.3

2 release files

0.5.2

2 release files

This release

0.5.1 This release

2 release files

0.5.0

2 release files

0.4.2

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page