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

Copying files with progress monitoring

To copy while monitoring the progress with rsync:

rsync -avh --info=progress2 /src/ /dest/

Explanations:
  -a                # archive mode (recursive, preserves perms, times, ownership, etc.)
  -v                # verbose output (shows which files are being copied)
  -h                # human-readable sizes (1K, 2M, 3G instead of raw bytes)
  --info=progress2  # overall progress bar for the whole transfer

Comments

Post a Comment