Steam

Steam automatically updates itself to the latest version whenever it is run.

This
is the platform for all recent Valve games. You can find out
information about whether or not individual games (such as Half Life)
run by checking out their respective sections in the database. This page is about Steam only.

In case of Windows 10 compatibility and -no-cef-sandbox, steamwebhelper.exe will fail regularly with an exception.

Workarounds

Cannot log in into Steam client. Account name and Password cannot be focused.Solution: click on the header of Steam login dialog and now they can be focused and filled in.If even that doesn't help, close and start client again or try Windows 7 or Windows XP compatibility.

Cannot type anything into a chat window.Solution: move around the Steam windows, close the main Steam window and Friends list, and click around.

Sometimes, after the exit of Steam, Wine won't close:

ps aux

and kill processes manually. Or if wine was run from terminal, Ctrl+C usually helps.
Admin Note:
it's much easier to run:

These guidelines ensure your submitted test results are actually relevant to other users of Wine and WineHQ.

1 The console version of the lshw utility is your friend. This command will dump your System hardware specification in a clean format. Post command and output in the Extra Comments section:

sudo lshw -short | egrep -v '(volume|disk|bus)'

2 inxi can be used to display information about your graphics card, and your OpenGL/ graphics driver versions. Post the command and output in the Extra Comments section:

inxi -G -c0

Installation

You need:

You are recommended to use the latest release of Wine (see Steam Client Build Issues below)You can get instructions on how to install the latest Wine release at WineHQ Download.

It is not necessary to use a clean Wineprefix, but this is recommended.

How to install:

The default Wineprefix Windows version is now set to Windows 7 ( see: wine.git / wine.inf: Set default Windows version to win7 ) since Wine Development version 2.2.This setting will cause issues with the current release of the Steam Client. It is recommended therefore to set your Steam Wineprefix Windows version to Windows XP, using:

env WINEPREFIX="❚❚❚❚❚❚" winetricks -q winxp

If you are unable to use Windows XP globally for your Wineprefix (e.g. a Steam game is only compatible with Windows 7, etc.) then a workaround is to use an appdefault setting, just for the Steam client and steamwebhelper executables.

It's also recomended to install the fonts: arial.ttf, tahoma.ttf, verdana.ttf and times.ttf. Steam will work without these fonts, but will look ugly. You can also install those fonts through winetricks by typing:

env WINEPREFIX="❚❚❚❚❚❚" winetricks corefonts

Note: Wine should automagically import all system fonts (e.g. TT fonts you may have imported from a Windows partition).

You can also automatically install steam with winetricks and apply the necessary patches with winetricks using the follow command.

env WINEPREFIX="❚❚❚❚❚❚" winetricks --no-isolate steam

To learn how to use winetricks and find out more about this monolithic BASH script, click WineHQ Winetricks.

Valve has announced that the Steam Client will no longer support Window XP, from January 2019. When this support is removed I will remove this workaround (both from the instructions here, and the winetricks steam verb).

The CEO of Codeweavers (Jeremy White) is aware that is a significant problem for Wine users (I discussed it with him briefly at Wineconf 2018)!

Note: this also presents a significant issue for Codeweaver's Crossover (commercial) product.

Steam Client Launcher

Create a .desktop file launcher file

The command line is for losers right? So why not create yourself a Steam launcher! Now you can launch your Steam games straight from your Ubuntu Unity Gnome menu.

Yeah... you shouldn't just copy those blocks!! Replace them with your actual Wineprefix path (typically "${HOME}/.wine" - by default).

