I found out that though the bug is pretty reproducible on long path lengths,
for short path lengths, the bug is sometimes reproducible, but sometimes not.
Test case:
1. Open an xterm with a bash.
2. Make sure that the command q is not present on your system.
3. cd / [Enter]
4. q [Enter]
The bug does not occur on Debian with
bash version 4.2+dfsg-0.1+deb7u3,
xterm version 278-4
and the de_DE.utf8 LANG and LC_... .
So, whoever has a chance to look for the error, take the diff...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I confirm the bug presence on Ubuntu Precise + some upstream packages.
bash version: 4.2-2ubuntu2.1
It is 100% repeatable and terribly annoying.
It is dependent on the path length. How to reproduce on my system:
1. Make sure that you have
Good catch. I confirm that path length does seem to be an issue here.
This bug has been around since 2008 now -- it's very annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/241331
Title:
It seems this has reappeared after some absence. Don't know if bash is
at fault. Anyway, in an xterm or gnome-terminal, typing
made_up_command
Will often but not always cause the terminal to vanish which is
extremely annoying!
--
You received this bug notification because you are a member
I just ran into this bug and there seems to be a path-name dependency on
it showing up. In some directories it happens consistently, making it a
real annoyance. If it is in fact dependent on the length of a pathname,
or the form of a directory name, that might be useful in locating the
cause.
This seems to not happen in later versions of Ubuntu. I guess it got
patched.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/241331
Title:
Running a non-existing command in the background causes
The same happends to me in Konsole (Kubuntu 10.4 alpha, Konsole 2.4.1,
GNU bash version 4.1.0(1)-release)
--
Running a non-existing command in the background causes exit
https://bugs.launchpad.net/bugs/241331
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sort of to my surprise, I managed to reproduce this. I entered does not
exist at the bash prompt, and the shell exited. On opening a new
Gnome terminal, I was quite surprised to find that that line made it
into my bash history (which suggests it's a fairly clean exit). I had
another succes with
I had a look at the bash code that handles this, but there's so much
conditional forking and all... really way over my head for now.
As a guidance for setting the importance of this bug (to whomever is
allowed to do that), I'd say it is of low importance. I just played
around a bit in gdb, and
Sorry: clarification to the file just appended with the previous comment:
I didn't type the line that says exit, it appears as a result of trying cats
. This is the manifestation of the bug...
--
Running a non-existing command in the background causes exit
I confirm.
When you try using xterm - it behaves alike, however it more frequently works
without crash - it prints new pid and after a while it prints bash: gdit:
command not found. It does not return to prompt - you need to press enter and
then it prints Exit 127.
Here:
gdit
[1] 6733
Sorry -- looking further I think this may be an issue with
command_not_found_handler not gnome-terminal at all.
--
Running a non-existing command in the background causes exit
https://bugs.launchpad.net/bugs/241331
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: bash (Ubuntu)
Sourcepackagename: gnome-terminal = bash
--
Running a non-existing command in the background causes exit
https://bugs.launchpad.net/bugs/241331
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
14 matches
Mail list logo
