Description of problem:
In its "superuser" settings, smb4k can add an entry in the sudoers file in order to make some /usr/bin/smb4k_* commands to work in sudo mode.

Fedora's sudoers defaults are to "requiretty" ; with this option, smb4k won't be able to execute its commands : it has to change the defaults.


Version-Release number of selected component (if applicable):
Name       : sudo                               
Arch       : i586                               
Version    : 1.7.1
Release    : 4.fc11

Name       : smb4k
Arch       : i586
Version    : 0.10.2
Release    : 1.fc11


How reproducible:
Always


Steps to Reproduce:
1. In smb4k, go to settings => superuser => and check "use superuser privileges to mount or umount shares". Give your root's password to smb4k_sudowriter
2. Mount any share 
3. "error : the share cannot be mounted/umounted"
  
Actual results:
sudo: sorry, you must have a tty to run sudo

Expected results:
The share to be mounted/umounted

Additional info:
Here's the thing :
smb4k_sudowriter is writing this entry to the sudoers :
# Entries for Smb4K users.
# Generated by Smb4K. Please do not modify!
User_Alias      SMB4KUSERS = myuser
Defaults:SMB4KUSERS     env_keep += "PASSWD USER"
SMB4KUSERS      myhost = NOPASSWD: /usr/bin/smb4k_kill
SMB4KUSERS      myhost = NOPASSWD: /usr/bin/smb4k_umount
SMB4KUSERS      myhost = NOPASSWD: /usr/bin/smb4k_mount
# End of Smb4K user entries.

In the first lines of this file, you'll find this :
Defaults    requiretty
We have to disable this "feature" (for SMB4KUSERS only, this is not a bug).

The only thing to do is to modify the Defaults's line in smb4k_sudowriter entry to get :
Defaults:SMB4KUSERS     env_keep += "PASSWD USER" , ! requiretty

And that's it ! With this little word, smb4k is just working fine again.