The Exec should have backslashes (\) escaped. If expressions are left unquoted then you need to escape your escape codes - as the Unix Command Shell will "eat them"!!To avoid a world of pain - just quote any paths...But note: you can only use double quotes (") in a .desktop file.

The Path variable is the working path - used when Wine starts execution of the Steam client (this is "double-quoted" by the system - so don't put any quotes around it!!)If not set - this can cause issues - since MS Windows executable include the present working directory (PWD) in the system executable path.

The .desktop file can be put in any sub-directory of:

"${HOME}/.local/share/applications/"

When your click on your desktop entry, in your Desktop Environment menu, and it appears to do nothing... Check it for common errors with:

Affects all Steam Client builds, since the Steam client release with build date Jun 1 2018. This issue results from an inability to verify certificates signed using an ECDSA signature. The symptom is that Steam is unable to install any new games, applications or updates (of these).

Wine Development and Wine Staging have a patch-set to support ECDSA signature verification. Wine Stable versions will not work, without the additional ECDSA signature verification patch-set.

Steam Client Fails to start

Affects all Steam Client builds, since the Steam client release with build date Jul 6 2017. The most obvious symptom of this issue is that the Steam Client self-updates and then crashes when it starts up the new version. Terminal output includes:

Affects all Steam Client builds, since Steam with build date Oct 7 2015. The most obvious symptom of this issue is that you get backtrace error pop-up(s) referring to steamwebhelper.exe crashing. Typically, with recent builds of Wine Staging, you will see black/blank areas - in place of rendered web content. The Chromium Embedded Framework" (CEF), that Steam is built on, now has sandboxing/kernel hooking enabled by default. The CEF sandboxing hooks directly into the Windows kernel and this breaks under Wine.

Ensure that your Wine (Windows) version is left at the default setting of Windows XP (this can easily be checked with the winecfg utility). Setting this to a more recent Windows release version introduces additional (known) compatibility issues. If a Steam game needs to use a newer version of Windows, for compatibility reasons, then you can override the Wine Windows version to Windows XP - just for the Steam client and steamwebhelper executables.

There is currently one semi-official patch to get the Steam store to work correctly. This patch partially fixes sandboxing support for the CEF runtime. However 64-bit Wineprefix 's are not supported at present.

This patch injects a --nosandbox parameter to the CEF runtime - when it is called from a steamwebhelper.exe process. This is a hack - so please indicate if you've used this patch when submitting AppDB tests for Steam!

Wine versions 1.7.37(-) do not fully implement the MSDN guidelines for Input Method Manager: cross-process/thread IME must be prohibited. For further details see bug 35361. The most significant symptom of this is that all Steam Games exit after any/the first key press.

This is a wine regression exposed by a Steam Client build dated 3 Dec 2013. Update your Wine version to 1.7.38 or disable the Steam overlay and Friends window.

Steam Client crashes after user login

This is an issue related to the Dec 3 2013 Steam Client
build. You will need to use a fairly recent version of Wine that has a
patch to fix this API implementation mismatch. Development releases of Wine 1.7.7(-) and Stable releases of Wine 1.6.1(-) no longer support the Steam Client.

The actual Windows implementation of the Win32 function NtAdjustPrivilegesTokenNtAdjustPrivilegesToken
does not match the MSDN specification for the API of the function...
Wine versions 1.7.7(-) incorrectly assume the MSDN specification is the correct one.
It should be emphasised that this is not a bug in the Steam Client - it
simply calls this Win32 function and assumes the standard MS Windows
behaviour. See bug 35030.

Steam API

Steam browser protocol

There are numerous system-wide commands available that interact with Steam. All of them open up Steam if it is not open.

Warning: all Wine terminal commands in this guide assume you are using a 64-bit Wineprefix!

General Troubleshooting

Steam freezes after opening the library.

This is a bug that affects some users. At this time, there isn't a solution to fix this problem. It is recommended to reinstall steam or (if necessary) start over with a clean Wineprefix.

When opening a new window in Steam, that window starts transparent.

This is a compositing-related problem. Try disabling compositing in the settings for your Window Manager.

Steam In-Game overlay will not close.

This is an intemitent issue with no permanent solution. You can try to close the overlay by clicking on the "Close the steam overlay" link at the top of the screen. This is currently the most effective solution, but, sometimes the only way is to close the game.

Big Picture Mode fail to open, asking for DirectX.

Until now Steam Big Picture mode doesn't work with Wine. Big Picture mode requires DirectX 10.1 libraries that Wine currently does not support.

Steam window is unresponsive or slow.

This bug is not yet resolved. If you're using Desktop compositing, you can disable-it and it will improve steam performance. The Steam client requires and uses OpenGL acceleration.

Steam window stealing window focus or not taking focus.

This is a common glitch with Wine running under X-Windows. The best solution in this case is minimize the steam window or close it to the taskbar.

Users of the KDE/Plasma Desktop can set fine grained Focus Stealing control over applications. It is recommended to set the Wine Steam class to None if you have problems with game draw windows not running in fullscreen.

When Wine draws windows using X-Server protocols these cannot guarantee or mimic the same ordering or focus that DirectX/Draw libraries provide under Microsoft Windows.

How to fix "Could not Connect to Network" Issue.

For those experiencing the "Could Not Connect to Network" problem often the Windows solution is to delete the ClientRegistry file. To do that, delete it:

rm "${WINEPREFIX}/drive_c/Program Files/Steam/ClientRegistry.blob"

Note: For most people simply restarting the client works around the issue.

Chat window doesn't work.

The chat appears to be working but messages are not displayed correctly. Try resizing and/or minimizing/maximizing the chat window.

Try to call any friend to chat from the friends list, and the window will show up again.

Unable to launch games with error: "The registry was in use by another process".

This is a Steam client bug resulting from the Linux kernel caching file operations. You can fix this problem by shutting down Steam cleanly (keep running and exiting steam itself until you get a clean shutdown without any errors after "Shutting down" - watch the console you ran steam from) and then restarting it. Once steam has been shut down cleanly and restarted the error should not occur.

If all fails, start Steam, right-click on the game and select Properties. Go to Local files tab and click on Verify integrity of game cache...

Some file systems support extra sync flag. This should solve the problem. However it will reduce performance, so use with care!

chattr -R +S ~/.wine/drive_c/Program\ Files/Steam

Most/All games crash after open or after a short time.

Try disabling the gameoverlayrender.dll.Run winecfg, go to Libraries, add a new library replace named gameoverlayrenderer and set to disabled. Note the In-Game Overlay will not work (including the Steam screenshot facility).

Steam client crashes when authenticating user.

This problem can be caused by WINE requiring the native ntlm_auth library to be installed (in order to authentic your login). On most Linux-based distributions this library is included in the Samba (server) package - typically this package includes winbind.

If you have this issue then you will see an console/debug error similar to the following:

err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.

­

Steam client window(s) do(es)n't render any text.

For Wine versions 1.5.10(+) stubs for the dwrite.dll were introduced and subsequently implemented. This results in the symptom that the Steam Client will render with invisible text without a workaround (see below). See bug 31374. Upgrading to Wine versions 1.7.49(+), with a fully implemented dwrite.dll, will fix this issue.

Ensure Steam client is launched as follows...

wine Steam.exe -no-dwrite

Backup/Restore games: file dialog displays files out of order.

The Symptom of this is that the Steam Client file browser, for Backing up or Restoring Steam games, displays files and folders in an apparently jumbled up order. Technically this is a bug in the Steam Client. It assumes that WinAPI functions FindFirstFile/FindNextFile will return files and folders in sorted order. This is however only the case for NTFS formatted drives. See bug 34122. Upgrading to Wine versions 1.9.10(+) fixes this issue.

General Workarounds.

If you have an problem that you can't solve one 'hack' is to force the Steam client to reinstall itself.

Shutdown your Steam client - if necessary force shutdown, with:

wineserver -k

Delete all files in your Steam folder (default is typically: ~/.wine/drive_c/Program Files/Steam/) except the file steam.exe and the Steam games directory: steamapps.

Re-launch your Steam client - in order to re-download all application files.

Your Steam games will be intact - since games are stored in subdirectories off the steamapps directory.

Steam Tips

How to disable/enable forced Steam Client updates.

This workaround disables write access to your Steam package folder where Steam downloads updates to. Caveat Emptor - disable updates for too long and your Steam installation will break... You have been warned!!

First, navigate to (32-bit Wineprefix):

cd "${WINEPREFIX}/drive_c/Program Files/Steam"chmod -w package

... this disables all subsequent Steam Client updates...

chmod +w package

... this re-enables all subsequent Steam Client updates...

Make fonts look less ugly.

To make fonts look better in Steam and in other applications, running via Wine, we need to change a few values in the Wine registry...

First make a new text document called fontfix.reg in your favourite text editor with the follow content:

Steam now uses the Chromium Embedded Framework runtime to render the webstore. Playback of trailer videos is handled by the builtin HTML5 / Pepper Flash players. No extra Windows software is required to support this.

If your Steam Chromium Embedded Framework is running with sandboxing enabled - then the Steam store will typically not be rendered at all...So you've got bigger problems, to deal with (see the Steam Client Build Issues section), than non-playing trailer videos!

How to completely re-install the Steam Client application.

To reinstall Steam without loosing your installed games, you need to move/copy the folder (and all sub-folders):

"${WINEPREFIX}/drive_c/Program Files/Steam/steamapps"

... or for a 64-bit Wineprefix ...

"${WINEPREFIX}/drive_c/Program Files (x86)/Steam/steamapps"

to a safe place.

In a clean Wineprefix, after reinstalling steam, you can just move back the steamapps folder (and all sub-folders). Hey Presto! All your backed up games should show up, as installed, when you launch the newly installed Steam Client...

NB This will not backup or restore your saved games!! These will need to be safely backed up separately.

Keep Saved Games in your Wineprefix

Using the:

winetricks sandbox

command will ensure that all symbolic links to your Linux HOME folder are removed from your Wineprefix. Your Steam games Saved Games will therefore all be stored directly within your Wineprefix.Note the winetrickssandbox command will remove the default link to your Linux / root directory:

There are legitimate reasons why you might want to access files outside of your Wineprefix. In order you to re-enable this access, you have to recreate the Linux / root directory symbolic link:

ln -s / "${WINEPREFIX}/dosdevices/z:"

Issues with Multi-Monitor Setups

Often issues arise when using a hardware set-up with 2 or more monitors... Symptoms are that games launched from your Steam client will render on the wrong display, mess up your X display resolution or not render/support your native (target) monitor resolution/refresh rate. A work around for this is to launch the Steam client in a virtual desktop (32-bit Wineprefix), e.g.:

Steam will not run in Windows XP & Vista in 2019 by Michele on Tuesday November 13th 2018, 7:38

Starting on January 1 2019, Steam will officially stop supporting the Windows XP and Windows Vista operating systems. This means that after that date the Steam Client will no longer run on those versions of Windows. In order to continue running Steam and any games or other products purchased through Steam, users will need to update to a more recent version of Windows.

The newest features in Steam rely on an embedded version of Google Chrome, which no longer functions on older versions of Windows. In addition, future versions of Steam will require Windows feature and security updates only present in Windows 7 and above.
support.steampowered.com/kb_article.php?ref=1558-AFCM-4577

After installing Steam, any attempt to login with a valid account will end with a message box "Steam is having trouble connecting to the Steam servers".
Setting the Wine configuration to "Windows XP" doesn't help.

suddenly no downloading/updating of games anymore by silelmot on Thursday August 23rd 2018, 3:29

i just recognized it yesterday, didn't use my steam on wine since one or two weeks, but now i suddenly can't update any games anymore
installing new games doesnt work either.
i installed everything new in a new wine-prefix, but the same . i am using 3.13 staging,
anybody else has this issue?

Steam Stuck in Loading or Upgrading etc... solution by wavejumper on Friday July 20th 2018, 4:44

So I am posting this comment to inform people on what is causing this problem in some distributions regardless of wine version. I have always had this problem with my Slackware installations, both 14.2 and current even after fresh installs and have all dependencies met. I'm cross-linking to the post I posted on the Lutris forum about this. In my case this also affected The Elder Scrolls Online Launcher not connecting to the servers. Please if there is a better way to maybe inform developers etc... I'm glad to do so as I'm lost on how to do it and who to contact.

No text... again. by William Tradewell on Sunday July 15th 2018, 18:49

Latest steam update is broken... Text stopped rendering again! I tried using -no-dwrite. No luck. Using 3.11 w/ staging patches. Text was working yesterday. Then it updated. Now it's not. The text on the steam store page is still working, but that's prob cause the web browser uses gecko.

Migration from ArchWiki by Svitozar Cherepii on Saturday December 23rd 2017, 20:42

You can move useful information to HowTo/Notes and delete this comment:

This article covers running Steam in Wine, in order to play games not available through the native Linux [[Steam]].

== Installation ==
Install Wine as described in [[Wine]].

Install the required Microsoft fonts: {{AUR|ttf-tahoma}} and {{AUR|ttf-ms-fonts}} from the [[AUR]]. You can also install these fonts through [[Wine#Winetricks|Winetricks]]: {{ic|winetricks corefonts}}.
{{Note|If you have access to Windows discs, you may want to install {{AUR|ttf-ms-win8}} or {{AUR|ttf-win7-fonts}} instead.}}

Go to ''Properties > Set Launch Options'', e.g.:
-console -dxlevel 90 -width 1280 -height 1024
* {{ic|console}}
: Activate the console in the application to change detailed applications settings.
* {{ic|dxlevel}}
: Set the application's DirectX level, e.g. 90 for DirectX Version 9.0. It is recommended to use the video card's DirectX version to prevent crashes. See the official Valve Software wiki developer.valvesoftware.com/wiki/DirectX_Versions for details.
* {{ic|width}} and {{ic|height}}
: Set the screen resolution. In some cases the graphic settings are not saved in the application and the applications always starts in the default resolution.
Please refer to developer.valvesoftware.com/wiki/Command_Line_Options for a complete list of launch options.

=== Using a pre-existing Steam installation/Content Library ===

If you have a shared drive with Windows, or already have a Steam installation somewhere else, you can use that.

In the Steam client, go to ''Steam'' > ''Settings'' > ''Downloads'' and click "Steam library folders". Then add a new library folder. For instance, if you have mounted your Windows drive at {{ic|/mnt/windows}}, add {{ic|Z:\mnt\windows\Program Files (x86)\Steam}}.

To make {{ic|}} urls in your browser connect with Steam in Wine, there are several things you can do. One involves making steam url-handler keys in gconf, another involves making protocol files for KDE, others involve tinkering with desktop files or the Local State file for Chromium. These seem to only work in Firefox or under certain desktop configurations. One way to do it that works more globally is using mimeo, a tool made by Xyne (an Arch TU) which follows. For another working and less invasive (but Firefox-only) way, see the first post [ubuntuforums.org/showthread.php?t=433548 here] .

* Make {{ic|/usr/bin/steam-wine}} with your favorite editor and paste:

* Restart the browser and you should be good to go. In Chromium, you cannot enter a {{ic|}} link in the url box like you can with Firefox. The forum link above has a {{ic|open/friends}} link to try if needed.

{{Note|Steam links in Firefox, Chrome, etc
* If you have any problems with file associations after doing this, simply revert to regular xdg-utils and undo your changes to {{ic|/usr/bin/xdg-open}}.
* Those on other distributions that stumble upon this page, see the link above for firefox specific instructions. No easy way to get it working on Chromium on other distros exists.
}}

wine-staging 2.20 x64, clean install, everything as recommended in latest report
whenever friend sends you message, and if you don't have chat with that friend open, after sound plays and pop-up shows up, steam just dies with message like bellow.
Not happening on 2.18 x86, don't know which of two could be the reason.

Steam isn't longer working since a few days ago by Wilson Wijaya on Friday July 14th 2017, 11:44

I faced a similar problem. The PC Steam works like charm until July 13th when it didn't want to respond. I am currently using a Mac OS X El Capitan 10.11, but I don't think that's a main problem since I can still run the steam installer.

RE: Steam isn't longer working since a few days ago by simon on Monday July 17th 2017, 3:07

I am not sure if this is relevant. I tried a version of wine that is 2.12-fix43315(got it from playonlinux database) and I can open steam and play the game i installed.
I don't know what did they fix though.

As of now the Steam build with date stamp: Thu, 06 Jul 2017 17:18:27 UTC; won't run at all... :-(
I've just tested with a clean 32-bit WINEPREFIX - set to Windows XP.
Both Wine Staging 2.11 + Wine 2.12 crash with the same net.cpp error...

I'll update the Steam AppDB page - to reflect this issue - later on today...

Could I copy this steam install (from in wine) into an offline Windows 8.0 after turning on "steam offline" mode? by Cory on Sunday May 28th 2017, 2:39

I'm gonna have to take a snapshot of the Registry in ~/.wine/*.whatever
which is gonna take 30 minutes - 5 hours I'm 89% sure.
Take a snapshot of every file in ~/.wine/
Install steam.
(buy? &) Install a game on steam.
Turn steam into offline mode.
Shutdown steam.
Disable networking.
Start steam and start game. If succeeds, yay.

Now the fun part.
Copy everything that has changed into my offline Windows 8.0, including key registry changes.

That's it!
Do you think I can do it? Do you think my steam game will run on this Windows 8.0 machine?

I have both wine and native steam installed. The problem is, i don't know which one is which!!! I've been trying to rename the linux/wine version to: Steam- WINE/LINUX but it won't allow me! what do i do? I'm running elementary os 0.4 loki.

I'm encountering a weird bug with steam. When steam starts it grabs the sound output device and sets that as the microphone. This of course means that this device is unavailable to use. I've managed a workaround by setting wine to use an output device I don't use so when steam grabs it the default device is still available. Of course the microphone still doesn't work. Any suggestions on how to resolve this properly? I'm using the alsa sound drivers on wine 1.9.15 (through playonlinux) on Fedora 24. For the record it did it on Fedora 22 and pulseaudio drivers as well.

Another workaround for steamwebhelper.exe crash on Windows 7 mode by Edward W. Koenig on Sunday July 24th 2016, 3:07

I forgot to add this in my recent test submission.

When steamwebhelper.exe crashes (blank store etc) you can either

1. Set winecfg to run everything as Windows XP; as stated in the "Steam Client Build Issues" section.

2. Set winecfg to Windows 7 default (or just Steam.exe) and then set c:\Program Files\Steam\bin\steamwebhelper.exe to run as Windows XP. This allows store access and even the videos play.

From the bug report, steamwebhelper.exe is launched as a separate application, and so far I have not noticed any issues running Steam in Win7 and steamwebhelper.exe in WinXP. This could allow newer games that do not support WinXP to work without breaking the Store and other CEF displays.

Hi, I’m using Win32bit Wineprefix on a Mac, OS X Lion. Successfully installed Steam using Winery, but ran into bug 39403. The consensus seems to be that workarounds 1 and 2 are solid. But I’m a Wine beginner with little coding experience- I don’t understand how to implement the workarounds. Where and how do you enter the script for workaround 1?

I tried Applications/Wineskin/Steam.app/Contents/Resources/drive_c/windows/command, but it won’t let me type any commands there.

Alternatively, I found a post that says I can install games without the store as long as I have the desired game’s ID (which I do) using the command rungameid/gameid#. But again, I can’t figure out where to plug in the script. The link to that post is below. Thanks!

RE: steamwebhelper.exe crashes even with workarounds by Rob on Saturday April 30th 2016, 7:00

Hi,

I'm running Gentoo + wine-9999 (+staging) and it's working OK here (ha ha!!) - with the Steam command line switch. The only issue is the steamwebhelper.exe crashes when exiting Steam. I think you can work around that by disabling the CEF runtime thunk staging patchset - not needed if sandboxing is disabled obviously.

Doesn't mean that everything is going to still be working tomorrow of course (damn Valve and their cursed updates)!! 8->?

RE: steamwebhelper.exe crashes even with workarounds by Rob on Saturday April 30th 2016, 16:32

If you get really stuck... Start a (WineHQ) forum thread and link to it here. These Wiki comments are hopeless for troubleshooting (no markup support, code bracketing, etc.)! Just post as much as you can (console logs, build logs, etc.) - using bpaste, etc. for big stuff obviously. I've got got some customised wine ebuild's in my overlay - so I've got some idea of what the "current issues" are...

Well personally I don't use a controller at all. I just pointing out that official Wine Development is quite "behind the curve".

You could always post a question into the Linux Game Cast podcast (if you don't take offence to quickly :-) )... Or on the forums at the website... There's bound to be someone who's tried to use a Steam Controller with Wine!

RE: Steam Controller by George Chappell on Monday March 28th 2016, 20:43

This may be a stupid question (in fact it's almost guaranteed), but isn't there a dll somewhere in the Steam installation directory that if found could be used in the override section of winecfg? i tried hunting for it myself but failed, but given my level of expertise in such matters that's only to be expected.

I don't think that this would be enough, because USB is on Hardware-Level. BTW.: Here is a workarround: wiki.archlinux.org/index.php/Gamepad#Steam_ControllerBut you can only use Xbox-Controller functionality with this.
So it would still be great to have direct wine-support.

I don't think that this would be enough, because USB is on Hardware-Level. BTW.: Here is a workarround: wiki.archlinux.org/index.php/Gamepad#Steam_ControllerBut you can only use Xbox-Controller functionality with this.
So it would still be great to have direct wine-support.

Quick tip for all you KDE users out there: To stop the Steam mouseover tooltips from appearing in all open windows, go into System Settings -> System Behaviour -> Window Behaviour and set "Focus Stealing Prevention" to Medium. This stopped Steam from showing it's tooltips everywhere for me.

I'd tried on and off for the past month or so, and then constantly for the past 6 hours to play Star Wars Battlefront II on my MacBook...

I find myself pretty good at computers on the surface, but I only dive into Terminal occasionally, so I'm not so good with all the computer commands and such. Which is why I decided to use WineBottler, so it can take care of a lot of it for me. So I had no problems installing Steam with WineBottler, but obviously I ran into the issue of the Store and such not being able to load because of the whole sandbox issue and whatnot. Now I know it lists several ways to fix this above, but since I'm using WineBottler and it's accompanying Wine app, and not just regular Wine, I'm not sure how or if I even can use any of these methods.

I've also tried using some prepackaged Steam Builds that used Wineskin, and after some trouble figuring out how to fix the disappearing text, I still ran into the same problem and looked through the Wineskin options and such and couldn't figure out how to use any of the methods.

I've just been up from 12-6AM relentless searching for ways to get the Steam Store to work with Wine, and I've probably reinstalled Steam around 20 times now (and verifying with Steam Guard codes each time). All I want is to relive my childhood memories of playing Battlefront II, as well as relive the epic Star Wars moments I've come to fall in love with recently...
Is there anybody out there who could please help me?

2) Buy a Crossover License (which also supports the majority of the paid Wine Developers)..
www.codeweavers.com/

3) Patch Wine with the Crossover hack I've listed above and compile from source yourself. This is hard way... But you'll probably learn a bit about how your computer works - rather than just treating it as an appliance...

4) The Wine Bottler Development release (currently Wine 1.8rc4) - will not support the Steam Store... MacOSX simply doesn't play nice with 32-bit Wine code running the Chromium Sandbox.
However you could always contact the developer and see if he'll rebuild Wine Bottler with the Crossover hack (as it's the only way the Steam client is going to run on MacOSX - for the foreseeable future). A donation to him might help speed along this process :-)
mikesmassivemess@kronenberg.org

NEVER spend fruitless hours exploring the same broken pathways on a computer...!! The worst hours for the human mind to function are at night (when your brain is expecting to be repairing itself during sleep)...!!

I didn't learn assembler, C, how to run Gentoo etc. in one sitting/at night. You need to leave a problem - DO SOMETHING ELSE - so your subconscious mind will help you think of a workaround for it...

SteamCMD as Browser alternative by Luna Crane on Thursday November 12th 2015, 12:35

There is also the alternative to use SteamCMD as an alternative to getting games when the Steam browser isn't working. SteamCMD is actually available on Window$ and Linux, but you'll be using the Window$ version.

Right-click on a Steam [Play Now] button for a game in Firefox and copy link. The game ID number is there.

Put steamcmd.exe in /Program Files/Steam/ and run it from there to put things properly in the Steam directory system! Run the following, filling in your own login name instead and your game ID number. More options at the link above. Also, if you can't type, use ALT+TAB to change window focus and then switch back to Steam on Wine.

login LunaCrane

app_update 299360

Run the the game via taskmgr.exe -> File -> Run, while Steam is running if the game doesn't show up in your Library!

Games known to work this way (Free to Play): Block N Load, Creativerse.

Hello. I have a problem with the context menus. Whenever I click on Community/Library/Store, even Steam/View/Friends etc, the context menus are placed to the center of the screen, instead of being placed right under the mouse.
Even more annoying is the fact that when I try to move the mouse there, the menu dissapears (because it detects the mouse leaving it, I think), so I have to use the keyboard arrows.

I've been having this issue for many months now, ever since I started using Arch+Gnome... Back when I used Ubuntu+Unity they worked fine.

I use Arch x86_64 with Gnome-Shell 3.16. The problem was there in Gnome 3.14 too
I tried many different Wine versions, both 1.6.x and 1.7.x, both vanilla Wine and PlayOnLinux...

The only way I could "solve" it was by unticking "Allow windows manager ot control the windows" but this way the application icon is not shown in the dock/taskbar anymore, and instead I get an annoying win32 floating icon on my screen which gets in the way and looks very inconsistent with my autohiding dock...

Disclaimer: I'm not a Wine developer... But I am aware that Wine is rendering the Steam Client menus as separate Windows under X. So I guess the Desktop Environment (Gnome Shell/Mutter) is causing some issues - shifting them around??

I've seen this sort-of behaviour before on KDE-4 - but as of recent Wine versions it's been pretty stable...

For the past couple of days it has been nearly impossible to login from a wineprefix where the Windows version is set to XP--nothing happens after clicking Login.

The connection issue under XP isn't a Wine bug. I tested real XP in a VM, and had the same problem connecting, though in Windows I also got a popup message about Steam being unable to connect to the servers.

Setting the Windows version in winecfg to Vista or higher solves the problem.

Rosanne,
Sorry for not responding sooner... I can't replicate this issue. In fact I can still login with my Windows version set to 2000!! The Steam client does popup the usual spiel about support running out in August 2012 of course...
Bob

I should have posted a follow-up; Valve fixed whatever the problem was with XP logins a couple of days after I posted that. At the time I posted, the problem had been going on for several days, and we had a couple of threads on the forum about it.

Current Steam beta hangs after launch in any version of wine.
There is big (1-5 seconds) delay between in the steam windows and response from it.
Steam window cannot be moved or closed, menus are irresponsible.

Can't Open Games by Vittoria Genovese on Sunday November 30th 2014, 19:28

Hello! I can't seem to play any games. Mostly I try to click "play", but then nothing shows up later on.. even after 30 minutes. Maybe it's because I'm using 64 bit? It notified me that there might be problems if I continue, even after I tried changing it to 32 bit.
Help?
Thank you!

After the latest Steam update I cannot start any games anymore. Before that everything worked perfectly fine. No idea what's going on.
Now client will just become highly unresponsive when I attempt to launch a game. The game will then cycle endlessly between its "installing ..vcdist/dx/.." windows and never proceed to actual launch.
Also, sometimes a message will pop up telling me that if I proceed then my save data might differ from that in the Steam cloud.
I end up having to kill the wine server since it becomes too unresponsive to terminate normally.

RE: Can't Open Games by Metalfyre on Thursday January 21st 2016, 12:13

Oh boy, I thought it was something on my end. A few Windows based games I have in my Steam library I have tried to run, but no go! No matter what Wine version I use, they won't start or they hang. I can play free-to-play MMORPG's (e,g.: LOTRO, Aion, Rift), but games like Game of Thrones or Grim Dawn I cannot get to work. I only discovered this a few days ago. But now I see more people encounter problems.

Can't Open Games by Vittoria Genovese on Sunday November 30th 2014, 19:28

Hello! I can't seem to play any games. Mostly I try to click "play", but then nothing shows up later on.. even after 30 minutes. Maybe it's because I'm using 64 bit? It notified me that there might be problems if I continue, even after I tried changing it to 32 bit.
Help?
Thank you!

I recently installed Wine (no PlayOnLinux, wine-1.7.28 on fedora 19) under steam to play a game available only under Windows. It all worked, except I need to use the font fix from here to be able to read the font:

RE: installing on playonlinux by Rob on Wednesday November 12th 2014, 17:14

Well your details of what you've done are pretty rubbish as well!

Please can you give the "$PWD" (present working directory) where you are running this command. Is the "SteamInstall.msi" file in this directory? If not the wine command will fail (like any Unix command with a non-existent path).

If you have winetricks installed (it's in most distro repo's) you can alternatively do:
export WINEDEBUG="fixme-all"
export WINEPREFIX="/home/tatsu/.PlayOnLinux/wineprefix/default"
winetricks --no-isolate steam

Exporting your environment variables is a lot easier to do. Then any subsequent wine commands (ONLY in that terminal tab/session) will reference your specified WINEPREFIX.

Not sure about the capitalisation and paths on your system. I don't use PlayOnLinux so I don't know where it stores it's application WINEPREFIX's.

Please note this isn't a support site for PlayOnLinux!! I agree with you that it sucks - but please go and moan about it somewhere else (e.g. www.playonlinux.com/en/)!!

Steam monitor crash with certain games by Xavier on Sunday August 10th 2014, 17:45

I installed steam via playonlinux on wine version 1.7.22 and Installed some of my games. most of them worked but when I installed Skyrim and Burnout Paradise I had problems. both of them start fine but if I wait to for more than a few minutes in the menus or if I try to start a game it will repeat a sound from the game and my monitor will disconnect from my computer. I end up having to force reboot because I cant see anything on screen. I've checked everywhere and nobody seems to have had this problem before so if someone can please let me know if there is a fix to this

RE: Steam monitor crash with certain games by Horațiu Mlendea on Sunday September 21st 2014, 19:32

I don't know how to solve this but I can give you a tip. Bind the command 'xkill' to he Ctrl+Alt+X shortcut (or anything else), this way, if a application freezez and there is no way to close it, you can press that key combination and then click on the application (if it's fullscreen then click wherever on the screen) and it's gone (sometimes you may have to also kill the process after that, but not always).

