RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 956704 - [RFE] limit number of items in overview
Summary: [RFE] limit number of items in overview
Keywords:
Status: CLOSED DUPLICATE of bug 1567161
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: baobab
Version: 7.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: 7.1
Assignee: Ondrej Holy
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1567161
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-25 13:07 UTC by Vladimir Benes
Modified: 2018-06-01 12:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-01 12:20:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 695421 0 None None None Never

Description Vladimir Benes 2013-04-25 13:07:51 UTC 
Description of problem:
when several items added and whole overview is full I cannot remove any of them or sort them. Nothing

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

baobab-3.8.1-1.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.try to change order or remove analyzed item 

  
Actual results:
no way

Expected results:
should be possible

Additional info:
Comment 1 Matthias Clasen 2013-09-03 19:10:45 UTC 
requires ui changes -> 7.1
Comment 3 Vadim Rutkovsky 2015-05-12 13:23:28 UTC 
Still valid for baobab-3.14.1-1.el7.x86_64
Comment 4 Ondrej Holy 2015-06-03 10:55:54 UTC 
Just a note that there are listed following locations in following order currently:

Main volume (i.e. /)
Home dir (i.e. /home/$USER)
All other volumes (e.g. removable disks)
All other mounts (e.g. gvfs mounts)
Max 5 other recent locations (added when user scan other location, sorted by recency)

(Max 5 recent locations is listed only when baobab is started, every newly scanned location is appended during program execution...)
Comment 6 Ondrej Holy 2016-01-13 09:25:41 UTC 
It doesn't make sense a lot to allow reordering, because current list of folder depends on actually connected devices, mount points, recent items etc. (Comment 4). So next time you might see different set of locations. Solution might be to limit number of recent items to be always five. Five recent locations are currently shown, when application starts, however new one is added when you scan custom folder. So we might remove one recent location if new one is appended... Is this acceptable solution?
Comment 8 Ondrej Holy 2017-02-23 16:49:02 UTC 
I have proposed the suggested change from Comment 6 to upstream, but it is not accepted yet.
Comment 9 Vladimir Benes 2017-03-03 11:55:57 UTC 
(In reply to Ondrej Holy from comment #8)
> I have proposed the suggested change from Comment 6 to upstream, but it is
> not accepted yet.

OK, works for me. Current behaviour seems to be pretty good and w/o restart it would be even better.
Comment 10 Ondrej Holy 2017-03-03 12:39:11 UTC 
The patch is in master, so let's fix it this way...
Comment 12 Ondrej Holy 2018-03-07 15:49:05 UTC 
The upstream fix should be part of the planned desktop rebase in RHEL-7.6.
Note You need to log in before you can comment on or make changes to this bug.