I just encountered the bug again. When I turned on the monitor the login
screen is at 1024x768 and the system log shows it is using Wayland:
Jun 15 14:03:49 nine gnome-shell[1225]: Running GNOME Shell (using
mutter 42.1) as a Wayland display server
Although the monitor was plugged in when the system booted, the kernel
failed to get a working connection:
Jun 15 14:03:50 nine kernel: i915 0000:00:02.0: [drm] *ERROR* Link
Training Unsuccessful
That's _after_ the login screen had started. So the bug is occurring
when the kernel can detect a monitor (hence bug 1919400 doesn't happen)
but can't establish a reliable display signal.
For me, the fix was just to log in as usual. Then the correct screen
resolution is detected and used.
If the problem persists for you after logging in then it's a sign you
probably need to replug or replace the monitor data cable. I don't see
any real bug here unless it's the kernel failing to train when it
shouldn't fail.
** Package changed: xorg-server (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
** No longer affects: mutter (Ubuntu)
** Summary changed:
- Desktop resolution was set incorrectly (1024x768) until I booted up the PC
AFTER turning on the monitor
+ [i915] Desktop resolution was set incorrectly (1024x768) until I booted up
the PC AFTER turning on the monitor
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1976567
Title:
[i915] Desktop resolution was set incorrectly (1024x768) until I
booted up the PC AFTER turning on the monitor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976567/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
