** Changed in: nautilus-share (Debian)
Status: New = Unknown
** Changed in: nautilus-share (Debian)
Status: Unknown = New
** Changed in: nautilus-share (Debian)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Changed in: nautilus-share (Debian)
Status: New = Unknown
** Changed in: nautilus-share (Debian)
Status: Unknown = New
** Changed in: nautilus-share (Debian)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Does anyone know where to find to code for nautilus-share?
We got a problem here:
https://bugzilla.gnome.org/show_bug.cgi?id=675450#c13
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Does anyone know where to find to code for nautilus-share?
We got a problem here:
https://bugzilla.gnome.org/show_bug.cgi?id=675450#c13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917906
Title:
https://bugzilla.gnome.org/show_bug.cgi?id=675450
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917906
Title:
Can't determine shared folders
To manage notifications about this bug go to:
Creating usershares:
gnomeuser@gnomeuser:~/Desktop/test$ mkdir
/home/gnomeuser/Desktop/test/{bb,gg,pp}
gnomeuser@gnomeuser:~/Desktop/test$ net usershare add cc
'/home/gnomeuser/Desktop/test/bb'
gnomeuser@gnomeuser:~/Desktop/test$ net usershare info
[cc]
path=/home/gnomeuser/Desktop/test/bb
Quote from bugziall.samba
(https://bugzilla.samba.org/show_bug.cgi?id=8852#c6)
Ok. This is a nautilus problem. The last step printing the error message prints
that error to stderr, the valid shares are listed on stdout. Again, I think
Samba just behaves correctly. Just tested this.
Regarding the
samba works correctly regarding this matter
The problem is with nautilus, respectively the handeling of the sharing
icons by nautilus.
** Changed in: samba (Ubuntu)
Status: Confirmed = Invalid
** Changed in: nautilus-share (Ubuntu)
Status: Triaged = Confirmed
--
You received
new bugreport on bugzilla.gnome:
https://bugzilla.gnome.org/show_bug.cgi?id=675450
** Bug watch added: GNOME Bug Tracker #675450
https://bugzilla.gnome.org/show_bug.cgi?id=675450
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Regarding the issue of the disappearing icons; isn't this a direct
nautilus problem (not nautilus-share)?
As far as I know, the nautilus-share extension package only extends the
context menu and communicates with samba via net usershare (which is a
samba tool).
Unfortunaltely I only have minor
Creating usershares:
gnomeuser@gnomeuser:~/Desktop/test$ mkdir
/home/gnomeuser/Desktop/test/{bb,gg,pp}
gnomeuser@gnomeuser:~/Desktop/test$ net usershare add cc
'/home/gnomeuser/Desktop/test/bb'
gnomeuser@gnomeuser:~/Desktop/test$ net usershare info
[cc]
path=/home/gnomeuser/Desktop/test/bb
Quote from bugziall.samba
(https://bugzilla.samba.org/show_bug.cgi?id=8852#c6)
Ok. This is a nautilus problem. The last step printing the error message prints
that error to stderr, the valid shares are listed on stdout. Again, I think
Samba just behaves correctly. Just tested this.
Regarding the
samba works correctly regarding this matter
The problem is with nautilus, respectively the handeling of the sharing
icons by nautilus.
** Changed in: samba (Ubuntu)
Status: Confirmed = Invalid
** Changed in: nautilus-share (Ubuntu)
Status: Triaged = Confirmed
--
You received
new bugreport on bugzilla.gnome:
https://bugzilla.gnome.org/show_bug.cgi?id=675450
** Bug watch added: GNOME Bug Tracker #675450
https://bugzilla.gnome.org/show_bug.cgi?id=675450
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Regarding the issue of the disappearing icons; isn't this a direct
nautilus problem (not nautilus-share)?
As far as I know, the nautilus-share extension package only extends the
context menu and communicates with samba via net usershare (which is a
samba tool).
Unfortunaltely I only have minor
Public bug reported:
When trying to share a folder via usershare extension (using the nautilus
context menu), a popup may notify about the missing samba package and wheather
you want to install it.
If you do so, you can share the folder, but you cannot access shared folder on
the network,
Public bug reported:
When trying to share a folder via usershare extension (using the nautilus
context menu), a popup may notify about the missing samba package and wheather
you want to install it.
If you do so, you can share the folder, but you cannot access shared folder on
the network,
same bug as this: https://bugs.launchpad.net/ubuntu/+source/nautilus-
share/+bug/917906
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/250464
Title:
shared folder still accessible after stop sharing
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/917906
Title:
Can't determine shared folders
To manage notifications
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917906
Title:
Can't determine shared folders
To manage notifications about this bug go
I have opened up a bug report at bugzilla.samba.org as well.
https://bugzilla.samba.org/show_bug.cgi?id=8852
** Bug watch added: Samba Bugzilla #8852
https://bugzilla.samba.org/show_bug.cgi?id=8852
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I have opened up a bug report at bugzilla.samba.org as well.
https://bugzilla.samba.org/show_bug.cgi?id=8852
** Bug watch added: Samba Bugzilla #8852
https://bugzilla.samba.org/show_bug.cgi?id=8852
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
If I restart my machine after I shared a folder the shared icon is
missing and the context-menu share-option is turned off as if the folder
isn't shared anymore. If I access the folder from another computer over
the network the folder is still shared. So I can't
How about this for a start:
Instead of just creating the error message, the net usershare command
should at least delete the corrupt usershare definitions. Still this
does not solve the remove/rename problem but that is not as severe as
obsolent share definition.
I cannot change the code myself
This bug also affects Ubuntu 12.04 Beta-2.
I didn't try it with different versions but the bug will probably affect
all versions of Ubuntu since this feature was added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
If I restart my machine after I shared a folder the shared icon is
missing and the context-menu share-option is turned off as if the folder
isn't shared anymore. If I access the folder from another computer over
the network the folder is still shared. So I can't
** Description changed:
If I restart my machine after I shared a folder the shared icon is
missing and the context-menu share-option is turned off as if the folder
isn't shared anymore. If I access the folder from another computer over
the network the folder is still shared. So I can't
This bug is related to this one: (solution already found)
https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/917906
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/198681
Title:
sending
The solution could be to add a removal command for the sahre definition
to the remove and move command, but this would end up dirty right?
How about letting the net usershare command react to the error message?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Well I don't now much about this but it seem rather important to me that
1. the obsolent share definitions will be removed, because creating a
new folder with the same name of a once shared (and then deleted) folder
will unintentionally share the new folder as well. Furthermore it is
importet that
** This bug has been flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917906
Title:
Can't determine shared folders
To manage notifications about this bug go to:
** Also affects: nautilus-share (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917906
Title:
Can't determine shared folders
To manage
I have experienced this problem several times now and I think it should
definitly be fixed.
The bug it has obviously something to do with how nautilus reads the usershares
definition under /var/lib/samba/usershares, which is affected by the usershare
settings in the smb.conf file.
So I think it
I got it, I reproduced the bug:
If you define a share, the definition is made in /var/lib/samba/usershares.
But if you delete a Folder that is being shared, the definition in
/var/lib/samba/usershares will not be removed.
After restarting all other shares will not be shown as shared (the share
Correction:
1. The shared folder does not have to own writing privileges for other users
for the bug to occur.
Deleting simply a shared folder produces the bug as well.
2. The bug is reproduceable using folder names one and two. I just
tried it with the names aa and bb but it didn't work for
Ok I got the hopefully final solution:
The bug only occurs if the name of the deleted folder beginns with a
letter that stands before the first letter of the second folder in the
alphabet.
For example: If you have the shared folders one and two, you have to delete
two for the bug to occur.
If
Correction:
The explanation with the alphabetical order was wrong (obviously ;))
But the order of the shares in net usershare info still counts.
It's just taht I cannot say how the order of the share definitions is
determined.
--
You received this bug notification because you are a member of
Again two additions:
1. The alphabetical order is relevant it's just that userg a and b is kinda
an exception with my system right now, but using other names the normal order
is alphabetically
2. The bug will also occur if you rename the shared folder, which is
logical, since the share
38 matches
Mail list logo
