id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
762	Linux manager doesn't start the client	Nicolas	romw	As reported on boinc_alpha: the BOINC Manager is not auto-starting the core client.\r\n\r\n> Manager still fails to start the client.\r\n> \r\n> This got broken somewhere before the 6.2 release and then fixed.  It was\r\n> broken again in the last alpha release and is still broken.\r\n\r\n\r\nThe cause:\r\n\r\nIf {{{g_use_sandbox}}} is not set, [source:tags/boinc_core_release_6_3_17/clientgui/BOINCClientManager.cpp@16327#L265 the manager adds --insecure] to the client command line. This is done even if {{{SANDBOX}}} wasn't defined at compile time. The client then promptly quits saying {{{--insecure}}} is not a valid option. It [source:tags/boinc_core_release_6_3_17/client/cs_cmdline.cpp@16327#L193 only recognizes the option if SANDBOX was defined at compile time].\r\n\r\nUnder OS X, the manager adding {{{--insecure}}} is [source:tags/boinc_core_release_6_3_17/clientgui/BOINCClientManager.cpp@16327#L240 wrapped in #ifdef SANDBOX]; but not on Linux.\r\n\r\nThe fix should come from both sides. The manager shouldn't add that switch if {{{SANDBOX}}} was disabled, but the client shouldn't quit if the switch is passed. If someone says he wants the client {{{--insecure}}}, and the client doesn't even have security compiled in, the client quietly ignoring the option would get the correct behavior: no security.\r\n	Defect	closed	Major	Undetermined	Manager	6.3.17	fixed	patch