protonscr

Game stuck in "Update Required" status

steamclosed reviewed3rd party gameSteam database
ValveSoftware/steam-for-linux#2869 · opened 2013-09-23 by apocalyptech · updated 2017-09-07 · 5 comments · github
Aapocalyptech 2013-09-23 github

One of my Linux games, X3: Reunion has been stuck in an "Update Required" status and I've been unable to get it out. I've tried verifying the local game cache, which reports that it's fine. If I try to play the game, I get a "Preparing to launch X3: Reunion" dialog whose progress bar never changes. In the "Downloads" view, it usually starts off in a "Suspended" state - I can hit "pause" and then "resume" which just brings it back into Suspended. The "Resume All" button doesn't seem to do anything. On that screen it says "Updated: 0 bytes / 0 bytes, Time Initiated: 21:20, Time Remaining:" (with no value after Time Remaining) - the "Time Initiated" value might change from run to run, I'm not sure about that.

I've also tried setting it to not auto-update, but that doesn't seem to change it either. This has persisted throughout many restarts of the Steam client over the course of the past week or two. I CAN play the game if I move Steam into offline mode first, at least, so that's nice. It'd be nice to figure out how to get it to start behaving on its own though.

I assume that I could probably fix it by completely deleting the game and then redownloading it, but I'd rather just figure out a way to fix it that's less destructive. There doesn't seem to be any useful output on the console. If there's more information I could provide, please let me know.

Processor Information:
    Vendor:  GenuineIntel
    CPU Family:  0x6
    CPU Model:  0x17
    CPU Stepping:  0xa
    CPU Type:  0x0
    Speed:  2936 Mhz
    2 logical processors
    2 physical processors
    HyperThreading:  Unsupported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Unsupported

Network Information:
    Network Speed:  

Operating System Version:
    "Fedora release 19 (Schrödinger’s Cat)" (64 bit)
    Kernel Name:  Linux
    Kernel Version:  3.10.11-200.fc19.x86_64
    X Server Vendor:  Fedora Project
    X Server Release:  11402000
    X Window Manager:  IceWM 1.3.7 (Linux 2.6.32-358.2.1.el6.x86_64/x86_64)
    Steam Runtime Version:  steam-runtime-release_2013-09-05

