[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Bug#14250: marked as done (dcopserver crash startup)
From:       owner () bugs ! kde ! org (Stephan Kulow)
Date:       2000-10-31 19:18:04
[Download RAW message or body]

Your message dated Tue, 31 Oct 2000 20:11:42 +0100
with message-id <39FF196E.24B740D0@kde.org>
and subject line Bug#14250: dcopserver crash startup
has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 31 Oct 2000 19:02:20 +0000
Received: (qmail 5010 invoked by uid 33); 31 Oct 2000 19:02:19 -0000
Date: 31 Oct 2000 19:02:19 -0000
Message-ID: <20001031190219.5009.qmail@master.kde.org>
To: submit@bugs.kde.org
Subject: dcopserver crash startup
From: ravi@ee.eng.ohio-state.edu

Package: kdelibs
Version: 2.0 final
Severity: grave
Installed from: Source

DCOPserver failed on startup, complaining that it is unable to establish any \
listening sockets. I removed the .ICE-unix directory in /tmp. Now, the DCOPserver \
starts up, but virtually every KDE application segfaults on startup. This did not \
happen with earlier beta versions of KDE 2. My system configurations have not changed \
and KDE 1.1.2 worked fine.

Background:
I am running RedHat 6.2 and XFree86 3.3.6. The Qt 2.2.1 package was compiled with the \
                flags
 -gif -system-jpeg -system-libmng -no-threads -no-opengl
The installation of KDE 2.0 works fine on the server in which it was compiled. \
However, the same binaries, on a file system NFS-exported to a different machine, \
cause the problem described above. The machines have identical libraries installed . \
(/usr and /local are exported from the same server, and all drives are mounted with \
suid and exec priveleges.) I will be happy to provide any further information.

An example backtrace for a segfault in kwrited:

0x40d6f8c9 in __wait4 () from /lib/libc.so.6
#0  0x40d6f8c9 in __wait4 () from /lib/libc.so.6
#1  0x40dce1cc in ?? () from /lib/libc.so.6
#2  0x4047086a in KCrash::defaultCrashHandler ()
   from /opt/local/kde/lib/libkdecore.so.3
#3  0x40cfcc48 in __restore ()
    at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127
#4  0x40e1ead7 in TEPty::openPty () from
/opt/local/kde/lib/libkonsolepart.so
#5  0x40e1eff4 in TEPty::TEPty () from
/opt/local/kde/lib/libkonsolepart.so
#6  0x404c7685 in KWrited::KWrited () from /opt/local/kde/lib/kwrited.so
#7  0x404c7a50 in main () from /opt/local/kde/lib/kwrited.so
#8  0x804a34a in launch ()
#9  0x804bcd1 in main ()
#10 0x40cf69cb in __libc_start_main (main=0x804b8d4 <main>, argc=7,
    argv=0xbffffcd4, init=0x8049774 <_init>, fini=0x804c0ac <_fini>,
    rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbffffccc)
    at ../sysdeps/generic/libc-start.c:92  

Regards,
Ravi

(submitted via bugs.kde.org)

 
> > Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]