ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.16k stars 173 forks source link

Steam window non-resizable after maximized once with openbox #3792

Open ghost opened 9 years ago

ghost commented 9 years ago

Hi,

I'm using Slackware 14.1 64bit with Steam 1.0.0.49.

I noticed that if I exit from Big Picture the title bar section of the window, where I can double click to maximise the window size or make it smaller, or the minimize/max button on the right side of the window, these no longer work and the window won't resize.

If I start Steam for the fist time I can click the title bar, or minimize/max button and the window resizes, this only seems to be some kind of issue exiting Big Picture that it doesn't work.

If you need any system specs or information let me know...

kisak-valve commented 5 years ago

Looks like this is DE-specific behavior and big picture mode isn't necessarily involved. On MATE and KDE5, Steam maximizes / restores once, but doesn't react to being told to maximize after that. Cinnamon and GNOME 3 are not affected by the quirk behavior.

Chiitoo commented 5 years ago

As an additional note, restoring the Steam window from a minimized state seems to always set the restore/maximize window button to a correct state, even after breaking it.

Tested on LXQt using kwin_x11 and openbox.

Using xfwm4 the issue doesn't seem to occur either.

McMarius11 commented 5 years ago

i have the same problem running Kubuntu 18.04 LTS same with #6089 edit: same problem with KDE Neon

kisak-valve commented 4 years ago

Hello @Chiitoo, are you still experiencing this issue on an up to date system?

Chiitoo commented 4 years ago

Yes with 'openbox', no with 'kwin_x11'.

damianatorrpm commented 4 years ago

@kisak-valve Yes the issue is still there with wayfire/wlroots. Maybe you can share what quirks are needed by steam.

chinoto commented 4 years ago

Still an issue on KDE/kwin for me. If I maximize, then restore, the icon stays in the restore state and can't be used to maximize again unless I minimize and unminimize. Steam can also be forced to maximize by right clicking its taskbar entry and clicking maximize.

openSUSE Leap 15.1
KDE Plasma: 5.12.8
KDE Frameworks: 5.55.0
Qt: 5.9.7
damianatorrpm commented 4 years ago

I doubt that any valve engineer has ever read this, just the qualifier, no offense. I mean it has been 3 years or more, and they are not adhering to spec, I am a wayland developer and I ask them what they do that is not according to spec, no answer.

EDIT: I stand corrected 5 years where steam is broken on everything except gnome, not to mention gaben hasn't responded to my email for 2 weeks now.

McMarius11 commented 4 years ago

Still an issue on KDE/kwin for me. If I maximize, then restore, the icon stays in the restore state and can't be used to maximize again unless I minimize and unminimize. Steam can also be forced to maximize by right clicking its taskbar entry and clicking maximize.

openSUSE Leap 15.1
KDE Plasma: 5.12.8
KDE Frameworks: 5.55.0
Qt: 5.9.7

For me on my manjaro kde 5.19 the problem is solved, could you test it and upgrade your plasma.

soreau commented 3 years ago

In the wlroots case, I noticed one difference from xprop output for steam in X and wayland is that in X, it showed _NET_WM_STATE(ATOM) = _NET_WM_STATE_FOCUSED while wayland did not. After setting this property for the client from the window manager, the bug is fixed. Can now maximize steam repeatedly and the icon maintains correct representation.

chinoto commented 3 years ago

Still an issue on KDE/kwin for me. If I maximize, then restore, the icon stays in the restore state and can't be used to maximize again unless I minimize and unminimize. Steam can also be forced to maximize by right clicking its taskbar entry and clicking maximize.

For me on my manjaro kde 5.19 the problem is solved, could you test it and upgrade your plasma.

Finally upgraded to new distro version, problem is resolved. I wonder if this is because KDE worked around broken usage like GPU drivers tend to do or KDE did something wrong before? I doubt the latter since this affected more than KDE.

openSUSE Leap 15.2
KDE Plasma: 5.18.5
KDE Frameworks: 5.71.0
Qt: 5.12.7
Kernel: 5.3.18-lp152.47-default