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

Environment variables

Most common user variables:

$HOME
Points to the users' home directory

$PATH
Points to the directories the shell needs to look at to execute a command or script when you enter it in the command line

  • $ export PATH=$HOME/bin:$PATH
    Adds the directory $HOME/bin
  • $ echo $PATH
    Lists the directories $PATH points to
In this link the difference between
$ PAH=directory-path-1:directory-path-2:directory-path-3 (etc)
and
$ export PATH=directory-path:$PATH

$SHELL
Points to the user's default command shell

$PSI
Your current Prompt Statement. There are 4 PSs in total.
Guide to modify the $PSx


Commands

To show a list of the current variables:
  • env
  • set
  • printenv

Comments

Post a Comment