Help needed!!
A challenge for somebody clever to investigate and solve - please!
Concerns a difference in behaviour in an LXDE/Openbox scenario compared to a JWM scenario.
Base system can be either LxPupSc or LxPupArtful - both behave similarly. (LxPupXenial and LxPup-16.07.1-s likewise)
Do a pristine frugal install and boot - when system is up and running (under LXDE/Openbox) open a terminal and type:
Code: Select all
run-as-spot light
and that the Default Browser configuration answers are not saved between invocationsGConf Error or Warning: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Now switch to JWM using Menu -> Setup -> Switch LXDE <> JWM....
Repeat the "run-as-spot light" test and note the absence of GConf/D-Bus messages in the terminal and that the configuration answers are now stored and remembered correctly.
So the question needing an answer is "How is the system started differently in the 2 cases such that the D-Bus message bus works correctly in run-as-spot mode under JWM but fails under LXDE/Openbox?"
I'm flummoxed and need some help! Here's hoping!
Thanks
peebee