I agree, it does look as if it still fails in a similar manner in the
case you strace'd. Perhaps the fix above works, but there's a race
condition where the checks don't always work.
--
bogus background command often causes shell to exit
https://bugs.launchpad.net/bugs/127399
You received this
I can still reproduce this bug with Ubuntu-9.10 Karmic (tested in a xterm).
It happens rarely but I managed to reproduce it at least twice.
I happens more often if I run it strace.
I ran...
$ strace -s 3000 -f -o /tmp/trace-xterm xterm
And in the xterm, I ran the non existing command:
$ foobar
I can't reproduce your symptoms on 9.10. For me, the original problem
is fixed; I no longer see the strace output I quoted above. Your need
to chdir away from your home directory is probably pertinent. I'd
suggest investigating that and perhaps using "strace -p -s
3000 -f -o /tmp/st" in anothe
Anyone reading this? Should I open a new bug? (Not sure about the
correct policy for bugs that are already marked as resolved.)
Anyway, an update: the fix in comment #6 of
https://bugzilla.novell.com/show_bug.cgi?id=470844 (with the paths to
command-non-found suitably adapted) works for me. At lea
I can confirm that this bug still exists in karmic.
Here's how I can reproduce it 80% of the time:
=
helm...@alfons:~$ bash && echo bash is done
helm...@alfons:~$ cd tmp/
helm...@alfons:~/tmp$ rubbish &
[1] 26946
helm...@alfons:~/tmp$ exit
bash i
** Package changed: command-not-found (Ubuntu) => bash (Ubuntu)
** Changed in: bash (Ubuntu)
Status: In Progress => Fix Released
--
bogus background command often causes shell to exit
https://bugs.launchpad.net/bugs/127399
You received this bug notification because you are a member of Ubu
** Changed in: command-not-found (Ubuntu)
Status: Confirmed => In Progress
** Changed in: command-not-found (Ubuntu)
Milestone: None => karmic-alpha-3
** Changed in: command-not-found (Ubuntu)
Assignee: (unassigned) => Michael Vogt (mvo)
--
bogus background command often causes
see https://bugzilla.novell.com/show_bug.cgi?id=470844
there is a fix for this bug
--
bogus background command often causes shell to exit
https://bugs.launchpad.net/bugs/127399
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
No, it isn't specifically to do with Python. See my comment above where
read(2) on stdin returns EIO; I think that's a route to tracking it
down.
--
bogus background command often causes shell to exit
https://bugs.launchpad.net/bugs/127399
You received this bug notification because you are a me
Update: this has nothing to do with python.
If I put
command_not_found_handle() {
ls
}
into /etc/bash_command_not_found or something similar.
And run
foobar &
bash will crash also (from time to time).
When handler contains only bash internals (echo ...), the crashes won't
happen. This ha
We created own implementation of command-not-found for SUSE and have the
same problem. So it is not Ubuntu specific, but it is broken somewhere
between command-not-found handler and python script.
--
bogus background command often causes shell to exit
https://bugs.launchpad.net/bugs/127399
You re
I get this with Hardy too. I strace'd the bash running in another
window. Here are some selected highlights after entering `sfkjsfskfjsd
&'.
write(2, "[1] 22001\n", 10) = 10
write(1, "\33]0;[EMAIL PROTECTED]: ~\7", 19) = 19
write(2, "$ ", 2) = 2
I still observe this bug after upgrade to Hardy.
--
bogus background command often causes shell to exit
https://bugs.launchpad.net/bugs/127399
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
I still observe this bug after upgrade to Gutsy.
--
bogus background command often causes shell to exit
https://bugs.launchpad.net/bugs/127399
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Bash is not using python but python is invoked from bash's
command_not_found handler (command-not-found is obviously implemented in
python). This may be a python issue of some sort but is still does not
explain why bash is exiting.
--
bogus background command often causes shell to exit
https://bu
I can also reproduce this bug fairly easily after a couple of tries on
my feisty laptop.
I tried to run bash within valgrind memory checker and it detects
several errors:
I run a bash with:
$ valgrind --trace-children=yes bash
... then try to run a non existing command in background and get sev
This is really strange. Thanks for reporting - I will look into it
** Changed in: command-not-found (Ubuntu)
Importance: Undecided => Medium
Status: New => Confirmed
--
bogus background command often causes shell to exit
https://bugs.launchpad.net/bugs/127399
You received this bug noti
> result: shell exists
er, shell _exits_ rather
--
bogus background command often causes shell to exit
https://bugs.launchpad.net/bugs/127399
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
18 matches
Mail list logo
