Ubuntu
bash package

Foreground ('fg') fails to resume stopped processes intermittently

Bug #175740 reported by Aaron Mitti
8
Affects Status Importance Assigned to Milestone
bash (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: bash

I think this fails for any appilcation, but has bit me most frequently with VIM.

 1) run vim
 2) control-z to background
 3) fg to foreground (might fail to actually complete, nothing happens, job shows as failed)

* If step three works, repeat step 2 until it fails. This fails for me with random frequency, at least once every 10 times, usually much more. When it does fail to foreground, you can control-z again, and fg again and it usually works on the first attempt.

I fixed this issue on my machine by downgrading from bash 3.2-0ubuntu11 (in Gutsy) to 3.2-0ubuntu7 (from Feisty).

Revision history for this message
Aaron Mitti (aaronmitti) wrote :

I was wrong, problem still persists after downgrade to Feisty package. Any ideas?

Revision history for this message
Dominique Pellé (dominique-pelle) wrote :

Do you use tabs in the gnome-terminal? I saw the following bug in vim which looks a tad similar (but not sure):

https://bugs.launchpad.net/ubuntu/+source/vim/+bug/129106

Bug #129106 is fixed by the way in recent patch 166 of vim-7.1 (which is not in Ubuntu yet as far as I know)

Revision history for this message
Aaron Mitti (aaronmitti) wrote :

Dominiko,

I am using gnome-terminal with tabs, however I was able to replicate the issue from another machine entirely when sshing into my box, and that machine was using xterm.

FYI, I've now tried to downgrade the vim* packages to the Feisty packages (which worked fine for me when I ran Feisty), but no luck there either. To eliminate any possible vim issues I removed my .vimrc, and I even tried another user account entirely on my box with no luck.

Also interesting, two other guys in my office are also running Gutsy, cannot replicate this problem on their machines, but when sshing into mine can get it within a few tries.

-Aaron

Revision history for this message
Aaron Mitti (aaronmitti) wrote :

Also, when using zsh I can't replicate this issue under the same conditions. I don't think it's anything in my .bash_rc since I've had other users have the same problem on my box.

-Aaron

Revision history for this message
Matthias Klose (doko) wrote :

please rename your .bashrc and try to reproduce.

Changed in bash:
status: New → Incomplete
Revision history for this message
Aaron Mitti (aaronmitti) wrote :

I move my .bashrc, .bash_profile and the /etc/bash.bashrc files out of the way, the bahavior is still the same.

Thanks,
-Aaron

Revision history for this message
Aaron Mitti (aaronmitti) wrote :

This is still broken. I guess I'll update to Hardy and report back.

-Aaron

Revision history for this message
Mika Fischer (zoop) wrote :

Aaron,

I cannot reproduce this in Hardy. Do you still have the problem? If yes, can you try to describe the steps to reproduce the bug as detailed as possible? Just starting vim and the repeatedly suspending with CTRL-Z and foregrounding with fg<CR> does not trigger the bug for me...

Thanks,
 Mika

Revision history for this message
Aaron Mitti (aaronmitti) wrote :

I just upgraded to Hardy and I'm no longer having the issue, closing bug report.

Changed in bash:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.