Description of problem:
When adding to a /etc/samba/smb.conf file "server signing = Auto",
system-config-samba aborts and presents a python backtrace.
The backtrace shows there's a default attribute missing on the defaults
presented to this tool.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Edit /etc/samba/smb.conf
2. Add in globals "server signing = Auto"
3. Execute system-config-samba
Traceback (most recent call last):
File "/usr/share/system-config-samba/system-config-samba.py", line 41, in ?
File "/usr/share/system-config-samba/mainWindow.py", line 75, in __init__
self.samba_data = sambaParser.SambaParser(self)
File "/usr/share/system-config-samba/sambaParser.py", line 41, in __init__
File "/usr/share/system-config-samba/sambaParser.py", line 75, in parseFile
token = self.createToken(line)
File "/usr/share/system-config-samba/sambaParser.py", line 147, in createToken
token = sambaToken.SambaToken(sambaToken.SambaToken.SAMBA_TOKEN_KEYVAL,
(name, value), self.parent)
File "/usr/share/system-config-samba/sambaToken.py", line 36, in __init__
raise AttributeError, value
AttributeError: ('server signing', 'Auto')
Some tracebacks ;-) but at least be able to use the tool.
Attached patch that adds to the tool the missing line.
Created attachment 140457 [details]
patch addinng the defaults missing line.
Created attachment 143400 [details]
patch adding all the options known by samba / testparm.
I've cloned this bug for RHEL5 beta -- it wouldn't be good to have this fixed in
a RHEL4 update but not in RHEL5.
The cloned bug is #219308.
I'm working on a more general solution than simply adding some options every now
and then, see bug #219308. I'm planning to backport these changes once they're done.
Held up by regression (bug #222595) introduced with new generalized solution.
system-config-samba-1.2.26 built in dist-4E-qu-candidate
reverted to system-config-samba-1.2.21-1.el4.1 which is building right now.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
The problem is fixed and my crm ticket is closed, therefore I closed this
Internal Status set to 'Resolved'
Status set to: Closed by Tech
Resolution set to: 'RHEL 4 U4'
This event sent from IssueTracker by saime