Bug 524699 - pkcon takes lot of CPU and does not seem to end the process until terminated manually.
Summary: pkcon takes lot of CPU and does not seem to end the process until terminated ...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-packagekit
Version: rawhide
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-21 19:11 UTC by vinod
Modified: 2009-10-14 10:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-14 10:41:17 UTC


Attachments (Terms of Use)
pkcon console trace and system-monitor (133.97 KB, image/png)
2009-09-21 19:14 UTC, vinod
no flags Details

Description vinod 2009-09-21 19:11:47 UTC
Description of problem: When an unknown command is typed and a package exists is not installed, it seems like pkcon will install the packages automatically with request from the user. Currently this process hangs and consumes more than 96% CPU.

Version-Release number of selected component (if applicable):gnome-packagekit-2.27.92-1.fc12.x86_64

How reproducible: Every time.

Steps to Reproduce:
1. type a command for which the packages not yet installed say...( mail, cc)
2. A prompt comes like 'install package gcc to provide command 'cc' ?'
    Type 'y'
3. A prompt appears like 'Proceed with the changes ? '
    Type 'y'
  
Actual results:Hangs at the terminal and is consuming more than 90% of CPU and does not seem to end process.

Expected results:The dependent packages should be installed.


Additional info: Please follow attachment.

Comment 1 vinod 2009-09-21 19:14:29 UTC
Created attachment 361981 [details]
pkcon console trace and system-monitor

Attached shows the system-monitor and the process execution at console.

Comment 2 Richard Hughes 2009-10-14 10:41:17 UTC
I've fixed this in the F12 packages, please can you confirm it now worked as expected. Thanks.


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