Awesome 4.3_p20260105, all windows are floating

[DerMouse]

On Gentoo Linux.

Lust upgraded from awesome 4.3-r104 to 4.3_p20260105. No change to the rc.lua file.
No errors when awesome starts, but windows are always created « floating », whatever the screen and layout. Meta+Ctrl+Space for each window gives back the (configured) behaviour.

Reverting to 4.3-r104 (nothing else, no libraries downgrade, etc.) gets the « proper » behaviour back.

[actionless]

could you please try to do git bisect?

[Aire-One]

I have tried to read the scripts from https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-wm/awesome, but I'm not familiar with Gentoo/Portage. My understanding is that the installed version depends on the value of $PV (which I don't know what it refers to), and can as well be the old latest 4.3 tag, a commit picked by the package maintainers, or the latest from git. So it's kinda hard to have a starting point to bisect 🤷

No change to the rc.lua file.

Is it the default awesomerc.lua, a custom one, or a special config provided by the package maintainers? The first option implies a regression on our side. The latter option implies changes downstream by the package maintainers.

[DerMouse]

Hello,

Sorry to be a little late to answer.

I have tried to read the scripts from https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-wm/awesome, but I'm not familiar with Gentoo/Portage. My understanding is that the installed version depends on the value of $PV (which I don't know what it refers to), and can as well be the old latest 4.3 tag, a commit picked by the package maintainers, or the latest from git. So it's kinda hard to have a starting point to bisect 🤷

The $PV variable is the package version, taken from the ebuild name (that's Gentoo-speak, do not bother too much). Here, it was 4.3_p20260105, which means release 4.3 patch 20260105.

Looking into the ebuild, it's the commit cab3e81 that is downloaded/compiled/installed.

No change to the rc.lua file.

Is it the default awesomerc.lua, a custom one, or a special config provided by the package maintainers? The first option implies a regression on our side. The latter option implies changes downstream by the package maintainers.

Nope, it's my rc.lua file. Not that much fancy stuff inside, but I did not test with the default rc.lua. Will do that this week and will keep you informed about the results.

[DerMouse]

Is it the default awesomerc.lua, a custom one, or a special config provided by the package maintainers? The first option implies a regression on our side. The latter option implies changes downstream by the package maintainers.

Nope, it's my rc.lua file. Not that much fancy stuff inside, but I did not test with the default rc.lua. Will do that this week and will keep you informed about the results.

So, with the default rc.lua from the package, no obvious problem seen.

There must be some weird play between modules or local configs. I'll dig into this to understand. Currently no need to loose sleep over this (except for me).