[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: Konsole 1.4.2 krippled by default PATH variable
From:       Dave Feustel <dfeustel () verizon ! net>
Date:       2005-08-23 19:39:02
Message-ID: 200508231439.02457.dfeustel () verizon ! net
[Download RAW message or body]

CORRECTION:
This morning I stopped using xdm as a graphical login manager.
Now ksh running in konsole works as documented.
It looks like xdm changes kde and konsole initiallization.
The reason I was using xdm instead of kdm is that login on OpenBSD
doesn't succeed when kdm is running. It has been written that kdm
does not understand BSD=stype authorization. But using xdm
was causing enough other problems that I went back to just
logging in and starting kde manually. For me, kde works better
when I start it up manually.

On Tuesday 23 August 2005 14:29, Dave Feustel wrote:
> On Tuesday 23 August 2005 13:58, James Richard Tyrer wrote:
> > Every time the shell is evoked the script: "~/.kshrc" is run.
> This does not happen on OpenBSD 3.7 running KDE 3.3.2.
> How do I know? The first line of .kshrc is "set -o vi"
> If this statement is executed, then pressing esc k brings up
> the previous command. This does not happen. This not happening
>  is what led me into this tarpit.
> 
> -- 
> 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!!!
> 

-- 
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!!!
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability

[prev in list] [next in list] [prev in thread] [next in thread]