Also you can make a key shortcut to restart the whole X server (I use Ctrl+Alt+Backspace)

i think promblem somewere there
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
and too many last strings
No have this before.. mb not update a change provider today also.. but how fix it..

So anyone else having problems launching any game from the steam client after the update? Worked fine this morning, saw that there was a client update, updated, nothing worked. I updated WINE to 1.7.17, wondering if it was my older version causing issues. Games still won't launch. (I tried the game via command line without steam--it's an Arcen game--and it worked fine.)

search "General Workarounds. " on above
and do what it said:
Delete all files in your Steam folder (default is typically: ~/.wine/drive_c/Program Files/Steam/) except the file steam.exe and the folder steamapps.

Re-launch your Steam client - in order to re-download all application files.

Your Steam games will be intact - since all these games are stored in subfolders of the steamapps folder.

After upgrading from Ubuntu 13.10 to Ubuntu 14.04 I'm finding an error that prevents me from login into my account and, thus, from starting any Steam game.

My Steam has previously worked fine, it was working ok the last time I tried it (maybe a couple of weeks ago or three). I just run into it today to check if the upgrade broke something... and well, apparently, it *has* :-)

When I run Steam using the short-link as usual it starts OK, the dialog announcing that "Connecting to account: username" pops up and as I have not logged in recently, it asks me to enter my password.

