[Panorama] crash on startup when using gamepads

[TypicalFence]

Your system information

• System information from steam: gist
• Have you checked for system updates?: No

Please describe your issue in as much detail as possible:

When I try to start the game via steam or the command line, the game creates a window, which just stays black and the game will crash after a bit.

When starting it via the cli I get this output.

When starting the game with the launch option "-scaleform", it starts up normal, how it should and I can play the game without any Issues. The OpenGL extension lines are the same in the command line output when running it this way. Please don't remove the scaleform ui for the moment.

Steps for reproducing this issue:

1. Start the game via steam or csgo.sh without any launch options

[Keplyx]

Same happened for me, with system up to date (kde neon 5.13.4), using nvidia card (gist) I found a way to start the game with panorama, but this is not practical: delete the folder .steam/steam/userdata/USERID/730

The bug seems related to the config.cfg files contained in the remote and local folders (at least in my case). If either one of those files is present (even if empty), the game will crash. Sadly, I must to this each time I start the game.

Launching the game with -scaleform option never crashes.

The strangest is that I can start the game perfectly on an other account, using the same game, on the same computer. Using the config files of the working account on the other did not fix the issue.

Here is the output when starting steam and csgo from the command line. I have the exact same output when starting the working account with the command line, except it prints the line ' ****loading serverbrowser_client.so' when the game actually starts.

The working account can start the game with or without launch options, but it crashes anyways on the other

[TypicalFence]

@Keplyx sadly deleting .steam/steam/userdata/USERID/730 doesn't seem to fix the problem for me

[pschichtel]

Crashed occasionally once on startup, retrying worked through.

Stacktrace: https://gist.github.com/pschichtel/7b7afab94e72bf1a4e0a123f7570cc20

[lionblaze55]

I have the same issue. For me I can work around this issue by putting -nojoy in the launch options.

[michaldaniel]

@AlexFence try disabling the cloud configuration backup first in steam game properties. That worked for me, but the issue returned after the first restart. The @lionblaze55 solution to my surprise works.

[TypicalFence]

@lionblaze55 yes panorama boots up with -nojoy

[ChemBro]

Can confirm -nojoy fixes it.

[fjavimartin]

Confirmed, -nojoy launch option works!!!!! But.....why???

https://steamcommunity.com/sharedfiles/filedetails/?l=spanish&id=379782151 -nojoy (Suggested by him) removes joystick support

[CircusMonkey]

I unplugged the PS3 controller. Now works. Anyone using anything other than a ps3 controller with this issue?

[ChemBro]

Only thing I have plugged in is the bluetooth dongle for my Logitech 710 gamepad, but it does not matter if that is plugged or unplugged. CSGO only starts with launch option "-nojoy".

[Keplyx]

If I unplug my mouse, the game starts without the -nojoy option. If I plug-in the mouse, the game crashes without -nojoy, and starts with it.

I have a Roccat Tyon, with some analogue buttons, which are detected as joysticks by the game.

[nightsky30]

Logitech Gamepad F310 also causes CSGO to crash on start if it is plugged in.

[odinu]

Happens to me too using the Steam controller. "-nojoy" works.

[acholt]

After the latest update, CS:GO will not start on OpenSuse. While the Steam client works fine, CS:GO fails unless I use "-nojoy" as a launch option. For some reason it's detecting my keyboard as a joystick.

Found joystick 'Corsair Corsair Gaming K95 RGB PLATINUM Keyboard' (030000001c1b00002d1b000011010000), but no recognized controller configuration for it.

They keyboard still works in game so it sorted my issue out. :-)

[travcunn]

CS:GO crashes on startup for me as well on Ubuntu 18.04

[acholt]

@travcunn - That's odd that you are having that issue on Ubuntu, have you tried adding "-nojoy" as a launch option?

[travcunn]

It would have helped if I read the fix in this thread :)

Thanks, "-nojoy" fixed my issue.

In the startup code for CS:GO, there should be something like this:

if (platform === "linux" && platform !== "steamos") {
  flags += "-nojoy"
}

On Tue, Aug 7, 2018 at 1:44 PM Andrew Holt notifications@github.com wrote:

@travcunn https://github.com/travcunn - That's odd that you are having that issue on Ubuntu, have you tried adding "-nojoy" as a launch option?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/csgo-osx-linux/issues/1757#issuecomment-411141952, or mute the thread https://github.com/notifications/unsubscribe-auth/ADjEPlMs_LQTf4182Y6L2Qh-iXlbeEiDks5uOdHegaJpZM4VuLPh .

--

Travis CunninghamSoftware Engineer

