Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#51790 - [weston] Add --enable-systemd-notify to the build script
Attached to Project:
Community Packages
Opened by Andrea Giammarchi (webreflection) - Friday, 11 November 2016, 12:19 GMT
Last edited by Sébastien Luttringer (seblu) - Thursday, 12 January 2017, 23:44 GMT
Opened by Andrea Giammarchi (webreflection) - Friday, 11 November 2016, 12:19 GMT
Last edited by Sébastien Luttringer (seblu) - Thursday, 12 January 2017, 23:44 GMT
|
DetailsDescription:
The systemd-notify.so module is apparently the best way to start weston on boot and be notified once it's ready, avoiding possible UI artefacts or bootstrap issues for other applications. Additional info: * latest weston does not build with the flag --enable-systemd-notify * the module systemd-notify.so is not found once specified Steps to reproduce: Create a .config/weston.ini file with the following content in: [core] modules=systemd-notify.so launch weston see the missing module error. |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Thursday, 12 January 2017, 23:44 GMT
Reason for closing: Implemented
Additional comments about closing: weston-1.12.0-2
Thursday, 12 January 2017, 23:44 GMT
Reason for closing: Implemented
Additional comments about closing: weston-1.12.0-2