But I cant find a way to get the text inside the input, not via direct typing, nor via copy-pasting the password from outside.

Today i purchased One Way Heroics.
When i run it from steam (clicking the Play button), it sometimes screws Xorg, and the steam terminal always spits indefinitely :
"libpng error: Read Error"
So it's unplayable this way.
If i run the game from another terminal (wine Game.exe) it runs fine but the steam terminal still spits the libpng error.

Using Steam Community without app crash by Sebastian Loncar on Thursday February 13th 2014, 0:11

I found out a way to use the steam community without app crash. There are to ways to solve it: using the native imm32.dll from an existing windows machine, or make a small patch in the wine buildin imm32.dll source and recompile it.

RE: Using Steam Community without app crash by Rob on Thursday February 13th 2014, 1:57

Sebastian,
I don't actually use the Steam in-game Community overlay myself. However I'll test this patch out on my Gentoo install and confirm that it works. If so... then I'll add a link to the patch in the WineHQ AppDB page for Steam.
Thanks,
Bob

There is a problem with steamoverlay when you launch a game.
Its that chat/community functionality where you can press Shift+Tab to go back to Steam when you are in-game.
Looks like a new Steam update broke Wine again.

works for you can you post a bug on WineHQ Bugzilla... Also posting back here would be useful or at least link to your bug report...

What graphics card and driver version/DE/Distribution are you using?? I'll update the Steam Wiki if there is still a general problem with the game overlay thingy and certain games... I certainly used to give a lot of grief...

RE: All games crash now (Wine 1.7.8) by Rob on Saturday December 14th 2013, 9:45

Working fine for me here (Sabayon Linux).

I force an update of the Steam Client to the latest version 11.12.2013. I am using a Git build of Wine (from the Portage tree) - as Sabayon is only rolling with 1.7.4 in the binary Entropy repositories.

The Steam client launches, detects my system hardware correctly (in the Help menu). I am able to launch and play games as normal. In fact the Steam Client appears to be more snappy than it used to be... Perhaps that's just my new shiny 44/19Mbit Fibre connection :-)

Given your error messages - I would say your Wineprefix is somewhat misconfigured... Just go on the WineHQ forums to get some proper help...

RE: Steam freezes after opening the library by Karol S. on Saturday December 7th 2013, 7:29

I investigated it a bit more; it only freezes when I select Civilization V, and it was the game that showed up first when I clicked the library. When I managed to select another game, I could select games at will and everything worked until I clicked Civ V again.

Steam dies after login by mzneverdies on Wednesday November 6th 2013, 2:21

Starting today -06 Nov 2013-, after a steam update, my Steam dies right after trying to log in. I'm using latest wine (1.7.5) which ran ok yesterday.
My prefix is not clean -steam, d3dx9, dotnet20, dotnet30, dotnet35 installed through winetricks-, and I'm using Steam Beta update.
When I get some time I'll try a new clean prefix and Steam stable, but my hopes are down, since it seems I'm not the only one complaining (ej: ubuntuforums.org/showthread.php?t=2186118)

RE: Steam dies after login by mzneverdies on Wednesday November 6th 2013, 2:32

Steam Beta Update is no longer working on wine -dies right after login, as explained on my previous post-. But after removing my .wine to get a clean prefix, Steam (vanilla) works. If you change to Steam Beta Update it will crash again, even on a clean prefix.

Steam is working fine here on Arch. Just ran all the Arch updates to check this (including wine 1.7.5 of course). I haven't logged into Steam for a couple of weeks on my laptop. Forced the Steam update - went through without any problems...

Are you sure you need all those extra applications in your wineprefix?? dotnet packages are known to break stuff in Wine... badly!! The full d3dx9 package is also rarely (ever??) recommended for any games...

RE: Steam dies after login by mzneverdies on Thursday November 7th 2013, 3:41

What broke my Steam yesterday was opting into the Steam Beta Update (developer.valvesoftware.com/wiki/Betas).About my prefix, it was clean the second time I tried. But as stated, Steam does work, what didn't work -yesterday at least- was Steam Beta.

Sorry I didn't catch that bit... Beta's are designated as unstable so I'm just not at all sure how this is of use to anyone else using Wine/Steam?? What's the point of using a Beta (especially via Wine) when Steam updates every 2 weeks these days??

I'm facing the exact same problem: non-beta Steam version, wine 1.5.20 and as soon as I hit enter to log into my Steam account, Steam.exe crashes and generates a dump file. I'm running wine through PlayOnLinux. More detailed information can be found here: www.playonlinux.com/en/issue-3500.html

What OS are you running Wine/POL on? Is a 32-bit build of the OS? Have you tried running Steam on stock vanilla Wine? For reference Steam is working fine for me on the latest build of stock Wine (1.7.5).

If stock Wine 1.7.5 doesn't work for you then you post on the WineHQ forums (don't mention POL there!!) Get some proper help. This AppHQ comments are useless for debugging... I don't really know why people insist on posting here... There is no support for mark-up, etc.

RE: Steam dies after login by Mariano on Tuesday December 3rd 2013, 20:15

I was running wine 1.5.31, when after the update I found myself with the exact same problem. I even updated wine in order to rule a version problem out, but the same thing happens (even after a full reinstall of Steam).

I am pretty sure that the last Steam update is responsible, I did restore a backup and disabled updating of Steam, problems gone... usual tricks like "delete all except Steam.exe and SteamApps" wont help.

Stuck on Connect/login by Joni Larsen-Haikarainen on Saturday July 20th 2013, 4:39

If I select to save password the client gets stuck at Connecting Steam Account: [my account name]
If I select not to save password it gets stuck on login screen with only abort button working.
Tried every surgestion I can find. Reinstalled multiple times in a clean prefix.

Thought it might be the login servers that are having problems but no. My Linux Steam Client can connect and works fine.

RE: Stuck on Connect/login by Joni Larsen-Haikarainen on Saturday July 20th 2013, 13:32

Once every 100 tries (no joke been at this for over 6h now) of deleting the blob file and starting Steam again it starts for me. But I can't install any game.
Then it just get stuck on Preparing files for whatever game. Download never starts.

Ok so if someone else happen to have the same problem as me here is a work around.
Start Steam/Steam Game you want with taskset -c 0
Then when your game is running check what its PID is with ps -U username

and then allow the game process to use all cores with:
taskset -p 0xFFFFFFFF PID

I'm using wine-1.6rc5 on my Gentoo install (basically haven't sync'd yet to get the final release). There must be something odd with your setup. I'm using a core i7 920 @4Ghz, 24Gb RAM, Nvidia 8800GTX (with driver version 325.08). Using a stock KDE Desktop. So a quad-core CPU (with hyper-threading enabled as well), no core-limiting options and Steam runs fine - along with all my installed games.

If you're using stock Mint - then it's probably just an issue with Gnome 3 or Mate... Possibly the gcc compiler version/switches used building your version of Wine in the Ubuntu PPA?

I'll probably delete this thread if no one else can duplicate your problem... It isn't going to help anyone you can't figure out what your issue is... Submit it as a bug report (but you'll probably receive the same response I've given you - "not duplicable".)

I agree its odd and its most likely some odd usecase.
Not sure what it would be though.
a lot of people use the PPAs I use.
And I have tried both in Cinnamon and Mate same thing.
Tried with 32bit and 64bit WINEPREFIX same thing.

Only unusual thing with my setup would be that I have a fairly new graphic card. But then why would a CPU thing fix it.

Just curious what kernel version do you use?
I have 3.8.0-26-generic. (its a level 5 update in Mint so most users wont apply it.)

As for what you do with the thread I don't really care.
I have a workaround that works for me so I'm happy :)

Kernel version is 3.9.5 (customised version - nothing fancy really). The latest Nvidia drivers don't yet support kernel 3.10 on Gentoo :-)
Doubt this will make much difference... Your problem is more likely a userspace issue (especially since that is where Wine runs).

Things to look out for:
* filesystem+mount options used for your Wineprefix
* Windows version set for Wineprefix/Steam client
* OpenGL acceleration required by Desktop (is the issue present in a fall-back session??) - IMHO Kwin is way more stable than Compiz/Muffin/Mutter :-), etc.

Just what I would check anyway...

Scott Ritchie (who maintains the Wine PPA) really knows what he's doing and will generally pick the best supported version of gcc, etc. Can't see your Wine build being an issue...

Well thing is Steam used to work fine for me in Wine before.
And the only things that I can think of that has changed sins last it worked as it should is Wine, Nvidia driver and Kernel update.
And update to Steam of course.

I have not changed filesystem/mount options on my /home for years.
And as for Windows version I tried XP, 2K, 7, 8 long before I contemplated trying to limit the number or cores it could use.

MATE uses no OpenGL at all as fare as I know. and I had the same issue there as in Cinnamon.

Worst case I just use my work around untill Linux Mint 16 when i do a clean install.

Also.
I really play a LOT of games.
Both native once and in Wine.
and no other game has any problems like this for me atm.
Only games I have had to use taskset on before has been really old Windows games that was made before there was multicore CPUs.

If this was a problem with anything else than Steam you'd think some other games would show similar problems.

With the new update Steam suddenly have stopped bootstrapping correctly under Wine-1.5.24 and later.

Now, when starting, Steam client tries to verify the files (just like after a fresh updating), finds all of them to be correct, then shuts itself down completely without messages and/or other signals. Neither bootstrapping log nor console output indicate any errors, it just looks like an ordinary shutdown process.

I've found this behavior under Wine versions from 1.5.24 to 1.5.29. With a downgrade to 1.5.23 everything works perfectly though.

Re-installation of a fresh Steam distribution within a fresh wineprefix have no effect, the problem is still present.

You got me worried for a second there!! However on my Gentoo (x64) system I'm still able to launch Steam (and then play my beloved S.T.A.L.K.E.R.:SOC) as normal - using wine 1.5.29. Your problem must be BSD related...

New Steam Versions by Christopher Cope on Sunday March 3rd 2013, 11:35

Since the recent updates I have to launch steam with -tcp or it won't connect to Steam. I tried a new wine prefix with the same behavior. I have the Linux version of Steam and do not have to do that with it.

Also, on the dwrite issue. You can download --link removed-- and apply it to your wine registry to prevent having to launch Steam via -no-dwrite each time. It will also hold between Steam issued restarts, unlike using the -no-dwrite option.
After you have it downloaded open a terminal in the same directory and run

wine regedit disable-dwrite.reg

EDIT: I was unaware that mediafire links were not allowed. The file contained the following

Bug: Steam window will auto-maximise by pfftzo on Friday February 22nd 2013, 0:13

I haven't maximised my steam window, because I have the friends list next to it.
But when I launch a game and exit it, the Steam window will maximise itself magically, so it covers the whole screen and the friends list with it.

Steam stopped working after killing wineserver by Josh Raymond on Friday February 8th 2013, 23:14

Ok, so I was using steam (the windows version, through wine*1.5.19*) and was downloading Fable 3. I did a wineserver -k command without realizing steam was still up, and ever since steam refuses to work.

Steam Client : purchasing new games broken? by Rob on Saturday January 5th 2013, 9:16

Anyone else tried purchasing games with the client over the holiday season :-) ??

I am seeing a problem similar to a network timeout - when running the Steam Client natively under Windows XP/7. When clicking on the "Purchase for myself" button the Steam Client gets stuck trying to load the secure purchase page? It doesn't crash - but one is unable to complete the purchase... Anyone else seeing this?

I've tried under both 1.4.1 and 1.5.20 - with the same results. I've also tried running Wine under a few different distros to double check the problem is specific to one...

