Linux Desktop locks or logs out with user password requirement no starting KSP!

[Arugela]

I've been trying to get this game working for a few days and each time I reinstall or try to fix something it literally gets worse and worse problems. I'm from the in game freezes to of various sorts, to game freezing my whole computer and requiring reboots manually from the front computer button, to now every time the game is launched it puts me to the login screen or basically it's locked down or is logging me out of my desktop when I start the game. How is it possible this game starting literally is seemingly controlling functions of my OS....?

Player.log <- From a fresh reisntall and crash... Behavior did not change.

Specs:

Fedora 24 x64

Phenom II 1100t

560ti 1gb (GF114) 367.44 drivers

GA-970A-D3 motherboard Rev1.0?

8gb (2x4Gib) 1600mhz(technically 1860 or 2000mhz but set lower)

 

Edit: Deleted Prefs again and restarted the game from the folder instead of steam this time.... Seems to have started up properly finally. Now I have to see if it keeps freezing withing a few minutes of starting a game or after going into the VAB/SPH. the ships in the open/load ship window do not fit and overflow the window they are in in the VAB/SPH. After a few moments the sound stutters and the game and comupter completely freeze up. I can't get past this atm.

https://www.dropbox.com/s/xfad70a5cy23ed9/NewPlayer9_23_1.log?dl=0

 

 

Edited September 23, 2016 by Arugela

[steve_v]

38 minutes ago, Arugela said:

logging me out of my desktop when I start the game.

Probably crashing your window manager, known (and unfixed) bug. What window manager / desktop are you running?

38 minutes ago, Arugela said:

the ships in the open/load ship window do not fit and overflow the window they are in in the VAB/SPH.

Tried '-force-gfx-direct' and/or '-force-glcore'? More (maybe) in the linux thread.

38 minutes ago, Arugela said:

After a few moments the sound stutters and the game and comupter completely freeze up. I can't get past this atm.

Dunno about this one though. I haven't encountered any freezing, but I've got plenty of CTDs. IME 1.1 is a bit of a shambles on GNU/Linux.
In this 'freeze up', can you still magic SysRq / drop to console / ssh into the machine? If you leave it a while, does it OOM kill X eventually?

 

Edited September 23, 2016 by steve_v

[Arugela]

I'm using KDE Plasma atm. whatever the latest one is for Fedora 24. Not sure where it lists which version. If it matters the install of fedora 24 is default with Gnome. But I installed KDE on top of it.

 

I'll have to try the force-gfx-direct things(Would this work in the steam launch options?). I was trying before but couldn't figure it out. I can't get a shortcut to be made on my OS.... I was wondering about the Pulseaudio thing too. Still trying to try these out.

 

It freezes the entire computer. I can't move mouse or use keyboard. The only thing I can do is hit the little button the front of the computer and hard reboot the computer.

Edited September 23, 2016 by Arugela

[steve_v]

16 minutes ago, Arugela said:

I'm using KDE Plasma atm. whatever the latest one is for Fedora 24. Not sure where it lists which version.

Ask your package manager? Alternatively, 'Help' -> 'About KDE' in any KDE app (or at least it is in KDE4).

17 minutes ago, Arugela said:

Would this work in the steam window thing?

Dunno, don't (won't) use Steam. Add to steam launch options or launch KSP from a terminal.

17 minutes ago, Arugela said:

I can't get a shortcut to be made on my OS

Seriously, just launch KSP from a terminal / script. Once you have launch options that work, think about making it into a shortcut for whatever (by 'plasma' I assume you mean KDE5?) desktop you use.

17 minutes ago, Arugela said:

I was wondering about the Pulseaudio thing too.

If it's the pulseaudio bug, KSP will crash at the loading screen. Simplest fix is to symlink /dev/null to libpulse-simple.so.0 in the KSP root directory.

17 minutes ago, Arugela said:

I can't move mouse or use keyboard as far as I can tell.

Err, didn't really answer the question, but ok. So no magic SysRq then? (Asking because rapid memory leaks can seem like a freeze untill the OOM killer does its thing). If the system isn't completely frozen, a SAK should get you a console (assuming your distro has it enabled, OFC).

If it is a hard freeze, perhaps examine system logs and / or do some (non-ksp) stability testing? It may be hardware, or possibly even GPU driver issues (no problem here though, with nvidia 352.79).

Edited September 23, 2016 by steve_v
More answer.

[Arugela]

Sorry but I have no idea how to do that. So, I can't.

I already have a shortcut for it on my desktop but all instructions are for windows and target. I don't know which thing is the equivalent or appropriate place to stick it to know if it's working or not. Can't find anything that explains it either on google.

No idea how to do the rest. Or will have to read up on it and try it.

