Description of problem: Adding a printer connected to a samba server in Windows fails. The problem is described in samba_bug 8554 https://bugzilla.samba.org/show_bug.cgi?id=8554 and in Ubuntu https://bugs.launchpad.net/ubuntu/+source/samba/+bug/967410 comment 75 has a clear description of the problem. Version-Release number of selected component (if applicable): samba-3.6.5-2.1.mga2.src.rpm How reproducible: The problem can be demonstrated quite easily without having to use Windows by using the command. # rpcclient localhost -Nc enumprinters flags:[0x800000] name:[\\LOCALHOST\] description:[\\LOCALHOST\,,PDF Generator (only valid users)] comment:[PDF Generator (only valid users)] flags:[0x800000] name:[\\LOCALHOST\] description:[\\LOCALHOST\,,HP Officejet Pro L7400] comment:[HP Officejet Pro L7400] The 'name' parameter contains the hostname, but it does not contain the printer name. It should look like this :- name:[\\LOCALHOST\Officejet-Pro-L7400] The samba bug report contains a patch which is reported to fix the problem https://attachments.samba.org/attachment.cgi?id=7311 Cauldron should not be affected, although I have not been able to try it out yet. Reproducible: Steps to Reproduce:
I have applied the samba.org patch to samba-server-3.6.5-2 and it works OK However it is necessary to delete and re add the printer before it will be properly declared. # rpcclient localhost -Nc enumprinters flags:[0x800000] name:[\\LOCALHOST\] description:[\\LOCALHOST\,,PDF Generator (only valid users)] comment:[PDF Generator (only valid users)] flags:[0x800000] name:[\\LOCALHOST\HP-Officejet-Pro-L7400] description:[\\LOCALHOST\HP-Officejet-Pro-L7400,,HP Officejet Pro L7400] comment:[HP Officejet Pro L7400]
Keywords: (none) => PATCH, UPSTREAMAssignee: bugsquad => bgmilne
Buchan, is it ok for you to include this patch in an update for Mageia 2? (either done by you or someone else)
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD