Cannot manage plugins
- App version: 0.11.5
- The output of
screenfetch:-` .o+` bodo@DEBER54-LXL007 `ooo/ OS: Arch Linux `+oooo: Kernel: x86_64 Linux 6.12.10-arch1-1 `+oooooo: Uptime: 2h 8m -+oooooo+: Packages: 1487 `/:-:++oooo+: Shell: zsh 5.9 `/++++/+++++++: Resolution: No X Server `/++++++++++++++: WM: wlroots wm `/+++ooooooooooooo/` GTK Theme: Breeze Dark [GTK3] ./ooosssso++osssssso+` Disk: 373G / 933G (43%) .oossssso-````/ossssss+` CPU: 12th Gen Intel Core i7-12700H @ 20x 4.7GHz [53.0°C] -osssssso. :ssssssso. GPU: Iris Xe Graphics :osssssss/ osssso+++. RAM: 32619MiB / 63986MiB /ossssssss/ +ssssooo/- `/ossssso+/:- -:/+osssso+- `+sso+:-` `.-/+oso: `++:. `-/+/ .` `/ - Type of installed package (Snap, AppImage, deb, rpm, pacman): AUR, pacman
Bug description I use figma-linux to develop a custom figma plugin, which is not possible in the browser version. It used to work just fine (at least until August 2024), but now it does not anymore. In particular I noticed:
- When clicking the figma icon in the top left corner of the window, nothing happens. It used to open a menu.
- There is a menu on the top right, with submenu `Plugins…" and an entry "Manage plugins…", but clicking the entry again has no effect.
I tried downgrading to 0.11.4 and clean-building 0.11.5, but no success.
In the console I see the following error:
I'm seeing the same error, Ubuntu 24.04. Has anyone seen this work on Linux?
Looking at the (minified) figma code where the error thrown, it looks like we should be using "manage-plugins" instead of "manage":
https://github.com/Figma-Linux/figma-linux/blob/d9a7a03a694464583138d7ab12fb4bc7af51bbc1/src/main/Ui/WindowManager.ts#L526
I tried changing that locally and the error is gone. Figma also switches to the main window when selecting "Mangae plugins...", but does not show the plugin ui.
I am now seeing a different exception. So it seems figma is changing more. Here is what I have gathered from their minified code:
- There needs to be a function
window.executeFullscreenEmscriptenCode, which callswindow.tsapi_initwith a context object. - That context object needs to contain a property
Fullscreen. - The
Fullscreenobject needs a methodtriggerAction, which is called with"clean-tools"as argument
Somehow this is also related to a WebASM Module, which is even harder to look at.