Bug 440088 - pirut needs command line option to start in list mode
Summary: pirut needs command line option to start in list mode
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pirut
Version: 5.1
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-01 18:09 UTC by Fred Handloser
Modified: 2013-03-12 20:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-12 20:08:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Fred Handloser 2008-04-01 18:09:39 UTC
Description of problem:
pirute always starts in browse mode and I then need to wait for it to finish
before I can switch to list mode which is the mode I use most often
~                                                                 

Version-Release number of selected component (if applicable):


How reproducible:

always
Steps to Reproduce:
1. start pirut 
2.
3.
  
Actual results:
pirut starts in browse mode

Expected results:
This is expected but not user friendly.  

Additional info:

Comment 1 James Antill 2013-03-12 20:08:37 UTC
Might be worth requesting this for the RHEL-6 GUI, as I don't think that has this feature yet.


This request was evaluated by Red Hat Engineering for inclusion in a Red 
Hat Enterprise Linux maintenance release.

Red Hat does not currently plan to provide this change in a Red Hat 
Enterprise Linux update release for currently deployed products.

With the goal of minimizing risk of change for deployed systems, and in 
response to customer and partner requirements, Red Hat takes a 
conservative approach when evaluating enhancements for inclusion in 
maintenance updates for currently deployed products. The primary 
objectives of update releases are to enable new hardware platform 
support and to resolve critical defects.


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