Weston fails to load after second boot
Description
Environment
Attachments
Activity
Walt Miner August 21, 2017 at 3:59 PM
gerrit 10111 for master. 10209 for dab
Martin Kelly August 4, 2017 at 4:45 PM
I see this is fixed . Do you have a patch to link to?
Jan-Simon Moeller July 5, 2017 at 7:34 PM
IIRC that is not the case - runqemu is a target (or we would not build the qemux86-64) at all. So this bug is still open.
We might need to fix a few of the QB_* variables to make it work, so patches are welcome.
Martin Kelly July 5, 2017 at 6:34 PM
I didn't know runqemu was not officially supported; it's the only thing I use, as I find it far more convenient for quick command-line development and iteration than virtualbox. I really don't think letting runqemu be broken and closing this bug is a good idea. IMO at the very least, we should keep the bug open, as it is a real bug affecting multiple people.
Ronan, did you try also with KVM? runqemu can be used both with and without KVM, and using KVM may change the timing.
That said, this is interesting, as the Qt crash seems like a new bug, separate from the one originally reported.
ronan Le Martret July 3, 2017 at 6:02 PM
Hi Martin,
I do some test:
1) build the last agl master.
2) test image agl-demo-platform (with runqemu and virtualBox).
Status:Qemu image on
a) with runqemu:
Weston OK
Homescreen KO
b) with virtualBox:
Weston OK
Homescreen OK
3) conclusion
a) Weston is always up, even after multi reboot, on runqemu and virtualBox.
b) Homescreen Failed with runqemu only. I can live with that, using "runqemu" is not officially supported by AGL.
"""
Jul 03 17:10:40 qemux86-64 kernel: HomeScreen[3710]: segfault at 58 ip 00007fb1855270eb sp 00007ffe67cebf10 error 4 in libQt5Core.so.5.8.0[7fb185274000+528000]
Jul 03 17:10:40 qemux86-64 kernel: audit: type=1701 audit(1499101840.490:62): auid=0 uid=0 gid=0 ses=3 subj=System pid=3710 comm="HomeScreen" exe="/usr/AGL/homescreen/HomeScreen" sig=11
Jul 03 17:10:40 qemux86-64 audit[3710]: ANOM_ABEND auid=0 uid=0 gid=0 ses=3 subj=System pid=3710 comm="HomeScreen" exe="/usr/AGL/homescreen/HomeScreen" sig=11
Jul 03 17:10:40 qemux86-64 kernel[212]: [ 489.822681] HomeScreen[3710]: segfault at 58 ip 00007fb1855270eb sp 00007ffe67cebf10 error 4 in libQt5Core.so.5.8.0[7fb185274000+528000]
"""
So, I think we should close this issue.
Regards,
Ronan
On various tested platforms (RPI3, qemu, and likely others) Weston fails to load after second or third boot with this message.
# cat /run/platform/display/weston.log
Date: 2017-05-16 UTC
[23:23:17.360] weston 1.11.0
http://wayland.freedesktop.org
Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.11.0
Build: 1.10.93-2-g2d825ed configure.ac: bump to version 1.11.0 for the official release (2016-05-31 17:10:40 -0700)
[23:23:17.360] OS: Linux, 4.4.50, #1 SMP Tue May 16 23:43:56 UTC 2017, armv7l
[23:23:17.360] warning: XDG_RUNTIME_DIR "/run/platform/display" is not configured
correctly. Unix access mode must be 0700 (current mode is 770),
and must be owned by the user (current owner is UID 200).
Refer to your distribution on how to get it, or
http://www.freedesktop.org/wiki/Specifications/basedir-spec
on how to implement it.
[23:23:17.409] Using config file '/etc/xdg/weston/weston.ini'
[23:23:17.461] Output repaint window is 7 ms maximum.
[23:23:17.481] Loading module '/usr/lib/weston/drm-backend.so'
[23:23:17.638] initializing drm backend
[23:23:17.647] logind: not running in a systemd session
[23:23:17.647] logind: cannot setup systemd-logind helper (-6), using legacy fallback
[23:23:17.652] couldn't open /dev/dri/card0, skipping
[23:23:17.652] failed to initialize kms
[23:23:17.710] fatal: failed to create compositor backend
This can be worked around with adding the line to the weston.service:
ExecStartPre=/bin/chmod 700 /run/platform/display