![](https://seccdn.libravatar.org/avatar/a4970b459710a99c60b82ba651c2aaaa.jpg?s=120&d=mm&r=g)
Sound about right, the first run is just odd like that and differently depending on graphics driver primarily and Steam version. A side note, the fact that Steam updates independent of bootstrap tarball found in package means the openQA test does not know if TW changes broke Steam or Steam broke Steam. Not much that could be done there short of keeping snapshots of steam and not allowing it to update until done independent of TW updates. Basically, a workaround for this is to catch the different error output like the one you got and handle it. In some cases just need to re-launch Steam, in others nuke a few files and then relaunch. Not sure if nastier ones are resolved as there were some that took 3-4 stages. The general Steam runtime fixes are present which resolve that class of issue, but still require a relaunch which could also be automated. -- Jimmy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org