Frequently Asked Questions (FAQ)
================================

(Version: 2005-06-06)


Reporting bugs
--------------

Q:  I think, I found a bug. Where can I report it?

A:  There are two possible ways, how to do it. You can either click on the 
    menu item Help->Report Bug... and submit your report there, or you go to
    the project's bug tracking site:
    http://developer.berlios.de/bugs/?group_id=769.
    

Compilation and Installation
----------------------------

Q:  I have compiled Smb4K from source. After starting it, I can't see the 
    toolbar. What went wrong?

A:  Most likely, you installed Smb4K to the wrong place. Please pass the 
    '--prefix=/path/to/root/of/KDE' option to the configure script. To check
    the root of KDE on your system, do something like
  
    $ which konqueror

    in the shell. As a result, you should get something like
  
    /usr/bin/konqueror

    The root of KDE in this case is /usr/. If you now do

    $ ./configure --prefix=/usr/ && make
    $ su -c "make install"

    everything should work fine.


Q:  The configure script fails and tells me, it can't find my Qt
    installation.
      
A:  There are three things you should consider:
    1. The Qt header files are not installed. Do it and try to recompile.
    2. The QTDIR environment variable is not set properly. Add the following 
       line to your ~/.bashrc file:
   
       export QTDIR=/root/of/Qt
   
       If you now do
   
       $ source ~/.bashrc
   
       you're set for a second attempt.
    3. If the header files still can't be found, pass the
  
       --with-qt-includes=/path/to/header/files
   
       option to the configure script.
   
   
Q:  The configure script fails and tells me, it can't find my KDE 
    installation.
  
A:  There are two things you should consider:
    1. The KDE header files are not installed. Do it and try to recompile.
    2. The KDEDIR environment variable is not set properly. Add the following 
       line to your ~/.bashrc file:
   
       export KDEDIR=/root/of/KDE
   
       If you now do
   
       $ source ~/.bashrc
   
       you're set for a second attempt.
    
    
Browsing
--------

Q:  When I start Smb4K, there is nothing in the network browser!

A:  Please follow this list to fix the problem: 
    - If your network has a WINS server, add it to the [General] section of
      your smb.conf file and restart Smb4K.
    - Make sure the SMB ports 137, 139, and 445 are not blocked by a firewall.
    - Make sure that all workgroup masters provide a browse list. If they 
      don't, enable this feature.
    - Try to use a different look-up method. Therefore, change the settings 
      under Network -> Browse List in the configuration dialog. - Retry.
      
    If there still isn't anything visible in the browser widget, ask for help
    on the Smb4K-general mailing list or file a bug report.
    
Q:  When I want to open a workgroup, there is nothing in it. What's wrong?

A:  Please check, whether the workgroup master needs authentication and enter
    it in the Authentication tab of the configuration dialog. If this doesn't
    help, file a bug report.

   
Mounting/Unmounting of shares
-----------------------------

Q:  If I want to mount a share, I get a message like this:
      
    smbmnt must be installed suid root for direct user mounts (500,500)
    smbmnt failed: 1
  
    What does that mean?
  
A:  It means, that you do not have the right permissions to mount SMB shares. 
    There are two things you can do:
    1. Set the SUID root bit for smbmnt. Therefore you have to find out, 
       where the binary is located. Try
        
       $ ls -la `which smbmnt`
   
       in the shell. If this is a symlink, follow it to find the binary 
       (e. g. under SuSE 8.x you get /usr/bin/smbmnt as result, but the 
       binary is actually lying under /usr/lib/samba/classic/smbmnt). 
       Change into the directory, where smbmnt resides and do
        
       $ chmod +s smbmnt
   
       Now the mounting should work. NOTE: Do not set the SUID root bit for 
       smbmount!
    2. Smb4K 0.4.0 and later provide the ability to execute mount and umount 
       SUID root using the program super or sudo. To enable this feature you 
       have to go to the configuration dialog's tab "Super User".
   
   
Q:  If I want to unmount a share, I get the following message:
      
    smbumount must be installed suid root
      
    What do I have to do?
  
A:  You have similar options as above. Either you set the SUID root bit for
    smbumount or you enable the feature "Use super user privileges to mount
    and unmount shares" under Super User -> Actions in the configuration 
    dialog. For details see above.
   

Q:  I'm using the CIFS filesystem for mounting and I've set the UID/GID in
    the mount tab, but Smb4K does not seem to care about that at all!
      
A:  This is a Samba issue. If the target server supports the CIFS Unix 
    extentions, the uid and gid option will be ignored. From the manual page
    of mount.cifs:

    [uid=arg|gid=arg]
      sets  the [uid|gid] that will own all files on the mounted filesystem.
      It may be specified as either a username or a numeric uid.  This
      parameter  is  ignored  when the target server supports the CIFS
      Unix extensions.
        
        
Q:  When I try to mount a share from a Windows 2003 server, I get this error
    message
      
    cli_negprot: SMB signing is mandatory and we have disabled it.
    4377: protocol negotiation failed
    SMB connection failed
      
    and the mounting fails. What's wrong?
      
A:  You are using the SMBFS file system that does not support signing. You 
    have to switch to the CIFS file system in order to be able to mount the
    share.
      
    Go to the configuration dialog -> Samba -> mount -> File system and 
    choose "CIFS" instead of "SMBFS".


Q:  Smb4K fails unmounting a share. The error message is: 

    Could not unmount /mount/point: Device or resource busy
      
A:  First of all, check that you haven't opened the mount point or one of its
    subdirectories in a shell or with a file manager. Also, make sure you 
    haven't opened any file belonging to the share. If neither is the case, 
    you might have encountered a problem, that is known but not related to
    Smb4K. It seems, that under certain circumstances (that we could not 
    figure out exactly) kdeinit (KDE < 3.4) background processes access files
    and/or directories of the share and keep them open. Unmounting is not 
    possible unless you send
      
    $ kill -HUP <PID>
      
    to each kdeinit instance that has access to the share or its files.
    
    
Miscellaneous    
-------------

Q:  I'm using Smb4K 0.4.x. After starting it, I cannot see the main window!
    Is this a bug?
    
A:  No. This is a special behavior of the 0.4.x series, which was changed in
    later releases. Smb4K 0.4.x immediately docks to the system tray. You'll 
    find an icon there with which you can bring up the main window. 
    
Q:  I want to use super to mount the shares. When I try to enable either "Use
    super user privileges to force the unmounting of (broken) shares" or "Use
    super user privileges to mount and unmount shares", Smb4K complains that 
    it cannot find the super.tab file. What do I have to do?
    
A:  Create the super.tab file in the appropriate etc directory. Therefore 
    change into it (most likely /etc (Linux) or /usr/local/etc (FreeBSD)) and 
    do 

    $ touch super.tab 

    as root. Smb4K will take care of the rest.