Re: startkde question
El mar, 23-08-2005 a las 08:48 -0500, Dave Feustel escribis: When I start kde via startkde after login, an instance of xconsole isalso started. This instance doesn't seem to be started in kdeinit. Where is it started from? I haven't a X installation at hand (I have only obsd acting as server here), but trying with google I got: http://archives.neohapsis.com/archives/openbsd/2004-01/0493.html Google has better memory than me. It may help you. regards, Juanjo -- Desarrollo y sistemas: http://www.usebox.net/ Pagina Personal: http://www.usebox.net/jjm/
Re: startkde question
On Tuesday 23 August 2005 09:12, Antoine Jacoutot wrote: Dave Feustel wrote: When I start kde via startkde after login, an instance of xconsole isalso started. This instance doesn't seem to be started in kdeinit. Where is it started from? Well, if you use an graphical login manager, I would say it might comes from this file : /etc/X11/xdm/Xsetup_0 As of about an hour ago, I stopped using xdm. -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: startkde question
Am Dienstag, 23. August 2005 15:48 schrieb Dave Feustel: When I start kde via startkde after login, an instance of xconsole isalso started. This instance doesn't seem to be started in kdeinit. Where is it started from? Is is mentioned in your ~/.xinitrc file? Regards, Stephan
Re: startkde question
On Tuesday 23 August 2005 09:50, Stephan Tesch wrote: Am Dienstag, 23. August 2005 15:48 schrieb Dave Feustel: When I start kde via startkde after login, an instance of xconsole isalso started. This instance doesn't seem to be started in kdeinit. Where is it started from? Is is mentioned in your ~/.xinitrc file? Regards, Stephan I don't have an .xinitrc. I run startkde from the command line after login. -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: startkde question
Dave Feustel wrote: I don't have an .xinitrc. I run startkde from the command line after login. Then add a .xinitrc in your homedir with the following line : exec startkde ... then launch startx. Antoine
Re: startkde question
On Tuesday 23 August 2005 11:43, Antoine Jacoutot wrote: Dave Feustel wrote: I don't have an .xinitrc. I run startkde from the command line after login. Then add a .xinitrc in your homedir with the following line : exec startkde ... then launch startx. I forget. What was the question? Oh. Yes. It was Where does the xconsole get invoked when I start kde using startkde?. Just trying to get back to the original (as yet unanswered) question. Antoine -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: startkde question
Dave Feustel wrote: Oh. Yes. It was Where does the xconsole get invoked when I start kde using startkde?. Because startkde is a script that will invoke startx which will by default (meaning if you don't have a .xinitrc in your homedir) use /etc/X11/xinit/xinitrc where xconsole is started from.
Re: startkde question
On Tue, Aug 23, 2005 at 08:52:40PM +0200, Antoine Jacoutot wrote: Because startkde is a script that will invoke startx which will by default (meaning if you don't have a .xinitrc in your homedir) use /etc/X11/xinit/xinitrc where xconsole is started from. startkde does exec /usr/X11R6/bin/startx $0 if DISPLAY is unset or empty, i.e. it runs startx with it's own name as the client, and startx shouldn't run xinitrc but startkde in this case. Indeed after looking at startx (which is a script, too), it should just run xinit /usr/local/bin/startkde -- near the end, and xinit in turn should then use /usr/local/bin/startkde as the client program (and not ~/.xinitrc or even /etc/X11/xinit/xinitrc). However, this *only* works if the client (startkde, in this case) is passed with a absolute or relative pathname (see that case statement in startx). So, if startkde is explicitely invoked as /usr/local/bin/startkde (instead of just startkde), it should work. Ciao, Kili
Re: startkde question
Selon Dave Feustel [EMAIL PROTECTED]: My problem is that xconsole starts running with kde and I cannot figure out where from it is started. I've tried grepping for xconsole and get no hits in my home directory. Please try to read the answers people give you. It is started from /etc/X11/xinit/xinitrc
Re: startkde question
On Tuesday 23 August 2005 14:58, Antoine Jacoutot wrote: Selon Dave Feustel [EMAIL PROTECTED]: My problem is that xconsole starts running with kde and I cannot figure out where from it is started. I've tried grepping for xconsole and get no hits in my home directory. Please try to read the answers people give you. It is started from /etc/X11/xinit/xinitrc OK. There is an xterm and a clock started from /etc/X11/xinit/xinitrc as well. Neither of those programs shows up on the kde screen where the xconsole is. Why not? But thanks for sticking with me. Dave -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: startkde question
On Tuesday 23 August 2005 14:31, Matthias Kilian wrote: On Tue, Aug 23, 2005 at 08:52:40PM +0200, Antoine Jacoutot wrote: Because startkde is a script that will invoke startx which will by default (meaning if you don't have a .xinitrc in your homedir) use /etc/X11/xinit/xinitrc where xconsole is started from. startkde does exec /usr/X11R6/bin/startx $0 if DISPLAY is unset or empty, i.e. it runs startx with it's own name as the client, and startx shouldn't run xinitrc but startkde in this case. Indeed after looking at startx (which is a script, too), it should just run xinit /usr/local/bin/startkde -- near the end, and xinit in turn should then use /usr/local/bin/startkde as the client program (and not ~/.xinitrc or even /etc/X11/xinit/xinitrc). However, this *only* works if the client (startkde, in this case) is passed with a absolute or relative pathname (see that case statement in startx). So, if startkde is explicitely invoked as /usr/local/bin/startkde (instead of just startkde), it should work. Ciao, Kili This post is a keeper! :-) Thanks! Dave -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
