Bug 55585 - Cannot start KDE - kdeinit: Communication error with launcher. Exiting!
Summary: Cannot start KDE - kdeinit: Communication error with launcher. Exiting!
Status: RESOLVED NOT A BUG
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: klauncher (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-06 00:20 UTC by Alex Walker
Modified: 2003-03-07 13:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
output of strace (17.51 KB, application/x-tar)
2003-03-06 15:04 UTC, Alex Walker
Details
kinit_klauncher.patch (781 bytes, text/x-diff)
2003-03-06 15:54 UTC, Waldo Bastian
Details
output of strace, with kdelibs patched. (17.72 KB, application/x-tar)
2003-03-07 12:49 UTC, Alex Walker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Walker 2003-03-06 00:20:43 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc-3.2.2 CFLAGS & CXXFLAGS = -march=pentium3 -O3 -pipe -fomit-frame-pointer -fforce-addr -falign-functions=4 -fprefetch-loop-arrays
OS:          Linux

Compiled latest CVS, which worked up to about 2 weeks ago, but now I can't start KDE.

I've tried CVS updating & recompiling qt, arts, kdelibs, kdebase about once per day for two weeks... but still no joy.

Tried removing all my ~/.kde* directories, no difference.

Have used multiple Xfree86 versions too..

Here's a dump of what happens when I try to start it... and when it fails I forcefully quit X...

XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20-gentoo-r1 i686 [ELF] 
Build Date: 01 March 2003
        Before reporting problems, check http://www.XFree86.Org/
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Wed Mar  5 23:13:05 2003
(==) Using config file: "/etc/X11/XF86Config-4"
(EE) Failed to load module "pex5" (module does not exist, 0)
(EE) Failed to load module "xie" (module does not exist, 0)
Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a
 is unresolved!
Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a
 is unresolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXMalloc from module /usr/X11R6/lib/modules/extensions/libGLcore.a is 
unresolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXLastContext from module /usr/X11R6/lib/modules/extensions/libGLcore.
a is unresolved!
Symbol __glXMalloc from module /usr/X11R6/lib/modules/extensions/libGLcore.a is 
unresolved!
Symbol __glXMalloc from module /usr/X11R6/lib/modules/extensions/libGLcore.a is 
unresolved!
Symbol __glXMalloc from module /usr/X11R6/lib/modules/extensions/libGLcore.a is 
unresolved!
Symbol __glXMalloc from module /usr/X11R6/lib/modules/extensions/libGLcore.a is 
unresolved!
Symbol __glXMalloc from module /usr/X11R6/lib/modules/extensions/libGLcore.a is 
unresolved!
Symbol __glXMalloc from module /usr/X11R6/lib/modules/extensions/libGLcore.a is 
unresolved!
Symbol __glXMalloc from module /usr/X11R6/lib/modules/extensions/libGLcore.a is 
unresolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
Symbol __glXMalloc from module /usr/X11R6/lib/modules/extensions/libGLcore.a is 
unresolved!
Symbol __glXMalloc from module /usr/X11R6/lib/modules/extensions/libGLcore.a is 
unresolved!
Symbol __glXFree from module /usr/X11R6/lib/modules/extensions/libGLcore.a is un
resolved!
(II) [GLX]: Initializing GLX extension
Warning: font renderer for ".pcf" already registered at priority 0
Warning: font renderer for ".pcf.Z" already registered at priority 0
Warning: font renderer for ".pcf.gz" already registered at priority 0
Warning: font renderer for ".snf" already registered at priority 0
Warning: font renderer for ".snf.Z" already registered at priority 0
Warning: font renderer for ".snf.gz" already registered at priority 0
Warning: font renderer for ".bdf" already registered at priority 0
Warning: font renderer for ".bdf.Z" already registered at priority 0
Warning: font renderer for ".bdf.gz" already registered at priority 0
Warning: font renderer for ".pmf" already registered at priority 0
Could not init font path element unix/:7110, removing from list!
INFO: imwheel started (pid=20457)
startkde: Starting up...
kdeinit: Communication error with launcher. Exiting!
Communication error with KInit.
startkde: Could not start ksmserver. Check your installation.
kio (KSycoca): WARNING: Found version 60, expecting version 61 or higher.
kio (KSycoca): WARNING: Outdated database found
kio (KMimeType): WARNING: KServiceType::offers : servicetype KDEDModule not foun
d
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
startkde: Shutting down...
Warning: connect() failed: : Connection refused
Error: Can't contact kdeinit!
xinit:  connection to X server lost.
Hangup
GOT SIGHUP
startkde: Running shutdown scripts...
startkde: Done.
Comment 1 Waldo Bastian 2003-03-06 12:27:55 UTC
Subject: Re:  New: Cannot start KDE - kdeinit: Communication error with launcher. Exiting!

On Thursday 06 March 2003 00:20, you wrote:
> Compiler:          gcc-3.2.2 CFLAGS & CXXFLAGS = -march=pentium3 -O3 -pipe
> -fomit-frame-pointer -fforce-addr -falign-functions=4
> -fprefetch-loop-arrays OS:          Linux
>
> Compiled latest CVS, which worked up to about 2 weeks ago, but now I can't
> start KDE.

[Snip]

> kdeinit: Communication error with launcher. Exiting!
> Communication error with KInit.

Most likely a compile(r) error. For some reason kdeinit and klauncher can't 
communicate with each other.

Start dcopserver manually with "dcopserver" (does that complain about 
anything?) and then try stracing "kdeinit --no-kded --no-dcop" e.g. with 
"strace -o /tmp/kdeinit -tt -f -ff kdeinit --no-kded --no-dcop".

Cheers,
Waldo
Comment 2 Alex Walker 2003-03-06 14:49:24 UTC
dcopserver starts up without errors.

Strace give the following output:
Process 5245 attached
Process 5246 attached
Process 5245 suspended
Process 5245 resumed
Process 5246 detached
Process 5247 attached
kdeinit: Communication error with launcher. Exiting!
Process 5245 detached
Process 5248 attached
kded: cannot connect to X server :0
Process 5248 detached
kded: ERROR: KUniqueApplication: DCOP communication error!
Process 5247 detached

attached is a tarball of /tmp/kdeinit* 
Comment 3 Alex Walker 2003-03-06 15:00:17 UTC
Sorry, gave the wrong command line (I had --nokded instead of --no-kded)

Strace run straight from command line gives the following output:
$ strace -o ~/stuff/kdebug/kdeinit -tt -f -ff kdeinit --no-kded --no-dcop
Process 5268 attached
Process 5269 attached
Process 5268 suspended
Process 5268 resumed
Process 5269 detached
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
kdeinit: Communication error with launcher. Exiting!
Process 5268 detached

Strace run from within X with just xterm loaded gives the following output:
$ strace -o ~/stuff/kdebug/kdeinit2 -tt -f -ff kdeinit --no-kded --no-dcop
Process 5300 attached
Process 5301 attached
Process 5300 suspended
Process 5300 resumed
Process 5301 detached
kdeinit: Communication error with launcher. Exiting!
Process 5300 detached

attached is a tarball of ~/stuff/kdebug/kdeinit* 
(so kdeinit is without X loaded and kdeinit2 is with X loaded)
Comment 4 Alex Walker 2003-03-06 15:04:27 UTC
Created attachment 1113 [details]
output of strace
Comment 5 Waldo Bastian 2003-03-06 15:54:45 UTC
Subject: Re:  Cannot start KDE - kdeinit: Communication error with launcher. Exiting!

Does the following patch make any difference?

Cheers,
Waldo


Created an attachment (id=1115)
kinit_klauncher.patch
Comment 6 Alex Walker 2003-03-07 02:40:50 UTC
Unfortunately, this does not change anything... want another strace etc?

Still get:
kdeinit: Communication error with launcher. Exiting!
Warning: connect() failed: : Connection refused
Comment 7 Waldo Bastian 2003-03-07 11:53:36 UTC
Subject: Re:  Cannot start KDE - kdeinit: Communication error with launcher. Exiting!

Can you send me a new strace with this patch in?
Comment 8 Alex Walker 2003-03-07 12:49:12 UTC
Created attachment 1125 [details]
output of strace, with kdelibs patched.

Outside X (kdeinit3 in tarball):
Process 31489 attached
Process 31490 attached
Process 31489 suspended
Process 31489 resumed
Process 31490 detached
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
kdeinit: Communication error with launcher. Exiting!

Inside X (kdeinit4 in tarball):
Process 31528 attached
Process 31529 attached
Process 31528 suspended
Process 31528 resumed
Process 31529 detached
kdeinit: Communication error with launcher. Exiting!
Process 31528 detached
Comment 9 Waldo Bastian 2003-03-07 13:06:50 UTC
main() nor kdemain() in klauncher is ever reached, that suggests that this problem is caused by either a 
compilation or a compiler error. 
 
Comment 10 Alex Walker 2003-03-07 13:31:50 UTC
So do I post a bug against gcc then?  Or is this going to be of no help to them?
 I suppose I should try another version of the compiler and see if that fixes it...
Comment 11 Waldo Bastian 2003-03-07 13:43:09 UTC
Subject: Re:  Cannot start KDE - kdeinit: Communication error with launcher. Exiting!

On Friday 07 March 2003 13:31, you wrote:
> ------- Additional Comments From alex@x3ja.co.uk  2003-03-07 13:31 -------
> So do I post a bug against gcc then?  Or is this going to be of no help to
> them? I suppose I should try another version of the compiler and see if
> that fixes it...

I suggest you try to find out if if there is any particular relation between 
compile flags and/or compiler version. Once you can pinpoint it to something 
in particular and this is indeed still a problem in the most recent version 
of gcc, then I would contact the gcc developers.

Cheers,
Waldo