RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
There are several CRITICAL messages that appear right after start of boxes.

$ gnome-boxes 

(gnome-boxes:8440): Gtk-WARNING **: 15:31:25.244: GtkFlowBox with a model will ignore sort and filter functions

(gnome-boxes:8440): Gtk-WARNING **: 15:31:25.244: GtkListBox with a model will ignore sort and filter functions
WaylandCompositor requires eglBindWaylandDisplayWL, eglUnbindWaylandDisplayWL and eglQueryWaylandBuffer.
Nested Wayland compositor could not initialize EGL

(gnome-boxes:8440): GLib-GIO-CRITICAL **: 15:31:26.843: g_file_new_for_uri: assertion 'uri != NULL' failed

(gnome-boxes:8440): GLib-GIO-CRITICAL **: 15:31:26.843: g_file_get_basename: assertion 'G_IS_FILE (file)' failed

(gnome-boxes:8440): GLib-GIO-CRITICAL **: 15:31:26.845: g_file_new_for_uri: assertion 'uri != NULL' failed

(gnome-boxes:8440): GLib-GIO-CRITICAL **: 15:31:26.845: g_file_get_basename: assertion 'G_IS_FILE (file)' failed

Version-Release number of selected component (if applicable):
gnome-boxes-3.36.5-2.el8.x86_64

How reproducible:
always

Additional info:
I'll try to provide a backtrace, I tried already but apparently it takes a lot of resources and it is crashing my vm.

In the past Boxes was very sensitive about its error handling, everything was treated as critical. Now (in master, and for gnome 3.38) I reworked the criticality of most alerts. Those you pasted in the logs aren't really critical. They don't affect the application funcionality.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (libosinfo bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4758