Bug 443049 - Duplicated samba share created
Summary: Duplicated samba share created
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-18 12:27 UTC by Jóhann B. Guðmundsson
Modified: 2015-03-03 22:32 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-11-05 10:40:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jóhann B. Guðmundsson 2008-04-18 12:27:31 UTC
Description of problem:

After I create a new "samba connected folder"
and I open the "samba connected folder" it creates an 
extra instance of itself on the desktop

But just one instance. 

I unmount the duplicate and another one gets
created soon as I open the "samba connected folder" that was created
to begin with but if I unmount the original created "samba connected folder"
and use the duplicate this does not happen this also does not happen if I
unmount both and connect using the bookmark nor does that "samba connected
folder" that gets create when using the bookmark create another instance of
itself as in that works as it should.

Has something to do with the "samba connected folder" that gets initially created.

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


How reproducible:

Always.

Steps to Reproduce:
1.Create a new windows connection and double click the folder that gets created.
2.
3.
  
Actual results:

The above.

Expected results:

It not create another instance of it'self

Additional info:

Comment 1 Bug Zapper 2008-05-14 09:38:05 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Jóhann B. Guðmundsson 2008-11-05 10:40:40 UTC
Closing this as fixed not an issue in F10Preview...


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