Package: nautilus-share Version: 0.7.3-1+b1 Severity: important Dear Maintainer,
* What led up to the situation? Renaming any previously shared folder doesn't update it's share status using samba daemon. It makes impossible to access the files if a privileged user renames that shared folder. * What exactly did you do (or not do) that was effective (or ineffective)? 0. Prerequisites: GNOME3, samba, nautilus-share 1. Sharing a folder, 2. Then renaming it, 2.1. It loses the sharing icon and therefore the shared folder status 3. Renaming it back, 3.1. Makes the shared folder back "online" * What was the outcome of this action? The folder was inaccessible over the Windows Sharing network. * What outcome did you expect instead? The folder still accessible over the network, and the renamed folder stills shared. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nautilus-share depends on: ii gnome-session-bin 3.4.2.1-3 ii libc6 2.13-37 ii libglib2.0-0 2.33.12+really2.32.4-3 ii libgtk-3-0 3.4.2-5 ii libnautilus-extension1a 3.4.2-1+build1 ii nautilus 3.4.2-1+build1 ii samba-common 2:3.6.6-4 ii samba-common-bin 2:3.6.6-4 nautilus-share recommends no packages. Versions of packages nautilus-share suggests: ii samba 2:3.6.6-4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org