Cannot run kcontrol on FreeBSD system

Cannot run kcontrol on FreeBSD system

Post by John Grim » Mon, 24 Dec 2001 17:12:34



I cannot start kcontrol on FreeBSD 4.4 sytem with XFree86 4.1.0, KDE 2.2.1.  I suspect its probably a configuration problem.  I try to start it this is the output I get:

deinonychus# kcontrol
kdeinit: Launched DCOPServer, pid = 2215 result = 0
DCOP: register 'anonymous-2215' -> number of clients is now 1
DCOPServer up and running.
DCOP: unregister 'anonymous-2215'
kdeinit: Launched KLauncher, pid = 2220 result = 0
DCOP: register 'klauncher' -> number of clients is now 1
DCOP: unregister 'klauncher'
DCOP: register 'klauncher' -> number of clients is now 1
DCOP: register 'anonymous-2220' -> number of clients is now 2
DCOP: new daemon klauncher
DCOP: unregister 'anonymous-2220'
kdeinit: Launched KDED, pid = 2222 result = 0
DCOP: register 'kded' -> number of clients is now 1
DCOP: unregister 'kded'
DCOP: register 'kded' -> number of clients is now 1
DCOP: register 'anonymous-2222' -> number of clients is now 2
kio (KDirWatch): KDirWatch: Can't use FAM
kio (KDirWatch): KDirWatch: Can't use FAM
kded: Does not exist! (/root/.kde/share/servicetypes/)
DCOP: register 'anonymous-2223' -> number of clients is now 3
kio (KLauncher): KLauncher: Got kdeinit_exec_wait('kbuildsycoca', ...)
kdeinit: Got EXEC_NEW 'kbuildsycoca' from launcher.
kio (KLauncher): kbuildsycoca (pid 2224) up and running.
DCOP: register 'kbuildsycoca' -> number of clients is now 4
kbuildsycoca: Recreating ksycoca file
kbuildsycoca: Database is up to date
DCOP: unregister 'kbuildsycoca'kdeinit: PID 2224 terminated.

DCOP: unregister 'anonymous-2223'
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-2222' to 'kded'
ERROR: KUniqueApplication: DCOP communication error!
DCOP: unregister 'kded'
kdeinit: PID 2222 terminated.
DCOP: unregister 'anonymous-2222'
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
DCOP: register 'kcontrol' -> number of clients is now 1
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
kcontrol: cannot connect to X server :0.0
DCOP: unregister 'kcontrol'
DCOP: register 'anonymous-2211' -> number of clients is now 1
ERROR: KUniqueApplication: Registering failed!
ERROR: KUniqueApplication: DCOP communication error!
DCOP: unregister 'anonymous-2211'
einonychus# DCOPServer : slotTerminate() -> sending terminateKDE signal.
klauncher: KLauncher::process ---> terminateKDE
kdeinit: terminate KDE.
kdeinit: Fatal IO error: client killedDCOP: unregister 'klauncher'

kdeinit: sending SIGHUP to children.
kdeinit: sending SIGTERM to children.
kdeinit: Exit.

Any help will be apreciated!

 
 
 

Cannot run kcontrol on FreeBSD system

Post by Dinesh Nai » Wed, 26 Dec 2001 15:56:32



> I cannot start kcontrol on FreeBSD 4.4 sytem with XFree86 4.1.0, KDE 2.2.1.  [..snipped..]
> Xlib: connection to ":0.0" refused by server
> Xlib: Client is not authorized to connect to Server
> kdeinit: Can't connect to the X Server.
> kdeinit: Might not terminate at end of session.

that's your problem. you need to check two things:

1. are you running X/KDE in the first place ? this is definitely needed.
2. are you executing kcontrol as a different user than the one running X/KDE
?

if #1, then just start X/KDE to get it to work.
if #2, then check the x access control with xhost. you need to allow access
control from the localhost. man xhost for this.

--
Regards,                           /\_/\   "All dogs go to heaven."

+==========================----oOO--(_)--OOo----==========================+
| for a in past present future; do                                        |
|   for b in clients employers associates relatives neighbours pets; do   |
|   echo "The opinions here in no way reflect the opinions of my $a $b."  |
| done; done                                                              |
+=========================================================================+

 
 
 

1. NFS io errors on transfer from system running 2.4 to system running 2.5

Speaking of weird errors:

For the last few months I encounter this:

When doing rsync or cp _from_ system running 2.4 _to_ system running 2.5
get Input/output error errors with random files.

- 2-5 > 2.4 is OK!
- SRebootting, swapping kernel causes the error on the system running 2.4    
- Fast machine > slow machine or slow machine > fast machine
  is no different
- Both systems run same distribution
- Encountered since 2.4.20 with about 2.5.64 (my first 2.5 kernel)

Example:

/temp contains a couple of crap files

system mhfl2 is running 2.5.6x to 2.5.70-mm3 mounted on
/mnt/mhfl2.

On system running 2.4.20 or 2.4.21-x:
  while ((1)); do cp -f /temp/* /mnt/mhfl2/temp; done

cp: cannot create regular file `/mnt/mhfl2/temp/blah: Input/output error
cp: writing `/mnt/mhfl2/temp/blah: Input/output error

Errors are random, so the files change every run, sometimes there are no errors,
sometimes thre are 3 errors

Q? Any (in)compatibility reason or should I investigate further?

Regards
Michael Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. trap on exit

3. Cannot rlogin or telnet to my system (FreeBSD 2.2.2-RELEASE)

4. Mach 64 unter X

5. 2.4.19-pre8-ac5: cannot mount FreeBSD file system

6. Hostname > 8 characters in HPUX. Is it possible??

7. Cannot install patches on system running 2.5.1

8. Network not accessible after booting

9. System cannot shutdown if X is running: Why???

10. Which FreeBSD version can run LFS (Log-Structured File System) ?

11. Got FreeBSD running - thanx for a great system

12. How is FreeBSD running on systems based on VIA chipsets?

13. FS: 486DX2-80 system (running FreeBSD)