When did this last work correctly for you? Which window manager are you running?
Could you please try this:
cd ~/.local/share/Steam
STEAM_RUNTIME=0 ./steam.sh
And see if the problem still exists.
Thanks.
I recieve "couldn't set up Steam Runtime, running low on disk space?" error windows, when I've plenty of disk space yet (122G avail).
$ STEAM_RUNTIME=0 ./steam.sh
Running Steam on gentoo 64-bit
STEAM_RUNTIME is disabled by the user
Unpack runtime failed, error code 1
I also still get the issue; However, It does seem to be something with my window manager, as minimizing and restoring the chat window seems to fix the issue (don't know why I didn't try this before...)
I'm running E17 with two monitors. The mouse is currently set to sloppy focus, although the only issue that's ever caused me is steam's menus disappearing if I move too quickly :smile:
Can you please try to reproduce this focus problem on Unity, Gnome, or KDE? E17 isn't yet supported by Steam.
I'm sorry, but enlightenment IS supported - As long as this application follows agreed upon standards such as the ICCCM, or hopefully the more up-to-date EWMH, then it follows the same window focus methods as it would under kWin or Metacity or Compiz/Emerald.
The window manager is not the issue, the way the client is implemented is. I am currently pulling ICCCM and EWMH stats for each window steam produces, and will place them here soon.
On an aside, I can't replicate this on XFCE (xfwm4) or Mint14.1's Cinnamon.
I dig E17, but I've had it perform strangely... so frequently that I stopped using it on my netbook. I'll use it in VMs for testing and whatnot.... but that's about it.
I disagree that it behaves unexpectedly, and this is the first (and only!) application that I've had focus issues with. E17 is perfectly stable, and I have been running it since it was still in beta testing as my main window manager. It certainly is different than metacity/cinnamon or kwin or xfwm4, but it does the same job complying to the same freedesktop, xdg, etc... standards.
The issue seems to have resolved itself, at least here on my end. I think restarting steam was all that was necessary. I'll still upload the netWM and ICCCM data though, for future use.
looks like I closed it too early; after some investigating, the window has the 'hidden' setting set when it first spawns, but not after minimizing and restoring, so it's something with the window that steam creates, not the window manager. here are the images showing the state of the windows steam produces.
Thanks for your replies. Steam has a bug, no question, however we're prioritizing finding and fixing bugs that occur on Unity / Gnome / KDE first. So my first question is, does this bug reproduce on one of those desktop managers?
Unfortunately, I don't have any of those environments currently installed, and do not plan to install any of them.
I'm guessing no further development has come in regards to this issue?
Im having the same problem as undeadrattler ...
And i have a temp solution till someone over at valve addresses this issue.
The way i got the chat window to activate was hold down the alt key
right click on the bar where you would drag the chat window around
from there you would select move to
move to another desktop, a desktop not activated.
You will notice you now can move that window around; move to that desktop and drag the chat window back into the main desktop and then you can continue about your chatting...
again, if someone from valve needs some debugging info or further information on what im running please let me know..

Nothing extracted yet.
With the latest steam cilent update, I have become unable to move the focus to the chat window and/or interact with it in any fashion other than through the windowmanager. I can move it with alt+click+drag, and I can close it with the right-click menu, but any keyboard and mouse interactions get sent to the main client window.
Steps to reproduce: 1)Run steam. 2)Attempt to message a friend or recieve a message.
System Information: