*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has finished using the drm driver
--
You received this bug notification because you are a member of Ubuntu-X,
which
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
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/1130827
Title:
SIGABRT - cannot run in framebuffer mode [cirrus]
To man
neither of the attached xorg logs are from the failing case, but the
symptom sure sounds familiar
--
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/1130827
Title:
SIGABRT - cannot run in fra
Looks like yet another instance of the drm race condition (bug #982889).
** Summary changed:
- SIGABRT
+ SIGABRT - cannot run in framebuffer mode [cirrus]
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launc
[ 614.374] (WW) Falling back to old probe method for cirrus
[ 614.374] (--) Assigning device section with no busID to primary device
[ 614.374] (--) Assigning device section with no busID to primary device
[ 614.374] (WW) CIRRUS: More than one matching Device section found:
Autoconfigured
5 matches
Mail list logo
