Lxtask is reporting chromium to be running as root [SOLVED]

[alexanders]

I have a problem with lxtask, i noticed that as i run chromium as a normal user, lxtask somehow shows root user to be the owner of some chromium processes together with some instances running under my normal user. I think it is a bug and a weird one too, does anyone has similar problem? I hope i am not hacked\trojaned\virused or anything related. When doing normal 'ps' in the terminal i only see my normal user being the owner of all the instances.

[hugovanwoerkom]

Hi,

This what I get:
hugo@SDB03:~$ ps -ef|grep /opt/google/chrome/chrome|cut -c 1-30
+ grep /opt/google/chrome/chrome
+ ps -ef
+ cut -c 1-30
hugo 6209 1 0 09:54
hugo 6214 6209 0 09:54
hugo 6215 6209 0 09:54
hugo 6242 6215 0 09:54
hugo 6250 6215 0 09:54
hugo 6265 6215 0 09:54
hugo 6272 6215 0 09:54
hugo 6281 6209 0 09:54
hugo 6287 6215 0 09:54
hugo 6297 6215 0 09:54
hugo 6308 6215 0 09:54
hugo 6315 6215 0 09:54
hugo 6322 6215 0 09:54
hugo 6339 6215 0 09:54
hugo 6395 6215 0 09:54
hugo 6402 6215 0 09:54
hugo 6413 6215 0 09:54
hugo 6421 6215 0 09:54
hugo 6432 6215 0 09:54
hugo 6439 6215 0 09:54
hugo 6450 6215 0 09:54
hugo 6471 6215 0 09:54
hugo 6478 6215 0 09:54
hugo 22197 6215 0 15:05
hugo 24969 6165 0 16:03

No root user at all...

Hugo

[Rex Bouwense]

I do not use Chromium or Chrome, but you have little to worry about when it comes to being hacked\trojaned\virused or anything related. There are somewhere in the vicinity of 350 versions of Linux OS out there and about 50 or so virus known to exist (none of which are active.) Anyway, Linux was once explained to me as a house with all of the doors and windows locked and you have the only key. So, if there was an active linux virus you would have to give your permission (open a window or door) for it to do any evil to your system.
Welcome to the lxde forums where we hope that all of your questions will eventually be answered by someone who knows what they are talking about.

[alexanders]

To clarify:
$ ps -ef|grep chromium|cut -c 1-30
edwin 1736 1 7 17:45
edwin 1738 1736 1 17:45
edwin 1739 1736 0 17:45
edwin 1742 1739 0 17:45
edwin 1746 1742 0 17:45
edwin 1747 1742 0 17:45
edwin 1771 1747 0 17:45
edwin 1789 1747 1 17:45
edwin 1796 1747 1 17:45
edwin 1805 1747 0 17:45
edwin 1838 1736 12 17:45
edwin 1886 1747 1 17:46
edwin 1908 1747 1 17:47
edwin 1915 1736 0 17:47
edwin 1924 1747 1 17:48
edwin 2086 2061 0 17:58

Output of Lxtask


That is what i am talking about.
A link on ask ubuntu of another guy having the same issue http://askubuntu.com/questions/56876/ch ... ng-as-root

[Rex Bouwense]

Did you do what was suggested to find out if you were the actual user?

I just checked launchpad for a bug and found this:
https://bugs.launchpad.net/ubuntu/+sour ... ug/1016178
Apparently this is normal and the post says that you can read more about it here:
http://code.google.com/p/chromium/wiki/LinuxSUIDSandbox

Hope that helps.

[alexanders]

Yes, 'ps -ef | grep <PID>' with PID taken from lxtask output shows that my currently logged in user "edwin" is the owner. I created another user on my system called "guest" and all is perfect, lxtask shows correct results.

[alexanders]

Read it, got it. I've found chromium-sandbox suid executable. Well, this solves my issue.