Bug 1265835

Summary:	[RFE] Baobab should expect that mountpoints may change after the location is added
Product:	Red Hat Enterprise Linux 7	Reporter:	Vera Budikova <vbudikov>
Component:	baobab	Assignee:	Ondrej Holy <oholy>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	tpelka
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-13 07:56:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vera Budikova 2015-09-23 21:37:33 UTC

Description of problem:
Baobab should expect that mountpoints may change after the location is added

Version-Release number of selected component (if applicable):
baobab-3.14.1-5.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. Mount several nfs folders
2. Run baobab
3. Scan filesystem
4. Wait a few minutes
5. Mount another nfs folder
6. Click on refresh button

Actual results:
Baobab is frozen, because new mountpoint is not omitted. The baobab application design doesn't expect that mountpoints may change after the location is added.

Expected results:
Baobab is not frozen and mounted folders are omitted.

Additional info:

Comment 2 Ondrej Holy 2015-09-24 06:20:12 UTC

I proposed upstream fix, but it hasn't accepted yet, let's fix it in 7.3.

Comment 3 Ondrej Holy 2016-01-12 14:27:38 UTC

The patch has not been accepted by the upstream yet.

Comment 6 Ondrej Holy 2017-10-13 07:56:16 UTC

The patch has been provided to upstream and unfortunately, it lies there without any feedback. Let's close this bug because this is not really anything serious and it doesn't have enough justification to maintain this patch downstream only. Desktop packages are regularly rebased anyway, so the fix will come soon after it is merged upstream...