Open karlemilnikka opened 1 year ago
Hey @karlemilnikka, thank you for your report. We are aware of the issue and are working on addressing the problem.
Until the bug is fixed, you can manually start the bridge with software rendering enabled:
/Applications/Proton\ Mail\ Bridge.app/Contents/MacOS/Proton\ Mail\ Bridge --software-renderer &
Is there any progress on this issue? Thanks!
I would recommend checking if the issue still persists in v3.4.
v3.4.2 still triggers a change to the dedicated GPU on my MacBook Pro.
Unfortunately, it seems that is a Qt6 issue rather than a bridge issue.
If you want, you can force the use of the software rendered by executing the following snippet in the terminal:
/Applications/Proton\ Mail\ Bridge.app/Contents/MacOS/Proton\ Mail\ Bridge --set-software-renderer
Unlike the previous suggestion this change will be remembered between runs of the bridge.
Running Proton Mail Bridge 3.0.17 in the background makes macOS on an Intel MacBook Pro with discrete graphics switch to the discrete graphics (in my case Radeon Pro Vega 20). As soon as I fully close the application, macOS switches back to the integrated graphics (in my case Intel UHD Graphics 630).
This wasn’t an issue with the last stable version of Proton Mail Bridge 2.x.
Expected Behavior
MacOS shouldn’t switch to discrete graphics since there’s no need for it.
Current Behavior
MacOS switches to discrete graphics, draining the battery.
Steps to Reproduce
Version Information
Proton Mail Bridge 3.0.17 macOS Ventura 13.2.1 (22D68)