A recent Steam update appears to have broken this feature!! I've previously been able to purchase games directly within the Steam Client when running under Wine...

RE: Steam Client : purchasing new games broken? by Rob on Thursday May 30th 2013, 15:21

Hi Joël,

Valve are updating the Steam client way more frequently then they did a few months ago - it's just such a moving target now.

I think game purchasing was working again (after my original comment) - can't remember though. I have no need to purchase anything myself just now :-) I'm naturally more concerned that the Steam application runs well and lets me play games that will run under Wine...

You can always purchase games directly from the the Steam website (using a native Linux browser)... Sorry I'm unable to help more with this issue... It's hard to fully test this problem without confirming a purchase...

(I added a space between slashes to prevent appdb from deforming it) Problem is that I'm post 1.5.9 (or whatever version they started using dwrite.dll) and it starts it w/o the -no-dwrite command. I fixed it with this registry entry:

The second problem is that, after running it once, steam changes it back to it's default. This is actually smart behavior to deter malware, but is getting in the way in this case. Still, I thought I would post it anyway (maybe I'll get an even better fix later).

Stuck in Tools listing view by Zeb on Thursday December 20th 2012, 3:21

Hi,

I have listed the Tools (using the View->Tools menu) but am unable to go back to the installed game list view. I can click on Games view in the View menu, I am stuck in the Tools list.
The native Steam (which has just been released) does not behave the same, so it seems to be a bug with the Windows Steam run under wine.

I reply to myself:: I think the problem is a focus issue. I have been able to unstuck from this situation by switching to the small mode. Then the menu "All Games"/"Tools" etc on top right is accessible, although sometimes the drop-down menu is under the window, making it difficult (but not impossible) to click. Switching back to large mode may fix it, but sometimes you may lose the focus again.
I am surprised I had no reply to my post: am I the only one to observe this?

Noticed that steam can lauunch bash scrips that renamed into *.exe files.
I can launch Anno 2070 from other wineprefix in steam from its own wineprefix.
Need to rename bash script to exe and add it to steam as other game.
When launching steam will say that it fails to start but then game launches.
Wine cannot launch that exe file itself.

I have installed libnss-winbind,libpam-winbind, libwbclient0 and winbind

I have installed the i386 nvidia drivers, and I tried to install steam using 'winetricks --no-isolate steam'. The normal installation windows open up, I click to accept the license, and the steam client begins to update itself.

After the installation finishes and attempts to run steam, it fails with "Fatal Error: VGUI_Setup failed.'

When I double-click on steam to start it, a window pops up with the message 'Fatal Error: VGUI_Setup failed'.

I am currently reading through the FAQ, but any help would be appreciated.

Steam windows will not unmaximise: by Benjamin on Friday October 5th 2012, 14:34

Steam works fine for teh most part, until you maximise a window. Once maximised the windows (including the friends list window) won't allow you to unmaximise them, clicking steam's unmaximise button causes the button to animate, but that is all.. Other buttons, such as minimise, and close, are working as intended.

It was fixed in 1.5.13 though, which is probably why you couldn't find it. That said, some people, including myself, are having other issues with window management of steam windows. Perhaps yours is the same. Personally, I only have major issues with Xfce's window manager regarding steam windows being screwed up. It seems hitting 'minimize' always fixes my issues until the window is brought back up again. I'm not sure if any of my other random problems (abnormal lockups of input in tf2 + mouse being moved out of the window at random etc) that started at about the same time are related to this or not.

I'm looking into doing some regression testing for this when I get the chance. Since our issues may not be related, you should probably do the same.

all games/installed dropdown issue by Tim Middleton on Tuesday September 25th 2012, 10:00

In the last week or so I suddenly noticed that the dropdown on the game library where you select "all games" or "installed" to filter your list of games no longer drops down. Not sure how long this has been a problem, as I had it set to list "installed" games and hadn't got any new games for quite a while. Now, having a new game, I find i can't change the list filter anymore, so can't see anything but my current "installed" games in the steam client... anyone else experiencing this?

Well, damn. It seems I was wrong, and the issue is still there. I just inadvertently figured out how to work around it. Accordingly, I'm not sure if the commit mentioned above is or is not the culprit.

In 1.5.15, this still happens for me. I think I know what's going on, however.

When it occurs, if I hit close on the steam window and then re-open it from the system tray and try the menu again, it works. (NOTE: I am using Windows7 mode. By "close", I am referring to the window manager border X instead of the steam window X. That may or may not make a difference.) From a few minutes of tinkering around, the menu appears to fail when steam is "unminimized" via the task manager, but works when the window is brought back up from scratch via the system tray icon 95% of the time. However, I just noticed something else -- when the menu fails to appear, it doesnt actually just fail. It is apparently drawn *under* the main steam window. So if you click the menu and it doesn't show up, and then just minimize steam, the menu will appear under it in the same position it would've been at if drawn properly.

I am in awe of your debugging skills with this. Thanks for looking in to it.

I switched wine on the steam wineprefix to use windows 7 mode and got the window manager frame. Using that to close I still couldn't get the menu to work.

However, thanks to your description of the menu being drawn underneath, I discovered another weird work around. If you click on the menu and hold your mouse button down, then move the pointer downwards (with mouse button still held down) and release mouse button where you think the menu item you want might be... it works. It activates the menu item, though you can't see the menu.

The order of the menu seems to be: All Games, All Software, Recent, Installed, Favourites. So drag the pointer down over the invisible menu to the approximate location of where you imagine the drop down menu entry should be, and release. It's like a mini-game.

Steam overlay works when running steam from windows partition by Adam on Sunday September 23rd 2012, 12:03

I am running slackware64-current with multilib and had steam working ok by running it from my real windows 7 installation where steam was already installed. Even the in game overlay works.

I wanted to get rid of windows from this PC, so I installed steam using winetricks and nothing would start. I found out now that this is because I need to disable the overlay, but find it strange I need to do this when the overlay works fine if I run my already installed Steam from my windows partition.

I am using the latest stable version of steam on both installations, and I have checked that I can definitely use the steam overlay by pressing shift-tab while in a game. Anyone have any ideas why this would be happening? From what I have read I shouldn't be able to use the overlay at all.

RE: Steam overlay works when running steam from windows partition by Rob on Sunday September 23rd 2012, 12:33

@Adam,

The Steam client overlay is still a bit flaky with some combinations of display drivers and desktop environments... Hence winetricks plays it safe and disables it. I don't really use it myself - so can't comment further...

If you do:
whereis winetricks
You can inspect the code. It's a pretty simple BASH and Perl shell script. Some might even say it's a "hack"!!

The settings that winetricks pokes into the user .vcf (Steam configuration file) don't seem to work so good anymore!! When you first start Steam, which was installed using winetricks, Steam thinks that the game overlay is enabled.

Winetricks also disables the gameoverlay.dll and dwrite.dll in Wine. You can re-enable either of these quite easily - just use winecfg in the appropriate wineprefix.

I've previously mounted my steamapps folder from my NTFS partition on a shared Linux (ext4) partition (using a bind mount point). I was forced to use a 64-bit Wineprefix to match my Windows 7 (64-bit) install. It appeared to work but was a bit flaky to say the least...

You potentially lose some FPS because the NTFS-3g libraries run in userland and aren't nearly as efficient as the ext4 kernel driver.

Also what bugs are caused by dodgy interactions between your Windows Steam client and Linux Steam client??

RE: Steam overlay works when running steam from windows partition by Adam on Sunday September 23rd 2012, 13:02

My Windows Steam and Linux Steam never interact with each other :) I have one running from the ntfs partition (with overlay) and one running from ~/.wine/drive_c.

You are right about the overlay being a bit flaky. Sometimes it will open up and then close itself again, I think this is probably because I have focus follows mouse set in the window manager. I also have window focus following the mouse in windows 7 and steam doesn't like it at all.

I have a simple request steam work out of the box for me with these instructions, I'd just like to drop my steam games from windows into the steamapps\common folder like I did so many other times, steam just has to check files and update registry and shortcuts rather than download the whole again.

However my Wine C drive shows empty program files and program files (x86). Steam isn't there, so where is it?

keyboard issues in Precise 64... by Mariano on Tuesday August 21st 2012, 13:51

I don't know if anyone has the same problems, but either in 1.4 or 1.5.11 (which, BTW, selecting dwrite in the overrides list on wine-cfg, and flagging it as DISABLED solves the problem in this and .10 versions), there is something that conflicts between wine and UBUNTU (12.04 64bits). Recently I upgraded from Lucid where everything related to wine worked mostly fine, but now, most games ignore the L-Ctrl and tilde (~) keys. The Control key is needed in most action games for things like crouching, and the tilde is used to bring up the debug editor (games like FO:NV are mostly unplayable if you don't know how to "get off a rock" from time to time). The thing is, most of my games work under STEAM, and that's why I came here to ask for ideas/solutions.

I've been trying to setup my usb microphone which is a logitech usb desk microphone. The chip itself is a Asahi Kasei Microsystems AK5370 I/F A/D Converter. I can use this microphone okay in Linux apps but Steam struggles.

I select the microphone in the Wine settings under the Audio tab. But Steam still tells me there is no microphone detected. Any thoughts?

RE: Official release STEAM linux by Rob on Friday July 6th 2012, 17:02

@Thomas,

I thought great to this at first. But surely we'll end up in a similar position to Mac users...

As an example games like STALKER aren't going to be ported to a Linux-based platform - by a (now) defunct studio. It only (pretty much) guarantees that most Valve games will have a native port. These games generally (my experience) run pretty well under Wine already.

I think the main thing that a native Linux Steam client does for Linux eco-system is perhaps to put the Linux Desktop on the road-map of bigger corporations (like EA/Bioware, etc.).

I've been following the dubious rumour-mongering by Michael Larabel @ Phoronix for some time now...

I personally think Kicker Starter projects have more potential to do justice to the Linux ecosystem. Put some of my money into Wasteland 2 for instance...

I've installed d3dx9 as recommended, but Steam is running incredibly slow when running it in wine, in comparison to the same machine running it in windows. Steam is using 10-40% of system resources even when completely idle and the interface is hugely choppy, even when just flipping through windows. The images load slowly.

Is there any way to improve the performance? I've merely used the automatic Winetricks install, coupled with installation of Gecko and as was mentioned the d3dx9. Still, I feel like there's something enormously wrong, because my computer gets all worked up just running the basic interface. As I said, this didn't use to be the case with Windows.

It happens because wine tryes to debug the running program by default. To disable debugging you should run steam like this:

WINEDEBUG=-all wine

Also I guess it wasn't necessary to install d3dx9 because wine notifies that this may lead to problems. Anyway, if you don't like the way of starting Steam described above, you can add the following line to your .xinitrc:

export WINEDEBUG=-all

and run Steam as you usually do.

I personally use a script which I wrote and saved in the /usr/bin/:

#!/bin/bash
WINEDEBUG=-all wine
exit

When using this script you can run Steam by just writing "steam" in your terminal and pressing Enter.

