** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Confirmed
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug
So apparently the reason why it can't be duplicated to bug #982889 is
because of a performance issue in Launchpad (see
https://answers.launchpad.net/launchpad/+question/227581 for more info).
I don't really feel comfortable changing the bug status in that bug in
order to duplicate this bug, so I
Aha - I just stumbled upon bug #982889 (X trying to start before
plymouth has finished using the drm driver). It certainly looks like
this bug could be related.
It would have been nice if you guys had pointed me to that bug before
now - oh well.
--
You received this bug notification because
I just received a fix for bug #982889 via software updates. After that
I tried rebooting 6 times and every boot was successful! So I think
this was a duplicate of that bug all along.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Marking the Unity bug invalid and duping this bug to bug #982889 since
the bug reporter is pretty confident the lightdm/plymouth updates fix
this.
** Changed in: unity
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is
Well, I would mark this as a duplicate to bug #982889, but the Save
duplicate function of the Mark as duplicate feature has been broken
all day:/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Yes - I wanted to mark it as a duplicate of the same bug this morning,
but was blocked by the same problem!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Unfortunately I'm still seeing this with the latest Raring updates. I
have Linux 3.8.0-19-generic with xserver-xorg-video-intel
2:2.21.6-0ubuntu3. Chris, can you elaborate on the race condition here?
This is a race between which two entities - the X server and plymouthd?
And they're both racing
I reinstalled Raring from a daily build in the hope that might fix
things. It didn't: booting still usually, but not always, fails. To
recap what I've said above, when I boot one of three things typically
happens:
1. I'm left looking at a black screen with a mouse cursor on virtual terminal
7.
Unknown hw! Can you please attach the full Xorg.0.log for the failing
case 1?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes fails
There you go.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes fails to start on MacBook Air 5,2: no screens found
Status in Unity:
** Attachment added: Xorg.0.log after boot to black screen
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1161371/+attachment/3640884/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Looks like state initialisation failed, but it still would have been
able to use the BLT for everything... So I guess unity setup (libGL)
also failed. I think another variation on the race as it too is
transient.
--
You received this bug notification because you are a member of Desktop
Packages,
I think it is clear that there is a kernel error beyond that of the
plymouth race. Can you please try testing with the latest drm-intel-
nightly kernel from ppa:mainline?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
OK - I installed linux-
image-3.9.0-994-generic_3.9.0-994.201304060409_amd64 and rebooted. On
my first boot I saw a blank screen on VT7, and when I switched to VT1
and logged in I saw that X and plymouthd had just crashed as evidenced
by files in /var/crash. The X log, however, included no error
Yes, a crash is even more unexpected.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes fails to start on MacBook Air 5,2: no screens
[7.012094] init: gdm main process (1254) killed by TERM signal
Same bug as the lightdm race, but with gdm instead?
Looking at upstart files, it looks like plymouth-stop is running in
parallel with gdm, causing the race you see above..
The dependencies in plymouth-stop:
start on (starting
/etc/init/gdm.conf would also need to have the 'started plymouth-splash'
line..
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes
I wasn't even aware that I had gdm installed on my system! Ah, I see -
it's a dependency of gnome-shell, which I installed experimentally.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
I just added the 'started plymouth-splash' line to /etc/init/gdm.conf,
then tried rebooting. Unfortunately it still took me three tries to get
a successful boot. On the first attempt I was left looking at a screen
with boot text including
Starting LightDM Display Manager
Starting Recovery
Drat. I was hoping apport would grab the unity logs as well. In that
set, unity exits abnormally at the 27s mark (noted by the server regen
in Xorg.0.log and the dmesg.txt) but since X is still intact but with
nothing to display, it ends up black.
So far all bugs are pointing away from -intel
I'm happy to repro this again and grab the unity log if you like - just
let me know.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes
Timo,
I made that change, then booted 11 times. 4 of the 11 boots were
successful. The other 7 times I was left looking at a blank screen or
the Ubuntu logo. In those cases I was able to switch to virtual
terminal 1 and log in in text mode. I never once ended up in low-
graphics mode with the
** Attachment added: X log after boot into blank screen
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1161371/+attachment/3609730/+files/Xorg.blank.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Looks like unity failed to start in that case, but I think Maarten is
right in that the original bug is a repeat of the plymouth race. Can you
reproduce the blank screen, then run 'apport-collect 1161371' from the
vt?
--
You received this bug notification because you are a member of Desktop
apport information
** Tags added: apport-collected raring ubuntu
** Description changed:
I'm running Ubuntu 13.04 (Raring) on a MacBook Air 5,2. The machine has
an Intel HD Graphics 4000 (Ivybridge Mobile) graphics chip. I have
xserver-xorg-core version 2:1.13.3-0ubuntu4.
On
Done. In the blank screen state I also noticed that both X and
plymouthd had crashed as evidenced by files in /var/crash. I'll attach
those crash files too.
** Attachment added: _sbin_plymouthd.0.crash
** Attachment added: _usr_bin_Xorg.0.crash
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1161371/+attachment/3610703/+files/_usr_bin_Xorg.0.crash
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
could you try modifying /etc/init/lightdm.conf to match:
start on ((filesystem
and runlevel [!06]
and started dbus
and (stopped plymouth or started plymouth-splash)
...
that is, add 'and (stopped plymouth or started plymouth-splash)' there
and see if
The problem is that Xorg hasn't registered the igfx as the boot-vga
device and so is looking for a primary display and fails (it loads the
-intel as a secondary GPU only screen).
What is the value in '/sys/devices/pci:00/:00:02.0/boot_vga' ?
You can manually specify:
Section Device
Thanks for looking into this.
/sys/devices/pci:00/:00:02.0/boot_vga is 1.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes
** Package changed: xorg (Ubuntu) = xserver-xorg-video-intel (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes fails to start
why in hell did you bought an macbook.. :(
well, appl doesnt love other OS'ses so didnt support making drivers for
it, youd better go with an chromebook.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in
By the way, this is a regression from Quantal, where Ubuntu booted every
time without a problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes
Why is this bug incomplete? Is there more information you'd like from
me?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes fails to
** Tags added: no-screens
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes fails to start on MacBook Air 5,2: no screens found
The complete Xorg.0.log and dmesg would be a start.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes fails to start on MacBook Air
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1161371/+attachment/3604011/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Here they are. If there's anything else I can provide, don't hesitate
to ask.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes fails
By the way, I have xserver-xorg-video-intel version 2:2.21.5-0ubuntu1.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1161371
Title:
X server sometimes fails to
** Attachment added: dmesg
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1161371/+attachment/3604012/+files/dmesg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
42 matches
Mail list logo
