BasedBased

Report a problem

The public bug tracker isn't open yet. Until it is, there's nowhere to file a report and be sure someone reads it. This page will carry the address the day there is one.

Collect the four things below anyway. Any report needs them, and gathering them often turns up the answer on its own.

What a report needs

  1. The release. The whole of cat /etc/based-release, pasted, not summarised. It names the edition, the version and the build the bug is in. On the pure editions, cat /etc/os-release.
  2. What you did. The steps, in order, starting from a fresh boot. If you can't make it happen again, say so; an intermittent bug is still a bug.
  3. What happened, and what you expected. Both. "It broke" is neither one.
  4. The log. journalctl -b -p warning for the boot it happened on, or journalctl -b -1 -p err if you had to power the machine off. A photo of the screen is fine when there's no log to get at.

Before you file it

Log in as a second, fresh user and try again. If the problem goes away, it's in your configuration rather than in the image, and Support is the better page.

If the problem is in a Debian or Ubuntu package that Based only ships, it belongs upstream. Where Based itself is at fault is the desktop we put together: the theme, the login screen, the boot splash, the installer and the first-login setup.