Output scale auto-detection has different result after restarting Sway

[winterqt]

Please fill out the following:

• Sway Version:

  • 1.8.1

• Debug Log:

  • https://gist.github.com/winterqt/d2776228d36f0651ce08549a7c5dbd2d#file-good-log
  • https://gist.github.com/winterqt/d2776228d36f0651ce08549a7c5dbd2d#file-bad-log

• Configuration File:

  • Default

• Stack Trace:

  • n/a

• Description:

  • I launched Sway from a TTY, and the output scale auto-detection successfully used a comfortable value of 2. However, after quitting sway with the exit shortcut and relaunching Sway the exact same way, the output scale is detected at 1. I did nothing in between these two invocations; I didn't change the configuration, or didn't attach a display, etc.
  • This very well might be an issue with Mesa (as it's Asahi Linux's experimental drivers), but I figured I'd report this here in case it happens to be a Sway issue, as there has been some issues with this functionality before, like Scale factor defaults to 2.0 upon reload #4960 (I did try to see if it was a similar issue by reloading -- it's not).

[emersion]

00:00:00.113 [INFO] [wlr] [backend/drm/drm.c:1230] Physical size: 0x0

It seems like the KMS driver is not setting the physical size of the connector on the bad run. Please report this to Asahi devs.