https://bugs.kde.org/show_bug.cgi?id=494524
--- Comment #4 from [email protected] --- (In reply to Nate Graham from comment #1) > (In reply to shibe99 from comment #0) > > If I set DRI_PRIME=1! to run firefox on my iGPU, the following happens: > > > > - Firefox launched through app menu or pinned icon works fine, shows it > > running on iGPU > > - Firefox's other actions as defined in .desktop file such as new private > > window, new window, etc do not respect this environment variable, thus > > firefox launched this way runs on my dGPU > > Unfortunately we don't have any control over this; using any of those > actions doesn't go through the .desktop file. It's all Firefox's internal > code. > > > - Most frustrating of all, if firefox is not open and I click on a link in > > some other application which launches firefox, then firefox is launched with > > dGPU (the DRI_PRIME environment variable is not passed). The same happens > > when using xdg-open http://somelink or kde-open http://somelink > > This one might be a bug we can fix. Needs to be investigates Hi, apologies for the confusion but I'm referring to the "New Private Window" action defined in the .desktop entry, not pressing New Private Window from inside firefox. The .desktop file has several Desktop Actions defined (each with their own Exec= key), and KDE does not modify environment variables for these. I've attached a screenshot to show what I'm referring to, and also my modified .desktop file which makes it so that the DRI_PRIME environment variable applies to all these actions -- You are receiving this mail because: You are watching all bug changes.
