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

Process prioritisation

                                                           User IDs                   Group IDs

Process starter (Real)                          RUID                        GUID

Right controller (Effective)                EUID                         EGID


$ ps -lf
To see the processes with their PRiority and NIce

NICE
-20 highest priority
+20 lowest priority

$ renice +x/-x <ppid>
To increase/decrease the nice of a process.
Child processes inherit the nice of the parent ones.

PRIORITY
Priorities are 0 to 139 in which 0 to 99 for real time and 100 to 139 for users.
Deepening: https://askubuntu.com/questions/656771/process-niceness-vs-priority

Comments

Post a Comment