|
Bugzilla – Full Text Bug Listing |
| Summary: | After update RC1->RC2: Could not start kstartupconfig | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Klaus Kämpf <kkaempf> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED WORKSFORME | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | ||
| Version: | RC 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Klaus Kämpf
2005-09-13 08:43:33 UTC
The host is heron.suse.de good to know. I will next time I report a yast bug also only tell the host name instead of providing meaningful logs. Is that autologin? Did you hurry on login? It seems NIS was up, but autofs wasn't yet. Did you try relogin? Sep 13 10:36:34 heron kdm: :0[23114]: Cannot chdir to kkaempf's home /suse/kkaempf: No such file or directory, using / kstartconfig exists nowhere on the distro.. where does it come from? On second try it worked. No, I didn't hurry the logn. Quite the contrary ;-) Closing for now. But it sure is puzzling. ah, its kstart_up_config The message mentioned "kstartupconfig". |