Bug 150259 - CTRL-Z in bash causes next command in && expression to proceed
Summary: CTRL-Z in bash causes next command in && expression to proceed
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: unspecified
Hardware: i686 SuSE Linux 10.0
: P5 - None : Major
Target Milestone: ---
Assignee: Dr. Werner Fink
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-12 22:18 UTC by Archie Cobbs
Modified: 2006-02-13 15:30 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Archie Cobbs 2006-02-12 22:18:45 UTC 
In bash, run a command like "command1 && command2". Then press CTRL-Z
while command1 is running. command1 will pause as it's supposed to,
but then also command2 will start, even though command1 is not 
finished yet and has not yet returned any exit value!

Here's a simple reproduction of the problem. In the below
script, I hit CTRL-Z a couple of seconds after the first
command was entered. Note the "foo" output was printed before
the full 5 seconds was up:

$ sleep 5 && echo foo

[1]+  Stopped                 sleep 5
foo
$ fg
sleep 5
$ uname -a
Linux lisa 2.6.13-15.7-default #1 Tue Nov 29 14:32:29 UTC 2005 i686 i686 i386 GNU/Linux
[archie@lisa] 1168 bash --version
GNU bash, version 3.00.16(1)-release (i586-suse-linux)
Copyright (C) 2004 Free Software Foundation, Inc.
Comment 1 Dr. Werner Fink 2006-02-13 11:43:18 UTC 
Q: Why is this major?  Beside this the new bash 3.1.5 used
   for the next release of SuSE Linux seems to be correct.
Comment 2 Dr. Werner Fink 2006-02-13 15:16:20 UTC 
Q: Why is this major?  Beside this the new bash 3.1.5 used
   for the next release of SuSE Linux seems to be correct.
Comment 3 Archie Cobbs 2006-02-13 15:26:06 UTC 
Not sure if this question is directed at me, but here goes..

I marked it major because to me it seems like a major bug.
But hey, I'm just just the guy reporting the problem, not
the guy fixing it, so change to whatever priority you like.

In any case, if this bug is already fixed in a later version
of SuSE (something I have no way of knowing since I'm using SuSE
10.0 at the moment) then I guess we're all done and you can
resolve the bug.

Thanks.
Comment 4 Dr. Werner Fink 2006-02-13 15:30:33 UTC 
fixed in next release