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

Accessing partitions by label

When I run something like:

sudo e2label /dev/sda2 LCS_RAW

I’m just giving the filesystem a name tag: LCS_RAW.
After that, Linux (via udev) automatically creates a shortcut:

/dev/disk/by-label/LCS_RAW -> ../../sda2

I didn’t create that path myself. Linux did. It’s a symlink that always points to the right partition, even if the kernel decides the device is /dev/sdb2 tomorrow instead of /dev/sda2.

The nice part: I can use this label path anywhere I would use the raw device:

# Mount by label (more stable than /dev/sdX)
sudo mount /dev/disk/by-label/LCS_RAW /mnt/LCS

This works the same as mount /dev/sda2, but doesn’t break when device numbers change.

Important detail:
/dev/disk/by-label/LCS_RAW is not a directory, it’s a device file. I don’t cd into it. I mount it, then access the filesystem via the mountpoint:

sudo mount /dev/disk/by-label/LCS_RAW /mnt/LCS
cd /mnt/LCS



Short version:

  1. Label the partition → e2label /dev/sdXn NAME.
  2. Linux auto-creates /dev/disk/by-label/NAME.
  3. Use that path for mounting and scripts instead of /dev/sdXn for a more robust setup.

Comments

Post a Comment