protonscr

After latest Steam update, windows hops/jumps downwards constantly.

steamopen Steam clientWindow manager
ValveSoftware/steam-for-linux#10639 · opened 2024-03-19 by angulion · updated 2024-03-28 · 2 comments · github
Aangulion 2024-03-19 github

Your system information

  • Steam client version (build number or date): 1709846872
  • Distribution (e.g. Ubuntu): OpenSUSE Tumbleweed (X11/Xorg/KDE)
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
  • GPU: Nvidia RTX3080 Ti

Please describe your issue in as much detail as possible:

Because applications own titlebars just are bad (does not follow system shortcuts, pin on all desktops etc.) I have system titlebar forced on Steam-windows (kwin_x11 rule) - if this has anything to do with my issue.
After latest update when ever window gains or looses focus (I use focus-follows-mouse), mouse hovers over Store, Library, Community, , enters or exits an opened menu from the "titlebar" etc., the whole window jumps down on screen about the pixel amount of Steams titlebar (or the real system titlebar).
Same happens seemingly with every Steam window - About Steam, Settings, Friend list.
Very very annoying, as trying to click Library becomes a chase to hit it.

Steps for reproducing this issue:

  1. Update Steam
  2. In KDE edit Application settings and force window decoration (titlebar & frame)
  3. Enjoy chasing window.

Best fix would be to remove steams subpar titlebar, but in meantime reverting some recent change that repositions window would help.

Aangulion 2024-03-21 github

If anyone else has this issue, as a temporary solution for anyone else facing this - add to the KDE Window rule that window-position is also forced (separate for title "Friend List" and "Steam"). At least it makes using Steam possible again, although far from perfect (not able to move window at all).

Ddsalt 2024-03-28 github

This looks exactly like the bug which I reported in #10408.

Nothing extracted yet.