Thanks.
Comment #36 shows the bug:
DP-2 connected 1600x900+1366+0 (0x95) normal (normal left inverted right
x axis y axis) 798mm x 334mm
Comment #34 does not show the bug:
[ 6.555] (II) modeset(0): Output DP-2 using initial mode 2560x1080
+1366+0
So I wonder if those are from different log
apport information
** Description changed:
$ lsb_release -rd
Description: Ubuntu 19.10
Release: 19.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.34.1-1ubuntu1
Candidate: 3.34.1-1ubuntu1
Version table:
*** 3.34.1-1ubuntu1 500
500 http://us.archive.ubuntu.co
Thanks. Those attachments appear to have been created when the correct
resolution was in use:
[ 6.555] (II) modeset(0): Output DP-2 using initial mode 2560x1080
+1366+0
So they don't demonstrate the bug. I wonder can you please reproduce the
bug such that the wrong resolution is in use and th
apport information
** Tags added: apport-collected eoan ubuntu
** Description changed:
$ lsb_release -rd
Description: Ubuntu 19.10
Release: 19.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.34.1-1ubuntu1
Candidate: 3.34.1-1ubuntu1
Version table:
*** 3.34.1-1ubuntu1
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1859071
When reporting bugs in the future please use apport by using 'ubuntu-
bu
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859071
Title:
Secondary monitor unpredictable behavior at boot
To manage notifications about this bug go t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
