[linux-beta] my container fig pops up in a place random in my screen.

[MarcosVeio]

Sanity checks

• [X] I have searched github.com/withfig/fig/issues and there are no duplicates of my issue
• [X] I have run fig doctor in the affected terminal session
• [X] I have run fig restart and tested again (tell us if that fixed it)

Issue Details

Description:

My container fig pops up in a place random in my screen. I Already try run fig doctor, but nothing happen.

Environment

fig-details:
  - cli-version: 1.5.0
  - desktop-version: 2.5.1
  - figterm-version: 5.2.0
hardware-info:
  - chip-id: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
  - cores: 4
  - mem: 15745.277 GB
os-info:
  - kernel: 5.15.0-48-generic
  - distro: "Ubuntu"
  - distro-version: "22.04.1 LTS (Jammy Jellyfish)"
environment:
  - shell: /usr/bin/bash
  - terminal: <unknown>
  - cwd: /home/marcos-redspark
  - exe-path: /usr/bin/fig
  - install-method: unknown
  - env-vars:
    - SHELL: /bin/bash
    - FIG_INTEGRATION_VERSION: 8
    - TERM_SESSION_ID: 21efbabd-efa1-4834-a6a2-353c534ad088
    - XMODIFIERS: @im=ibus
    - XDG_SESSION_DESKTOP: ubuntu
    - XDG_SESSION_TYPE: x11
    - FIG_WORKFLOWS_KEYBIND: ^f
    - XDG_CURRENT_DESKTOP: ubuntu:GNOME
    - FIG_TERM: 1
    - FIG_TERM_VERSION: 5.2.0
    - TERM: xterm-256color
    - FIG_PID: 276077
    - DISPLAY: :1
    - QT_IM_MODULE: ibus
    - PATH: /home/marcos-redspark/.nvm/versions/node/v16.13.2/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/home/marcos-redspark/.local/bin:/home/marcos-redspark/.fig/bin

[lephattan]

I have the same problem, the autocomplete just appears at random bottom corner of the screen. For more information, I use 2 monitors.

[MarcosVeio]

In terminal of Visual Studio Code

[miversen33]

I am experiencing the same issues on Arch.

fig-details:
  - cli-version: 1.5.0
  - desktop-version: 2.4.11
  - figterm-version: 5.2.0
hardware-info:
  - chip-id: 12th Gen Intel(R) Core(TM) i5-12500H
  - cores: 12
  - mem: 31776.629 GB
os-info:
  - kernel: 5.19.12-arch1-1
  - distro: "Arch Linux"
  - distro-build: rolling
environment:
  - shell: /usr/bin/zsh
  - terminal: <unknown>
  - cwd: /home/miversen
  - exe-path: /usr/bin/fig
  - install-method: unknown
  - env-vars:
    - DISPLAY: :0
    - FIG_INTEGRATION_VERSION: 8
    - FIG_PID: 9063
    - FIG_TERM: 1
    - FIG_TERM_VERSION: 5.2.0
    - GLFW_IM_MODULE: ibus
    - GTK_IM_MODULE: ibus
    - PATH: /home/miversen/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/miversen/.local/bin:/home/miversen/.fig/bin:/opt/containerd/bin:/opt/inkscape/bin:/opt/neovim-0.7.0/bin:/opt/neovim/bin:/opt/nextcloud/bin:/home/miversen/.local/kitty.app/bin:/home/miversen/.luarocks/bin
    - QT_IM_MODULE: ibus
    - SHELL: /bin/zsh
    - TERM: alacritty
    - TERM_SESSION_ID: b0e3ed0c-5820-4c74-8dc1-fa61e153079c
    - XDG_CURRENT_DESKTOP: KDE
    - XDG_SESSION_DESKTOP: KDE
    - XDG_SESSION_TYPE: x11
    - XMODIFIERS: @im=ibus

I noticed early on that fig complained that ibus couldn't start in wayland and needed me to run systemrunning5 or something, however I am not running wayland, I am running Plasma on X11.

Note, I am also running 2 monitors

[DennisFeldbusch]

Facing the same issue

fig-details:
  - cli-version: 1.5.0
  - desktop-version: 2.4.11
  - figterm-version: 5.2.0
hardware-info:
  - chip-id: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  - cores: 6
  - mem: 15780.445 GB
os-info:
  - kernel: 5.19.13-arch1-1
  - distro: "BlackArch Linux"
environment:
  - shell: /usr/bin/zsh
  - terminal: <unknown>
  - cwd: /home/dennis
  - exe-path: /usr/bin/fig
  - install-method: unknown
  - env-vars:
    - DISPLAY: :0
    - PATH: /home/dennis/.ebcli-virtual-env/executables:/home/dennis/.ebcli-virtual-env/executables:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin:/home/dennis/.local/bin:/usr/lib/jvm/default/bin
    - SHELL: /bin/zsh
    - TERM: screen-256color
    - XDG_SESSION_DESKTOP: qtile
    - XDG_SESSION_TYPE: x11

[MarcosVeio]

Problem resolved! I didn't notice that fig beta didn't support vscode snap version. So i removed and isntalled version not snap kkkk, and now run perfect!!!

Note, i had the same the problem in terminal by linux but it was solved by itself

[kiberOgur4ik]

have same issue

fig-details:
  - cli-version: 1.5.0
  - desktop-version: 2.4.11
  - figterm-version: 5.2.0
hardware-info:
  - chip-id: AMD Ryzen 5 3600 6-Core Processor
  - cores: 6
  - mem: 15934.633 GB
os-info:
  - kernel: 6.0.7-zen1-1-zen
  - distro: "Arch Linux"
  - distro-build: rolling
environment:
  - shell: /usr/bin/bash
  - terminal: <unknown>
  - cwd: /home/ogur4ik
  - exe-path: /usr/bin/fig
  - install-method: unknown
  - env-vars:
    - SHELL: /bin/bash
    - GLFW_IM_MODULE: ibus
    - GTK_IM_MODULE: ibus
    - TERM_SESSION_ID: 75835b1a-abd3-44f4-942b-f39499a39a6b
    - XMODIFIERS: @im=ibus
    - XDG_SESSION_DESKTOP: gnome
    - XDG_SESSION_TYPE: x11
    - FIG_WORKFLOWS_KEYBIND: ^f
    - XDG_CURRENT_DESKTOP: GNOME
    - FIG_TERM: 1
    - FIG_TERM_VERSION: 5.2.0
    - TERM: xterm-256color
    - FIG_PID: 4919
    - DISPLAY: :1
    - QT_IM_MODULE: ibus
    - PATH: /usr/local/bin:/usr/bin:/usr/local/sbin:/home/ogur4ik/.local/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/ogur4ik/.fig/bin