Flutter inspector using embedded DevTools is resized and moved (linux)

So this is happening to me in Ubuntu right now when trying to use the Flutter Inspector with a sample app in a Pixel emulator. You’ll see the inspector with its layout explorer gets in the middle of the window instead of its intended place at the top right under the tab:

The view mode in the gear is at its default “Dock pinned”.

Android Studio 4.2 Build #AI-202.7660.26.42.7322048, built on April 29, 2021 Runtime version: 11.0.8+0-b944-P17168821 amd64 VM: OpenJDK 64-Bit Server VM by N/A Linux 5.8.0-56-generic GC: G1 Young Generation, G1 Old Generation Memory: 1280M Cores: 8 Registry: external.system.auto.import.disabled=true Non-Bundled Plugins: com.thoughtworks.gauge, Dart, org.jetbrains.kotlin, io.flutter, org.intellij.plugins.markdown Current Desktop: ubuntu:GNOME

Emulator info:

Name: Pixel_3a_API_30 CPU/ABI: Google Play Intel Atom (x86) Path: /home/fran/.android/avd/Pixel_3a_API_30.avd Target: google_apis_playstore [Google Play] (API level 30) Skin: pixel_3a SD Card: 512M fastboot.chosenSnapshotFile: runtime.network.speed: full hw.accelerometer: yes hw.device.name: pixel_3a hw.lcd.width: 1080 hw.initialOrientation: Portrait image.androidVersion.api: 30 tag.id: google_apis_playstore hw.mainKeys: no hw.camera.front: emulated avd.ini.displayname: Pixel 3a API 30 hw.gpu.mode: auto hw.ramSize: 1536 PlayStore.enabled: true fastboot.forceColdBoot: no hw.cpu.ncore: 4 hw.keyboard: yes hw.sensors.proximity: yes hw.dPad: no hw.lcd.height: 2220 vm.heapSize: 256 skin.dynamic: yes hw.device.manufacturer: Google hw.gps: yes hw.audioInput: yes image.sysdir.1: system-images/android-30/google_apis_playstore/x86/ showDeviceFrame: yes hw.camera.back: virtualscene AvdId: Pixel_3a_API_30 hw.lcd.density: 440 hw.arc: false hw.device.hash2: MD5:0e6953ebf01bdc6b33a2f54746629c50 fastboot.forceChosenSnapshotBoot: no fastboot.forceFastBoot: yes hw.trackBall: no hw.battery: yes hw.sdCard: yes tag.display: Google Play runtime.network.latency: none disk.dataPartition.size: 6442450944 hw.sensors.orientation: yes avd.ini.encoding: UTF-8 hw.gpu.enabled: yes

OS info:

$ neofetch 
            .-/+oossssoo+/-.               fran@oso 
        `:+ssssssssssssssssss+:`           -------- 
      -+ssssssssssssssssssyyssss+-         OS: Ubuntu 20.04.2 LTS x86_64 
    .ossssssssssssssssssdMMMNysssso.       Host: MACHC-WAX9 M1150 
   /ssssssssssshdmmNNmmyNMMMMhssssss/      Kernel: 5.8.0-56-generic 
  +ssssssssshmydMMMMMMMNddddyssssssss+     Uptime: 1 day, 52 mins 
 /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Packages: 2450 (dpkg), 21 (snap) 
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Shell: bash 5.0.17 
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Resolution: 3000x2000 
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   DE: GNOME 
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   WM: Mutter 
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   WM Theme: Prof-Gnome-Dark-3.6 
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Theme: Prof-Gnome-Dark-3.6 [GTK2/3] 
 /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/    Icons: kora [GTK2/3] 
  +sssssssssdmydMMMMMMMMddddyssssssss+     Terminal: gnome-terminal 
   /ssssssssssshdmNNNNmyNMMMMhssssss/      CPU: Intel i7-10510U (8) @ 4.900GHz 
    .ossssssssssssssssssdMMMNysssso.       GPU: Intel UHD Graphics 
      -+sssssssssssssssssyyyssss+-         GPU: NVIDIA GeForce MX250 
        `:+ssssssssssssssssss+:`           Memory: 7765MiB / 15755MiB 
            .-/+oossssoo+/-.

Flutter doctor output:

$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.2.2, on Linux, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 4.2)
[✓] Android Studio (version 4.1)
[✓] Android Studio
[✓] IntelliJ IDEA Ultimate Edition (version 2021.1)
[✓] Connected device (2 available)

• No issues found!

[helin24]

@fmmarzoa thanks! I see the logs we’re expecting. I don’t notice anything suspect from first glance, but I’m hoping that the JxBrowser team will have more insight about why this might be happening.

[helin24]

@fmmarzoa thanks for checking! Sorry to hear it didn’t fix the problem; I’ll keep investigating.