Sigstr Email Signature Marketing www.sigstr.com http://www.sigstr.com/?utm_campaign=Sigstr+Watermark&utm_medium=Email+Signatures&utm_source=Website+URL+in+Sigstr+team+member+signatures [image: Twitter] https://twitter.com/sigstr [image: linkedin.png] https://www.linkedin.com/company/sigstr

[image: Overlooked ad channel ebook] http://signatures.sigstr.com/uc/59e4b0ad825be9286cbb0d35 [image: Powered by Sigstr] http://signatures.sigstr.com/uc/59e4b0ad825be9286cbb0d35/watermark

[Morganamilo]

So what you're saying is all Linux non steam OS users should be blocked from using a controller all together without choice?

[lionblaze55]

Although one would think that controllers are not ideal for CS:GO, I have to agree with @Morganamilo. "joystick" is a pretty general input parameter and removing it could cause more compatibility issues.

[travcunn]

Ah, that was an oversight on my part. I was under the impression "-nojoy" disabled the panoramic UI (The game isn't as "cool" without the panoramic UI, hence no-joy. I didn't realize people played this game with controllers). Perhaps the startup code should include a flag to disable the panoramic UI for Linux users, or perhaps something more like:

if (platform === "linux" && platform !== "steamos") {
  disable_panoramic_ui = true;
}

On Wed, Aug 8, 2018 at 2:47 PM lionblaze55 notifications@github.com wrote:

Although one would think that controllers are not ideal for CS:GO, I have to agree with @Morganamilo https://github.com/Morganamilo. "joystick" is a pretty general input parameter and removing it could cause more compatibility issues.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/csgo-osx-linux/issues/1757#issuecomment-411511954, or mute the thread https://github.com/notifications/unsubscribe-auth/ADjEPovniUnvSeG6kKMQoWjC9pUFu5VMks5uOzJJgaJpZM4VuLPh .

--

Travis CunninghamSoftware Engineer

Sigstr Email Signature Marketing www.sigstr.com http://www.sigstr.com/?utm_campaign=Sigstr+Watermark&utm_medium=Email+Signatures&utm_source=Website+URL+in+Sigstr+team+member+signatures [image: Twitter] https://twitter.com/sigstr [image: linkedin.png] https://www.linkedin.com/company/sigstr

[image: Overlooked ad channel ebook] http://signatures.sigstr.com/uc/59e4b0ad825be9286cbb0d35 [image: Powered by Sigstr] http://signatures.sigstr.com/uc/59e4b0ad825be9286cbb0d35/watermark

[Morganamilo]

Okay so again, you want to stop all the Linux users from using the new UI, without choice, just because it won't start when there's a controller plugged in?

[travcunn]

IMO, it would be nice to fix the root cause that makes the game crash on startup, but a quick fix such as the one I mentioned would at least make the game not crash upon startup. On my machine, it crashes without a controller plugged in, so this solution would fix my computer.

[Keplyx]

If you don't want to use panorama, just use the -scaleform launch option, no need to edit the game code. We just need to wait until they fix the game, joysticks can be very useful in csgo, especially if you want to shoot a trailer, record a cinematic video.

[ChemBro]

You need to fix it, because Valve already wrote, that they will remove the "-scaleform" launch option. Panorama UI will be the only option in the near future.

[nightsky30]

@travcunn If it is crashing without a controller and the -nojoy option fixed the issue for you, then it is likely that another device on your system is detected by steam/csgo as a joystick for some reason. Perhaps your mouse or keyboard just like @acholt stated above with his Corsair keyboard.

It seems they need to fix the detection of certain devices AND the root of the crash with actual controllers, not so much the UI.

[bp0]

Same issue, but if I unplug the controller before starting the game, I can re-connect it once in the game, and it will work.

[osomdev]

I also confirm this issue (crash during startup). I don't have any gamepad connected. The -nojoy option works as workaround in my case.

Adding message printed in dmesg to increase chance that other people will find this bug by searching on google ;)

traps: csgo_linux64[29597] general protection ip:7f7621e03cf3 sp:7ffd04aa7d40 error:0 in libSDL2-2.0.so.0[7f7621db4000+f8000]

[ghost]

I can confirm this issue for me and another Linux user. We both couldn't start up CS:GO. Tried using the launch option -nojoy and it worked.

He was using Ubuntu 16.04 and I was using Arch Linux. We had no gamepads, controllers or any joysticks plugged in. Just our standard peripherals.

I don't mind using this as we don't have any controllers, but it is pretty unfortunate for the users who do intend to use gamepads on not just CS:GO as we can't use Scaleform UI anymore.

[kiroma]

Can anyone affected try out launching without -nojoy but with Steam Runtime updated? You can get the new Steam Runtime by opting into Steam Beta client and restarting the client after checking for new updates.

[ChemBro]