And you might want to spell it out since I have no idea what on that page you gave would be appropriate to this or any situation. You like the rest of the linux community need to learn to write and use appropriate information instead of insulting and bashing everyone in the head who is not familiar with the information, which is not formatted for anyone who is not familiar(Which I cannot control under the current circumstances), and is impossible to learn from.

I don't have a clue how to do any of that. And that info does not give any idea without prior other knowledge to do so. neither do any of the linux documents on any of the major linux sights. They are all written for people with specific already existing knowledge and do not help anyone trying to learn or become familiar to use them. It's the single biggest problem with linux. Besides the reason that problem exists.

You have to understand what is needed for someone to learn the things for those documents to be useful. As this is a problem with every single last linux document on the Internet. Nobody can learn any of it to get further!

sorry if this makes yo angry but I'm so tired of everyone linking documents like this and expecting them to be useful. Nothing in those show what is needed or any information to do that. I've been using linxu for a while but because of this garbage  haven't been able to learn because the information is so spread out and hard to put together if you don't already know it. there is a reason learning to write from a technical standpoint used to be considered so important. And this is it. Audience!!!! too many children or greedy people in the linux community(probably this problem started as so many were charging so much money in the 90's for teaching linux and the info probably become hidden for them to make money! As tends to happen in that sort of situation.)

Edited September 23, 2016 by Arugela

[steve_v]

10 minutes ago, Arugela said:

I don't know which thing is the equivalent or appropriate place to stick it to know if it's working or not.

Launch KSP from a terminal: Open terminal emulator (konsole in KDE4), cd to KSP root directory (probably '~/.local/share/Steam/SteamApps/common/Kerbal Space Program' if installed via Steam), launch KSP with ./KSP.x86_64 <insert launch options, e.g. -force-gfx-direct here>.
N.B. Save pain and use tab to auto-complete directory / file names.

14 minutes ago, Arugela said:

You like the rest of the linux community need to learn to write and use appropriate information instead of insulting and bashing everyone in the head who is not familiar with the information

Suit yourself then. I was going to attempt to explain in laymans terms, but having read this edit I don't think I'll bother. ¯\_(ツ)_/¯

Edited September 23, 2016 by steve_v

[Arugela]

No sweat off my back.

Quote

Seriously, just launch KSP from a terminal / script. Once you have launch options that work, think about making it into a shortcut for whatever (by 'plasma' I assume you mean KDE5?) desktop you use.

Not my fault if you want to come to a help forum and act like a complete condescending prick! maybe consider how you talk to people next time! Get rid of your damn attitude! Nobody should condone you masking a bad attitude like this and acting like you're trying to help someone!

I have enough stress to put up with these constant errors. I'm not putting up with your attitude also!

Edited September 23, 2016 by Arugela

[steve_v]

Riiight. I said "Seriously, just launch KSP from a terminal / script." because it's easier / faster to test launch options this way, and since I don't know what desktop/version you are running, I can't tell you how to make a shortcut.
If you want to go off the deep end over it, knock yourself out.

20 minutes ago, Arugela said:

People aren't here for you to abuse!

Abuse? what "abuse". You are the one yelling and swearing here. If you want to have a rant, this is not the place.

43 minutes ago, Arugela said:

sorry if this makes yo angry

Apparently, I'm not the angry one here.

43 minutes ago, Arugela said:

I'm so tired of everyone linking documents like this

Dude, I linked Wikipedia.

I gave you concise information. If you don't know what to do with it, ask and I will attempt to explain.
If you just want me to ignore you, by all means, call me names.

Edited September 23, 2016 by steve_v
Quote the quoting thing.

[Arugela]

Get out of my thread! Go help someone else where you are wanted. Or drop the attitude. And yes it is way more than enough. That was only a paraphrase of the attitude you are masking. And nobody frustrated enough is going to put up with your attitude because you have the room to be so flipped. Get lost!

Edited September 23, 2016 by Arugela

[steve_v]

46 minutes ago, Arugela said:

probably this problem started as so many were charging so much money in the 90's for teaching linux and the info probably become hidden for them to make money!

Also, ROFL. Disorganised, possibly. Hidden, no.

[Green Baron]

Arugela,

no need to get angry, steve_v tried to help. The information you provided us is not sufficient to track down the problem.

If you start KSP from a terminal you might see an error message, that is why steve_v asked you to do that. Also there are a few standard problems that could be ruled out by starting the program from a terminal with launch options. If you don't know how to do that just ask, there are a lot of people here who can help with the handling of your os.

Maybe we can say more if there is some sort error message displayed. What i see from the log: pls try again with AA and Edge-Highlighting switched off.

 

Edited September 23, 2016 by Green Baron