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

File Scripts vs Commands Scipts

If a file automates tasks or configures something without calling the main tool—even if I could run every line manually—it’s a script file, and giving it a .sh extension makes sense.

But when something grows into a real tool—a launcher, a wrapper, a utility with its own settings declared inside the script itself—it becomes a command script, and commands need no extensions.

No actual standards about all of this, however it's a commonly recognised approach.

Comments

Post a Comment