Bug 38955 - dcopserver could not start (segmentation fault)
Summary: dcopserver could not start (segmentation fault)
Status: RESOLVED NOT A BUG
Alias: None
Product: dcop
Classification: Frameworks and Libraries
Component: dcopserver (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Matthias Ettrich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-04 19:03 UTC by boti
Modified: 2003-03-19 19:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description boti 2002-03-04 18:56:22 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           dcopserver
Version:           KDE 2.2.2 
Severity:          normal
Installed from:    Debian testing/unstable Packages
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Debian sid all packages are up to date updated from ftp.de.debian.org

I started a pure X server only with an xterminal running on it. I typed the startkde command and I got this output:
boti:~$ startkde
DCOPServer self-test failed.
kdeinit: DCOPServer could not be started aborting.
/usr/bin/kde2: line 102: 22113 Segmentation fault      ksmserver --restore
connect() failed: : Connection refused

The command dcopserver returned with:
DCOPServer self-test failed.

The command dcopserver --nofork got segfault.
I straced the docserver (w/o any argument) and its child go segfault too.

(Submitted via bugs.kde.org)
Comment 1 Simon Hausmann 2002-10-01 00:11:55 UTC
Could it be that you have multiple KDE versions installed or that you have a 
path to an old KDE installation in your /etc/ld.so.conf? Does ldd 
/path/to/dcopserver yield any errors about missing libraries? 
Comment 2 Waldo Bastian 2003-03-19 19:14:01 UTC
No feedback from user, assumed to be an installation problem.