Hi, Michael Nottebrock wrote: > > I'm almost willing to bet that if you wait a really long time (up to ten > minutes) without hitting ctrl-alt-backspace, KDE will eventually start > up, which would indicate that a DNS problem appeared on your network - > perhaps some infrastructure change happened over the last few days?
No, it didn't. As I said, I did not work at the station building (where the clients, nameserver and router/firewalling machine are located) during the last days. No machines added, reconfigured or removed. And I waited for about 1/2 an hour before applying the "monkey's grip". > Check that /etc/hosts has no stale entries, make sure the machine(s) in > question have a hostname set and can resolve localhost properly. I did not change the default /etc/hosts on the clients. Yes, 'hostname' gives the expected output, 'host localhost' as well. I know that this can be a problem with X since I (once upon a time...) removed 'options INET' from the kernel config file ;) I've become less adventurous since then. > You can > find quite a bit of correspondence about this problem in the archives > of this mailing list (mostly under the subject of 'slow startup' and > similar). I read that thread, and I almost thought that I could rejoice, but it did not apply, i.e. it did not solve my problem :( I have a dedicated name server which I did not fiddle with in almost a year. No firewall or anything is preventing access to 127.0.0.1 on the clients and hostnames are set via rc.conf. And: all other window managers and desktop environments I tried (even Gnome) work as they should. When starting X manually, no error messages show up. What's so strange is that the clients are configured absolutely identical to the old, working configuration (5.4-RELEASE), except the OS and KDE version upgrades. I mangage the alterations to client configs on the file server via RCS, namely sysctl.conf, devfs.conf, devd.conf and fstab from /etc and did synchronize them to the changes in the defaults for 6.0, i.e. applied the changes after checking that they are still valid. I looked there thoroughly for something that could be the culprit, but without "success". And as I said, the machines worked fine for several weeks _after_ the reinstall with the new versions. I normally don't contact support lists lightly, but this time I'm really desperate and running in circles. Thanks for the hints so far, but where from here? I'm without any clue. Andreas -- Andreas Braml Netzwerk für radio 98eins PGP: http://www.braml.org/radio.asc Please avoid sending me Microsoft Office (e.g. Word, PowerPoint) attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
signature.asc
Description: OpenPGP digital signature
_______________________________________________ kde-freebsd mailing list [email protected] http://freebsd.kde.org/mailman/listinfo/kde-freebsd
