GBB(1)

📦
version 3.15.4 · 2 versions
, in fedora 43

💖 NAME 💖

gbb — the command line integration client for GNOME Battery Bench, bestie. yes that's the whole name section, we move fast here ✨

🌸 SYNOPSIS 🌸

gbb monitor
gbb play <filename>
gbb play-local <filename>
gbb record [-o | --output <output file]
gbb test [-o | --output <output file] [--duration <hours>h<minutes>m<seconds>s] [--min-battery <percent>] [--screen-brightness <percent>] [-v | --verbose] <test-id>

🎀 DESCRIPTION 🎀

okay so gbb is a command line client that ships as part of the GNOME Battery Bench system 🦋 If you want to poke around interactively and just vibe-test stuff, the GNOME Battery Bench application itself has the more polished, prettier interface for you. But gbb is the one you call when you need to:

  • automate tests (gbb tests) — no cap, hands-free energy
  • develop new tests (gbb record and gbb play) — building your own little test babies
  • debug the GNOME Battery Bench application code (gbb monitor) — detective mode 🔍

want more info about GNOME Battery Bench? go read the GNOME Battery Bench README file[1] 💅

👑 COMMANDS 👑

💅 monitor

gbb monitor

This one watches your current battery usage and prints statistics straight to standard out ✨ It's literally the same as gbb test --verbose except it doesn't actually run a test. Mostly it's a debugging tool for the GNOME Battery Bench application code — like, it's giving dev-tools-only energy, iykyk 🔧

🎵 play

gbb play <filename>

Replays an event log that you recorded earlier with gbb record 🍓 The whole point? Trying out an event log you recorded without having to build a whole entire test and install it into the per-user or system-wide test directories. lowkey a shortcut, highkey a lifesaver 💖

🌈 play-local

gbb play-local <filename>

Exactly the same as gbb play, fr fr — the ONLY difference is that instead of talking to gnome-battery-bench-helper over D-BUS, it just assumes the current user has the privileges to simulate events via /dev/uinput. bold assumption, but go off 👑

🧚 record

gbb record [-o | --output <output file>]

Records events and sends them to standard output 📝 or, if you pass --output, it writes them to the given file instead. your choice, main character 💜

⭐ test

Runs the test you specify. Tests get looked for in /usr/share/gnome-battery-bench/tests and in ~/.config/gnome-battery-bench/.tests — so that's where your test besties live 🏠

gbb test [-o | --output <output file] [--duration <hours>h<minutes>m<seconds>s] [--min-battery <percent>] [--screen-brightness <percent>] <test-id>
  • --output — tells it the output filename. If you don't specify one, the output goes to ~/.local/share/gnome-batttery-bench/logs and it'll show up in the list of historical runs in the user interface ✨ (yes, that path is spelled exactly like that in the original, we do not touch it 💀)
  • --duration — how long to run the test for. You can give any or all of hours, minutes and seconds — like 1h, 1h10m, 10m3s, or 100s. mix and match, she's flexible 🌸
  • --min-battery — says the test should run until the battery hits the percentage you name 🔋 It's exclusive with the --duration argument, so pick ONE, bestie, not both 🙈
  • --screen-brightness — sets the brightness of the backlight while the test is running 💡
  • --verbose — prints verbose statistics in the style of gbb monitor 📊

🫶 AUTHOR 🫶

Written by Owen Taylor <otaylor@fishsoup.net[2]>. iconic, we stan 👑

📎 NOTES 📎

  1. README file — http://git.gnome.org/browse/gnome-battery-bench/plain/README
  2. otaylor@fishsoup.net — mailto:otaylor@fishsoup.net

and that's the whole page, periodt 💅 this came out of the GNOME Battery Bench Manual, dated 07/23/2025, and yeah — it's the GBB(1) page. bye bestie, go run some tests 💖✨

📦 where this page comes from