troubleshooting

Troubleshooting

• CPU-X won't start
• A label is empty
• High CPU usage
• AppImage issues

---

CPU-X won't start

• First of all, check binary permissions (do a chmod 755 if they are wrong).
• If this doesn't solve the problem, run CPU-X with --verbose argument, and read produced output in terminal. If you are confronted to a bug, please open a new issue.

---

A label is empty

• If you manually build CPU-X, check dependencies.
• CPU-X needs root privileges to run fine. Opening CPU-X as regular user will lead of blank labels. You can start the daemon to avoid to run the UI as root user (on a graphical environment, use the Start daemon button; you can read how to start the daemon without asking password).
• If none of previous cases, your hardware is not recognized by a library.

---

High CPU usage

• You can decrease refresh time with --refresh argument to avoid CPU-X high CPU usage.
• If current tab is Caches or Bench (and a benchmark is running), this is a normal behavior.

---

AppImage issues

See AppImage page.