*** 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
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1130827/+attachment/3557091/+files/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1130827/+attachment/3538708/+files/CoreDump.gz
** Changed in: xorg-server (Ubuntu)
Im
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1130827/+attachment/3557090/+files/Stacktrace.txt
--
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:
S
StacktraceTop:
OsAbort () at ../../os/utils.c:1266
AbortServer () at ../../os/log.c:655
FatalError (f=f@entry=0x7ff1ad5ef118 "Cannot run in framebuffer mode. Please
specify busIDsfor all framebuffer devices\n") at ../../os/log.c:793
xf86PostProbe () at ../../../../hw/xfree86/common/xf8
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
Public bug reported:
in kvm in ubiquity-dm boot.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-core 2:1.13.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CasperVersion:
9 matches
Mail list logo