** Changed in: xorg-server-lts-quantal (Ubuntu Precise)
Status: Triaged => Won't Fix
** Changed in: xorg-server-lts-quantal (Ubuntu Precise)
Milestone: ubuntu-12.04.4 => None
** Changed in: xorg-server-lts-quantal (Ubuntu Precise)
Assignee: Maarten Lankhorst (mlankhorst) => (unass
Just confirming that on 15.04 I get the symptoms mentioned in
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1115177
Where Nouveau won't load, which is apparently because of this bug
[ 27074.122] (II) [drm] nouveau interface version: 1.2.1
[ 27074.122] (II) Loading sub module "dri2"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kde-workspace (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server-lts-quantal in Ubuntu.
https://bugs.l
I know rather old thing, but this got irritating me now. one bit of
info:
This shows that plymouth-ready is after lightdm...
/var/lib/plymouth/boot-duration
0.978:avahi-daemon
0.979:statd
0.979:udev-finish
0.993:rc-sysinit
0.993:rc
0.993:tty4
0.993:tty5
0.993:acpid
0.993:anacron
0.993:tty2
0.993
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kde-workspace (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server-lts-quantal in Ubuntu.
https://bugs.launchpad
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: kde-workspace (Ubuntu Saucy)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subsc
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: kde-workspace (Ubuntu Raring)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is su
The gdm oackages in raring and precise-proposed have been released so
removing the verification-needed tag.
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server-lts-quantal in Ubuntu.
https://bugs.laun
This bug was fixed in the package gdm - 3.0.4-0ubuntu15.2
---
gdm (3.0.4-0ubuntu15.2) precise; urgency=low
* Merge changes from lightdm to fix plymouth race (LP: #982889)
- lightdm.upstart: Add a start condition on plymouth-ready, and
drop conditions already handled by ply
This bug was fixed in the package gdm - 3.6.1-0ubuntu4.1
---
gdm (3.6.1-0ubuntu4.1) raring; urgency=low
* Merge changes from lightdm to fix plymouth race (LP: #982889)
- lightdm.upstart: Add a start condition on plymouth-ready, and
drop conditions already handled by plymou
** Branch linked: lp:ubuntu/precise-proposed/plymouth
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/plymouth/precise-
updates
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server-lts-quantal in Ubuntu.
https://bugs.launchpad.net/bu
Maarten, is this something you could have a look at?
** Changed in: xorg-server-lts-quantal (Ubuntu Raring)
Status: New => Invalid
** Changed in: xorg-server-lts-quantal (Ubuntu Saucy)
Status: New => Invalid
** Changed in: xorg-server-lts-quantal (Ubuntu Precise)
Status: New
** Also affects: xorg-server-lts-quantal (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server-lts-quantal in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start be
Ok I have the necessary changes tested locally, and they seem to work
when plymouth is started from the initrd too.
** No longer affects: xorg-server (Ubuntu)
** No longer affects: linux (Ubuntu)
** Also affects: plymouth (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affe
** No longer affects: libdrm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notifications
Same problem here. A sleep 10 workarounnd solved it, but can't we have a
fix ?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using
Moving to High prio in oem-priority since we have a workaround.
** Changed in: oem-priority
Assignee: (unassigned) => James M. Leddy (jm-leddy)
** Changed in: oem-priority/precise
Assignee: (unassigned) => James M. Leddy (jm-leddy)
** Changed in: oem-priority/precise
Importance: Cri
Hi,
had the same problem.
/etc/init/lightdm.conf:
...
sleep 2
exec lightdm
...
sleep 2 was enough to solve the problem for me.
i am using intel graphics an a l520 with a ssd (msata)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
So, the proposed change from #115 doesn't work if plymouth is started
from the initramfs, like when cryptsetup is used. In such a case no
'started plymouth-splash' is ever emitted, so something else needs to be
used:
00:34 < tjaalton> slangasek: heh, yeah. I was wondering if there was some more
g
plymouth:debug log from a failed boot from tjaalton
** Attachment added: "plymouth-debug-bad.txt"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3637580/+files/plymouth-debug-bad.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which i
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/982889
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu-X,
which is subsc
** Changed in: oem-priority
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
** Changed in: oem-priority/precise
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/precise
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority/precise
Importance: Undecided => Critical
-
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm dr
** Changed in: lightdm (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm d
On Wed, Mar 27, 2013 at 07:14:39AM -, Franck wrote:
> Just a question: what if the no-splash is passed as a boot option ?
That only controls whether you have a graphical splash, not whether the
plymouth-splash job runs.
> Or if plymouth is removed ?
That is absolutely unsupported.
--
You r
Just a question: what if the no-splash is passed as a boot option ? Or
if plymouth is removed ?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth h
+1 for this change. It should be safe because plymouth-splash is only
ever started once at boot, so there's no risk of 'and started plymouth-
splash' causing a maintainer script hang at package upgrade time.
Since plymouth-splash itself waits for the video device before starting,
I think the ligh
I can confirm that adding 'and started plymouth-splash' after the 'and
dbus' line in /etc/init/lightdm.conf , as Maarten suggests, does fix the
problem for me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchp
Wrong, in any case the race happens because plymouth-splash is racing
against lightdm. if you add 'and started plymouth-splash' after the 'and
dbus' line in /etc/init/lightdm.conf the race should be gone.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscri
Those errors show that X is running without the correct privileges; that
has nothing to do with Plymouth.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before
Just fixed for me, but it seems that last update in Lightdm and / or
upstart broke things again. Symptoms are not quite the same, but the
issues might be related...
Now X fails with these messages:
[ 4.746] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[ 4.746] (WW) xf86Ope
I'm also affected by this #969489 which I solved by always restarting lightdm
in my /etc/rc.local
But still I get a Xorg crashreport after starting once in a while, so maybe
those two bugs are also related?
--
You received this bug notification because you are a member of Ubuntu-X,
which is sub
Woops, judging from the activity log it looks like you did attach it, it
just doesn't show up in the comments somehow.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to
@Maarten. Sorry, forgot to attach it and did it on a second post. Here
it is.
** Attachment added: "Works."
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3581439/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Yes xorg log of working would be nice, but I don't see it attached. ;-)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the dr
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3581229/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Tit
The problem(s) seem to be fixed for me. No more boot delay, lightdm starts
fine, no console appearing...
My boot time is under 10 sec.
No warning or anaivalable drm in Xorg.0.log... Kind of miraculous :-)
Attached are my logs, in case this matters.
--
You received this bug notification because
I posted a new version of the patch that should fix xorg-server, it
should be in 1.13.3-0ubuntu1.
However it might not be enough to make things work, since there might
still be bugs in plymouth and lightdm
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Also affe
** Attachment added: "Latest Xorg.0.log amd64"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3571594/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bug
Sorry for duplicate post... can't seem to attach my log. Last try :-)
** Attachment added: "Xorg.0.log, PPA at 20130313"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3571621/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Here is a Xorg.0.log with new patch (under amd64).
Regarding the whole boot process, I didn't get the 10 sec stale at the very
beginning at the boot process that was in my latest bootchart graph... but this
might be totally unrelated, I don't know.
** Attachment added: "Xorg.0.log"
https://b
Here is a Xorg.0.log with new patch.
Regarding the whole boot process, I didn't get the 10 sec stale at the very
beginning at the boot process that was in my latest bootchart graph... but this
might be totally unrelated, I don't know.
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.
Alrighty, I've posted an update to the PPA for folks to test.
https://launchpad.net/~bryce/+archive/lp982889/
As before, it looks like i386 has built, but amd64 is having some
troubles - I've restarted it and hope it'll build by morning. Those of
you on amd64 who are comfortable building packages
[14.278] (II) config/udev: Adding drm device (/dev/dri/card0)
[14.716] drm device access denied
[15.140] drm device access denied
[15.568] drm device access denied
[15.992] drm device access denied
[16.415] drm device access denied
[16.844] drm device access denied
[
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3567859/+files/syslog
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X
** Attachment added: "Xorg.log"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3567860/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title
** Attachment added: "bootchart"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3567858/+files/franck-ThinkPad-T430s-raring-20130311-2.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bug
Here are some materials about what I see happen here:
- a video showing how the console shows after plymouth and before X comes back
- a bootchart
- syslog
- Xorg.0.log
There is indeed a huge gap (10 seconds) without any activity at the beginning
of the boot, maybe not related to X, but still he
The flip/flap I don't know about; this patch shouldn't *cause* that
afaict. Maybe that relates to the underlying bug though.
The patch does cause a delay in the boot, just the nature of the beast.
However it's set to 2 sec. If you're seeing a 5-20 sec delay, that's
longer than I would think it s
thanks Bryce.
One question: this workaround results in a flip-flap between console mode /
graphical mode during boot, and a 5 to 20 seconds delay in the boot. This is
better than lightdm failing to start, but not the best we can aim...
So my question is: should I open another bug report, maybe me
This bug was fixed in the package xorg-server - 2:1.13.2-0ubuntu3
---
xorg-server (2:1.13.2-0ubuntu3) raring; urgency=low
* Add drm_device_keep_trying.patch: When kernel reports drm device is
not available, don't give up immediately, but keep retrying for a
little bit. Fixe
Thanks Adam and Bruce - for those logs it looks like you just lucked out
and didn't hit "the bug", but that at least verifies the patch doesn't
introduce any regressions. I'll go ahead and upload it. It's probably
going to be largely random whether or not you hit the bug, but with the
patch hopef
This is the failed crash file
** Attachment added: "_usr_bin_Xorg.0.crash"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3560650/+files/_usr_bin_Xorg.0.crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm i
This is the failed log
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3560649/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launch
xserver-xorg-core:
Installed: 2:1.13.2-0ubuntu3~lp982889~2
Which I guess means the newer build is installed?
I'm having more success with this one. Before it was failing everytime,
now it fails about 50% of the time.
I have got logs of the successful boot and failed boot if that helps
This a
Here is my log with latest from PPA.
** Attachment added: "Xorg.0.log, PPA at 20130306-0900"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3559875/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to l
Would love to apply but running quantal
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notification
I've polished up the patch and tweaked it to give more informative error
messages. I've stuck the patch into the PPA if anyone would like to
test.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/
Thanks everyone for the recent testing. In comparing everyone's logs
the following observations can be drawn:
1. The assertions made in comment #11 are incorrect. We are not seeing
EAGAIN (error code 11) but apparently EACCES (error code 13).
2. The patch I prepared is suited for handling EAG
On Tue, Mar 05, 2013 at 02:57:55AM -, Adam Bruce wrote:
> Apport won't let me report as it's not an official package
>
> I don't know if you can make use of the crash file itself?
>
> Otherwise let me know how I can report it to you
Thanks, yes I know how to unpack .crash files. The file co
Apport won't let me report as it's not an official package
I don't know if you can make use of the crash file itself?
Otherwise let me know how I can report it to you
** Attachment added: "_usr_bin_Xorg.0.crash"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3557761
On Tue, Mar 05, 2013 at 01:13:39AM -, Adam Bruce wrote:
>
> It did not boot successfuly though and went to Low Graphics mode. There
> is a crash report if you want me to upload that as a report. But I don't
> know if it will just be the same as: bug 1130667 - let me know if you
> want me to po
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3557630/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982
I ran apt-cache policy xserver-xorg-core yesterday and realised the
patched hadn't been applied when I originally posted my Xorg logs.
I saw a update today from your PPA and now I see
xserver-xorg-core:
Installed: 2:1.13.2-0ubuntu3~lp982889~1
So it has now been applied. I guess this was due to
I have compiled xorg-server from PPA localy. So now I have tried it, and "kind
of" works. Not really satisfactory, although.
What happens is that lightdm end up starting, BUT in the meantime, I have a TTY
console showing off (ie no plymouth), and it takes a looong time.
Here is the log of such a
Still no amd64...
>From the PPA status page:
Build status
[CANCELLED] Cancelled build
Started on 2013-03-03
Finished 8 hours ago (took 20 hours, 38 minutes, 42.3 seconds)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
All 5 boots produced a usable X session. I haven't had a problem booting up
successfully since the 1st. By cold boot I just mean a normal power on
after a normal power off. In actual fact I haven't had to do a hard reset
(or manually hold down the power button to power off and then power on
again),
On Sun, Mar 03, 2013 at 06:39:55PM -, Mark Murphy wrote:
> I think I was a bit confused this morning!
>
> I've done a few cold boots and restarts since then, I've included them
> in the attached file. I included all the Xorg log files in the first
> directory. The first four directories in th
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.04.
Pressing the reset button or executing a FULL power shutdown prior to
completion of
On Sun, Mar 03, 2013 at 04:06:47PM -, Franck wrote:
> Build for amd64 running for 12 hours and an half, and ils still
> ongoing... ils that expected ??
Yes, unfortunately. PPA rebuilds are executed at the lowest priority,
and it's possible all the ARM virtualized builds for phone stuff may be
I think I was a bit confused this morning!
I've done a few cold boots and restarts since then, I've included them
in the attached file. I included all the Xorg log files in the first
directory. The first four directories in the tar contain log files from
cold boots, the last one is a reboot.
apt
On Sun, Mar 03, 2013 at 10:50:43AM -, Mark wrote:
> Hmmm, I was fairly sure I added the PPA, it's in my sources.list. I did
> another apt-get update and dist-upgrade this morning though and the Xorg
> build date didn't change, so I'm not sure what I'm doing wrong. I can
> tarball up the Xorg.0.
Build for amd64 running for 12 hours and an half, and ils still
ongoing... ils that expected ??
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth h
Just looking at the dpkg log myself and noticed this:
2013-03-01 07:31:31 upgrade xserver-xorg-core:i386 2:1.13.2-0ubuntu2
2:1.13.2-0ubuntu3~lp982889~1
2013-03-01 07:31:31 status half-configured xserver-xorg-core:i386
2:1.13.2-0ubuntu2
2013-03-01 07:31:31 status unpacked xserver-xorg-core:i386 2:1
Hmmm, I was fairly sure I added the PPA, it's in my sources.list. I did
another apt-get update and dist-upgrade this morning though and the Xorg
build date didn't change, so I'm not sure what I'm doing wrong. I can
tarball up the Xorg.0.logs as they are if you wish but I'm not sure if they
would be
On Sat, Mar 02, 2013 at 04:34:00PM -, Franck wrote:
> I was quite sure I activated the PPA, and it failed. But looking at the
> version in Xorg.0.log, it seems I didn't get the right version. I did
> not pin any specific version... Looking at what is installed, I only
> have xerver-common comin
I was quite sure I activated the PPA, and it failed. But looking at the
version in Xorg.0.log, it seems I didn't get the right version. I did
not pin any specific version... Looking at what is installed, I only
have xerver-common coming from the PPA...
And looking at the PPA web page, it seems tha
On Fri, Mar 01, 2013 at 08:03:17AM -, Mark Murphy wrote:
> Installed PPA, rebooted, aok. Rebooted / Shutdown another couple of
> times to be sure, every restart successful. It looks like the PPA works
> for me, Raring Ringtail development branch with Intel GM965 graphics.
>
> ** Attachment add
On Fri, Mar 01, 2013 at 08:03:17AM -, Mark Murphy wrote:
> Installed PPA, rebooted, aok. Rebooted / Shutdown another couple of
> times to be sure, every restart successful. It looks like the PPA works
> for me, Raring Ringtail development branch with Intel GM965 graphics.
>
> ** Attachment add
Tested the PPA: it still fails here. Attached is the log...
I'm availalbe to do test whatever is needed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before p
Sorry, wrong attachment file extension... here it is.
** Attachment added: "Failed with PPA"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3552485/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to l
Installed PPA, rebooted, aok. Rebooted / Shutdown another couple of
times to be sure, every restart successful. It looks like the PPA works
for me, Raring Ringtail development branch with Intel GM965 graphics.
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+
Bryce, would love to try this but I'm a bit worried that this is a
raring PPA with for example xserver-common 2:1.13.2-0ubuntu3 based
package and my system (12.10) has 2:1.13.0-0ubuntu6.1 installed. Warning
bells in my head say upgrading could break my work computer.
What do you think? Any chance
I need someone to install the xserver from this ppa, and verify it fixes
the issue:
https://launchpad.net/~bryce/+archive/lp982889
All the Xorg.0.log files posted since I mentioned this PPA are from the
stock xserver (or older). What we need is an Xorg.0.log from a session
with this PPA insta
I just have a plain old hdd, no ssd.
On Feb 28, 2013 8:41 a.m., "Franck" wrote:
> Yes, SSD too here. but I guess this ain't extraordinary nowdays... Also
> this most probably has an impact, as it seems to be a race condiction...
>
> --
> You received this bug notification because you are subscrib
Yes, SSD too here. but I guess this ain't extraordinary nowdays... Also
this most probably has an impact, as it seems to be a race condiction...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982
Mine has an ssd too, ocz agility 3 120GB. Maybe loading certain parts of
the system too fast make this happen if there aren't any checks
On Feb 28, 2013 8:06 AM, "Jason Robinson" wrote:
> ** Attachment added: "Xorg.0.log.old"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/982889/+
Yesterday booted first time, today took 5 times. Computer has SSD if
that has something to do with things (timings).
Xorg logs logs attached. Interesting ending to the .old log :)
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/982889/+attachment/3
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/982889/+attachment/3550695/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bug
I also just had a success on rebooting ! Here is the relevant
Xorg.0.log. Hopes that helps.
** Attachment added: "Successful Xorg.0.log on reboot"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3549545/+files/Xorg.0.log.ok
--
You received this bug notification becau
On 13 Feb 19, Bryce Harrington wrote:
> Oh, and if you do run the PPA, I'd like to see your Xorg.0.log,
> regardless of whether it worked or not, so I can verify the error code
> being passed up.
Please find my Xorg.0.log and Xorg.0.log.old attached. I see Xorg win
sometimes (1 out of 5 reboots?).
in ubiquity-dm installer, we pre-empt lightdm. Then execute "plymouth
deactivate" followed by "plymouth quit" if plymouth does not have an
active-vt. Then we start Xorg straight away, if Xorg fails to start, we
retry with modified 'fallback' configs using fbdev and finally vesa. I
guess in ubiquity
@Franck, yes the bugs belong in the same general class of issue (race
condition with drm), but the stacktraces and code paths differ so the
patch does not address the type of fault you saw.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm i
@Bryce: Chris Wilson commented on bug #1129220 saying both bugs are really
related. I quote:
"It is that bug. What's changed in the meantime is Xorg now has a platform
probe first so hits the error even earlier."
--
You received this bug notification because you are a member of Ubuntu-X,
which
@Adam, thanks; will follow up on bug 1130667 for the crash.
@Franck, thanks for reopening #1129220; will re-review and follow up
there.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Tit
On Wed, Feb 20, 2013 at 02:18:25PM -, Tomas Vanderka wrote:
> I don't think the patch from #31 will fix this because X is really
> getting EACCESS (0xfff3) not EAGAIN as can be seen in #22
No it will; I don't check for EAGAIN specifically yet, but just a
non-zero return. I want to make it
I don't think the patch from #31 will fix this because X is really
getting EACCESS (0xfff3) not EAGAIN as can be seen in #22
I also think this is probably an issue in plymouth because plymouth is
told to quit and release drm before X starts but it somehow does not
allways do this in time. Mayb
Ok, I reopen bug report #1129220 as it is not an exact duplicate...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm dr
1 - 100 of 122 matches
Mail list logo
