Automatic hardware-observe connection request for ares-emulator

This request has been added to the queue for review by the @reviewers team.

I recorded this video to demonstrate what happens when I try to start it without hardware-observe. https://youtu.be/lh7idssUuK4?si=EcT3qxhhnNCZnPKq

1 Like

Hello @Kyuyrii and sorry for the late reply!

In the video you provided, I noticed the message: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.

I am not sure if this is a critical error or just a warning. Have you tried using snappy-debug? If you run it in a second terminal alongside your app, it will monitor for denials and suggest potential fixes. (#askForInfo)

1 Like

The Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try not to load it. is probably just a warning.

Honestly, I don’t know how to replicate the error from the video.

It appeared randomly, so when I stopped seeing it, I thought hardware-observe wouldn’t be necessary.

But whenever it happened, connecting hardware-observe solved the problem.

Perhaps looking at apparmor denials may provide some clarity about what happen. Could you please share the apparmor denials if any?

To do that, with the hardware-observe interface DISconnected

  1. Open a terminal and run `sudo dmesg -wH | grep DENIED`
  2. In a different terminal, start ares-emulator

I suppose I would have to replicate the problem that caused Ares to crash in order to test this.

Honestly, I have no idea what caused it.