I've had wine running with steam perfectly for some time now, but recently, after both updating steam and my OS from Ubuntu 11.10 to 12.04 (which in turn upgraded my wine to version 1.4), I get the error "ERROR: Failed to set file attributes, Win32 Error 5". I have the wine folder on my windows partition (separate from my programs installed on windows, though) and I'm not sure how to fix this or what to do. I've tried re installing but it didn't work. My other games(Crysis 2 v1.0, Assassin's Creed 2 latest version), however, still work. Anyone got an idea on what I should do?

Thanks for the comment! I looked at the permissions and it was Owner: root, Group: plugdev, and others: none and I believe that the permissions were only to access files except for the owner. I installed the ntfs configuration tool (which I had on my old ubuntu), set it up and it worked perfectly. Thanks for recommending to check the mount permissions! No I feel bad that I uninstalled it and have to reinstall my games. At least soon there will be a Steam for Linux (recently verified with photos of left 4 dead on ubuntu 11.10)!

Ah remember you can always pull around/copy the steamapps folder (including from a Windows install). Glad you got your problem sorted out though!

RE Steam for Linux - it'll be a shot in the arm for (GNU!!/)Linux Gaming but a lot of non-Valve games will never be ported to it. Any that use GFWL, Punkbuster?? How many "real games" can the Mac Steam client actually run? Especially thinking of my love of the S.T.A.L.K.E.R. series here (SOC/CS run quite well in Wine these days)! GSC ain't going to be porting anything if the studio is "closing"!

I seem to have the problem that steam refuses to launch any game on a fast computer almost most all the time. It's not related to steam overlay and no information is shown except that the game starts but no window pops up and it can only be killed with kill -9.

Yesterday I finally figured out it might be due to my computer being too fast which triggers a race condition, and I created a simple burner script that seems to workaround launching:

How to SOLVE bug 21770 "Keyboard not recognized" by Mariano on Sunday March 18th 2012, 9:33

When playing on a VD, after wine 1.3.38, sometimes, some games won't recognize the keyboard, and no matter what you do, you only have the mouse to use. The problem resides in the fact that wine is using a VD and Steam opens a VD for itself when you start the game. The only thing you need to do in order to have the main window (the game) in control, is Alt-Tab into "wine" again. :)

Sadly, there are games outside Steam that present the same issue, but this solution won't work. :/

However I am not seeing this on my Kubuntu 11.10 install (Nvidia 290.00 drivers I think - not booted into it just now)... Anyway it's probably one of the many multi-arch errors introduced in 11.10 (perhaps Upstream Debian problems).

Can you play any native games that have 32-bit binaries? If not then the ball is in your distribution's court...

Steam does use OpenGL for rendering. I'm not seeing any OpenGL errors, reported in the console output, when running the most recent update (20.03.2012) of the Steam client. I am using wine 1.4, x64_86 ARCH-Linux, ATI Catalyst 12.1, and 32-bit wine prefix. It also works fine with wine 1.5...

Can you detail the steps you used to install Steam. Have you tried this in a clean 32-bit wineprefix?

I presume you have the 32-bit proprietary Nvidia libraries installed - since you say Eve works in a 32-bit prefix.

Please don't be vague about the information you are giving - what version number of the Nvidia drivers are you actually using? Not everyone in the world uses Ubuntu after all... :-)

Just for future reference it's better if you say what version of Wine you are using (wine --version)!! We know the Ubuntu Wine PPA tracks the release version of Wine quite closely (Scott Ritchie is "on the case") - but it's easier if you are exact when asking Wine-related questions... No code of conduct @WineHQ :-)

Anyway...
You need to install the 32-bit version of the drivers for your graphics card. You are using a 32-bit application (Wine) - on a 64-bit version of Ubuntu. Depends on your graphic card make (Intel. AMD or Nvidia) and model... Whether you are using the proprietary driver (AMD or Nvidia) or not... But it's usually easy to find in Synaptic (package manager). It'll be a package with ia32 or similar...

Thanks for the solution, although it dosen't make thing any less complicated. My uses a GPU integradedd into the CPU for graphics; and as such, the drivers are compiled directly into the kernel for Ubuntu. In addition, when I have tried to use a 32-bit kernel on the system, I have numerous provlems with memory and cache usage; so I'm probably going to have to use a virtual machine runing 32-bit linux and run wine on that, in which case I won't have enough processing power availible to even be worth trying to run Steam.

If it's not too old an Intel GPU you will may have quite decent OpenGL support. The kernel module may be pure 64-bit (it has to be because only user space applications can switch to the 32-bit comptability originally introduced by AMD) - but you should still have 32-bit intel libraries to allow 32-bit applications to interface to the OpenGL layer.

On my ARCH install on a laptop, with an AMD HD Radeon 4650, the FOSS library is called "lib32-ati-dri":
multilib/lib32-ati-dri 7.11.2-3
Mesa DRI radeon/r200 + Gallium3D for r300 and later chipsets drivers for AMD/ATI Radeon (32-bit)

Ask on the Ubuntu forums (this is __not__ a Wine problem!!) Or have a poke about in Synaptic for something similar with "intel" in the name instead of ati and a "32" for 32-bit... On ARCH Linux the package you want is called "lib32-intel-dri" - must be something similar on Ubuntu...

Don't bother with running Steam in a OS on VBox or similar - unless you are planning to play 3D chess or similar... :-)

BTW do read the faq on this page as well (you have right??!!) You need to have the _native_ Linux Samba package - Windows filesharing protocol - installed as well (Wine needs to interface with winbind, I think from memory, to run the Steam client).

I get the same problem recently. Same install I've been using for well over a year, but after a steam update I got that error. Given that it worked until Steam updated I would assume this is something Steam changed and not a graphics issue? Thoughts?

1) It would be nice if you actually read through the FAQ on the WineHQ AppDB page for the Steam client application. The fact that you are posting console output with a missing win_bind error doesn't encourage me to help you!!

