| Summary: | kde-base/kdm-4.6.3 - start-stop-daemon: did not create a valid pid in `/var/run/kdm.pid` | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Vasyl <senalba> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | senalba |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Vasyl
2011-05-21 19:02:22 UTC
Please read the instructions and file your bugs in the 'Gentoo Linux' category next time. (In reply to comment #1) > Please read the instructions and file your bugs in the 'Gentoo Linux' category > next time. I thought I marked Product: Gentoo Linux. Sorry, I will try my best next time Please don't add the x86 alias yourself. We do arch-testing, bug fixing is for maintainers. Please post the output of `emerge -vpq kde-base/kdm' too. (In reply to comment #4) > Please post the output of `emerge -vpq kde-base/kdm' too. # emerge -vpq kde-base/kdm [ebuild R ] kde-base/kdm-4.6.3 USE="(consolekit) handbook pam (-aqua) -debug (-kdeenablefinal) (-kdeprefix) -kerberos" Sorry for delay. I may have found the reason, why: In "/etc/rc.conf" set "rc_start_wait = 100" => start-stop-daemon: did not create a valid pid in `/var/run/ConsoleKit/pid' Commenting this line out: => no more false error-messages Setting "rc_start_wait = 500" => also no more false error-messages I have tried only consolekit so far, but I think it might help with kdm also. ;) (In reply to comment #6) > I may have found the reason, why: > > In "/etc/rc.conf" set "rc_start_wait = 100" > => start-stop-daemon: did not create a valid pid in `/var/run/ConsoleKit/pid' > > Commenting this line out: > => no more false error-messages > > Setting "rc_start_wait = 500" > => also no more false error-messages > > I have tried only consolekit so far, but I think it might help with kdm also. > ;) That helps to avoid ERROR messages! However, KDE works inappropriate... I have two KDM processes. And I can not run programs... I got message "KDEInit can not start "/usr/bin/ksysguard".: Unable to create new processes. System may reach maximum possible number of processes possible or the maximum number of processes that you are allowed to use has been reached" This looks openrc-related... What's your current kde version, and do you still have this problem? it's working for me with kde-base/kdm-4.6.3 and sys-apps/openrc-0.9.3 # cat /var/run/kdm.pid 4164 # ls -l /proc/4164/exe lrwxrwxrwx 1 root root 0 Sep 17 01:23 /proc/4164/exe -> /usr/bin/kdm rc_start_wait is not set by default. If you enable/set it then you have to deal with the consequences. Removing openrc from CC... Works for me with kde-base/kdm-4.7.2 and sys-apps/openrc-0.9.3-r1 OK by consent of the last posts resolving as WORKSFORME, missing feedback. If you still have this problem with latest kde-4.7.3 please reopen. Sorry for having posted a "wrong solution". I don't want to violate this closed bug too much, but I want to excuse and share my experience: (In reference to comment #6) > ... > In "/etc/rc.conf" set "rc_start_wait = 100" > => start-stop-daemon: did not create a valid pid in `/var/run/ConsoleKit/pid' > > Commenting this line out: > => no more false error-messages > > Setting "rc_start_wait = 500" > => also no more false error-messages I've been using a wait-time of 500 for half a year now. But since my last "emerge world" I get those false warnings again. => 500 still seems to be too little. Or as Christian Ruppert (idl0r) said in comment #11: > rc_start_wait is not set by default. If you enable/set it then you have to deal with the consequences. => I commented "rc_start_wait" out and everything works fine again. So my advice (reason for this post): The option "rc_start_wait" looked usefull at first glance, but caused only trouble to me. So keep it off. Maybe a warning about "possible false error messages" should be added to the comments for "rc_start_wait" in "rc.conf". |
