Hello everyone,
you can find the results from the testing cycle for 9.99.2 tag here:
Overall summary: unstable
Bluetooth*, ethernet and wifi are working.
Navigation, mixer messaging, contacts recents are working.
Observed issues:
I am hesitant to say/open a jira issue that m3ulcb has a problem with bluetooth audio - in order to get bluetooth audio playing on m3 - I had to restart bluetooth, bluealsa-gst-helper and agl-service-bluetooth, but this may be caused by the connman/agl-service-network race;
h3 also has shown issues with mediaplayer and metadata but appeared to be more stable.
Along with the regular pipewire warnings and errors mediaplayer segfaulted a couple of times on m3.
RPi4 also had similar symptoms regarding bluetooth, although it is known to have a peculiar behavior.
The issues related to mediaplayer do not have clear reproducibility pattern and happen often but intermittently.
Pipewire on RPi4 generates a massive logging journal (20MB in ~ 5 minutes) due to a lot of errors.
Known issues:
SPEC-3509 - agl-service-network failing to start properly
I said yesterday on the call that I didn't see it happening on h3 - systemd apparently restarts the service on failure and according to the journal there are immediate no error logs after the restart.
New issues:
SPEC-3518 - agl-compositor exits prematurely on upsquared
Upsquared booted properly the first time, however I usually need to switch the pipewire output sink to test audio, it refused to show GUI after that.
Minnowboard boots exactly the same image without issues related to the compositor.
Links:
You receive all messages sent to this group.
View/Reply Online (#8553) |
Reply To Group
| Reply To Sender
|
Mute This Topic
| New Topic
Your Subscription |
Contact Group Owner |
Unsubscribe
[list-automotive-discussions82@xxxxxxxxxxx]
