Steam for Linux > Limited Beta > Topic Details
FlyLow Dec 17, 2012 @ 10:00pm
Issue Report: Steam fails to launch
Steam fails to launch when launched from command line. Running Ubuntu 12.10 under fvwm, using fglrx drivers. Error message was:

Major opcode of failed request: 155 (ATIFGLEXTENSION)
Minor opcode of failed request: 66
Serial number of failed request: 13
xerror_handler: X failed, continuing
SteamUpdateUI: An X Error occurred
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 45
xerror_handler: X failed, continuing
SteamUpdateUI: An X Error occurred
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 74
xerror_handler: X failed, continuing
SteamUpdateUI: An X Error occurred
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 14 (X_GLXGetVisualConfigs)
Serial number of failed request: 103
xerror_handler: X failed, continuing
Installing breakpad exception handler for appid(steam)/version(1355789024_client)
unlinked 0 orphaned pipes
Installing breakpad exception handler for appid(steam)/version(1355789024_client)
Gtk-Message: Failed to load module "overlay-scrollbar"
[1217/215335:WARNING:proxy_service.cc(646)] PAC support disabled because there is no system implementation
The program 'steam' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 34 error_code 1 request_code 155 minor_code 66)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
CAsyncIOManager: 0 threads terminating. 0 reads, 0 writes, 0 deferrals.
CAsyncIOManager: 120 single object sleeps, 3 multi object sleeps
CAsyncIOManager: 0 single object alertable sleeps, 1 multi object alertable sleeps
peek of pipe from 0/0 failed: 11