VectorLinux
August 01, 2014, 02:07:26 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1]
  Print  
Author Topic: k3b doesn't start and a strange message appears  (Read 719 times)
Alb
Member
*
Posts: 74


« on: May 08, 2011, 12:19:11 pm »

Yesterday I installed k3b and used it successfully once (I copied a CD) launching it by terminal.
Today I added it in .icewm > menu-multimedia and tried to launch it by icewm menu: the first image of k3b appeared but hanged in the middle of the screen doing nothing, so I rebooted and launched k3b by terminal obtaining:

alberto:$ k3b
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/alberto/.DCOPserver_vector.linux.net__0
and start dcopserver again.
---------------------------------

DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
WARNING: DCOP communication problem!
kdeinit: Communication error with launcher. Exiting!
ERROR: KUniqueApplication: Pipe closed unexpectedly.
vector:/~
alberto:$

Have you a suggestion? What is the meaning of that message?
Best Regards
Logged
tomh38
Vectorian
****
Posts: 913



« Reply #1 on: May 12, 2011, 04:27:41 am »

This could be a file ownership problem.  If the current user doesn't have ownership and read/write permission of the ".kde" and all the files in it, this could occur.  The ".kde" folder is in /home/[your-user-name].

Try this:  login as root in a terminal (type "su," then your root password).

Then type the following:  chown -hR [your-user-name] .kde - no brackets, just the user name you're logged in as.

Post back and let us know if this helps or not.  I'm confident there's a solution to this problem

Tom
Logged

"I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones." - Linus Torvalds, April 1991
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!