Yes, I install as flatpak.
Kernel: 6.3.7-200.fc38.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.39-9.fc38 Desktop: GNOME v: 44.2 Distro: Fedora release 38 (Thirty
Type: Convertible System: LENOVO product: 82LU v: Yoga 9 14IAP7
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: SDK0T76461 WIN
serial: <superuser required> UEFI: LENOVO v: HNCN43WW date: 12/26/2022
ID-1: BAT0 charge: 53.9 Wh (74.9%) condition: 72.0/75.0 Wh (96.0%)
volts: 16.5 min: 15.5 model: Celxpert L21C4PH0 status: discharging
Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-1280P bits: 64
type: MST AMCP arch: Alder Lake rev: 3 cache: L1: 1.2 MiB L2: 11.5 MiB
L3: 24 MiB
Speed (MHz): avg: 1854 high: 2000 min/max: 400/4700:4800:3600 cores:
1: 2000 2: 2000 3: 2000 4: 2000 5: 2000 6: 2000 7: 2000 8: 2000 9: 453
10: 2000 11: 642 12: 2000 13: 2000 14: 2000 15: 2000 16: 2000 17: 2000
18: 2000 19: 2000 20: 2000 bogomips: 79872
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Device-1: Intel Alder Lake-P Integrated Graphics vendor: Lenovo driver: i915
v: kernel arch: Gen-12.2 bus-ID: 00:02.0
Device-2: Luxvisions Innotech Integrated RGB Camera driver: uvcvideo
type: USB bus-ID: 3-8:3
Display: wayland server: X.Org v: 22.1.9 with: Xwayland v: 22.1.9
compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: iris gpu: i915 resolution: 2880x1800~90Hz
API: OpenGL v: 4.6 Mesa 23.1.2 renderer: Mesa Intel Graphics (ADL GT2)
Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Lenovo
driver: sof-audio-pci-intel-tgl bus-ID: 00:1f.3
API: ALSA v: k6.3.7-200.fc38.x86_64 status: kernel-api
Server-1: PipeWire v: 0.3.71 status: active
Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel
IF: wlp0s20f3 state: up mac: <filter>
Device-1: Intel driver: btusb v: 0.8 type: USB bus-ID: 3-10:4
Report: rfkill ID: hci0 rfk-id: 3 state: up address: see --recommends
Local Storage: total: 476.94 GiB used: 18.54 GiB (3.9%)
ID-1: /dev/nvme0n1 vendor: SanDisk model: SKHynix HFS512GEJ9X115N
size: 476.94 GiB temp: 38.9 C
ID-1: / size: 124 GiB used: 18.17 GiB (14.7%) fs: btrfs dev: /dev/nvme0n1p6
ID-2: /boot size: 973.4 MiB used: 297.5 MiB (30.6%) fs: ext4
ID-3: /boot/efi size: 256 MiB used: 80.1 MiB (31.3%) fs: vfat
ID-4: /home size: 124 GiB used: 18.17 GiB (14.7%) fs: btrfs
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
System Temperatures: cpu: 33.0 C mobo: N/A
Fan Speeds (RPM): N/A
Processes: 441 Uptime: 32m Memory: available: 15.33 GiB
used: 4.66 GiB (30.4%) Init: systemd target: graphical (5) Compilers: N/A
Packages: 26 note: see --rpm Shell: Bash v: 5.2.15 inxi: 3.3.27
I have continued my research and have isolated the problem to window sizes. I will tell you more:
When I open a window, it opens with an unusual size (smaller than usual). And when it loses the focus or when you try to change the size, the window changes the size it had when it was opened (it doesn’t have to be the correct one).
Once it has undergone this resizing, the problem does not persist.
When does it happen?
When opening a new window and switching windows (i.e. losing window focus).
When a window opens another window (happens to the first one, which also loses focus).
When you try to resize the window for the first time.
These three cases happen as long as the window has not faced any of these situations before (it means, when you change its initial size, it does not happen again).
In which situation does it happen?
After testing different cases I can confirm that this problem only occurs, in my case (two screens, 1- 2880x1800 16:10, 2- 2560x1440 16:9) when the two monitors have a different scaling, it doesn’t matter which of the two has the higher percentage.
Depending on the configuration of the position of the screens, the problem occurs on one or the other.
The following are the casuistries detected (note that the screen number refers to the nomenclature used in this text, not to the screen number of the operating system):
If screen 1 is below screen 2, the problem occurs on screen 1.
If screen 1 is above screen 2, the problem occurs on screen 2.
If screen 1 is to the left of screen 2, the problem occurs on screen 2.
If screen 1 is to the right of screen 2, the problem occurs in screen 1.
These tests have been done running the terminal and the extension manager, but it also happens with other windows.
In the case of the terminal the strange size happens as soon as the window appears. In the case of the extension manager when a configuration is opened in a new window, it happens to the original extension manager window.
With other aspect ratios it also happens.
I have checked the problem on Fedora 38 as well as on Debian 13 and it happens on both.
I don’t know what to do in these situations, I guess report the bug. But I don’t know how or where, to be honest.