Running steam as root is not supported (and a very bad idea), and a valve dev would need a CrashID to look into your issue, this might be found when running steam from a terminal or going to Help -> System Information.

Don't make me laugh )
Running steam as root...
It supported, just comment some lines in /usr/bin/steam xD
I don't wanna create special user just for steam, and I know what I'm doin' )

It supported, just comment some lines in /usr/bin/steam xD

https://github.com/ValveSoftware/steam-for-linux/issues/2317#issuecomment-16477020

Even if it is supported, you should not run any application as root if it doesn't need to be (in this case, anything Steam related).

Also, I might be missing something but you shouldn't need to create another user for Steam. You should be able to use whatever user you're logging into your DE with or what you're starting Xorg with

Such lines:
if [ "$(id -u)" == "0" ]; then
show_message --error $"Cannot run as root user"
exit 1
fi

And what the hell? I'm running as root, my user is root. I don't have sudoers users, all I have is ROOT. I'm starting X as root, and DE as root, using xinit (startx). There is only one user in my system, and it's root.

I compiled almost all of the packages in my system by my own, even kernel (custom 3.11)

Unless Valve have changed their minds since, that is not supported. That is
a HUGE security risk since everything you execute is now running with super
user privileges.

On 18 November 2013 03:46, Pon3 [email protected] wrote:

Such lines:
if [ "$(id -u)" == "0" ]; then
show_message --error $"Cannot run as root user"
exit 1
fi

And what the hell? I'm running as root, my user is root. I don't have
sudoers users, all I have is ROOT. I'm starting X as root, and DE as root,
using xinit (startx). There is only one user in my system, and it's root.

—
Reply to this email directly or view it on GitHubhttps://github.com/ValveSoftware/steam-for-linux/issues/2994#issuecomment-28673764
.

Daniel Evans
Web: http://bytecove.co.uk
Games: http://razor-studios.co.uk
OAOSIDL:
http://officialaberystwythopensourceinternationaldevelopersleague.org

@danharibo
"Security risk" of my system, not Valve's. I'm using 2 hardware firewalls, raid 10, backups and everything I need to protect my system.

The user poses the greatest threat to the system. I can realize what I'm doing. I'm not a user, I'm an admin

Given that some software doesn't even run (not to mention the software that runs incorrectly unintentionally) under root, you're clearly not doing "everything [you] need to protect [your] system".

It's explicitly placed in the script to not allow root execution for a reason, not just because you don't "know what [you're] doing". I don't think you know what you're doing if you believe running all software as root as being viable.

"Security risk" of my system, not Valve's. I'm using 2 hardware firewalls, raid 10, backups and everything I need to protect my system.

I don't think that your firewalls are going to prevent you from getting exposed to a threat inadvertently delivered via Steam (which is why the client launch script prevents it from being run as root). Not all malicious software needs a connection to the outside world.

I think focusing on running as root is probably only going to bog this issue down (and there are other issues discussing that such as the one that @danharibo linked to).

Were you able to get a CrashID as @Tele42 suggested?

@computerquip
For example?
Okay, for example google-chrome package.
Run [code] hexedit hexedit /opt/google/chrome/chrome [/code]
Search for "geteuid" and change it to "getppid".
Now run your Chrome browser. Voila! Working. Same with any application which won't run as root

What does that achieve other than cause security risks?
EDIT: Also, I doubt that actually works in some cases.

@computerquip
I don't need to write "sudo" every time.

You don't run chrome as root EVER. You don't need root.

Chrome is only my browser. I'm using a lot of apps for developing. And I always changing something in my system.

@Cheeseness
"delivered via Steam"
It's their problem

@computerquip
"EDIT: Also, I doubt that actually works in some cases."
Prove!

It's their problem

Not really. If you've manually edited scripts to run as root, you'd really only have yourself to blame.

Seriously though, stop focusing on root related stuff. That's not going to get this issue anywhere.

I don't really need proof, it's just a hunch. I know damn well that it causes security issues in the case the software does something its not supposed such as edit a system configuration file or try to grab data its not supposed too... or delete a directory its not supposed to.

Not really the point though. You're not supposed to run some software as root. When that software doesn't work like its supposed too, you don't just blame the software.

Why in the heck are you trying to run something from root? I can't think of a single good reason for doing so. Are some kind of Linux noob? It's a written rule that one should NEVER run as root. Sudo/Root is for administrative tasks only. In all reality, the root account should be completely disabled because having it enabled is a security risk.

Stop saying me that running system as root is a terrible catastrophe, go ****. It is not related to the problem. This issue happening on ANY *[edit] USER. If you have a problems with root, [edited]. I'm running as root since 2003, and I NEVER faced such problem as " it causes security issues in the case the software does something its not supposed such as edit a system configuration file or try to grab data its not supposed too... or delete a directory its not supposed to". What the heck? You are running root? Faced such problems? Then the problem is in you, rather than system. Don't worry about my security, it's fine. And I have NO problems running root.

IF you have nothing to say about this issue other than telling me "root is a bad idea", do NOT say anything. As I said, IT is NOT RELATED to the PROBLEM.

It's worth mentioning that my experience with HD4000 series integrated and big picture is abysmal.

CrashIDs are available in the steam info (Help>System Information).

On an aside, to clarify some things, running Steam as root is not officially supported. Furthermore, while I understand your need to be root for most of the things you do, the vast majority of professionals, admins, professors, students, and end users would say that running as root exclusively is a bad idea. This is especially true with the new focus on Linux as a mainstream desktop (partially spurred by Steam and the poor reception of Win8) and the interest in viable 0days on a blooming market.

That being said, it's your risk to take and most likely does NOT have anything to do with the issue. What may have something to do with it is the custom everything you've decided to deploy. As @gdrewb-valve mentioned, a crash report would be infinitely useful.

@gdrewb-valve
There is no crash reports

Problem has been fixed. Almost.

1. Crash has been fixed after latest update.
2. I still can't watch anything in Youtube. (lib32-flashplugin installed)

Anyway, closing.

@Pon3 - There are a few tricks to getting the flash plugin working properly with the client. Just look around and you'll probably find one of the solutions works.

@MrSchism
Yes, thanks for respond