| 1 |
Liu Chuan posted <19f373bf05082622587a2f8410@××××××××××.com>, excerpted |
| 2 |
below, on Sat, 27 Aug 2005 13:58:20 +0800: |
| 3 |
|
| 4 |
> After installing kde through "emerge kdebase-meta" and test with |
| 5 |
> "startx" of no problem, I add xdm to default runlevel with modifying |
| 6 |
> display manager to kdm in "rc.conf". However when I reboot the |
| 7 |
> computer, the screen turn black for a second and then up without kdm |
| 8 |
> start. The log file only contain following info about kdm: |
| 9 |
> |
| 10 |
> kdm[5526]: x server for display: 0 terminated unexpectedly |
| 11 |
> kdm[5526]: unknow session exit code 0 (sig 9) from manager process |
| 12 |
> |
| 13 |
> "ps -ef" show kdm[5526] are still running. |
| 14 |
> However when I del xdm from default runlevel or kill 5526 then type: |
| 15 |
> /etc/init.d/xdm start |
| 16 |
> the kdm just turn out to run smoothly. |
| 17 |
> |
| 18 |
> Start with default xdm in rc.conf also had no problem. |
| 19 |
> It is so strange that there is no problem to start kdm after login |
| 20 |
> from command line, and only to fail at start-up in default runlevel. |
| 21 |
> |
| 22 |
> Any idea about the problem appreciated. |
| 23 |
> Actually I want to know what is the difference between running |
| 24 |
> "/etc/init.d/script start" and running from default level. |
| 25 |
|
| 26 |
This could very likely be a real-world example of something that came up |
| 27 |
on the dev list recently. As currently implemented, stuff started from a |
| 28 |
runlevel doesn't get the normal environment that something started from |
| 29 |
the command line will inherit. There was at least one other bug relating |
| 30 |
to this as discussed in that thread, tho I don't remember what the package |
| 31 |
was. |
| 32 |
|
| 33 |
In any case, everyone in the discussion agreed that the environments |
| 34 |
should /not/ differ if an init.d script is run directly from the command |
| 35 |
line, and that the start-stop daemon or init script /should/ clear the |
| 36 |
environment of anything it wouldn't have if started by the runlevel, to |
| 37 |
avoid exactly this type of issue with varying behavior one way as opposed |
| 38 |
to the other. |
| 39 |
|
| 40 |
Therefore, if the KDE guys don't step in and say something different |
| 41 |
within a day or two, I'd suggest filing a bug on it. Meanwhile, you can |
| 42 |
take a look at your exported environment and start whiddling down the |
| 43 |
candidates. Perhaps it'd be useful to try clearing the (exported) |
| 44 |
environment altogether, then trying to invoke the xdm init script, to see |
| 45 |
if it still works that way or not. If this /is/ the issue, it should then |
| 46 |
fail from the command line as well, and you can start the whiddling |
| 47 |
process on the exported environment you normally run. If it doesn't fail |
| 48 |
with an empty exported environment, then it's some other factor, but I'm |
| 49 |
guessing it will. Of course, mentioning your findings on the bug when you |
| 50 |
file it should be helpful, as well. |
| 51 |
|
| 52 |
-- |
| 53 |
Duncan - List replies preferred. No HTML msgs. |
| 54 |
"Every nonfree program has a lord, a master -- |
| 55 |
and if you use the program, he is your master." Richard Stallman in |
| 56 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
| 57 |
|
| 58 |
|
| 59 |
-- |
| 60 |
gentoo-desktop@g.o mailing list |
Archives