Skip to content

[Sway] when setting a geometry and then setting a rule to be floating the window force different size #16114

@akrram09

Description

@akrram09

mpv Information

mpv v0.39.0-dirty Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on Mar 13 2025 08:13:20
libplacebo version: v7.349.0
FFmpeg version: n7.1
FFmpeg library versions:
   libavcodec      61.19.100
   libavdevice     61.3.100
   libavfilter     10.4.100
   libavformat     61.7.100
   libavutil       59.39.100
   libswresample   5.3.100
   libswscale      8.3.100

Other Information

- Linux version: Arch Linux
- Kernel Version: Linux arch 6.13.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 23 Mar 2025 17:17:30 +0000 x86_64 GNU/Linux

- GPU Model: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02)

- Mesa/GPU Driver Version: Mesa 25.0.2-arch1.2
- Window Manager and Version: swayfx version 0.5 (based on sway 1.10.1)
- Source of mpv: pacman
- Issue started after the following happened: on my 1920x1080 (scale set to 1.5) the mpv window looks so small, so i try to do geometry and it works but when setting a rule for mpv to be floating, it opens in different size then the one i set, but when no rule set for example its in tiling mode then press $mod+Shift+space to be floating it works

Reproduction Steps

  1. place the following in mpv.conf
    geometry=1400x788
  2. add a rule to sway to be floating
    for_window [app_id="mpv"] floating enable
  3. open mpv
  4. see bug

Expected Behavior

the window follow the geometry and also fix the size problem on 1920x1080 displays
(default no rules no geometry)
Image

Actual Behavior

the window doesn't follow geometry when setting a rule

Log File

output.txt

Sample Files

geometry=1400x788

I carefully read all instruction and confirm that I did the following:

  • I tested with the latest mpv version to validate that the issue is not already fixed.
  • I provided all required information including system and mpv version.
  • I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
  • I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
  • I attached the full, untruncated log file.
  • I attached the backtrace in the case of a crash.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions