[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 50754] New: KDE startup hangs due to invalid NIS(YP) domainname
From: Torsten Kasch <tk () Genetik ! Uni-Bielefeld ! DE>
Date: 2002-11-15 11:04:19
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=50754
Summary: KDE startup hangs due to invalid NIS(YP) domainname
Product: kdelibs
Version: unspecified
Platform: Compiled Sources
OS/Version: Solaris
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: coolo@kde.org
ReportedBy: tk@Genetik.Uni-Bielefeld.DE
Version: (using KDE KDE 3.0.99)
Installed from: Compiled From Sources
Compiler: gcc 2.95.3
OS: Solaris
During startup, KDE hangs (ksplash showing "Initializing peripherals") as I already \
mentioned (the third issue) on kde-solaris (see \
http://lists.kde.org/?l=kde-solaris&m=103717896719055&w=2).
I managed to track this down a little bit: We're using NIS as a system for \
passwd/group/netgroup information and DNS for hostname resolution (config running \
perfectly for _years_ and working flawlessly with 3.1beta1). The DNS domainname is \
different from the NIS domainname (the latter being the lowercase form of the first \
which is mixed-case).
Somehow something inside KDE (not sure right now where to look) tries to use the DNS \
domainname as the NIS domain, trussing ypbind shows it's trying to open \
/var/yp/binding/<DNSdomain>/ypservers. For testing purposes I created a symlink \
pointing to the correct place which would allow me to log in finally, but kcheckpass \
still wouldn't unlock the screen. If called manually it just hangs (trying to \
communicate with ypbind I assume).
trussing 3.1beta1's kcheckpass shows that it's using sysinfo(SI_SRPC_DOMAIN) which \
obvoiusly succesds, whereas 3.1RC3's does something else. I already browsed through \
the CVS logs but could not find any changes that might be related to this problem :-(
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic