Re: include ~/bin in $PATH under kde on debian (sarge)

[John Stumbles]

Jon Dowland wrote:

At 1146072858 past the epoch, John Stumbles wrote:


On my system .[x|X]session doesn't exist by default, so
kde (or whatever is chosen at the start-session menu) is
getting started by some other mechanism.



Yes, KDM is calling startkde which in turn calls kdeinit.


Thanks. I have recently learned that, though I'm still trying to get my 
brain around what the various components do.



At the 'Start new session' option from the K menu the new
user has the option to choose the type of session (KDE,
Gnome etc) they want to run. I guess whatever is doing
this session management bypasses 'conventional' X session
startup methods.



What is the full range of options for type of session: there
should be an equivalent to gdm's "Default system session"
that executes $HOME/.xsession .


I have a menu of

Session Type
Remote Login
Console Login
Shutdown

Session Type -> submenu:
Default
Custom
GNOME
Failsafe

I can't see where that's configured (I've looked mainly in 
/etc/kde3/kdm/). In particular, I don't know what/where/how the 'Custom' 
Session Type is configured. I'm also in the dark about the 'Remote 
Login' option, and how 'Console Login' differs from Session Type -> 
Failsafe. (I haven't tried all the options: I'm still learning about 
Linux in general and Debian, KDE, KDM etc etc and there's so much to do, 
so little time to do it in :-()



John Stumbles


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: include ~/bin in $PATH under kde on debian (sarge)

[Felix C. Stegerman]

On 2006-04-26 16:41:47, Michael M. wrote:
> Felix C. Stegerman wrote:
> >
> >Since I use openbox + perlpanel + my_own_session_manager,
> >I just source my .bashrc in my .xinitrc.
> 
> Sorry, Felix, could you explain what you mean my "my own session 
> manager"? You mean something other than gdm, kdm, xdm or wdm?

No. I use GDM as Desktop Manager.
What I meant was that I don't use KDE/GNOME/whatever.

As I said (wrote), I use openbox + perlpanel.
But since I wanted an easy way to start some programs when I log in
(e.g. xscreensaver, xmodmap), I wrote a Perl script to do just that
based on an XML configuration file. It can even display a splash
screen similar to the one KDE uses. So what I meant was that I use my
Perl script in a similar way KDE and GNOME have their session managers
to load programs at startup.


Felix

-- 
Felix C. Stegerman <[EMAIL PROTECTED]>

"Any sufficiently advanced bug is indistinguishable from a feature."
 -- R. Kulawiec


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: include ~/bin in $PATH under kde on debian (sarge)

[Jon Dowland]

At 1146072858 past the epoch, John Stumbles wrote:
> On my system .[x|X]session doesn't exist by default, so
> kde (or whatever is chosen at the start-session menu) is
> getting started by some other mechanism.

Yes, KDM is calling startkde which in turn calls kdeinit.

> At the 'Start new session' option from the K menu the new
> user has the option to choose the type of session (KDE,
> Gnome etc) they want to run. I guess whatever is doing
> this session management bypasses 'conventional' X session
> startup methods.

What is the full range of options for type of session: there
should be an equivalent to gdm's "Default system session"
that executes $HOME/.xsession .

-- 
Jon Dowland
http://alcopop.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: include ~/bin in $PATH under kde on debian (sarge)

[Michael M.]

Felix C. Stegerman wrote:


Since I use openbox + perlpanel + my_own_session_manager,
I just source my .bashrc in my .xinitrc.


  


Sorry, Felix, could you explain what you mean my "my own session 
manager"? You mean something other than gdm, kdm, xdm or wdm?


--
Michael M. ++ Portland, OR ++ USA
"No live organism can continue for long to exist sanely under conditions of absolute 
reality; even larks and katydids are supposed, by some, to dream." --S. Jackson



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: include ~/bin in $PATH under kde on debian (sarge)

[Felix C. Stegerman]

> Aha! that works! Thanks.

You're welcome.

> Is that documented somewhere?
> I've looked at http://www.kde.org/documentation/ especially 
> http://www.kde.org/areas/sysadmin/, and http://docs.kde.org/

I found it out by reading (the comments in) /usr/bin/startkde,
but in unstable it's now documented in the man page for startkde.

> Of course it only works for kde. That's good enough for now since
> I only use kde but I'd like to know how to do it for gnome and
> other sessions.

Each DE has it's own startup scripts. So it's usually easier to start
KDE/GNOME/whatever from a customised .xsession / .xinitrc, especially
since KDE and GNOME don't seem to document this.

Since I use openbox + perlpanel + my_own_session_manager,
I just source my .bashrc in my .xinitrc.


Felix

-- 
Felix C. Stegerman <[EMAIL PROTECTED]>

"Any sufficiently advanced bug is indistinguishable from a feature."
 -- R. Kulawiec


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: include ~/bin in $PATH under kde on debian (sarge)

[John Stumbles]

Jon Dowland wrote:


It depends entirely on which session manager is used or
which method of starting your session. If you create a
~/.xsession script which execs "startkde" you could specify
the PATH before that and have it inherited by startkde and
all subsequent processes. You then would need to instruct
your display manager (KDM?) to execute this. With GDM, you
would choose "default system session". I don't have KDM
handy to check.

Example .xsession:

#!/bin/sh
export PATH=$HOME/bin:$PATH
startkde



On my system .[x|X]session doesn't exist by default, so kde (or whatever 
is chosen at the start-session menu) is getting started by some other 
mechanism. From my regular debian sarge installation I installed kdm so 
that I could have a user-friendly way for users to start a new session 
when an existing session is logged-in and locked. At the 'Start new 
session' option from the K menu the new user has the option to choose 
the type of session (KDE, Gnome etc) they want to run. I guess whatever 
is doing this session management bypasses 'conventional' X session 
startup methods.



The KDE sysadmin guide covers startup in this kind of
detail: .
KDM calls startkde which calls kdeinit which is the magic X
process and spawns most of everything else.


Thanks.

--
John Stumbles


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: include ~/bin in $PATH under kde on debian (sarge)

[John Stumbles]

Felix C. Stegerman wrote:


Try renaming `setpath' to `setpath.sh'.


Aha! that works! Thanks.
Is that documented somewhere?
I've looked at http://www.kde.org/documentation/ especially 
http://www.kde.org/areas/sysadmin/, and http://docs.kde.org/


Of course it only works for kde. That's good enough for now since I only 
use kde but I'd like to know how to do it for gnome and other sessions.


--
John Stumbles


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: include ~/bin in $PATH under kde on debian (sarge)

[Felix C. Stegerman]

On 2006-04-26 16:06:20, John Stumbles wrote:
> Felix C. Stegerman wrote:
> 
> >I personally use .xsession / .xinitrc to start a custom X session and
> >add ~/bin to my $PATH in there.
> >To do the same with GNOME, you can edit ~/.gnomerc.
> >To do the same with KDE, you can create a new executable file in
> >~/.kde/env and set $PATH in there.
> 
> Doesn't work for me. I created
> $ mkdir .kde/env
> $ lsl .kde/env/
> total 12
> drwxr-xr-x  2 bart bart 4096 Apr 26 15:56 .
> drwx--  5 bart bart 4096 Apr 26 15:54 ..
> -rwxr-xr-x  1 bart bart  170 Apr 26 15:56 setpath
> -rw-r--r--  1 bart bart0 Apr 26 15:56 setpath-20060426155614
> 
> $ cat .kde/env/setpath
> #!/bin/bash
> # set PATH so it includes user's private bin if it exists
> if [ -d ~/bin ] ; then
> PATH=~/bin:"${PATH}"
> fi
> touch ~/.kde/env/setpath-`date '+%Y%m%d%H%M%S'`
> 
> The tag file (setpath-20060426155614) was created by me running the 
> script manually after creating it. I then logged out of my kde session 
> and logged in again: no new tag file, no extension to $PATH

