If you mean the borders on top and bottom, I got rid of them by this answer by ogra answer.
But no matter what I did I could not get rid of what I think is the “launcher”.
For the output, I ran “snap get ubuntu-frame display” and it printed the one I provided, for an output like you mentioned I had to run “snap logs -n 100 ubuntu-frame” from your answer here. And it prints
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: layouts:
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: default: # the current layout
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: cards:
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: # a list of cards (currently matched by card-id)
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: - card-id: 0
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: HDMI-A-1:
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: # This output supports the following modes: 1024x768@60.0, 800x600@60.3,
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: # 800x600@56.2, 848x480@60.0, 640x480@59.9
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: #
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: # Uncomment the following to enforce the selected configuration.
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: # Or amend as desired.
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: #
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: state: enabled # {enabled, disabled}, defaults to enabled
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: mode: 1024x768@60.0 # Defaults to preferred mode
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: position: [0, 0] # Defaults to [0, 0]
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: orientation: normal # {normal, left, right, inverted}, defaults to normal
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: scale: 1
2025-01-17T09:26:30Z ubuntu-frame.daemon[6347]: group: 0 # Outputs with the same non-zero value are treated as a single display
But its fullscreen and I’m more confused now. Why does it have a different resolution in the logs and in the “snap get ubuntu-frame display” is a mystery to me.
Could I be creating the ubuntu-core image in a faulty way or something? Is it an ubuntu-frame thing?