Gentoo Archives: gentoo-amd64

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-amd64@l.g.o
Subject: [gentoo-amd64] Re: No kdm after 2005.0 upgrade
Date: Sat, 28 Jan 2006 11:44:12
Message-Id: pan.2006.01.28.11.42.12.672750@cox.net
In Reply to: [gentoo-amd64] No kdm after 2005.0 upgrade by Daiajo Tibdixious
1 Daiajo Tibdixious posted
2 <a4a9bfcb0601280121r303494fds74ebf107b9810280@××××××××××.com>, excerpted
3 below, on Sat, 28 Jan 2006 20:21:40 +1100:
4
5 > According to<br>
6 > <a
7 > href="http://www.gentoo.org/doc/en/kde-config.xml">http://www.gentoo.org/doc/en/kde-config.x</a><br>
8 > I only have to put DISPLAY_MANAGER=&quot;kdm&quot; in /etc/rc.conf,
9 > which I have done:<br>
10
11 First, please kill the HTML. Many on mailing lists, particularly FLOSS
12 community lists, consider HTML posts comparable to sliming your hand with
13 snot and then offering to shake hands -- it's both rude and a good way to
14 spread viruses!
15
16 > $ grep DISPLAY /etc/rc.conf
17 > DISPLAY_MANAGER="kdm" and have xdm in the startup:
18 > $ /sbin/rc-update show xdm default | grep xdm
19 > xdm | default
20 > and kdm should start.
21 >
22 > However, xdm starts instead of kdm.
23
24 Are you sure kdm is merged? Note that there's now two ways to merge KDE,
25 as the split packages (kde-base/kdm) or as the monolithic ebuilds
26 (kde-base/kdebase includes it, I believe). If you merge the split
27 ebuilds, it will be pulled in as a dependency in some cases (I don't use
28 it here but have it for that reason), but perhaps you don't have it, for
29 some reason.
30
31 If it's merged, will it start from the (root) command line? It has been
32 awhile since I ran any of the ?dm things, so don't know if it should or
33 not, but in any case, you should be able to trace how the initscript
34 should start it (trace thru the scripts), and do likewise, if it won't
35 start from the command line directly.
36
37 What about logging? Have you tried checking your logs to see if it says
38 anything there?
39
40 > I have tried setting XSESSION in /etc/rc.conf to various values, however
41 > these all give X with no login manager and no kde.
42
43 As I said, I haven't used ?dm in ages, but I DO run KDE, from the command
44 line, using the XSESSION settings you mention. It works here, and has
45 since at least sometime in the KDE 3.3.x timeframe if not earlier. I'm
46 running 3.5.0 (~amd64) now.
47
48 1) Set XSESSION to the version you have merged. Therefore, I have:
49
50 XSESSION="kde-3.5"
51
52 2) Start KDE by issuing the "startx" command at the command line.
53
54 3) Actually, I have a little script that starts it, then exits the
55 session:
56
57 $cat /usr/local/bin/k
58 #!/bin/bash
59
60 startx &
61 disown -a
62 sleep 30
63 exit 0
64
65 Of course, /usr/local/bin is in my path, so I start it like this:
66
67 . k
68
69 Of course, the dot indicates source the following script in the same
70 shell, and the & after startx runs that command in the background, so the
71 result is that X is started (with the assigned XSESSION, so KDE) then the
72 startx process disowned, a 30-second sleep to make sure things are going
73 OK, then it logs me out of the terminal.
74
75 If I'm troubleshooting something, I'll simply run k without sourcing it,
76 so it'll leave me logged in and I can continue what I was doing on the
77 command line.
78
79 > I had kdm running find under 2004.3, it stopped working when I upgraded
80 > to 2005.0 (as did many other things,
81 > everything is now fixed except this). I have to be missing something
82 > obvious, I can find no more in the documentation. I'm running kde 3.4.3
83 > I'm going to go thru the xdm startup to try to figure this out, which
84 > will take a while,
85 > I just wonder if anyone can spot the flaw straight away?
86
87 I gave up on ?dm back when I was on Mandrake. It quit working at some
88 point and I couldn't get it working right away, so I just left it and
89 began starting KDE directly from the command line. That worked, and soon
90 I decided I liked that better than the graphical login anyway,
91 particularly when I'm working from the command line anyway and don't want
92 to wait for X and KDE to come up (if it's not X or KDE that I'm
93 troubleshooting because they /won't/ come up). From my experience, it's
94 just a whole lot more robust to end up at the command line, than to try to
95 boot to X/KDE, and doing that from startx is more robust than ?dm, as
96 well. If I want KDE, I can then login and start it. There's nothing wrong
97 with ?dm. It's just not my preferred way of working any more.
98
99 --
100 Duncan - List replies preferred. No HTML msgs.
101 "Every nonfree program has a lord, a master --
102 and if you use the program, he is your master." Richard Stallman in
103 http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
104
105
106 --
107 gentoo-amd64@g.o mailing list