Re: Brain dead question!
On Sunday 17 December 2000 10:50, Nick wrote: Sorry to ask such a newbie question, but how do I get KDE to start as the default system window manager? It's been working fine for weeks, and then after an upgrade a few days ago it has gone back to a blank grey twm desktop when I log in ... :-( Same thing happened here. Ivan, is that an oops? What I did was remove the symlink /etc/alternatives/x-window-manager which pointed to twm, and make one which pointed to /usr/bin/startkde. -- Bud Rogers [EMAIL PROTECTED] http://www.sirinet.net/~budr/zamm.html All things in moderation. And not too much moderation either.
Re: Brain dead question!
On Sun, 17 Dec 2000, Nick wrote: Sorry to ask such a newbie question, but how do I get KDE to start as the default system window manager? It's been working fine for weeks, and then after an upgrade a few days ago it has gone back to a blank grey twm desktop when I log in ... :-( I just have exec startkde in my ~/.xsession Bart
Re: Brain dead question!
On Sun 17 Dec, Ivan E. Moore II wrote: If your using startx you need to manually add kde2 to your alternatives update-alternatives --install /usr/bin/x-window-manager x-window-manager /usr/bin/kde2 the package will not do that anymore as it's against policy...we are working on getting a x-session-manager setup... update-alternatives 1.6.15 (potato) needs a 'priority' argument as well - I chose 50 and it all works lovely again :-) update-alternatives --install /usr/bin/x-window-manager x-window-manager /usr/bin/kde2 50 Thanks -- Nick Smith, Webmaster, Climbers.Net UK. http://www.climbers.net/ Low-cost Internet services for the climbing and outdoor pursuits industry
Re: Brain dead question!
update-alternatives 1.6.15 (potato) needs a 'priority' argument as well - I chose 50 and it all works lovely again :-) update-alternatives --install /usr/bin/x-window-manager x-window-manager /usr/bin/kde2 50 oops...yea..forgot to finish the line out. :) -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
Re: Brain dead question!
On Sun, 17 Dec 2000, Ivan E. Moore II wrote: if you use kdm just log in using kde2 ..dont' use default. (this is just a tip: I'm sure Ivan already knows this ...) unless you want to have your ~/.xsession executed: then you _have_ to use default; important if you want to have some environment variables set up at startup. kdm's shutdown button works properly now by the way. And what's that? kdm's configuration panel suddenly has some convenience settings: Enable automatic login, truly automatic login, enable password-less logins, show previous user. Hmm. Reminds me of something else ;-) I'll still have to check out kdm's chooser: it seems to be quite broken at this time: chooser BROADCAST works for xdm's chooser, but for kdm's chooser it says: chooser: Unexpected argument 'BROADCAST'. chooser: Use --help to get a list of available command line options. and the --help does not help: gives generic qt and kde options. Is there a way to avoid this, or should I just drop in xdm's chooser. I might just do a bug report for kdm at kde. I could have sworn I had explained this several times already. Yes you have. Bart
Re: Brain dead question!
hmmm kdm should tag the /etc/X11/Xsession file for all chosen options... it seems to be doing it in part at least (I don't use a .xsession file so I have no clue)... because it is using the .xsession-errors file for logging. the Xsession file is supposed to be what actually launches the wm..which is what also tags the users .xsession (and other) files...so if it's not tagging those files than something whacky is wrong... Ivan -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
Re: Brain dead question!
Bart, Or anyone for that matter - can you suggest a site for reading up on what kdm/xdm does. Why one would load this. what it does, what it's for etc. I have never had a firm understanding of any of it and I would like to learn much more about it, but never found any place to learn about it. The books I have don't talk about them at all. Thank you. On Sunday 17 December 2000 09:41, Bart Oldeman wrote: On Sun, 17 Dec 2000, Ivan E. Moore II wrote: if you use kdm just log in using kde2 ..dont' use default. (this is just a tip: I'm sure Ivan already knows this ...) unless you want to have your ~/.xsession executed: then you _have_ to use default; important if you want to have some environment variables set up at startup. kdm's shutdown button works properly now by the way. And what's that? kdm's configuration panel suddenly has some convenience settings: Enable automatic login, truly automatic login, enable password-less logins, show previous user. Hmm. Reminds me of something else ;-) I'll still have to check out kdm's chooser: it seems to be quite broken at this time: chooser BROADCAST works for xdm's chooser, but for kdm's chooser it says: chooser: Unexpected argument 'BROADCAST'. chooser: Use --help to get a list of available command line options. and the --help does not help: gives generic qt and kde options. Is there a way to avoid this, or should I just drop in xdm's chooser. I might just do a bug report for kdm at kde. I could have sworn I had explained this several times already. Yes you have. Bart -- Jaye Inabnit, ARS ke6sls e-mail: [EMAIL PROTECTED] 707-442-6579 h/m 707-441-7096 p http://www.qsl.net/ke6slsICQ# 12741145 This mail composed with kmail on kde on X on linux warped by debian If it's stupid, but works, it ain't stupid.
Re: Brain dead question!
On Sun, 17 Dec 2000, Ivan E. Moore II wrote: hmmm kdm should tag the /etc/X11/Xsession file for all chosen options... it seems to be doing it in part at least (I don't use a .xsession file so I have no clue)... because it is using the .xsession-errors file for logging. the Xsession file is supposed to be what actually launches the wm..which is what also tags the users .xsession (and other) files...so if it's not tagging those files than something whacky is wrong... It is indeed executing /etc/X11/Xsession for all chosen options, but from looking at the script my understanding is that $startup (later $real-startup) has the following value: kdm option kde2: kde2 kdm option default: $HOME/.xsession kdm option failsafe: x-terminal-emulator only $startup is executed: if it's kde2, $HOME/.xsession is not executed. Now if such a file (`which kde2` or $HOME/.xsession) does not exist it tries to execute x-window-manager and if that does not exist it executes x-terminal-emulator and if that does not exist it complains. Bart
Re: Brain dead question!
On Sun, 17 Dec 2000, Jaye Inabnit ke6sls wrote: Or anyone for that matter - can you suggest a site for reading up on what kdm/xdm does. Why one would load this. what it does, what it's for etc. I have never had a firm understanding of any of it and I would like to learn much more about it, but never found any place to learn about it. The books I have don't talk about them at all. no not really, but take a look at http://www.linuxgazette.com/issue27/kaszeta.html for some examples and the XWindow-User-HOWTO for a basic explanation and of course there's man xdm. The part which I find hardest to understand is the network part, so let's give that a try: Let's have two hosts: workstation server hostA --- hostB Let's say that hostA and hostB both run xdm: hostA runs xdmA and hostB runs xdmB. hostA is going to run an X server. host B does not need to. Now of course in terms of X, A is the server and B is the client. Normally xdm on A will start the X server on A, present a login screen, let the user login and executes /etc/X11/Xsession. But you can also run (also without xdm running on hostA) X -indirect hostB or X -query hostB on hostA to connect to the xdm running on hostB. Then hostB will present its login screen (can be Solaris or anything else X). And from there on your using your computer A as an X terminal: all programs run on B but screen/keyboard input/output is done by the X server on A. Now instead of presenting a login screen straight away you can also instruct xdm in /etc/X11/xdm/Xaccess to bring up a chooser screen listing the hosts. If both hostA and hostB are running xdm and give access at that point it will list hostA hostB the the user can choose one of these, and the xdm on the chosen host presents its login screen. Note that you can either have the chooser from hostA or the chooser from hostB. all similar for kdm. That's what I understand of it. Bart