Try renaming `setpath' to `setpath.sh'.


Felix

-- 
Felix C. Stegerman <[EMAIL PROTECTED]>

"Any sufficiently advanced bug is indistinguishable from a feature."
 -- R. Kulawiec


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: include ~/bin in $PATH under kde on debian (sarge)

[Felix C. Stegerman]

On 2006-04-26 10:39:43, John Stumbles wrote:
> On kubuntu (and SuSE, IIRC) if I have a ~/bin directory it gets included
> in my $PATH but this doesn't happen under debian. (In all cases I'm
> using kde with kdm as my window manager.)
...
> I've googled www and usenet and searched debian lists but not found an
> answer to the question of setting the environment for my whole X
> session, not just for console session within X.

I personally use .xsession / .xinitrc to start a custom X session and
add ~/bin to my $PATH in there.
To do the same with GNOME, you can edit ~/.gnomerc.
To do the same with KDE, you can create a new executable file in
~/.kde/env and set $PATH in there.

> I would also like to understand what happens when a gui session starts
> under kdm - what scripts etc get run?

AFAIK: The X server runs some stuff in /etc/X11/Xsession.d and the
chosen desktop environment / session runs its own stuff. (like
~/.gnomrc or ~/.kde/env/*)


Felix

-- 
Felix C. Stegerman <[EMAIL PROTECTED]>

"Any sufficiently advanced bug is indistinguishable from a feature."
 -- R. Kulawiec


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: include ~/bin in $PATH under kde on debian (sarge)

[Liam O'Toole]

On Wed, 26 Apr 2006 12:41:36 +0100
Jon Dowland <[EMAIL PROTECTED]> wrote:

> At 1146047983 past the epoch, John Stumbles wrote:
> > I've googled www and usenet and searched debian lists but
> > not found an answer to the question of setting the
> > environment for my whole X session, not just for console
> > session within X.
> 
> It depends entirely on which session manager is used or
> which method of starting your session. If you create a
> ~/.xsession script which execs "startkde" you could specify
> the PATH before that and have it inherited by startkde and
> all subsequent processes. You then would need to instruct
> your display manager (KDM?) to execute this. With GDM, you
> would choose "default system session". I don't have KDM
> handy to check.
> 
> Example .xsession:
> 
>   #!/bin/sh
>   export PATH=$HOME/bin:$PATH
>   startkde
> 
> > I would also like to understand what happens when a gui
> > session starts under kdm - what scripts etc get run?
> 
> The KDE sysadmin guide covers startup in this kind of
> detail: .
> KDM calls startkde which calls kdeinit which is the magic X
> process and spawns most of everything else.
> 

I do it in a similar way:

~$ cat .Xsession 
#!/bin/sh --login
exec gnome-session

Here the "--login" option ensures that .bash_profile is read, so I get
the same environment regardless of how I log in.

-- 

Liam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: include ~/bin in $PATH under kde on debian (sarge)

[Jon Dowland]

At 1146047983 past the epoch, John Stumbles wrote:
> I've googled www and usenet and searched debian lists but
> not found an answer to the question of setting the
> environment for my whole X session, not just for console
> session within X.

It depends entirely on which session manager is used or
which method of starting your session. If you create a
~/.xsession script which execs "startkde" you could specify
the PATH before that and have it inherited by startkde and
all subsequent processes. You then would need to instruct
your display manager (KDM?) to execute this. With GDM, you
would choose "default system session". I don't have KDM
handy to check.

Example .xsession:

#!/bin/sh
export PATH=$HOME/bin:$PATH
startkde

> I would also like to understand what happens when a gui
> session starts under kdm - what scripts etc get run?

The KDE sysadmin guide covers startup in this kind of
detail: .
KDM calls startkde which calls kdeinit which is the magic X
process and spawns most of everything else.

-- 
Jon Dowland
http://alcopop.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]