Only works with "-nojoy" for me with the Steam beta client and the new Steam runtime on Arch Linux.

[LuFlo]

"-nojoy" doesn't work for me, but I am opted out from beta. I'm using the build from Oct 13 2018 UPDATE: It neither works in beta. The "-nojoy" option doesn't have any effect

[codl]

the new steam runtime makes no difference for me. -nojoy worked before and still works, no -nojoy didn't work before and still doesnt work

[bp0]

Ubuntu 18.10 (64 bit) 4.18.0-10-generic; Xorg 12001000; Xfwm4 Steam Runtime Version: steam-runtime-beta-release_2018-10-23

For me, the game no longer crashes on startup for CS:GO when a controller is connected. The controller support is still broken, however. Once inside the game, it is impossible to select anything but the "News" panel, for example "Settings", even using the mouse. If a controller is not connected, then things work as expected. As before, once the game is started, I can plug in and use the controller.

[macmota]

Having the exact same problem, but -nojoy doesnt work for me. Ubuntu 18.04.

[hifi]

Why is this still an issue? I was really puzzled why my game was suddenly crashing on startup and after finding this thread I disconnected the PS3 gamepad that was charging from my USB port.

[TypicalFence]

@hifi thanks for reminding me

[N00byKing]

This also happens with a Wooting One (Analog Keyboard)

[TypicalFence]

how is this still a problem >_< valve please fix

please everyone just give my original post a thumbs up instead of replying (see the readme of this repo)

[pipebomb]

I've had the same issue. Even though I was able to start CSGO normally with my x360 pad plugged in yesterday, today it started crashing on startup.

I've tried the following:

• verifying game cache
• reinstalling the client
• moving client to other Steam Library on another physical drive

Turns out all I had to do was to unplug my x360 controller. Lol!

[juicefreak]

I have this issue too on Xubuntu 18.04.1. I usually have PS3 or PS4 compatible controllers connected to my computer. -nojoy parm or disconnecting all PS3/PS4 controllers seems to successfully work around the problem.

[74331.305042] csgo_linux64[24815]: segfault at 1 ip 00007f266a360e73 sp 00007ffd61a18b90 error 4 in libSDL2-2.0.so.0[7f266a311000+f8000]

[woohooyeah]

Adding "-nojoy" fixes launching the game here. ArchLinux testing, Steam beta, Logitech Chillstream USB.

[thatvirtualboy]

I still get the error with the close or wait upon launch in Ubuntu 18.04.1. Strange since the game ran without any issues in Linux Mint 19. It also won't go full screen for some reason.

[zqcc]

I am using switch pro controller.The -nojoy option really works for me on archlinux.also it fixed some other bugs.But motion control can't use anymore.

Some methods like copy libpng works fine.

It seems that some key is repeatedly pressed because before I try this I can't select CT or t ,I can't choose map,instead I hear the key press sound repeatedly.

[ars-magna]

Starting to think my issue maybe is related to this, but haven't found a workaround that works for me Can't even play the game, -nojoy does not make it launchable, gamepads have no impact on the logs It's interesting tho that my keyboard is seen as a gamepad :thinking: (but unplugging it doesn't make the game launch)

Also tried linking libpng as suggested in #1801 but no dice

These are in my dmesg when I try to launch, logs are about the same as posted above

[1419057.924652] csgo_linux64[28349]: segfault at 58 ip 00007fd72575b58b sp 00007ffcf72c7890 error 4 in libSDL2-2.0.so.0[7fd7256a4000+f8000]

[ 268.042980] csgo_linux64[6303]: segfault at 0 ip 00007f1c8e85578d sp 00007ffeb39483d0 error 6 in engine_client.so[7f1c8e336000+b34000]

[dribbleondo]

Can confirm that -nojoy is required in launch options to load the game.

[nightsky30]

@Keplyx Can you supply the USB Device ID for your Roccat Tyon mouse? Should be something like:

1e7d:xxxx

[sy-be]

I have Thrustmaster T.16000M plugged in and have the same issue. -nojoy helps to start CSGO. Fedora 30.

[Shugyousha]

If I have a Mad Catz TE2 plugged in when starting the game, I get a SIGSEGV. If I unplug the fight stick and then start the game, everything works without an issue.

I remember there being an issue with one of the Unity version that also crashes on startup when my fight stick is plugged in. Apparently it's due to the space in my fight stick's name and it still hasn't been fixed...

[soulseekah]

confirmed, nojoy worked

[Keplyx]

Crash still happening with my Roccat Tyon mouse, as well as my steam controller. Here are the USB Device IDs @nightsky30

Bus 001 Device 006: ID 1e7d:2e4a ROCCAT 
Bus 001 Device 007: ID 28de:1142  (the steam controller)

The -nojoy option still works though.