Hi,
I thought Lucid was working fine until this morning. I needed to change
permissions on a partition and launched Konsole to do it through bash.
Unfortunately, after about 30 secs or so of waiting, all I got was an empty
Konsole Window with a message in big red letters to say that it was un
On Sun, 16 May 2010 10:38:34 +0100, Terry Coles
wrote:
> From this, I suspect that the problem isn't anything to do with bash,
> but with whatever it is that makes the link between Konsole and bash.
The first thing I would try is checking what shell is being fired up by
the other terminal
On Sun, 2010-05-16 at 10:38 +0100, Terry Coles wrote:
> Hi,
>
> I thought Lucid was working fine until this morning. I needed to change
> permissions on a partition and launched Konsole to do it through bash.
> Unfortunately, after about 30 secs or so of waiting, all I got was an empty
> Kons
On Sunday 16 May 2010, Robert Bronsdon wrote:
> The first thing I would try is checking what shell is being fired up by
> the other terminal emulator. Just run 'ps' in a session that is not doing
> anything and you will usually see two entries.
>
> An example:
> $ ps
>PID TTY TIME CMD
On Sun, 16 May 2010 11:09:26 +0100, Terry Coles
wrote:
> I'm not sure I understand this; are you suggesting that bash might be
> locked? I thought you could run as many instances of bash as you wanted?
Correct - I was implying that you may not have been using bash on the
virtual console. Y
Hi Terry,
> I thought Lucid was working fine until this morning. I needed to
> change permissions on a partition and launched Konsole to do it
> through bash. Unfortunately, after about 30 secs or so of waiting,
> all I got was an empty Konsole Window with a message in big red
> letters to say
Would you believe that Konsole is now working normally, but I didn't find out
until I got to the end of the process. I'm going to send this anyway, because
I have some related queries along the way and the answers would be useful for
future reference.
On Sunday 16 May 2010, Ralph Corderoy wrot
Hi Terry,
> > could try running `konsole' in that to see if any messages give a
> > clue.
>
> Well I got Konsole up and running with some errors being logged. I
> can't work out how to capture the messages to put them here. There is
> quite a bit.
If you're running a command, e.g. ls(1), then
On Sunday 16 May 2010, Ralph Corderoy wrote:
> > Well I got Konsole up and running with some errors being logged. I
> > can't work out how to capture the messages to put them here. There is
> > quite a bit.
.
.
.
.
> bash provides a short-cut,
>
> ls foo nonexist &>foo
I knew there was a wa
9 matches
Mail list logo