View previous topic :: View next topic |
Author |
Message |
MalleRIM Guru
Joined: 23 Jul 2007 Posts: 563 Location: China
|
Posted: Fri May 23, 2014 11:33 am Post subject: kde-workspaces-5 won't start - access to /tmp denied |
|
|
Hi,
I wanted to try out kde-workspaces 5 from the kde overlay, but I ran into a problem: After signing in, it informs me that it cannot access /tmp because the permission is denied. The strange thing is, that whenever I sign in, permissions on /tmp change from drwxrwxrwx to drwx------. Even kdm won't work anymore until I change the permissions back. I can't find out what's causing this. I removed kde-workspaces 5 for now, because it collides with kde4, which I'm using as my main desktop. I suppose I should install a backup desktop.
Any help would be appreciated
Cheers,
Malle |
|
Back to top |
|
|
MalleRIM Guru
Joined: 23 Jul 2007 Posts: 563 Location: China
|
Posted: Sat May 24, 2014 6:50 am Post subject: |
|
|
OK, I now installed razorqt so my computer is usable without working KDE. I tried to launch startkde from within razorqt, this is what I got:
Code: | QCoreApplication::arguments: Please instantiate the QApplication object first
QCoreApplication::arguments: Please instantiate the QApplication object first
QCoreApplication::arguments: Please instantiate the QApplication object first
QCoreApplication::arguments: Please instantiate the QApplication object first
QStandardPaths: wrong ownership on runtime directory /tmp, 0 instead of 1000
QStandardPaths: wrong ownership on runtime directory /tmp, 0 instead of 1000
startkde: Starting up...
2014/05/24 08:42:56 socat[19625] E connect(3, AF=1 "<anon>", 2): Invalid argument
FATAL: The application binary appears to be running setuid, this is a security hole.
kdeinit5: Communication error with launcher. Exiting!
QStandardPaths: wrong ownership on runtime directory /tmp, 0 instead of 1000
kdeinit5_wrapper: Warning: connect(/kdeinit5__0) failed: : No such file or directory
The following installation problem was detected
while trying to start KDE:
Writing to the temp directory (/tmp) failed with
the error 'Permission denied'
KDE is unable to start.
QStandardPaths: wrong ownership on runtime directory /tmp, 0 instead of 1000
Failed to create secure directory (/tmp/pulse): Permission denied |
Permissions of /tmp before and after "startkde":
Code: | workoft ~ # ls -dn /tmp
drwxrwxrwx 16 0 0 560 May 24 08:41 /tmp
workoft ~ # ls -dn /tmp
drwx------ 16 0 0 560 May 24 08:42 /tmp |
it appears kdeinit5 is causing the problem. The same change of rights to /tmp happens when I launch kdeinit5 as root. But when I start it as a normal user, this is what I get:
Code: | malte@workoft ~ $ kdeinit5
QStandardPaths: wrong ownership on runtime directory /tmp, 0 instead of 1000
kdeinit5: Aborting. bind() failed: Permission denied
Could not bind to socket '/kdeinit5__0 |
Any ideas would be highly appreciated. |
|
Back to top |
|
|
kensington Developer
Joined: 02 Jan 2013 Posts: 177 Location: Australia
|
Posted: Sun May 25, 2014 6:32 am Post subject: |
|
|
Which version are you using - 4.96.0 or 9999? |
|
Back to top |
|
|
EliasP Guru
Joined: 06 Dec 2002 Posts: 318 Location: South-West Germany
|
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|