Bug 44653 - New printer shares not shown in Windows, only after additional samba reload (4.1)
New printer shares not shown in Windows, only after additional samba reload (...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Printserver
UCS 4.1
Other Linux
: P3 normal (vote)
: UCS 4.1-4-errata
Assigned To: UCS maintainers
UCS maintainers
:
Depends on: 44153
Blocks:
  Show dependency treegraph
 
Reported: 2017-05-22 21:00 CEST by Arvid Requate
Modified: 2019-01-03 07:19 CET (History)
4 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.103
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2017-05-22 21:00:52 CEST
We should also backport this trivial fix to errata4.1-4


+++ This bug was initially created as a clone of Bug #44153 +++

New printer shares are not shown in Windows, only after an additional /etc/init.d/samba reload, see attached patch for a workaround.

I've experimented with other things, reloading cups and sleeping 30 seconds between lpadmin, cups reload and samba reload. In the end, only a double samba reload fixed the issue, a cups reload was not required between lpadmin and samba reload.
Comment 1 Stefan Gohmann univentionstaff 2019-01-03 07:19:36 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.