It does sound like a configuration error with your system rather than a Wine error/Steam client update issues... For reference the latest version of Steam is working OK here (can't verify with OSS ATI driver - due to the fact it sent my laptop into thermal meltdown...)

I was trying to solve the primary issue...aka the OPENGL32.dll as again this was working on this exact setup for well over a year. So reading through the Steam FAQ seemed unnecessary. I have fixed the winbind issue, but still left with the real problem.

I have reinstalled manually, using winetrick, and deleted dlls to force steam to redownload them (as suggested in half a decade old steam forum posts). There is nothing recent on the internet about this that I can find other then this comment set. I am more surprised that no one else is having this issue.

Deleted entire wineprefix directory. I went ahead and did `export WINEARCH=win32` and attempted to run winetricks, but it outputs an error. I then proceeded to install manually by downloading and executing the msi. After installing I am left with the same message. That seems consistent since as I said I had been running this for well over a year, apparently on 64bit prefix. Something else changed in steam and if you look online you will see this exact error about the filesystem.dll used to be an issue on windows many years back and a few reports in the steam forums more recently.

Thanks for you things to try, really not sure where else to look. For whatever it's worth here is the more recent output paste.kde.org/435782.

FYI I've updated the Steam Client FAQ with the correct instructions for installing to a 32-bit Wineprefix (with a Multilib Wine/Linux distro) using winetricks. I don't know if the latest winetricks script release fixes the bug you found - but it's easily worked around in the 2011 version :-)

Could potentially be an OpenSUSE packaging glitch then... I have been using a Wine64 wineprefix for Steam, with my AMD/ATI GPU, it works fine for Steam - it's only the odd game (e.g. BioShock) that won't run correctly... Sadly I can't test using the FOSS ATI driver.

Why not post in the WineHQ forums (which are an excellent resource). I know a lot of the Wine developers will be able to spot the difference between distro packaging errors vs. missing libraries (native-Linux or Windows).

One of the reasons I mentioned the "winbind thing" - is that will drive the Wine devs. crazy if they see that error in someones' console output! They are right though -the console output is telling you **exactly** what is wrong!!

Yeh to use winetricks to create a 32-bit WinePrefix from scratch is a bit fiddly (with a newer multi-lib Wine). I will update the Steam AppDB page wiki instructions on how to do this correctly... Thanks for the feedback!!

Games Launching Is Quirky by Christopher Cope on Thursday February 16th 2012, 15:24

This problem has been with me for as long as I've used Steam. From wine version 1.2.3 to 1.3.37. Steam with say it is preparing to launch the game, but no extra processes are started. I've tried using applaunch and disabling Steam In-Game Community, with no effect. If I go launch the games directly some of them work. However, most disable online play or just refuse to work when launched directly. The thing that confuses me the most is that this doesn't happen all of the time. If I close steam and open it up later it may or may not launch the games. No terminal errors are thrown or anything that would let me know when or why this is happening.

How I do steam for steam games testing by Maquis196 on Thursday February 9th 2012, 10:32

Just in case this suits anyone the way I do it is to have a /home/maquis196/wine_games directory and create a wine_global_steam directory in there.

Then wineprefix a dir in wine_games (like WINEPREFIX=/home/maquis196/wine_games/wine-steam-gold) and do a mount bind -o /home/maquis196/wine_games/wine_global_steam to the usual Program\ files/Steam in the wineprefix.

This way, you can share one steam install but different prefixes can use different dll's, settings, etc. A symlink won't work because steam is very fussy when it comes to installing/updating games but wont be an issue with using mount bind.

Very very good for testing a game in a fresh prefix without having to backup/restore games which can take a while.

If I whistle at my self - I can hear myself and the microphone level works! (Ok I has no Steam friends :-( ).

I still see the "[ No recording device detected ]" notifier above this... But hey so what if the device/audio actually works!

Can you confirm this finding with your setup and a recent version of Wine? Ideally the latest Git which has other Steam client fixes which you would benefit from (like the mouse click capture and jumping Steam window are fixed now)...

If you can duplicate my findings then I will add it into the FAQ and Git bisect to work out exactly when it started working!!

I am using wine 1.3.37 on arch-linux x86_64. I see the 'no recording device detected' message, and when I test I don't see the bar moving. I'll try updating to wine 1.4 when I have time to mess around with it and report what happens...

I just use a hack to roll with the latest version of WINE. I enabled the [multilib-testing] repository but I move it down below the [multilib] repository (in pacman.conf). I force pacman to install Wine from the testing repository by using:
$> pacman -S multilib-testing/wine

Have you tried tinkering in with winecfg for your Steam WINEPREFIX? It lets you choose the default WINE device for recording/playback (in more recent versions). I haven't really tested how well this works - but it's a step up from only being able to select 'ALSA'!!

If you get messages like "Completing Installation ... 1%" followed by errors like "Steam servers were too busy to fulfill your request. Error Code (2)" or "Error Code (55)", Steam is yelling at you for these reasons:

1. You are not running Steam from its normal installation path on C:\Program Files\Steam. Go into winecfg, make sure your C:\ drive is configured, and make this path exist.

2. You may think it'd be clever to symlink or something. Do NOT do this. Newer Valve games like LFD2 and Portal 2 choke to death if the folder used to access the game doesn't have certain likeable attributes (unsure what these are). A symbolic link will not fix anything, you will continue to get the same errors. You must move the Steam and steamapps folders into that path for real in order to launch.

I do not believe this is a WINE bug as many Windows configurations experience similar issues if Steam is not placed in the expected path or drive.

Spent a couple of hours struggling with this tonight. Portal 2 seems to run great after this workaround. Hope it helps someone out there.

Forgot to mention, use wine start "C:\Program Files\Steam\Steam.exe" in order to get WINE to read Steam like it's from the C drive. You must place the "start" parameter between the call to the wine binary and the C:\ drive path.

--
2. You may think it'd be clever to symlink or something. Do NOT do this. Newer Valve games like LFD2 and Portal 2 choke to death if the folder used to access the game doesn't have certain likeable attributes (unsure what these are). A symbolic link will not fix anything, you will continue to get the same errors. You must move the Steam and steamapps folders into that path for real in order to launch.

--
It's really clever coz it's working for me. Sure if u mean what Steam folder can't be a symlink u'r right (was tested this). I'm using symbolic links on steamapps folder and all works fine(Portal 2 etc).

So, the problem where Wine/steam doesn't detect the mouse release (so the Window keeps following the mouse cursor) still exists in wine 1.3.25. In addition, I now have a problem that occurred some time ago recurring: All of Steam's windows flicker constantly. They disappear (i.e. become completely transparent, as opposed to turning solid black or white) and reappear several times per second.

It is possible to use Steam like this, but difficult - when the Windows happen to be 'invisible', buttons are also not clickable, so it is often necessary to click the same button several times.

Are you running with Wine 1.4-rc2? It has some important Steam client handling bug fixes.

In KDE (ARCH-Linux and Kubuntu) I am still seeing a minimise to system tray bug and a window disappears when moved off the side of the desktop. The inability to release mouse click capture and accelerated jerky movements (literally like you are pushing it off the side of the screen with your mouse cursor) have been fixed in RC2.

In the off chance anyone else runs into the same quirk I did, where the 'account' tab was glitched and didn't show up right, the problem is one of the files in your steamapps folder. Either sourceinit.gcf or winui.gcf, both of which appear to be created when you make an empty wineprefix and run steam for the first time. To fix this issue, basically you need to start from scratch, run steam in wine the first time, then copy everything over to the new wineprefix EXCEPT those two files. If you run steam the first time in a fresh wineprefix before copying over any files, you should see the account tab shows up properly. My guess is something in winui.gcf comes from an old version of steam, so it doesn't show up properly if you copy it over to a newer steam version. I doubt this is related to wine, but I expect someone else out there will run into this at some point given how often some of us mess with different wine folders/prefixes.

Yes. Another user commented that it crashed when they tried it - so I tested it and found the system info crashed with Wine 1.3.21 at the weekend. Testing it yesterday (after updating to Wine 1.3.22) it appears to generate very accurate records!

Can some maintainer here assign this bug to the application? It's not only TF2 specific. This bug happens not in Steam client itself, it happens in Steam ingame overlay, for every game, in the same way as it happens in most of Source engine games except the ones based on old Source releases like Lost Coast or HL: Source.
bugs.winehq.org/show_bug.cgi?id=19522

RE: steam with gnome3 and gnome-shell by Rob on Monday June 13th 2011, 16:45

I believe this problem is caused because the STEAM client window area is set to be infinitely large - with only part of the area being drawn to. Hence this bug report (affecting Unity and Gnome 3 I believe):
bugs.winehq.org/show_bug.cgi?id=23841

I would cc: yourself onto that bug. (Comment 2 might be of use...)

Personally I won't be using Unity or Gnome 3 till they are out of alpha release status :-)

I'm having a strange problem with Steam. When I grab the top of the window to try to move it around the screen, or to my secondary monitor, as soon as I let go of the mouse, Steam will jump to a random point on the screen. It sometimes even goes offscreen, and I have to kill the process and restart Steam to get the window back. I don't use the command to run Steam in it's own window (I think the command is something like "wine desktop=1024x768" or something similar), but maybe I have to? Here's the command the launcher is using:

I can confirm that the problem goes away when emulating a virtual desktop, but this is not an optimal solution for me (also, in that mode I see a lot of graphical issues with steam windows that I don't see otherwise, particularly when moving windows)

RE: Different Window Problem by Anna on Wednesday May 18th 2011, 16:13

The patch didn't help; in fact, it seemed to make the behavior worse, and caused the application to break badly whenever you try to move the window.

Turning off 'allow the window manager to handle windows' in winecfg fixes the problem, but introduces a new one: whenever the window is being moved, and the button is released, it 'jumps' to a new position on the screen. Needless to say, this is not a great solution.

Tested on 1.3.22. The original problem is gone, but it created new problems. Now, when the mouse is released the window will often jump to a new position suddenly (usually in the general direction the window was already moving, but not always). Also, while dragging, the window will start moving erratically, 'shaking' back and forth (usually horizontally).

Okay, some interesting results. I've been testing this on two different machines. The one where I saw the problems I reported in my last post isn't accessible at the moment, but I tested on the following system:

The 'original' problem of the screen continuing to move with respect to the cursor after letting go manifested itself, but only very occasionally - one time out of 20 instead of every other click. I saw *none* of the problems I saw on the other box (the jitter and jumping to new positions after release).

I'll get detailed specs on the other machine tomorrow - in the meantime, I know it is fedora 14 x86_64, with a, I believe, an nVidia Quadro card of some flavor in it. It probably has the same driver version as the above machine.

If this is some obscure problem that will only occur on Quadros, then I'm personally not very worried about it - I don't think many people buy Quadros to run Steam; I was only doing so because it was a convenient test box at the time. Of course, if you want to keep troubleshooting the problem, I'd be happy to test anything you care to throw my way as well :)

RE: Different Window Problem by Rob on Wednesday June 15th 2011, 11:23

Hi Anna

My main test rig (a laptop running Linux-Mint 10.0 w/ ATI 4650 and Catalyst 11.5 - XOrg 1.9.0) runs Steam OK. Occasionally the Steam window will attach itself to the mouse inputs with a single L-click. This is much more of a papercut - especially given the hassle to actually get Steam games running!

RE the graphics card I was just checking you weren't beta testing the Nouveau driver, using an Intel Atom "graphics card" or something similar :-)

More likely to be a Display Manager issue on Fedora 14 - no? What are you using on that box? I would have thought Nvidia's professional GPU drivers would be better - no?!

I am trying to test out Fedora 15 but the guest additions don't work on my (Windows 7-based) Virtual Box. It reminds me a great deal of Debian - a lot of rough edges and principles! Just wanted to have a play with Gnome 3 really... but it goes straight to fall-back Gnome 2.3...

Installing allfonts with winetricks by Bobby on Sunday April 24th 2011, 21:43

When trying to install allfonts using winetricks, I got the same 404 and "opensymbol failed" response as a few other people. My problem was that my winetricks script was out of date. I checked the version number on the couple of winetricks files in my home folder; there was "winetricks," but there was also "winetricks.1" and "winetricks.2". I checked the version numbers, and the original one was an older file, while my "winetricks.1" file was the up-to-date. Fix: make sure your latest version of winetricks is named "winetricks" and not "winetricks.". Then downloading allfonts works perfectly.

I am using Steam Guard on my (Wine-installed) Steam client. It works fine. I get emailed a random code when I try to (initially) run the Steam client on a new Wineprefix. I only have to enter the code ONCE - for a fresh install/ Wineprefix.

I would add it to the HOWTO guide but I am not sure what problems folk are having with this feature...? I could say it works great (which it does for me) - but does that reflect other peoples experience? People don't seem to be commenting on it very much.

(The main issues I see being discussed are the Steam window composition bugs and the gameoverlayrender.dll issues.)

This was a while ago so probably 1.3.16 or so. I'll give it a go again tonight but at the time it simply wouldn't work!

Fact that no one else seems to have had a problem suggests it might have been just my box at the time, as you can imagine I have about 40 wineprefixes for games, half of them steam so no way was I going through that process every time :)

I don't think you can hardlink to directories in native Linux filesystems (especially if the link goes to other physical media). If I was you I would make sure the SD card is formatted with ext2. Make sure the partition on the SD card is mounted with full R/W access for your user. Then setup a WINEPREFIX on the external media for all your Steam games.

On flash media EXT3 and EXT4 will typically do more write access as they "journal" accesses to harddisk (in the event the FS gets corrupted). EXT2 is not particularly secure in this regard - but it's go to cause less wear to the NAND cells on your flash memory.

If you are new user (I presuming this!!) I would ask this question on the forums for your distro... E.g. how to create an EXT2 partition on a flash memory drive and mount this with your user (i.e. not root user). You can pretty much mount an external partition in any folder in Linux. E.g. you could mount it in a folder called /home/user/steam if wanted to. Typically the folders /media and /mnt are used.

On my Desktop rig my /home folder is on a different partition (and different physical harddisk) from my / root partition.

The Steam WINEPREFIX is separate issue you would tackle after you have completed the first step.

Don't run before you can walk! Also don't bother posting complex questions on the AppDB comments. It isn't the best place. Use the WINEHQ forums or the forums for your distro!

RE: GameOverlayRenderer Bug Fix by a player on Sunday December 2nd 2012, 8:50

Just tried this and it works perfectly! The default Shift+Tab shortcut wasn't detected but it is easy enough to change in Settings, I chose F9 because the modifier keys like Ctrl were already assigned in game.

Problem with Winetricks package download by Rashkavar on Sunday February 13th 2011, 6:27

Running Debian unstable, Wine 1.3.13, and attempting to download the fonts packages using the "sh winetricks corefonts allfonts tahoma gecko gecko-dbg vcrun2005" command as given in the procedure. If "allfonts" is excluded, the remaining packages install normally, but with "allfonts," after successfully downloading a couple of hundred fonts, it encounters the following error:

This error causes the command to stop. By looking at the error message, I checked the ftp server being accessed, and while the ftp.us.debian.org/debian/pool/main/o/openoffice.org/ folder exists, it does not contain the file being accessed; instead of "ttf-opensymbol_3.2.1-11_all.deb," it has "ttf-opensymbol_3.2.1-11+squeeze2_all.deb". This is likely an updated version of the file, but it causes problems with the download.

As some fonts were installed and I am quite certain Steam does not call for everything contained in something with such a broad name as "allfonts," I ignored the error and continued with the installation. Installation proceeded normally, and the login screen works fine, but after the dialog attempting to log on to Steam, the program simply cuts off.

Presumably the two errors are linked. Is there some way to either have the sh winetricks command ignore errors or redirect it to this alternate opensymbol file?

I resolve some strange attitude during restoring some of my steam games with wine-1.3.11. The problem appears when the game is downloaded of installed but when i'm trying to play the game steam runs "Completing Installation" dialogue. It hangs for a while then steam says that "Incomplete installation of DeathSpank: Thongs of Virtue (or Left 4 Dead 2)"

first game I tried to install Super Meat Boy on the same with help of restoring a copy being backup and it worked well and it still works.

I'm trying to figure how to run games from wine submenu in kde menu. When I try to run game this way nothing happens. So I looked into menu entry and it looks for example like that:
env WINEPREFIX="/home/users/Arvenil/.wine" wine winebrowser rungameid/20820

I tried to run this from console (wine winebrowser rungameid/20820) and nothing happens. Then I tried to run a webpage in same way (wine winebrowser www.google.com) and it worked - a google webpage opened in my firefox. So I tried to run rungameid/20820 directly from firefox and it worked - game launched. But still runing wine winebrowser rungameid/20820 doesn't work and doesn't emit any error. Any idea how to debug this?

if you're having trouble connecting to steam or downloading games try quitting/pausing your torrent client. I have always had trouble connecting, where I have to click retry many times to connect and I just realized that it only happens when transmission is running. when installing games it will say the steam content servers are too busy. starting the torrent client after the game is downloading or after logging in to steam causes no problems.

Tried to install with much google searching and stuffing around I can get the app to launch and I was able to start it once without it crashing, but every other time it opens the screen and crashes. What I tried:

Winetricks...doesn't work in x64, so not able to install most things

Tahoma font: solved the crash after initial load where the CellID: nothing beat our initial best time of 7 MS point message was displayed

Where I'm at now is I can logon, steam loads, gets to the point of trying to load the store, and then crashes to desktop, last error output from wine is about being unable to determine the processor information. So I've given up on using steam except within a VM

I had the same problem (fixed for a moment by copying Tahoma font, then crashed on next run). I copied some other fonts in: cour.ttf tahoma.ttf times.ttf trebuc.ttf verdana.ttf; and haven't had a crash since.

steam games wont start up by elliot on Thursday November 18th 2010, 11:49

im useing linux ubuntu 10.10 on my alienware m11x i had to remove my windows 7 cause it would not start up so when i go to steam steam loads up but when i go play america's army it dose'nt load it wont say preparing to start up america's army like when you start up a game normal i have wine 1.2 and PlayOnLinux that is were i downloaded steam on PlayOnLinux but i got wolfenstien to work the online version but no games wont work at all i followed you steps please help me i want to play america's army so much.

RE: steam games wont start up by Cheeseness on Friday November 19th 2010, 1:21

It sounds as though you're saying that Steam itself is working (though what you've said is hard to follow without punctuation), so here might not be the best place to ask your question.

I don't use PlayOnLinux, and I've never been interested in playing America's Army, but here are a couple of pointers that might help you:

* Upgrade to the latest version of Wine. A lot of improvements have been made since 1.2 that may be of benefit to the application you're trying to run.

* Where you can, include extra information on your configuration and what you've tried. This helps other people help you. Some things that can help you get details can be: running your Wine application from a terminal and recording any errors that come out; whether or not you have similar applications (3d games) working outside of Wine; which specific DLL overrides you may have configured (I personally have found that Steam games don't run for me unless I disable gameoverlayrenderer). If you're not sure how to do these things, ask - you'll be more likely to get assistance if you give some extra details.