Video Card:
    Driver:  NVIDIA Corporation GeForce GTX 650 Ti/PCIe/SSE2

    Driver Version:  4.3.0 NVIDIA 319.32
    OpenGL Version: 4.3
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 60 Hz
    VendorID:  0x10de
    DeviceID:  0x11c6
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1920 x 1080
    Desktop Resolution: 1920 x 1080
    Primary Display Size: 20.51" x 11.54"  (23.50" diag)
                                            52.1cm x 29.3cm  (59.7cm diag)
    Primary Bus: PCI Express 16x
    Primary VRAM: 1024 MB
    Supported MSAA Modes:  2x 4x 8x 16x 

Sound card:
    Audio device: TriTech TR28602

Memory:
    RAM:  5970 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF-8
    Microphone:  Not set
    Total Hard Disk Space Available:  238752 Mb
    Largest Free Hard Disk Block:  40951 Mb

Installed software:

Recent Failure Reports:
Aapocalyptech 2013-09-23 github

Interestingly, I got tired of having this visual annoyance in my games list, and when I deleted local content and tried to reinstall, I encountered a similar issue, which happens to have been just recently added to this issue tracker: https://github.com/ValveSoftware/steam-for-linux/issues/2871

What he describes there fits my symptoms perfectly, now - I'm guessing that it's probably the same root cause that was getting in the way of my update issues as well.

Aapocalyptech 2013-09-24 github

I've mentioned something very similar over in the other bug I mentioned above, but when I look back at my old content_log.previous.txt, I can see the following when it had been trying to update X3: Reunion:

[2013-09-23 10:34:50] Scheduler update appID 2810: Priority Last, legacy=no, restore=""
[2013-09-23 10:34:50] AppID 2810 state changed : 0x00000106 = Update Required,Fully Installed,Update Running,
[2013-09-23 10:34:50] AppID 2810 state changed : 0x00010106 = Update Required,Fully Installed,Update Running,Reconfiguring,
[2013-09-23 10:34:50] Got 20 download sources via "/serverlist/95/20/" from 209.197.20.102:80
[2013-09-23 10:34:50] HTTP (CS,86) - valve100.cs.steampowered.com (valve100.cs.steampowered.com): OpenConnection - Success!
[2013-09-23 10:34:50] HTTP (CS,114) - valve181.cs.steampowered.com (valve181.cs.steampowered.com): OpenConnection - Success!
[2013-09-23 10:34:50] HTTP (CS,28) - valve199.cs.steampowered.com (valve199.cs.steampowered.com): OpenConnection - Success!
[2013-09-23 10:34:50] HTTP (CS,129) - valve42.cs.steampowered.com (valve42.cs.steampowered.com): OpenConnection - Success!
[2013-09-23 10:34:50] HTTP (CS,130) - valve43.cs.steampowered.com (valve43.cs.steampowered.com): OpenConnection - Success!
[2013-09-23 10:34:50] HTTP (CS,128) - valve11.cs.steampowered.com (valve11.cs.steampowered.com): OpenConnection - Success!
[2013-09-23 10:34:50] HTTP (CS,128) - valve11.cs.steampowered.com (valve11.cs.steampowered.com): AuthenticateDepotID (229330) - ERROR: HTTP response 403 (Forbidden)
[2013-09-23 10:34:50] HTTP (CS,86) - valve100.cs.steampowered.com (valve100.cs.steampowered.com): AuthenticateDepotID (229330) - ERROR: HTTP response 403 (Forbidden)
[2013-09-23 10:34:50] HTTP (CS,28) - valve199.cs.steampowered.com (valve199.cs.steampowered.com): AuthenticateDepotID (229330) - ERROR: HTTP response 403 (Forbidden)
[2013-09-23 10:34:51] HTTP (CS,130) - valve43.cs.steampowered.com (valve43.cs.steampowered.com): AuthenticateDepotID (229330) - ERROR: HTTP response 403 (Forbidden)
[2013-09-23 10:34:51] HTTP (CS,114) - valve181.cs.steampowered.com (valve181.cs.steampowered.com): AuthenticateDepotID (229330) - ERROR: HTTP response 403 (Forbidden)
[2013-09-23 10:34:51] HTTP (CS,129) - valve42.cs.steampowered.com (valve42.cs.steampowered.com): AuthenticateDepotID (229330) - ERROR: HTTP response 403 (Forbidden)
[2013-09-23 10:36:50] Update job for app 2810 canceled: missing manifest 6909182178174349347 (Connection timeout)
[2013-09-23 10:36:50] AppID 2810 state changed : 0x00810106 = Update Required,Fully Installed,Update Running,Reconfiguring,Update Stopping,
[2013-09-23 10:36:50] AppID 2810 state changed : 0x00800106 = Update Required,Fully Installed,Update Running,Update Stopping,
[2013-09-23 10:36:50] AppID 2810 state changed : 0x00000006 = Update Required,Fully Installed, (Connection timeout)
[2013-09-23 10:36:50] Scheduler finished appID 2810: removed from schedule
[2013-09-23 10:36:50] HTTP (CS,86) - valve100.cs.steampowered.com (valve100.cs.steampowered.com): Closing connection
[2013-09-23 10:36:50] HTTP (CS,128) - valve11.cs.steampowered.com (valve11.cs.steampowered.com): Closing connection
[2013-09-23 10:36:50] HTTP (CS,114) - valve181.cs.steampowered.com (valve181.cs.steampowered.com): Closing connection
[2013-09-23 10:36:50] HTTP (CS,28) - valve199.cs.steampowered.com (valve199.cs.steampowered.com): Closing connection
[2013-09-23 10:36:50] HTTP (CS,130) - valve43.cs.steampowered.com (valve43.cs.steampowered.com): Closing connection
[2013-09-23 10:36:50] HTTP (CS,129) - valve42.cs.steampowered.com (valve42.cs.steampowered.com): Closing connection

So yes, it looks like the two bugs are essentially exactly the same problem: Steam is seeing 403 Forbidden errors from the Steam servers when it tries to grab the new manifests.

Jjohndrinkwater 2013-09-25 github

#2871 is caused by the same issue as this.

Aapocalyptech 2013-09-27 github

This was mentioned over in the other issue, but for the record here as well: it looks like at least the India servers can serve up the repo without trouble. I had tried various download locations previously but hadn't left North America, but setting it over to India did the trick for me. Nothing like putting a burden on undersea trunks, yeah?

Kkisak-valve maintainer 2017-09-07 github

Closing as this appears to have been resolved. If anyone is still encountering this issue, please open a new issue report.

Upstream links