canonical / ubuntu-frame

The foundation for many embedded graphical display implementations
GNU General Public License v3.0
156 stars 21 forks source link

Wayland Socket Not Found Even After Successful Connection on Ubuntu Core 24 (Raspberry Pi 5) #193

Closed Luciogc closed 1 month ago

Luciogc commented 1 month ago

I'm trying to set up a web kiosk using wpe-webkit-mir-kiosk on Ubuntu Core 24 running on a Raspberry Pi 5. While the snap connection to Ubuntu Frame's Wayland interface appears to be established, the kiosk service fails to launch, continuously reporting that the Wayland socket is not available.

Steps to Reproduce:

  1. Installed wpe-webkit-mir-kiosk and Ubuntu Frame on Ubuntu Core 24 on a Raspberry Pi 5.
  2. Set the desired URL using sudo snap set wpe-webkit-mir-kiosk url=<my-url>.
  3. Enabled the service to start automatically: sudo snap set wpe-webkit-mir-kiosk daemon=true
  4. Connected the snap to Wayland: sudo snap connect wpe-webkit-mir-kiosk:wayland
  5. Started the service: sudo snap start wpe-webkit-mir-kiosk
  6. Observed repeated errors in the logs:
    Wayland socket not available, waiting one second...

Expected Behavior:

The kiosk should start up and display the specified URL.

Actual Behavior:

The kiosk service fails to launch, and the logs show the error mentioned above.

Additional Information:

Environment:

Possible Causes:

Potential Solutions (Attempted):

Additional Considerations for Raspberry Pi 5:

I would greatly appreciate any assistance in resolving this issue, especially considering the Raspberry Pi 5 context. Please let me know if there are any other details I should include. Thanks!

Saviq commented 1 month ago

@Luciogc thanks for the detailed report!

This looks suspiciously like https://github.com/canonical/ubuntu-frame/issues/192#issuecomment-2196675104, can you try changing dtoverlay= from fkms to kms in the config.txt file? I'll post the exact location in a few minutes.

EDIT:

Here: /run/mnt/ubuntu-seed/config.txt

Saviq commented 1 month ago

FYI: we'll be fixing Core 24 images to have kms by default, as fkms is not supported any more. Unclear how it works on my setup :shrug:.

Saviq commented 1 month ago

Please reopen if that doesn't help in your case.