* Pick another game that's easy to get running under Steam and has a high rating on the AppDB (eg: Alien Swarm) and report your success. This can help you narrow down the problem by identifying whether it's a Steam problem, or a problem specifically with the application you're trying to run.
appdb.winehq.org/objectManager.php?sClass=version&iId=20839

RE: steam games wont start up by Daniel on Sunday November 21st 2010, 4:58

I've got exactly the same problem with ALL my steam games! I've tried HL2, TF2, Garry's Mod and CSS. But it just doesn't work! The dialog that says "Preparing Start of Garry's Mod" comes up and then dissapears, and after around 5 seconds it says I'm not in game.

I'm running PlayOnLinux too and the problem started occuring after I upgraded to 3.8.6 yesterday, but I do not see how it can have a connection really.
This is the terminal output I get pastebin.com/MWzG1WsQ

I'm having some trouble with steam and a manually compiled wine. Each time that I'm using a manually compiled wine version, steam will crash when it should get to displaying the login-window (it patches just fine, asks me to install the service if I've chosen w7 as windows version, otherwise skips this step.). It also spawns steamerrorreporter.exe, and the Steam.exe process is still there, but nothing happens.

If I resort to install wine from the ppa, steam works as it should. I've installed all the stuff through winetricks, checked bug reports and everything, but still can't solve the problem. Ideas? Need more info?

Hello, I am using the stable version of wine (1.2), compiled from source, running on a custom 64 bit kernel with BFS, ubuntu 10.04 on an athlon 64 x2 5000+, 1024 mb of ram and a 8600gt. I installed Steam just yesterday, and I immediately noticed the ram usage, it uses 130-250 mb of ram, which frankly is too much for a system with only one gig of memory. And it is quite slow. Is there a patch or a tweak that could lower the memory usage ? Or is it just the webkit based browser of Steam that's using so much memory ?

Another fix for "Cannot connect to Steam network" by Ivan Vučica on Wednesday August 11th 2010, 12:28

Ubuntu 10.04 LTS, without any updates (installed yesterday, will update immediately after this)

The fix that involves writing to /etc/sysctl.cfg mentioned in the Howto helped me not the "Steam takes too long to start" problem. It has in fact helped me with Steam's inability to connect to its servers.

Since I did not want to change system settings, I used a temporary fix. (I presume it will affect the system only until restart.) As the root, I ran

When someone sends a message to you and you don't already have a message window up for that person, the message window will show up as a steam icon in the upper left corner. Resizing it does nothing, to fix it you have to minimize it them restore it or close it and reopen it via the friends menu.

I first installed Steam with defaults and it worked just great. I wanted to try first Civ III, but the installer reported "not enough space" - it found less than 1.5 GB, and I had more than 10 GB free on my /home partition. Nonetheless, I deleted some crap, but it still did not work. I then decided to uninstall Steam and try to reinstall on a different "drive". The uninstall went uneventfully but the Steam icon was left on the desktop. I then tried to reinstall, and could not.

On subsequent attempts I am asked "Are you ready to have the Installation Wizard continue the installation?", I say yes, then an "install" happens very quickly, then I get a message titled "Steam has been successfully installed." with "Steam will now continue installation." inside. Clicking "Finish" closes the window, but nothing else happens. Wineserver, services.exe and winedevice.exe die soon thereafter.

If you can't uninstall the things installed in WINE, you can delete your wine directory(/home/USERNAMEHERE/.wine) and it'll remove everything installed in wine. The next time you use Wine it'll rebuild the .wine directory and it'll be a fresh, no programs installed setup.

Yes. Uninstall wine first using your package management system (synaptic etc.). Then once it has been removed check to see if the .wine folder is still there in your Home folder. If so, delete it. Also, don't forget to delete the .winetrickscache folder which is also in the Home folder.

If after that you can still see wine in your applications menu then there will be 1 more folder to get rid of located in ~/home/.local/share/applications. Delete the wine stuff in there manually also.

I am running newest version of wine, but i am sure somewhere i am messing up. When I click steam it updates 100% then it just sits there on what should be the login screen and does nothing. I dont see anything on my desktop but steam shows up as running on my task bar. I dont have direct X installed yet. I am a linux n00b but would really like if someone could give me step by step instructions on how to do every detail.thanks

When i do some work on steam interface i can't close the main windows or the friends window using the 'x' button.
When i click on the 'x' button the window disappear but after 1 second it reappears. On windows it don't happen...

i have noticed the same thing, kinda wierd, but iv'e noticed that in order to close the main steam window you have to close all other steam windows first, otherwise it will reopen, i haven't had the friend problem yet...

RE: steam keeps downloading games on its own...? by Edward on Tuesday June 1st 2010, 22:22

It is a Steam bug (Windows bug?) and it is super annoying. I had it with Dawn of War 2 the other week and Steam suggest (or the forums, don't remember) doing a total reinstall of Steam including removing all registry keys.

In the end I 'fixed' the download paused game by deleting all local game content then going to the Steam folder and deleting ClientyRegistry and AppUpdateStats blobs and some other choice files that looked important. I then ran Steam again and let it fix up everything and then copied the game files back and verified local content. This was a suggestion on the forums and it worked for me so the original suggestion seemed a little extreme.

Yes, you'll have to remove your ~/.wine and start from scratch. Remember to go into ~/.wine/drive_c/Program Files/Steam and move the steamapps folder out (which contains all your games) before you delete it all! After you install Steam again, move the folder back before logging into Steam.

All of the fonts in steam are very aliased and italicized. Which fonts do I need to install in order to get the fonts in the new Steam UI to display correctly? I don't want to use winetricks as I don't like how it messes up the wineprefix.

Found a workaround. It seems that there is a Wine bug where variations of the Arial font in the .wine folder override the regular Arial font. So in other words, if you have the Arial Narrow variation in your .wine folder, it will override regular Arial and make it seem like Arial Narrow. By removing all Arial variations except the regular one from .wine, the Steam fonts are fixed.

Steam installs and seems to run until first update by Wrinkled Cheese on Friday May 14th 2010, 17:00

Hey everyone,

I'm a bit confused as to why steam seems to be running but I get no GUI.

I'm running Slackware 64 with multi-lib for wine 32-bit compatibility. I installed wine and everything seemed to go okay. The first time Steam ran it said updating steam and went to 24% then closed and then came back at 33% and the window colour changed from green to dark grey. It gets to 100% updating but Steam.exe keeps running. Now when I run the command provided in this appdb entry or if I just click on the Steam icon in the KDE wine menu entry. Steam runs, and uses nearly 100% processor, but nothing comes up, IE a GUI. So I tried running the command used by the KDE menu entry item at command line and I get the same thing as if I use the command:

These both produce this outputs as well as a process called steam(appdb recommended command) or Steam.exe(menu item):
appdb recommended command
CellID: Fetching server list from CSDS. . .
CellID: CSDS returned 165 servers.
CellID: Connecting to 119.167.242.114:27031. . .
CellID: Connect to 119.167.242.114:27031 took 336 MS
CellID: Nothing beat our old best time of 33 MS

I'm tempted to wait for a day or so just to make sure it's not doing something that takes a long time in the background.

I am running Wine 1.1.44
I have a GeForce 6200 using the latest nVidia driver, as of a week ago or so: 195.36.24

I had wine running steam and counterstrike source 5 years ago under the same distro, Slackware, although my version back then was 9.0 or 10.0. I am curious as to what I should do to get this to work properly. As you can tell there aren't any errors that I can Google or search for so I'm asking questions and hope someone knows the answer. I can provide you with any information you need.

I tried installing it manually by running the wine msiexec /a SteamInstall.msi. I tried using winetricks but everything ends in the exact same behaviour except the slight difference mentioned above.

RE: Steam installs and seems to run until first update by Edward on Friday May 14th 2010, 18:06

Two suggestions.

In winecfg add the application Steam.exe and set it to use Windows version 7. If that doesn't work go to the graphics tab and enable a virtual desktop. In the event this still doesn't work undo both changes and delete ClientRegistry.blob from the C:\Program Files\Steam\ directory and try again.

Please update this thread with which solution works, assuming one does.

RE: Steam installs and seems to run until first update by Markus on Sunday May 30th 2010, 10:06

Hi

I have the same problem described above (Fedora 13 - x64 + wine 1.2-rc2).
None of your solutions seem to work. If I delete ClientRegistry it updates just fine to crash again with the message above.
It also seems to take a whole core of the processor, memory stays the same over time.

Thanks to an awesome poster at the steam forums, "Hit in the Head", there's a workaround for the steam icon being completely missing.

[Shortened and paraphrased]

Open $HOME/.wine/drive_c/Program Files/Steam/Public, right-click steam_tray.ico and open it with Gimp. Simply File->Save As, and overwrite the original, with default settings. You can remove the layers you don't like to change the icon to one of the others available. Note the background of the icon is still non-transparent when I tried, but I believe that's a wine bug, and it's better than no icon for sure.

So now minus the background quirk, after the workarounds mentioned in my previous posts here, the only issue I've noticed is the windows sometimes don't close. This can be worked around by minimizing them first, then right clicking their systrem tray entry and clicking close there. Obnoxious, but not a showstopper.

Apologies for the numerous posts (I REALLY wish this site had edit and remove functionality), but I've come across something interesting. You do NOT need to install gimp apparently to make the icon reappear. You can simply rename steam_tray.ico to steam_tray.ico.orig or perhaps delete it. It appears to ignore the icon layer you choose entirely if you re-save the file, and loads steam_tray.tga instead as it can't deal with the change for some reason. The icon working after file->save-as was misleading. If anyone knows how to work with image file formats, you might try fiddling with that tga to see if its possible to get the proper transparency working. I don't have any other programs with systray icons to find out if it's universally broken with wine..

I noticed this Valve seem to be using url shortcuts for some stange reason instead of standard desktop shortcuts so you end up with something like wine "winebrowser" steam: //rungameid/220 which attempts to start the game using winebrowser which fails. This is a stupid thing to do in my opinion.

On another note, this text input box doesn't support code tags yet automatically turns anything it thinks is an url into one, which is just as stupid.

No, it's not just you. I'm having the exact same problem (Wine 1.1.43).
Steam starts up and it's able to run (enough to update itself which it did successfully for me once, or to allow me to enter my username and password), but once it logs in to my account something goes wrong and the Xserver crashes.

Basically some one with this bug has to firstly create a bug stating that it exists and secondly run a regression test between 1.1.43 and 1.1.41 to see which patch started the problem. Until this happens it simply cannot be fixed.

Any one with a bugzilla account can open the bug.

And any one with an hour or so can also do the much needed regression test. To do this first make sure the crash still happens with Wine 1.1.43, then make sure it doesn't happen with 1.1.41, and finally run a Regression Test to find the offending patch within those two versions.

I'm using steam on two computers, on one it seems to run very well, on the second when I try to open steam, X crashes!
the two computers are similar in software, all have 195 graphic dirvers, wine 1.1.43 and ubuntu 9.04.