Bug 676838 - Bash freezes while two or more unknown commands are being executed
Summary: Bash freezes while two or more unknown commands are being executed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 14
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-11 13:46 UTC by Vojtech Vitek
Modified: 2015-03-04 23:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 15:16:03 UTC
Type: ---


Attachments (Terms of Use)

Description Vojtech Vitek 2011-02-11 13:46:25 UTC
Description of problem:
When I tried to run two (or more) unknown commands at the same time, PackageKit-command-not-found suddenly locked the bash.
Sometimes it could be interrupted, but sometimes the terminal was completely frozen.

Version-Release number of selected component (if applicable):
PackageKit-command-not-found-0.6.12-2.fc14.x86_64

How reproducible:
Almost every second attempt.

Steps to Reproduce:
1. Run bash with PackageKit-command-not-found enabled
2. Try to execute several non-existent commands in a row
  
Actual results:
$ whatever;whatever
bash: whatever: command not found...
<LOCKED HERE>
^C
$

$ ps -Al | grep pts/8
0 S  502 23786  9124  0  80  0 - 27860  wait   pts/8  00:00:00 bash
1 S  502 24003 23786  0  80  0 - 27860  wait   pts/8  00:00:00 bash
0 S  502 24004 24003  0  80  0 - 39117  poll_s pts/8  00:00:00 pk-command-not-

Expected results:
$ whatever;whatever
bash: whatever: command not found...
bash: whatever: command not found...
$

Comment 1 Vojtech Vitek 2011-02-11 13:57:14 UTC
Another test case (with freeze):

$ whatever|whatever|whatever;whatever
bash: whatever: command not found...
bash: whatever: command not found...
bash: whatever: command not found...

^C^C^C^C^C^C

^C^C^C^C

(after few minutes)

Getting the list of files failed: cannot-get-lock, Yum is locked by another application. The other process has the command line '/usr/bin/python /usr/share/PackageKit/helpers/yum/yumBackend.py search-file ~installed                                                             
newest
arch /usr/bin/whatever&/usr/sbin/whatever&/bin/whatever&/sbin/whatever' (PID 4451)
Getting the list of files failed: cannot-get-lock, Yum is locked by another application. The other process has the command line '/usr/bin/python /usr/share/PackageKit/helpers/yum/yumBackend.py search-file ~installed
newest
arch /usr/bin/whatever&/usr/sbin/whatever&/bin/whatever&/sbin/whatever' (PID 4451)


Meanwhile the lock:

# yum update
Loaded plugins: auto-update-debuginfo, downloadonly, fastestmirror, presto, priorities, refresh-packagekit
Existing lock /var/run/yum.pid: another copy is running as pid 4451.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: PackageKit
    Memory :  25 M RSS (704 MB VSZ)
    Started: Fri Feb 11 14:23:12 2011 - 04:21 ago
    State  : Sleeping, pid: 4451

Comment 2 Fedora End Of Life 2012-08-16 15:16:06 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.