afm-appli-hvac@0.1.service can't start

Description

I downloaded the source from https://git.automotivelinux.org/apps/hvac/ and successfully compiled hvac.wgt in the sdk environment.

But when I want to run on the target system, I am prompted with the following error.

root@qemux86-64:~/AGL-wgt# afm-util run hvac@0.1
Error org.freedesktop.DBus.Error.Failed: "can't start"

Nov 15 14:49:08 qemux86-64 afm-user-daemon[353]: ERROR: can't start user unit afm-appli-hvac@0.1.service [/usr/src/debug/af-main/eel+gitAUTOINC+d68c224367-r0/git/src/

 

This will have something to do with /etc/afm/afm-unit.conf. What configuration do I need to modify?

Environment

qemux86-64 AGL:5.03eel Kernel:4.10.17-yocto-standard sdk:poky-agl-glibc-x86_64-agl-demo-platform-crosssdk-corei7-64-toolchain-6.0.1.sh

Attachments

5

Activity

Show:

jose bollo 
November 16, 2018 at 8:24 AM

hi I'm very happy to read that you solved the issue. The fact that a library miss should be something that the installation should detect. I'm opening a bug to track progress in that direction: .

You asked about how to turn the display, I have to admit that the best way is to turn the display itself. I don't know how to do that for QEMU. A look to might help you.

You also asked whether you have to write your own service for writting an application. The answer is no. AGL divides its demo applications in two parts, the underlying service and the interfacing demo. this has the advantage for you that write demo that the existing services are available for free. When you need a service, it probably already exists. Then write in the config.xml that you need it and it will be available to your application.

If you have to write your how service, you can either link it to your application or bind it as a binding. The former way, by creating a binding is better because it will at the end allow you ot export your service to other applications. But it is not enforced. And even more in any case, it can be shipped with your application in the same widget.

Wang xiyuan 
November 16, 2018 at 6:57 AM
(edited)

The previous problem has been solved. I found that there is less lib in the packaged file. After repackaging, it can be successfully run.
But I still have two questions I would like to ask:
After I installed the system, the current interface is horizontal. Is there any way to make it stand up?
And is it true that every app needs to rely on a service to bind? If I want to write a demo myself, does it mean that I also need to write a corresponding service myself? 

Wang xiyuan 
November 16, 2018 at 3:44 AM

Yesterday I updated the latest system, the current version is:

AGL:6.0.1flounder

Kernel:4.12.21-yocto-standard

 

But the operation still fails. The prompt is:

qemux86-64:~/wgt# afm-util run hvac@0.1
null

Nov 16 11:25:30 qemux86-64 afm-system-daemon[441]: NOTICE: – INSTALLING widget /home/0/wgt/hvac.wgt to /var/local/lib/afm/applications – [/usr/src/debug/af-main/flo
Nov 16 11:25:30 qemux86-64 afm-system-daemon[441]: NOTICE: – UNINSTALLING widget of id hvac@0.1 from /var/local/lib/afm/applications – [/usr/src/debug/af-main/floun
Nov 16 11:25:47 qemux86-64 afm-system-daemon[441]: ERROR: can't start system unit afm-appli-hvac--0.1--main@.service for uid 0 /usr/src/debug/af-main/flounder+gitAUTOINC+bd95c04335-r0/git/src/afm-urun.c:258

[^afm-appli-hvac-0.1-main@.service]

jose bollo 
November 15, 2018 at 11:41 AM

Can you please add 2 documents:

  • the service file afm-appli-hvac@0.1.service (probably in /var/local/lib/systemd/user)

  • more errors of the journal if it exists (command journalctl)

Won't Fix

Details

Assignee

Reporter

Labels

Contract ID

Components

Due date

Priority

Created November 15, 2018 at 9:56 AM
Updated November 28, 2018 at 9:20 AM
Resolved November 20, 2018 at 5:41 PM