Portable/Qt detection USB flash drive: failed to connect to socket... System_bus_socket: Connection refused Solution

After today's research, I finally understood how to use the middleware after it is transplanted to arm.

Often run for the first timeProgramThis problem occurs,

"????????? Qdbusinterface? "Failed to connect to socket/usr/local/ARM/dbus-1.0.

2/var/run/clusters/system_bus_socket: Connection refused"

The reason is that the supervisor is not enabled.

Solution: CD/usr/local/ARM/dbus-1.0.2/bin/, run:

[Root @ friendlyarm bin] #
./Configure-daemon -- System
Failed to start message Bus: The PID file "/usr/local/ARM/dbus-1.0.2/var/run/mes
Sagebus. PID "exists, if the message bus is not running, remove this file

Switch to the directory where messagebus. PID is located and RM deletes it. Return to the bin of the worker to run../Configure-daemon -- system will run normally this time!

(Note that I have run the adduser Command yesterday! See yesterdayArticle.)

Switch to the my application directory again, and the prompt is displayed after running:

"????????? Qdbusinterface? "" The name org. freedesktop. Hal was not provided by any
. Service files"

Org. freedesktop. Hal was not provided by any. service files what does this mean? Google has no solution. This should not be the issue of failover. The tiny210 Development Board does not have Hal ???????????????????? Hope you can give me some advice!