Public bug reported:
Binary package hint: gdm
Since the gdm upstart rule was changed to start very early (graphics-
device-added fb0 or drm-device-added card0), I only get a working
startup in about one out of ten cases:
(1) standard 80x25 VT appears for some seconds
(2) KMS gets switched on, and I see a big text VT for a fraction of a second
(3) X.org starts up
But in 9 out of 10 cases I just see (1), then lots of flickering, and
eventually an X.org "low graphics" dialog (which is utterly distorted
when the laptop runs standalone with internal screen, and looks fine
when I have the external screen attached, for some curious reason). In
this case the VTs are broken as well ("frequency not supported" monitor
message, and otherwise black).
It seems that KMS and X.org start at roughly the same time, and thus
fight each other. Can we introduce a signal that fires only when KMS has
actually finished its setup, instead of begin setup?
** Affects: gdm (Ubuntu)
Importance: High
Assignee: Scott James Remnant (scott)
Status: New
** Tags: regression-potential ubuntu-boot
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
** Tags added: ubuntu-boot
** Changed in: gdm (Ubuntu)
Importance: Undecided => High
** Tags added: regression-potential
--
gdm starts too early, races with KMS, X.org/VTs fail
https://bugs.launchpad.net/bugs/502838
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
