mirror of
https://github.com/johannesjo/super-productivity.git
synced 2026-01-23 02:36:05 +00:00
fix: attempt to fix snap once more 2 #5252
This commit is contained in:
parent
ac8ebf93cf
commit
53eaaddea9
2 changed files with 19 additions and 5 deletions
|
|
@ -61,14 +61,23 @@ export const startApp = (): void => {
|
|||
const isSnap = process.platform === 'linux' && !!process.env.SNAP;
|
||||
if (isSnap && !isForceGpu) {
|
||||
log(
|
||||
'Snap: Disabling hardware acceleration to avoid Mesa driver lookup crashes (issue #5252)',
|
||||
'Snap: Disabling hardware acceleration to avoid Mesa driver access issues (issue #5252)',
|
||||
);
|
||||
log(
|
||||
'Snap: Using software rendering (llvmpipe) with snap strict confinement security',
|
||||
);
|
||||
log('Snap: Launch with --enable-gpu to attempt hardware rendering (may crash)');
|
||||
|
||||
// Disable hardware acceleration in Electron
|
||||
app.disableHardwareAcceleration();
|
||||
|
||||
// Additional command-line switches to ensure snap compatibility
|
||||
// Disable GPU completely to prevent GPU process spawn attempts
|
||||
app.commandLine.appendSwitch('disable-gpu');
|
||||
app.commandLine.appendSwitch('disable-gpu-sandbox');
|
||||
|
||||
// Disable Chromium's internal sandbox - rely on snap's strict confinement instead
|
||||
// This is the recommended approach per Snapcraft documentation for strict confinement
|
||||
// Chromium's sandbox conflicts with snap confinement causing launch failures
|
||||
app.commandLine.appendSwitch('no-sandbox');
|
||||
}
|
||||
|
||||
// Initialize protocol handling
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue