Printers: Workaround for broken print server connection.
* The actual problem is that the launch_daemon does not notice the manual launch of system services (because of the missing registrar that provides that service). * So not checking if the print server is running actually solves the issue; otherwise the launch_daemon starts its own server, that will then get shut down, as there already is a print server (the one launched by the Printers preferences). * Closes ticket #12531.
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
/*
|
||||
* Copyright 2001-2010, Haiku.
|
||||
* Copyright 2001-2016, Haiku.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -39,10 +39,6 @@ ActivePrinterName()
|
||||
status_t
|
||||
GetPrinterServerMessenger(BMessenger& msgr)
|
||||
{
|
||||
// If print server is not yet running, start it
|
||||
if (!be_roster->IsRunning(PSRV_SIGNATURE_TYPE))
|
||||
be_roster->Launch(PSRV_SIGNATURE_TYPE);
|
||||
|
||||
msgr = BMessenger(PSRV_SIGNATURE_TYPE);
|
||||
return msgr.IsValid() ? B_OK : B_ERROR;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user