Hello everyone,
you can find the results from the test run here:
All of the platforms are booting, including qemux86-64 on qemu and VirtualBox.
Known issues:
- SPEC-3223 - WAM Sliders for Wifi and Bluetooth unresponsive
- SPEC-3224 - WAM Version Info in Settings menu is not working
- SPEC-3225 - "Scan" button in HTML5 Settings-Bluetooth app does not work
- SPEC-3227 - Unable to pair a device from Bluetooth settings HTML5 app
- SPEC-3228 - Unable to connect to a Wifi network from Wifi Settings HTML5 app
- SPEC-3229 - HTML5 Mediaplayer hides bluetooth metadata
- SPEC-3230 - HTML5 Mediaplayer does not show cover art
- SPEC-3859 / SPEC-3995 - Freezing web apps
- SPEC-3998 - Sometimes WAM has slow startup
- SPEC-4010 - Pipewire does not play some .wav formats on intel platforms
The chromium browser app is back. Doesn't seem to crash with multiple tabs, so even SPEC-3226 was marked as "won't fix", is actually fixed. Trying to open settings in it however makes it freeze. Youtube playback from it is actually pretty decent on h3ulcb-refhw/kf. Some hiccups on m3ulcb in the beginning, and a bit of audio popping on raspberrypi4(much rarely observed pops with local audio). Menus and config pages like "chrome://settings" for example have either broken font rendering or resource/translation files with texts are missing - text fields and labels are blank. Regular pages with media are fine and behavior is like a proper desktop browser with the exception of intel platforms which refuse to play most videos. I suspect it might be related to SPEC-4010 - I've seen this behavior on a completely regular desktop with broken pulseaudio for example. "wpctl status" shows that the mediaplayer app for example is in the clients list, but chromium does not register itself as a client on intel boards.
Mixer displays multiple channels but has the same behavior like settings - to see the reflected change you have to switch back and forth to homescreen.
HVAC has the same behavior like mixer and settings. input works better with a mouse.
Interface updates seem to work better and reflect changes immediately in runqemu/Virtualbox.
It seems that there is an issue redrawing the interface after an action.
Running qemux86-64.vmdk in Virtualbox causes a small message flood every 10 seconds with about 200 messages for 2 seconds with the following message but GUI seems to work:
```
[ 276.198236] [drm:vmw_kms_fb_create [vmwgfx]] *ERROR* failed to create vmw_framebuffer: -22
```
Best regards,
Eddie
_._,_._,_
Links:
You receive all messages sent to this group.
View/Reply Online (#9313) | Reply To Group | Reply To Sender | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [list-automotive-discussions82@xxxxxxxxxxx]
_._,_._,_