*** This bug is a duplicate of bug 1157614 ***
https://bugs.launchpad.net/bugs/1157614
I don't mind so long as we don't have a mysterious unresolved bug on our
hands! Thanks for your feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 1157614 ***
https://bugs.launchpad.net/bugs/1157614
Actually since, bug 1157614 was fixed I no longer get put into Low
Graphics mode. So I guess it is best to mark as a dup of that?
Not sure why, but bug 982889 never fixed it for me
** This bug has been ma
I don't understand: the fix for 982889 is to delay X starting
(technically lightdm starting) until plymouth finishes - which is
exactly the symptom you have.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => New
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Let me know what I need to do to change this from Incomplete
** Description changed:
After successfully installing 13.04 on my Dell XPS 15z, I restarted the
laptop, successfully booting into Ubuntu with no issues.
Restarting after that then gives the 'System is running in low graphics
After testing in bug 982889 I think we found I was never hitting the
same bug there, so I will unduplicate this for now
** This bug is no longer 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
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
64-bit 3.8.0-9-generic #18-Ubuntu SMP Thu Feb 28 17:02:06 UTC 2013
Desktop with Intel e8500 cpu, Nvidia GT9500 and default (non-Nvidia) video
driver.
I get this problem frequently following a restart from 12
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
Bryce, I have added sleep to lightdm.conf as mentioned in comment #5 in
bug 982889
This boots up perfectly everytime, even without the /etc/X11/xorg.conf
file I needed before
So I guess we can assume plymout
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
The xserver crash we'll follow up on as bug #1127023 which has full
stack trace info. The plymouthd race (actually we're not sure plymouth
is really the root cause) is effectively dupe of #982889, which is wh
apport-unpack can be used to decompress the .crash file to review things
locally, however note this doesn't run the apport hook itself, so it
contains a subset of the stuff usually collected into bug reports.
apport-collect run from the troubled machine will collect
the appropriate data files, an
I just noticed that Xorg.0.log file in /var/log/ if it helps
Again, I don't know which boot it's from
Should I delete those files and then repeat the boot?
** Attachment added: "Xorglog.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1125759/+attachment/353200
OK, I have attached the files from that folder, there are only one of
each, so I don't know how to tell which crash it's from?
** Attachment added: "lightdmlogs.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1125759/+attachment/3532002/+files/lightdmlogs.tar.g
Hmm, they should make sense to the bot, but I don't know what tools I
need to use on ubuntu to decode them. As it stands it didn't have the
information I was looking for.
There should be /var/log/lightdm/:0.log (and friends). See if you can
find one that corresponds to the crash upon boot.
--
Yo
Can you explain how to find this? I have searched my system for that
file name and nothing is found
I have 3 files in /var/crash/ if that helps?
See attached
** Attachment added: "xorgcrash.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1125759/+attachment/35
Can you attach the crashing Xorg.0.log from that boot, as I'd like to
see if the nouveau failure is related to that race? I don't think it is,
but it will be interesting nevertheless.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
"Does it boot up properly more often if you add 'plymouth.enable=0' to
the kernel boot options?"
So I removed the /etc/X11/xorg.conf file and added plymouth.enable=0
to the boot options (after quiet splash - correct?)
And no, it does not boot up properly, it still goes to low graphics mode
--
As for the nouveau crash, it looks like it does not correctly uncouple
itself from the BlockHandler chain upon removal - but I can't see
anything obvious there. (Time to look for a less obvious cause.) As for
why nouveau is removed and replaced with the modesetting driver???
--
You received this
Also note in the fbdev fallback case the error is inside RandR,
specifically it fails to check that the root window is not NULL before
calling xf86RandR12TellChanged() in
hw/xfree86/modes/xf86Crtc.c::xf86SetSingleMode(). See
sna_set_fallback_mode() for a comparison.
--
You received this bug notif
18 matches
Mail list logo
