251397 is the bug number for last bug samba failed again after updates

[perezomail]

Binary package hint: samba

251397 was the last bug number for samba in that case it was found invalid due to the fact that some updates corrected the problem. recently I received some new updates which made samba unusable again. Unlike the first time I am able to get into the Windows Shares and the local network folder however I cannot open the shared folder at all. I have tried deleting all folders that are to be shared and making new ones and sharing those however I still cannot mount them I have changed their permissions and so on still to no avail still after several reboots and shutting down my firewall settings and deleting the firewall configurations all together. While doing the updates I do recall being asked if I wanted to keep the current or replace them looking back i may have opted wrong this time. I have never had an issue by opting for the maintainers version before bug # 251397 produced no samba shares on record and I this time do not have the intended shared files under encryption folders. last time I brought up samba issues i was asked to attach a file however i forgot currently which file I am to attach to help in viewing this bug currenly

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: samba 2:3.4.7~dfsg-1ubuntu3.3
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic i686
Architecture: i386
Date: Fri Jan 21 13:07:02 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SambaServerRegression: Yes
SourcePackage: samba
WindowsFailedConnect: Yes

[Chuck Short (zulcss)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

[perezomail (perezomail)]

On Mon, Jan 24, 2011 at 7:46 AM, Chuck Short <email address hidden> wrote:
> Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
> 1. Is this reproducible? yes
> 2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible. click on widows share than it opens to workgroup however ever workgroup never opens
> This will help us to find and resolve the problem.
> sending smb confg file
> ** Changed in: samba (Ubuntu)
>   Importance: Undecided => Low
>
> ** Changed in: samba (Ubuntu)
>       Status: New => Incomplete
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/706038
>
> Title:
>  251397 is the bug number for last bug samba failed again after updates
>
> Status in “samba” package in Ubuntu:
>  Incomplete
>
> Bug description:
>  Binary package hint: samba
>
>  251397 was the last bug number for samba in that case it was found
>  invalid due to the fact that some updates corrected the problem.
>  recently I received some new updates which made samba unusable again.
>  Unlike the first time I am able to get into the Windows Shares and the
>  local network folder however I cannot open the shared folder at all. I
>  have tried deleting all folders that are to be shared and making new
>  ones and sharing those however I still cannot mount them I have
>  changed their permissions and so on still to no avail still after
>  several reboots and shutting down my firewall settings and deleting
>  the firewall configurations all together. While doing the updates I do
>  recall being asked if I wanted to keep the current or replace them
>  looking back i may have opted wrong this time. I have never had an
>  issue by opting for the maintainers version before bug # 251397
>  produced no samba shares on record and I this time do not have the
>  intended shared files under encryption folders. last time I brought up
>  samba issues i was asked to attach a file however i forgot currently
>  which file I am to attach to help in viewing this bug currenly
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 10.04
>  Package: samba 2:3.4.7~dfsg-1ubuntu3.3
>  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
>  Uname: Linux 2.6.32-28-generic i686
>  Architecture: i386
>  Date: Fri Jan 21 13:07:02 2011
>  EcryptfsInUse: Yes
>  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
>  ProcEnviron:
>   PATH=(custom, no user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SambaServerRegression: Yes
>  SourcePackage: samba
>  WindowsFailedConnect: Yes
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/706038/+subscribe
>

[Launchpad Janitor (janitor)]

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]

[perezomail (perezomail)]

this is no longer an issue i notice samba was working about 2 weeks
ago when i thought I was checking it in vain guess this must have been
resolved by an update

On Mon, Jan 24, 2011 at 7:46 AM, Chuck Short <email address hidden> wrote:
> Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
> 1. Is this reproducible?
> 2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
> This will help us to find and resolve the problem.
>
> ** Changed in: samba (Ubuntu)
>   Importance: Undecided => Low
>
> ** Changed in: samba (Ubuntu)
>       Status: New => Incomplete
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/706038
>
> Title:
>  251397 is the bug number for last bug samba failed again after updates
>
> Status in “samba” package in Ubuntu:
>  Incomplete
>
> Bug description:
>  Binary package hint: samba
>
>  251397 was the last bug number for samba in that case it was found
>  invalid due to the fact that some updates corrected the problem.
>  recently I received some new updates which made samba unusable again.
>  Unlike the first time I am able to get into the Windows Shares and the
>  local network folder however I cannot open the shared folder at all. I
>  have tried deleting all folders that are to be shared and making new
>  ones and sharing those however I still cannot mount them I have
>  changed their permissions and so on still to no avail still after
>  several reboots and shutting down my firewall settings and deleting
>  the firewall configurations all together. While doing the updates I do
>  recall being asked if I wanted to keep the current or replace them
>  looking back i may have opted wrong this time. I have never had an
>  issue by opting for the maintainers version before bug # 251397
>  produced no samba shares on record and I this time do not have the
>  intended shared files under encryption folders. last time I brought up
>  samba issues i was asked to attach a file however i forgot currently
>  which file I am to attach to help in viewing this bug currenly
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 10.04
>  Package: samba 2:3.4.7~dfsg-1ubuntu3.3
>  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
>  Uname: Linux 2.6.32-28-generic i686
>  Architecture: i386
>  Date: Fri Jan 21 13:07:02 2011
>  EcryptfsInUse: Yes
>  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
>  ProcEnviron:
>   PATH=(custom, no user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SambaServerRegression: Yes
>  SourcePackage: samba
>  WindowsFailedConnect: Yes
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/706038/+subscribe
>