Bug 10503 - print settings not saved to samba4 server registry
Summary: print settings not saved to samba4 server registry
Status: RESOLVED WONTFIX
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Printing (show other bugs)
Version: 4.1.6
Hardware: All Linux
: P5 normal (vote)
Target Milestone: ---
Assignee: printing-maintainers
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-18 14:35 UTC by Mark
Modified: 2014-04-04 12:59 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark 2014-03-18 14:35:37 UTC
Some print drivers use a subkey of the server registry to save default settings. 

The driver trys to make a subkey in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\<printername>\

values can be stored there, but the creation of a subkey is not possible.


The log.smbd on the moment of creation:

[2014/03/18 15:36:41.706867, 10, pid=24335, effective(10500, 10513), real(10500, 0), class=rpc_srv] ../source3/rpc_server/winreg/srv_winreg_nt.c:785(_winreg_CreateKey)
  _winreg_CreateKey called with parent key 'HKLM\SYSTEM\CurrentControlSet\Control\Print\Printers\nlvwprt10' and subkey name 'Nieuwe sleutel nr. 1'
[2014/03/18 15:36:41.706937,  7, pid=24335, effective(10500, 10513), real(10500, 0), class=registry] ../source3/registry/reg_api.c:143(regkey_open_onelevel)
  regkey_open_onelevel: name = [Nieuwe sleutel nr. 1]
[2014/03/18 15:36:41.706989, 10, pid=24335, effective(10500, 10513), real(10500, 0), class=registry] ../source3/registry/reg_backend_db.c:846(regdb_open)
  regdb_open: incrementing refcount (4->5)
[2014/03/18 15:36:41.707036, 10, pid=24335, effective(10500, 10513), real(10500, 0), class=registry] ../source3/registry/reg_cachehook.c:125(reghook_cache_find)
  reghook_cache_find: Searching for keyname [\HKLM\SYSTEM\CurrentControlSet\Control\Print\Printers\nlvwprt10\Nieuwe sleutel nr. 1]
[2014/03/18 15:36:41.707079, 10, pid=24335, effective(10500, 10513), real(10500, 0)] ../source3/lib/adt_tree.c:367(pathtree_find)
  pathtree_find: Enter [\HKLM\SYSTEM\CurrentControlSet\Control\Print\Printers\nlvwprt10\Nieuwe sleutel nr. 1]
[2014/03/18 15:36:41.707125, 10, pid=24335, effective(10500, 10513), real(10500, 0)] ../source3/lib/adt_tree.c:440(pathtree_find)
  pathtree_find: Exit
[2014/03/18 15:36:41.707164, 10, pid=24335, effective(10500, 10513), real(10500, 0), class=registry] ../source3/registry/reg_cachehook.c:130(reghook_cache_find)
  reghook_cache_find: found ops 0x7f36f9782980 for key [\HKLM\SYSTEM\CurrentControlSet\Control\Print\Printers\nlvwprt10\Nieuwe sleutel nr. 1]
[2014/03/18 15:36:41.707225, 10, pid=24335, effective(10500, 10513), real(10500, 0), class=registry] ../source3/registry/reg_backend_db.c:1725(regdb_fetch_keys_internal)
  key [HKLM\SOFTWARE\MICROSOFT\WINDOWS NT\CURRENTVERSION\PRINT\PRINTERS\nlvwprt10\Nieuwe sleutel nr. 1] not found
[2014/03/18 15:36:41.707273, 10, pid=24335, effective(10500, 10513), real(10500, 0), class=registry] ../source3/registry/reg_backend_db.c:883(regdb_close)
  regdb_close: decrementing refcount (5->4)
[2014/03/18 15:36:41.707329,  1, pid=24335, effective(10500, 10513), real(10500, 0)] ../librpc/ndr/ndr.c:333(ndr_print_function_debug)
       winreg_CreateKey: struct winreg_CreateKey
          out: struct winreg_CreateKey
              new_handle               : *
                  new_handle: struct policy_handle
                      handle_type              : 0x00000000 (0)
                      uuid                     : 00000000-0000-0000-0000-000000000000
              action_taken             : NULL
              result                   : WERR_NOT_SUPPORTED
[2014/03/18 15:36:41.707489,  5, pid=24335, effective(10500, 10513), real(10500, 0), class=rpc_srv] ../source3/rpc_server/srv_pipe.c:1417(api_rpcTNP)
  api_rpcTNP: called \winreg successfully
Comment 1 Andreas Schneider 2014-04-04 12:59:54 UTC
This is how Windows does it. Right-Click on the Printer, go to Properties and rename it :)