Bug 243522 - Samba printers are not displayed
Summary: Samba printers are not displayed
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: 7
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F8Target
TreeView+ depends on / blocked
 
Reported: 2007-06-09 11:54 UTC by The Source
Modified: 2008-08-02 23:40 UTC (History)
2 users (show)

Fixed In Version: 0.7.74.2-1.fc8
Clone Of:
Environment:
Last Closed: 2007-09-21 17:46:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description The Source 2007-06-09 11:54:44 UTC
Description of problem:
When adding new printer this tool does not display list if samba printers. I can
only set url manually (everything is fine in that case). It sees samba groups
but displays nothing in them.

Version-Release number of selected component (if applicable):
system-config-printer-0.7.63.1-1.fc7

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Tim Waugh 2007-06-12 17:26:35 UTC
What output do you get when you run this command?:

python /usr/share/system-config-printer/pysmb.py


Comment 2 The Source 2007-06-13 06:04:58 UTC
{'IP': '192.168.0.2', 'DOMAIN': 'ITPROTECT'}

That's it.

Comment 3 Patrice Vetsel 2007-07-25 08:50:36 UTC
Same problem in Ubuntu look at #127152
(https://bugs.launchpad.net/fedora/+source/system-config-printer/+bug/127152)
for instructions how we solve it for gnome-cups-manager.

kagou@satori:~$ python /usr/share/system-config-printer/pysmb.py
{'IP': '192.168.1.100', 'DOMAIN': 'ENTREPRISE'}


kagou@satori:~$ findsmb 
                                *=DMB
                                +=LMB
IP ADDR         NETBIOS NAME     WORKGROUP/OS/VERSION 
---------------------------------------------------------------------
192.168.1.102   PATRICE        [        ENTREPRISE    ]
192.168.1.103   RENE           [        ENTREPRISE    ]
192.168.1.104   SECRETAIRE     [        ENTREPRISE    ]
192.168.1.105   JEANCLAUDE     [        ENTREPRISE    ]
kagou@satori:~$ 

and doing :
(for i in `export LC_ALL=C; findsmb 2> /dev/null | egrep
'^[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+' | tr -s " " | cut -f2 -d ' ' | uniq | sort`;
do echo $i; echo ---------------; export LC_ALL=C; smbclient -N -L $i 2>
/dev/null | grep Printer; echo; done
)

output :
JEANCLAUDE
---------------

PATRICE
---------------
        HP 1120C A3     Printer   

RENE
---------------

SECRETAIRE
---------------
        EPSON5700       Printer   

kagou@satori:~$ 


Comment 4 Till Kamppeter 2007-08-05 13:41:22 UTC
Patrice, can you run the following commands and post the output here:

smbclient -N -L //192.168.1.100
nmblookup -R 'ENTREPRISE'
nmblookup -A 192.168.1.102
nmblookup -A 192.168.1.103
nmblookup -A 192.168.1.104
nmblookup -A 192.168.1.105

The first one is used by s-c-p and probably will not give any useful output for
you. The second one should give you the IPs of all servers in the domain
"ENTREPRISE" (which are the four IPs of the boxes findsmb has found for you).
The last four commands reveal the NetBIOS names of each of your four boxes.

Does this happen that way? Can you post the output here? With this we will be
able to fix s-c-p.


Comment 5 Till Kamppeter 2007-08-21 19:15:55 UTC
I have done a possible fix in the upstream Subversion repository of
system-config-printer now.


Comment 6 Till Kamppeter 2007-08-27 21:18:31 UTC
My fix was confirmed now and it is part of system-config-printer 0.7.73. This
version will probably soon get RPMized by Tim.


Comment 7 Simon 2007-09-04 23:04:27 UTC
It appears that 0.7.63 has just been released, did you mean that one?

Comment 8 Till Kamppeter 2007-09-04 23:15:47 UTC
The freshly released one with my fix is 0.7.73. If you got 0.7.63 you have an
old release still containing the bug. Perhaps Red Hat packaging did not catch up
yet.


Comment 9 Tim Waugh 2007-09-05 09:59:16 UTC
No, 0.7.63 does not contain that fix.

Please try out this pysmb.py file:
https://bugzilla.redhat.com/show_bug.cgi?id=225351#c7



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