k3b can not "talk" to klauncher

Pumalite · 04-30-2007, 01:20 PM

The result is that I cannot access my files from k3b. What is klauncher?. And, how can I fix the problem? Thanks a lot for your help. I'm using Suse 10.2 with Gnome.
P.S. I reviewed "Find Similar Threads", but couldn't find anything useful.

Pumalite · 04-30-2007, 10:58 PM

Quote:

Originally Posted by Pumalite

The result is that I cannot access my files from k3b. What is klauncher?. And, how can I fix the problem? Thanks a lot for your help. I'm using Suse 10.2 with Gnome.
P.S. I reviewed "Find Similar Threads", but couldn't find anything useful.

I found out I can run k3b from the terminal as root, so, it's all a matter of permissions. Granting permission to <username> doesn't work. I have to grant permission to specific files. Which ones?. Help appreciated.

Pumalite · 05-01-2007, 06:58 AM

Quote:

Originally Posted by Pumalite

I found out I can run k3b from the terminal as root, so, it's all a matter of permissions. Granting permission to <username> doesn't work. I have to grant permission to specific files. Which ones?. Help appreciated.

Well guys, problem solved. I had to grant permission to file /.ICEauthority and I did. Now Amarok as well as k3b work fine as user. Thanks anyway.I hope this helps someone in the future.

yinrunning · 05-22-2007, 09:37 AM

puma, this did nothing for me. I chmod 777 on ~/.ICEauthority. No effect. finally went back to 600. Was there anything else you did?

Pumalite · 05-23-2007, 03:26 PM

Quote:

Originally Posted by yinrunning

puma, this did nothing for me. I chmod 777 on ~/.ICEauthority. No effect. finally went back to 600. Was there anything else you did?

No, that's all I did. It worked for me. Run dcopserver and find out what else is wrong with your system.

Splatt · 06-06-2007, 03:53 AM

Hi! I just had the same problem. I tried the same thing with changing the permissions but it didn't work. Then i got pissed of and deleted the file. (.ICEsomething) and when i restarted amarok the file was created again and everything worked perfect...

PS. (had u just changed the permission of your home dir? that was the reason for me...) DS

Pumalite · 06-07-2007, 04:58 PM

Quote:

Originally Posted by Splatt

Hi! I just had the same problem. I tried the same thing with changing the permissions but it didn't work. Then i got pissed of and deleted the file. (.ICEsomething) and when i restarted amarok the file was created again and everything worked perfect...

PS. (had u just changed the permission of your home dir? that was the reason for me...) DS

I just changed the permission, but deleting the file is just as good because whoever uses the socket recreates the file. Good luck.

egag · 08-03-2007, 05:18 PM

Just found out that running "kdeinit" in a terminal solves this prob.

Abdrahim · 12-13-2011, 01:53 PM

Thanks for the help folks. kdeinit4 finally did it for me. Then I had to change the permissions for the files it indicated (./home/user/.kde/share/k3brc). Man, Oeiric is like going ten steps back. I hope they restore all of the user friendly features to the next version, because Oneiric is very disappointing. I much prefer Gnome2. And Unity is for the birds.