Figma canvas renders completely blank

[azuredusk10]

• App version: 0.11.3

• The output of screenfetch:
  OS: Fedora 39 ThirtyNine
  Kernel: x86_64 Linux 6.6.14-200.fc39.x86_64
  Uptime: 57m
  Packages: 3146
  Shell: bash 5.2.26
  Resolution: 3840x2160
  DE: GNOME 45.2
  WM: Mutter
  WM Theme: Adwaita
  GTK Theme: Adwaita [GTK2/3]
  Icon Theme: Adwaita
  Font: Cantarell 11
  Disk: 1.3T / 1.9T (68%)
  CPU: 12th Gen Intel Core i5-1240P @ 16x 4.4GHz [65.0°C]
  GPU: Mesa Intel(R) Graphics (ADL GT2)
  RAM: 13200MiB / 31802MiB

• Type of installed package (Snap, AppImage, deb, rpm, pacman):
  Flatpak

Bug description
When opening any file, none of the elements are rendered. Only the file background colour and any comments on the file are shown.

The dashboard displays correctly, however.

Screenshots

Additional context
This problem has occurred for about 2 months

[shelvaldes]

Same issue here. Both Figma and figjam.

OS: Fedora 39 ThirtyNine
Kernel: x86_64 Linux 6.6.14-200.fc39.x86_64
Uptime: 1h 13m
Packages: 2171
Shell: pkcommand-not-found
Resolution: No X Server
GNOME 45.2
WM: Mutter
WM Theme: Adwaita
GTK Theme: Adwaita [GTK2/3]
Icon Theme: Adwaita
Font: Cantarell 11
Disk: 34G / 465G (8%)
CPU: Intel Core i5-5350U @ 4x 2.9GHz [79.0°C]
GPU: Mesa Intel(R) HD Graphics 6000 (BDW GT3)
RAM: 5223MiB / 7841MiB

[shelvaldes]

installed via rpm package

[DominickVale]

Same happening to me. These are my logs:

[175089:0209/151607.649527:ERROR:gl_utils.cc(398)] [.WebGL-0x136006f30700] GL_INVALID_OPERATION: Feedback loop formed between Framebuffer and active Texture. [175089:0209/151607.649685:ERROR:gl_utils.cc(398)] [.WebGL-0x136006f30700] GL_INVALID_OPERATION: Feedback loop formed between Framebuffer and active Texture. [175089:0209/151607.649779:ERROR:gl_utils.cc(398)] [.WebGL-0x136006f30700] GL_INVALID_OPERATION: Feedback loop formed between Framebuffer and active Texture. [175089:0209/151607.649853:ERROR:gl_utils.cc(398)] [.WebGL-0x136006f30700] GL_INVALID_OPERATION: Feedback loop formed between Framebuffer and active Texture. [175089:0209/151607.649923:ERROR:gl_utils.cc(398)] [.WebGL-0x136006f30700] GL_INVALID_OPERATION: Feedback loop formed between Framebuffer and active Texture. [175089:0209/151607.649994:ERROR:logger.cc(46)] Too many GL errors, not reporting any more for this context. use --disable-gl-error-limit to see all errors. [175089:0209/151609.082461:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!

Host: XMG CORE (REN/E21) Standard
Kernel: 6.7.4-arch1-1
CPU: AMD Ryzen 7 4800H with Radeon Graphics (16) @ 2.900GHz
GPU: AMD ATI Radeon RX Vega 6
dGPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q

In my case, switching to my dGPU solves it. ( prime-run figma-linux )

edit: apparently i lied. It only works randomly half the time. The other half it hangs at the loading screen.

[luna-skye]

Very similar issue here with the same log errors as above, directly after a large Arch system update.
Happens on both bin and git AUR packages

I've also tried various chromium flags, none of which seem to resolve the issue
use-vulkan
ignore-gpu-blacklist
enable-gpu-rasterization
enable-unsafe-webgpu

Figma itself works perfectly fine through up-to-date Firefox (122.0.1) and Chrome (121.0.6167.160)

Specific Behavior
When opening a FigJam file it's always completely blank, however Design files often display broken and unpredictable visual artifacts, which seem to be mangled renderings of the file itself.

Specs:
OS: EndeavourOS Linux x86_64
Host: MS-7C37 1.0
Kernel: 6.7.4-arch1-1
DE: Plasma 5.27.10
CPU: AMD Ryzen 9 3900X (24) @ 3.800GHz
GPU: AMD Radeon RX 7900 XT

Result of the chrome://gpu page
about-gpu-2024-02-12T23-24-05-566Z.txt

[luna-skye]

Downgrading to 0.11.2 seems to have fixed this in my case.

I know it's been closed and should have been fixed with the two bumps in Electron version at 5602de4 and da70945, resolving the issue in 0.11.3, but I'm wondering if #354 could be related to this somehow.

[Phosphorus-M]

Same problem, I'm using the flatpak version.

[SoyDiego]

Same problem here (MANJARO). In my case all black maybe for my dark mode, but I changed the themes and always I can see black.

OS: Manjaro Linux x86_64 
Kernel: 6.6.16-2-MANJARO 
Uptime: 2 hours, 43 mins 
Packages: 1229 (pacman), 12 (flatpak), 12 (snap)
Shell: zsh 5.9 
Resolution: 3440x1440 
DE: Xfce 4.18 
WM: Xfwm4 
WM Theme: Matcha-sea 
Theme: Matcha-dark-sea [GTK2/3] 
Icons: Papirus-Maia [GTK2], Adwaita [GTK3] 
Terminal: kitty 
CPU: 13th Gen Intel i7-13700K (24) @ 5.300GHz 
GPU: Intel Raptor Lake-S GT1 [UHD Graphics 770] 
Memory: 12408MiB / 31838MiB 

[Besuf]

The same issue is happening in Fedora38. Any updates?

[azuredusk10]

For Flatpak users who need a workaround until this is fixed, here's the terminal command to downgrade to Figma for linux v 0.11.2, the latest version where the canvas appears to be rendering correctly.

sudo flatpak update --commit=c161b0f7054c56e21ab68ef22c09ca722b7518658c21c286aafcdf2ce57b490c io.github.Figma_Linux.figma_linux

Not sure what the command will be for other package formats like Snap

[Besuf]

For Flatpak users who need a workaround until this is fixed, here's the terminal command to downgrade to Figma for linux v 0.11.2, the latest version where the canvas appears to be rendering correctly.

sudo flatpak update --commit=c161b0f7054c56e21ab68ef22c09ca722b7518658c21c286aafcdf2ce57b490c io.github.Figma_Linux.figma_linux

Not sure what the command will be for other package formats like Snap

I installed but didn't help I'm getting the same issue :(

[darionco]

this just happened to me after a large Arch update, the way I fixed it was by closing the app then deleting the settings folder:

rm -rf ~/.config/figma-linux/

it will ask you to login again after reopening, but figma functionality will be back.

[raluvy95]

Deleting settings folder worked for me.

I wonder how did the configuration folder managed to corrupt the canvas area?

[red3nzo]

@darionco Your solution worked, this happened to me after a Fedora 39 update.

[azuredusk10]

this just happened to me after a large Arch update, the way I fixed it was by closing the app then deleting the settings folder:

rm -rf ~/.config/figma-linux/

it will ask you to login again after reopening, but figma functionality will be back.

This also worked for me. Thank you!