Open AlanGriffiths opened 2 years ago
log with window-management-trace: miral-app.log
Huh, we size a fullscreen window to {0, 0}
? That's probably down to:
2022-08-17 17:54:55.534355] <information> mirserver: Initial display configuration:
[2022-08-17 17:54:55.534381] <information> mirserver: * Output 1: eDP connected, unused
[2022-08-17 17:54:55.534416] <information> mirserver: . |_ EDID manufacturer: LGD
[2022-08-17 17:54:55.534429] <information> mirserver: . |_ EDID product code: 1048
[2022-08-17 17:54:55.534444] <information> mirserver: . |_ Physical size 13.9" 310x170mm
[2022-08-17 17:54:55.534456] <information> mirserver: . |_ Power is off
[2022-08-17 17:54:55.534468] <information> mirserver: * Output 2: DisplayPort disconnected
[2022-08-17 17:54:55.534480] <information> mirserver: * Output 3: HDMI-A disconnected
[2022-08-17 17:54:55.534492] <information> mirserver: * Output 4: DisplayPort disconnected
[2022-08-17 17:54:55.534504] <information> mirserver: * Output 5: HDMI-A disconnected
And no outputs?!
And (now the snap has built), there's no problem with Ubuntu Frame:
frame-it mir_demo_client_wayland_egl_spinner
Works consistently
...and sure enough Frame has a sensible "Initial display configuration"
We don't get a clear diagnostic when we have no active outputs.
The reason for the original report is I had a forgotten
~/.config/miral-kiosk.display
lying around which explicitly disabledePD-
, and the external display it enabled wasn't connected.We should probably have a better failure mode for this case (it took me a couple of hours to track down, most users would give up), but it isn't a blocker for the release.
Original report
Found testing #2562
This is on 22.04, running on a VT
(The "terminal" doesn't seem to matter, as I first saw this with the default gnome-terminal)
Expect: Application displays Actual: Nothing displays
Log: miral-app.log
The same command works on the desktop (X11 platform) and switching to
miral-shell
ormir_demo_server
works fine