[SOLVED] Chromium over ssh and /tmp permissions

fhtagn · 2011-01-06 21:06:18

Hello, community.

In the last few weeks I assembled a headless Arch server on an somewhat 'old' desktop, for sandbox purposes.. right now it it acts as a LAMP server, seedbox, storage center, Stephen Hawking emulator (espeak)

X seems to be forwarded properly (as per ssh_config both in client as in the server) seeing as

xclock &

works as expected.

However... chromium does not. I get this:

[6140:6140:70816047217:ERROR:chrome/browser/process_singleton_linux.cc(949)] Failed to create socket directory.
[6140:6140:70816047971:ERROR:chrome/browser/browser_main.cc(1150)] Failed to create a ProcessSingleton for your profile directory. This means that running multiple instances would start multiple browser processes rather than opening a new window in the existing process. Aborting now to avoid profile corruption.

I ssh to my server using an Ubuntu eeepc.

How can I troubleshoot this?

Thank you for your help both here and in the wiki.
This has been an exciting trip.

Last edited by fhtagn (2011-01-09 21:03:55)

Mektub · 2011-01-07 00:15:05

fhtagn,

have you tried another browser ?

Possibly it as nothing to do with ssh.

Look if there is a lock file in /tmp or /var/tmp (.org.chromium*) and remove it.

If not, move ~/.config/chromiun out of the way.

Try as root.

Mektub

fhtagn · 2011-01-07 11:47:22

thank you for your feedback

I have found no lock file. And removing

~/.config/chromium

did not help

firefox gives me

** ERROR **: I can't write to '/tmp/orbit-USER', ORB init failed

(USER being my username...)

uzbl loads up, and navigation is fine (quite fast, I must say) but gives me

** (uzbl-core:7143): WARNING **: init_fifo: can't create /tmp/uzbl_fifo_44040225: Permission denied
** (uzbl-core:7143): WARNING **: init_socket: could not open in /tmp/uzbl_socket_44040225: Permission denied

Never seen these errors so in time I will try to understand / google them...
But why would a browser need these permissions? or the other way around: why would they be wrong?

 drwxr-xr-x root root Jan  7 11:42 tmp

Shouldn't these browser tmp files be user specific (as in: located somewhere inside my ~/ and on on /tmp/ ?)
Or am I misunderstanding the purpose of /tmp/ ?

I never ran a server so I always thought 'normal' users would forever ignore most of the filesystem outside their ~/

Ramses de Norre · 2011-01-07 12:24:12

chmod 1777 /tmp

Your /tmp should be writable to all and have the sticky bit set (that's the first 1), so it should look like

drwxrwxrwt  13 root root  280 Jan  7 11:53 tmp

And it is expected that those programs write their temporary stuff to /tmp, that's what /tmp is for.

satanalin · 2011-01-09 12:12:26

Same error. changing permission for /tmp did not help, firefox works.
also trying to reinstall, remove ~/.config/chromium and cache/chromium. no effect.
via sudo it works.

fhtagn · 2011-01-09 16:56:32

Ramses de Norre wrote:

chmod 1777 /tmp
Your /tmp should be writable to all
drwxrwxrwt  13 root root  280 Jan  7 11:53 tmp

Thank you.
I understand this solves the permission problem (and it did), I was just a bit puzzled because this lets users other's tmp...

Problem solved

Ramses de Norre · 2011-01-09 17:07:08

fhtagn wrote:

Ramses de Norre wrote:
chmod 1777 /tmp
Your /tmp should be writable to all
drwxrwxrwt  13 root root  280 Jan  7 11:53 tmp
Thank you.
I understand this solves the permission problem (and it did), I was just a bit puzzled because this lets users other's tmp...
Problem solved

It doesn't let others access your files under /tmp when you set the permissions of whatever you place in /tmp correctly, normally when you put something in /tmp you set the permissions on 700. Only /tmp itself is world read/writable, but this is logical since it should be the temporary directory for everyone.
The sticky bit (the first one) also makes sure that no matter what no one else can delete or rename your stuff.

fhtagn · 2011-01-09 17:16:02

Ramses de Norre wrote:

It doesn't let others access your files under /tmp when you set the permissions of whatever you place in /tmp correctly, normally when you put something in /tmp you set the permissions on 700. Only /tmp itself is world read/writable, but this is logical since it should be the temporary directory for everyone.

I see. Point taken! Thanks again

ps. changing the title to "Chromium over ssh and /tmp permissions"

satanalin wrote:

Same error. changing permission for /tmp did not help, firefox works.
also trying to reinstall, remove ~/.config/chromium and cache/chromium. no effect.
via sudo it works.

Assuming everything else works as expected (X, ssh, pacman resolved the dependencies correctly) I don't know what to suggest.
Changing the permissions to /tmp solved my error.

Last edited by fhtagn (2011-01-09 17:16:21)

Mektub · 2011-01-09 21:03:11

fhtagn,

please insert "[SOLVED]" in title.

Mektub

fhtagn · 2011-01-09 21:05:09

I was going to, but satanalin still had a problem.

Marked it SOLVED now.

Arch Linux

#1 2011-01-06 21:06:18

[SOLVED] Chromium over ssh and /tmp permissions

#2 2011-01-07 00:15:05

Re: [SOLVED] Chromium over ssh and /tmp permissions

#3 2011-01-07 11:47:22

Re: [SOLVED] Chromium over ssh and /tmp permissions

#4 2011-01-07 12:24:12

Re: [SOLVED] Chromium over ssh and /tmp permissions

#5 2011-01-09 12:12:26

Re: [SOLVED] Chromium over ssh and /tmp permissions

#6 2011-01-09 16:56:32

Re: [SOLVED] Chromium over ssh and /tmp permissions

#7 2011-01-09 17:07:08

Re: [SOLVED] Chromium over ssh and /tmp permissions

#8 2011-01-09 17:16:02

Re: [SOLVED] Chromium over ssh and /tmp permissions

#9 2011-01-09 21:03:11

Re: [SOLVED] Chromium over ssh and /tmp permissions

#10 2011-01-09 21:05:09

Re: [SOLVED] Chromium over ssh and /tmp permissions

Board footer