KDE Plasma + Brave on Debian

  This is the “how do I make Brave do what I want” note --- especially when Brave profile UI is broken and KDE is strict about .desktop launchers. 1) Know what you’re running. Check where Brave comes from. which brave-browser If it returns /usr/bin/brave-browser , you’re on the APT-installed build (good, predictable). Also note that on Debian you often have both commands available. brave-browser is commonly a wrapper. brave-browser-stable is commonly the actual binary. 2) Where Brave stores its data. Default Brave user-data root (APT install). ~/.config/BraveSoftware/Brave-Browser/ If you only see Default/ , then you effectively have a single Brave “profile” in that directory. 3) Multiple isolated Brave sessions without Brave profiles. This is the clean workaround: run separate user-data directories . Create a new isolated environment. mkdir -p ~/.config/BraveSoftware/Brave-RDT Launch Brave using that directory. brave-browser-stable --user-data-dir= ...
0

CPU(s) load average

The load average is the average of the CPU load in a given period of time. It takes into account processes that are:

  • Actively running on a CPU
  • Considered runnable, but waiting for a CPU to become available
  • Sleeping: i.e. waiting for some kind of resource (typically, I/O) to become available

$ w
$ top (also shows real-time processes)
$ uptime

The CPU load is summarised in a line with 3 values which are 0.00 to 1.00. Translated in percentages 0% to 100%. If more than 1.00, the CPU is overloaded. If it's too high, there is probably some process in a non-responding state.

  • The first value is related to the last minute
  • The second value is related to the last 5 minutes
  • The first value is related to the last 15 minutes

Comments

Post a Comment