Bug 327251 - samba client
samba client
Product: Fedora
Classification: Fedora
Component: samba (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Simo Sorce
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-10-11 00:53 EDT by Darwin H. Webb
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-11 09:01:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Darwin H. Webb 2007-10-11 00:53:38 EDT
Description of problem:
Pre1 3.2 on F8 devl
connection to winodws xp share pushing works fine but pulling from share gets
popup message invaild parm for smb// (press skip, cancel, close)
Pressing skip continues, files seem to be ok. (This occurred more often with
picture (jpeg, png, bmp) than data (rpm's iso's)

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

How reproducible:
Most all ways when pulling from share.

Steps to Reproduce:
1.rpm -Uvh 
open Places, click on Share Name, enter user and password,
select from share, copy, select /home/Dlownload, paste.
Actual results:

Expected results:

Additional info:
Comment 1 Simo Sorce 2007-10-11 09:01:02 EDT
F8 will ship with 3.0.26a please try with that package. has been currently retired while waiting on licensing evaluation.
Comment 2 Darwin H. Webb 2007-10-11 12:03:27 EDT
It still has a bug and that is what you s/b concerned about.
Samba-3.2 and 4.0 will be used by almost all Linux's and it doesn't matter one
bit about Licensing. Especially nit picking on a gpl version.
There are a half billion Windows uses and only a few million Fedora users.
It is impossible to exsit without samba.
I will use 3.2.0 in F8 weather Fedora likes it or not.
So tell the nit pickers to get real. 
This is samba, not nvidia.

Comment 3 Simo Sorce 2007-10-11 12:29:44 EDT
Just to make it clear:
I *do* care about this bug, and I will test for it, that's why it is just
DEFERRED. The right place for this bug, right now, is upstream though.

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