Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
On Thu, Feb 20, 2003 at 09:32:06AM -0500, Ken Gosier wrote: > So in the end, the decision was that some file in my home dir was causing > the problem. I had made some changes to my .bashrc lately. (I hadn't > mentioned this b/c the changes I made were pretty simple. duh. :-( ) But > after renaming to .bashrc.old, voila, kde starts again! So after > investigating the .bashrc file, it turns out the offending line was > (drumroll please...) > > set -o noclobber > > I'm a little worried that this now confirms my status as a Redhat luser. > :-/ But seriously, this seems strange to me that a simple thing like this > will cause kde so many problems. Am I just complaining, or should kde be > able to deal more gracefully with something like this? I would expect it to handle that situation, perhaps you should report it as a bug. In the meantime, does this work: # If running interactively, then: if [ "$PS1" ]; then set -o noclobber fi -- ~'`^`'~=-.,__,.-=~'`^`'~=-.,__,.-=~'`^`'~=-., \|/ (___) \|/ _,.-=~'`^` Brian Medley @~./'O o`\.~@ "Knowledge is Power" brian.medley at verizon.net /__( \___/ )__\ *PPPFFBT!* -- Francis Bacon `\__`U_/' _,.-=~'`^`'~=-.,__,.-=~'`^`'~=-.,__,.-=~'`^`'~= <____|' ^^`'~=-.,__,.-= ~`'^`'~=-.,__,.-=~'`^`'~=-.,__,.-=~'`^`'~=-.,__,.-==--^'~=-.,__,.-=~'`^`
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |