Firefox not start as user but OK in root

[vlaporte]

HowTO - change permissions on  /home/vlaporte/tmp  folder
03/2/2012

Problem - after update all in Synaptic I could not open Firefox or Chromium browsers as ordinary user but worked fine in root.
I got this error code when I tried to open Firefox with command   /usr/bin/firefox
ERROR  can't write to  /home/vlaporte/tmp/orbit-vlaporte
So it looks like I lost permission to my own tmp folder which these browsers use.

Solution - Open file manager, Dolphin, as root and add permissions (was  rwx,w x,w x) and changed to (rwx,wrx,wrx) specifically I need write permission as ordinary user.
Now both browsers work fine.
Luck,
Vince

[demilord]

HowTO - change permissions on  /home/vlaporte/tmp  folder
03/2/2012

Problem - after update all in Synaptic I could not open Firefox or Chromium browsers as ordinary user but worked fine in root.
I got this error code when I tried to open Firefox with command   /usr/bin/firefox
ERROR  can't write to  /home/vlaporte/tmp/orbit-vlaporte
So it looks like I lost permission to my own tmp folder which these browsers use.

Solution - Open file manager, Dolphin, as root and add permissions (was  rwx,w x,w x) and changed to (rwx,wrx,wrx) specifically I need write permission as ordinary user.
Now both browsers work fine.
Luck,
Vince

My firefox works great and uses permission
drwx------

And firefox never complained.. Id be very carefull with the rwx,rwx,rwx it means everyone and everyone can access those files, which is a huge security risk.. Prefer use, rwx,rwx,--- becos noone else except you and the system need access...

what you could have done is CHOWN the folder instead because I think it was a ownership problem then a permission problem...
And this is not really a tip or trick..

[Tony]

Hi vlaporte , not sure if you've solved your issue ?

I had a problem were I could only run Firefox as root. Had it twice so have the 'fix' logged.
http://www.pclinuxos.com/forum/index.php/topic,99845.0.html

The fix is at the bottom of that page, basically changes ownership back to what should be 'user' files, rather than root.

Will post to save you time. Lots of mucking around till OP stated the obvious.

Old-Polack:

In a terminal, as root;

[root@localhost ~]# chown -R jimi:jimi /home/jimi         <Enter>

This returns all files and sub directories in your ~/ directory to user jimi group jimi.

Of course insert your username.  

Suppose it's what demilord meant when he said to CHOWN:

what you could have done is CHOWN the folder instead because I think it was a ownership problem then a permission problem...
And this is not really a tip or trick..