Steam no longer starts
I seem to have the same issue on Arch Linux, with Steam beta, though it seems to work for my wife on the same network and same OS, but different DE.
I seem to have the same issue on Arch Linux with Steam Beta too, It works fine on my Deck and on my laptop.
I tired to reset Steam, tried native and runtime, but that didn't seem to help, I just have to enter my account details every time I try now :P
I have different terminal output tho here is a small snippet, It just keeps going with these messages but the client never shows
Xlib: sequence lost (0x10000 > 0x45f) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x461) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x463) in reply type 0xc!
....
And only when I close steam from the tray I get this at the end of the terminal output
(steam:30898): GLib-GObject-CRITICAL **: 13:50:12.329: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(steam:30898): GLib-GObject-WARNING **: 13:50:12.330: instance with invalid (NULL) class pointer
(steam:30898): GLib-GObject-CRITICAL **: 13:50:12.330: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(steam:30898): GLib-GObject-CRITICAL **: 13:50:12.330: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[2023-01-19 13:50:12] Shutdown
I am not sure if it is related to the Original Issue, but in all these years I never had Steam refusing to start, and the timing matches, So I guess it is likely.
Xlib: sequence lost (0x10000 > 0x45f) in reply type 0xc! Xlib: sequence lost (0x10000 > 0x461) in reply type 0xc! Xlib: sequence lost (0x10000 > 0x463) in reply type 0xc!
I also get these errors, not sure if they are related? Hex number goes up every time. I move mouse over the window.
P.S. Steam still doesn't start today, seems to be the same issue, I didn't try removing my profile to log back again yet and logging from Deck as well, but I also never had problems logging to Steam daily.
I tried removing all .local/share/Steam folder and relogging, but it seems it's stuck, just on a different screen now.
Well, it seems to have fixed itself now, both with the new and old profile; any clue what could be the issue?
Ahahaha! You've got to be kidding me! I just wrote out and formalized all my observations up to the dpkg log in the period between the last successful launch of steam and yesterday, when your message popped up and my steam also started (even though it wasn't working an hour ago)! Looks like the issue was on the side of the Steam servers, as I thought.
So I guess the issue can be closed now. However, due to the clearly mysterious nature of the issue, I don't exclude a re-opening in the future.
p.s. Just in case, I indicate the lines that were missing in the terminal output during unsuccessful launches:
These lines appeared between
migrating temporary roaming config store and Background update loop checking for update. . . ones from the terminal output in the original post.
Changed terminal output segment
Installing breakpad exception handler for appid(steam)/version(1671236931)
Installing breakpad exception handler for appid(steam)/version(1671236931)
Installing breakpad exception handler for appid(steam)/version(1671236931)
Installing breakpad exception handler for appid(steam)/version(1671236931)
BRefreshApplicationsInLibrary 1: 37ms
Installing breakpad exception handler for appid(steam)/version(1671236931)
Failed to init SteamVR because it isn't installed
ExecCommandLine: "'/home/max/.steam/debian-installation/ubuntu12_32/steam' '-nominidumps' '-nobreakpad'"
System startup time: 31.98 seconds
BuildCompleteAppOverviewChange: 31795 apps
RegisterForAppOverview 1: 346ms
RegisterForAppOverview 2: 365ms
Installing breakpad exception handler for appid(steam)/version(1671236931)
Installing breakpad exception handler for appid(steam)/version(1671236931)
Yes also fixed here, Still curious what was the issue tho, I see all of us have 1000+ games, maybe that has something to do with it?
If so, then this once again indicates that the root of the problem is on the side of Steam. However, I find it strange that this issue has affected a very small group of users.
I have no doubt it was not on the side of steam, it was fixed for all 3 of us when doing nothing after trying everything. It is strange only a few people were affected, It is probably some niche hard/software configuration, the big library, or something else, or maybe a combination. I am also pretty sure not everyone knew where or felt like reported it here, and many many more didn't even launch Steam during this time. I doubt we will get an answer tho, so it is all speculation and that is all that it will ever be.
Nothing extracted yet.
System information
OS: Debian GNU/Linux 11 (bullseye) x86_64
Kernel: 5.10.0-20-amd64
WM: i3
CPU: Intel i5-4670 (4) @ 3.800GHz
GPU: NVIDIA GeForce GTX 770
Description of the issue:
Freshly installed system (a bit over a week old), steam has been launching successfully every day for the past week (last session was around Sunday), but today it doesn't progress beyond the inscription "Connecting Steam account:..". All required libraries (both 64 and 32) are installed, there were no any updates or installs since the last session.
Terminal output
Gtk-WARNINGs were present before, so I think they have nothing to do with it.
Steps for reproducing this issue: