** Changed in: lightdm (Ubuntu Saucy)
Importance: Undecided => High
** Changed in: plymouth (Ubuntu Saucy)
Importance: Undecided => High
** Changed in: gdm (Ubuntu)
Importance: Undecided => High
** Changed in: gdm (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: gdm (
** 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"
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
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 Kubuntu
Bugs, which is s
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
Bugs, which is
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
T
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
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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X tr
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 Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before p
We have the same problem on the platfrom runs with Ubuntu 12.04.2 with
quantal backported.
I reviewed the raring patch from
https://launchpad.net/ubuntu/+source/xorg-server/2:1.13.2-0ubuntu3 and tried to
backport it to 12.04.2.
It looks work fine on our platfrom.
** Patch added: "drm_device_kee
Well I forwarded the patch to that closed bug anyway since look like
userspace race too ...
Next step would be to open a new one and update that patch (see TODO )
to see if upstream want to integrate this sleep workaround or give hints
to fix this elsewhere ...
--
You received this bug notificat
because it's not the same bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notifications about this bug
Wondering why this bug has not been forwarded upstream ?
https://bugs.freedesktop.org/show_bug.cgi?id=42972
does not mention about :
setversion 1.4 failed
nor https://bugzilla.redhat.com/show_bug.cgi?id=855677
Also I feel the patch worth to be forwarded/upstreamed too :
https://launchpad
** Branch linked: lp:~robert-ancell/lightdm/ubuntu-1.7.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage no
** Branch linked: lp:ubuntu/precise-updates/lightdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notific
Hello Tomas, or anyone else affected,
Accepted gdm into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/gdm/3.0.4-0ubuntu15.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
** Branch linked: lp:ubuntu/precise-proposed/gdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notificati
** Tags added: saucy
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notifications about
** Branch linked: lp:ubuntu/precise-proposed/lightdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notifi
ok - the fix might have been releaased but can someone please let those
idiots at intel open technologies know about the fix - i used theirrepos
to install the latest intel graphics stack - which then results i a
distro upgrade and whammo - had to put the "sleep 10" workaround into
/etc/init/lightd
** Branch linked: lp:ubuntu/raring-proposed/gdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notificatio
Hello Tomas, or anyone else affected,
Accepted gdm into raring-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/gdm/3.6.1-0ubuntu4.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
Either this fix isn't complete or I have a similar problem.
On my fast hardware (a Clevo W370ET with SSD and a quad core i7) I
observe the same effects. Even after updating to latest versions I get
the fault. I'm running raring (XUbuntu 13.04).
I observe at 50% of booting a black screen with a bl
On Wed, Jun 05, 2013 at 05:39:07PM -, William Pietri wrote:
> Aesthetically, making something vital (UI startup) depend on something
> decorative (splash screens) seems odd. Perhaps future versions of this
> can be made more robust.
To clarify, plymouth is not "merely decorative". It is the b
Thanks, Steve. The box was set up by a vendor (Emperor Linux), so
perhaps they did something custom with the splash screens when I got it
18 months ago.
Aesthetically, making something vital (UI startup) depend on something
decorative (splash screens) seems odd. Perhaps future versions of this
can
William, you have a broken upstart config on your system. The /etc/init
/plymouth-splash.conf system file has apparently been removed, by you,
another admin, or a filesystem error. To restore it, you should run
reinstall the plymouth package with the '--force-confmiss' option.
--
You received t
Hi! I suspect this fix may be causing a problem for me. I'm using an up
to date 12.04.2 LTS setup that worked fine until now.
My symptom is that upon reboot, I end up with a black screen. By hitting
Control-Alt-F1, I can get things working properly with "sudo service
start lightdm". Looking at the
** Changed in: oem-priority/precise
Status: In Progress => Fix Released
** Changed in: oem-priority
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launc
This bug was fixed in the package lightdm - 1.2.3-0ubuntu2.1
---
lightdm (1.2.3-0ubuntu2.1) precise-proposed; urgency=low
* lightdm.upstart: Add a start condition on plymouth-ready, and
drop conditions already handled by plymouth-splash (LP: #982889).
* control: Depend on the
This bug was fixed in the package plymouth - 0.8.2-2ubuntu31.1
---
plymouth (0.8.2-2ubuntu31.1) precise-proposed; urgency=low
* plymouth-ready.conf: Send an event to indicate plymouth is up. Needed
to inform login managers that they can start without racing with
plymouth-spl
** Branch linked: lp:~darkxst/ubuntu/raring/gdm/lp982889
** Branch linked: lp:~darkxst/ubuntu/precise/gdm/lp982889
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start befo
This bug was fixed in the package gdm - 3.6.1-0ubuntu6
---
gdm (3.6.1-0ubuntu6) saucy; 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 plymouth-sp
** Branch linked: lp:ubuntu/saucy-proposed/gdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notification
** Branch linked: lp:ubuntu/gdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notifications about this bu
** Changed in: gdm (Ubuntu Saucy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
After all the proposed packages work fine here.
I've installed them on 2 laptops and a desktop (all suffering from this issue )
and been using them for a week. I started up these hosts several times a day
and for the sake of testing I also rebooted them a couple of times every day
and each time
** Branch linked: lp:~darkxst/ubuntu/saucy/gdm/lp982889
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage not
** Changed in: gdm (Ubuntu Saucy)
Assignee: (unassigned) => Tim (darkxst)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the dr
** Tags removed: verification-failed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm drive
I reinstalled the proposed plymouth/lightdm packages, confirmed that I have the
unmodified files from both packages.
I rebooted my desktop 30 times in a row, not a single failure. If I happen to
experience the issue again I'll report back.
--
You received this bug notification because you are a
Miklos, please confirm the version numbers of both lightdm and plymouth
that you have installed, and please verify that all of the upstart job
files for both of these packages are the unmodified versions from the
package. If you already had a modified /etc/init/lightdm.conf on your
system, perhaps
The proposed version of lightdm/plymouth did not fix the issue for me. Lightdm
sometimes fails to start, see Xorg log attached.
For now I had to put back the "and stopped udevtrigger" workaround into
/etc/init/lightdm.conf. With that lightdm never failed to start for me.
** Attachment added: "Xo
Hello Tomas, or anyone else affected,
Accepted plymouth into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/plymouth/0.8.2-2ubuntu31.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
** Branch linked: lp:ubuntu/xorg-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notifications about
** Changed in: lightdm (Ubuntu Precise)
Importance: Undecided => High
** Changed in: lightdm (Ubuntu Precise)
Status: New => Triaged
** Changed in: lightdm (Ubuntu Precise)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: plymouth (Ubuntu Precise)
Importance: U
This bug was fixed in the package plymouth - 0.8.8-0ubuntu6.1
---
plymouth (0.8.8-0ubuntu6.1) raring-proposed; urgency=low
* plymouth-ready.conf: Send an event to indicate plymouth is up. Needed
to inform login managers that they can start without racing with
plymouth-splash
This bug was fixed in the package lightdm - 1.6.0-0ubuntu2.1
---
lightdm (1.6.0-0ubuntu2.1) raring-proposed; urgency=low
* lightdm.upstart: Add a start condition on plymouth-ready, and
drop conditions already handled by plymouth-splash (LP: #982889).
* control: Depend on the n
This bug was fixed in the package plymouth - 0.8.8-0ubuntu6.1
---
plymouth (0.8.8-0ubuntu6.1) raring-proposed; urgency=low
* plymouth-ready.conf: Send an event to indicate plymouth is up. Needed
to inform login managers that they can start without racing with
plymouth-splash
This bug was fixed in the package lightdm - 1.6.0-0ubuntu2.1
---
lightdm (1.6.0-0ubuntu2.1) raring-proposed; urgency=low
* lightdm.upstart: Add a start condition on plymouth-ready, and
drop conditions already handled by plymouth-splash (LP: #982889).
* control: Depend on the n
I have verified that these new package versions from raring-proposed do
fix the problem. Thanks!:
lightdm (1.6.0-0ubuntu2.1)
plymouth (0.8.8-0ubuntu6.1)
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of
** Tags added: verification-needed
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notifi
for the record, plymouth and lightdm updates available on raring-
proposed for testing
** Changed in: lightdm (Ubuntu Raring)
Status: In Progress => Fix Committed
** Changed in: plymouth (Ubuntu Raring)
Status: In Progress => Fix Committed
--
You received this bug notification bec
** Branch linked: lp:ubuntu/raring-proposed/lightdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notific
** Branch linked: lp:~tjaalton/lightdm/lp982889
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notificatio
** Also affects: kde-workspace (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Branch linked: lp:~tjaalton/plymouth/race-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notificati
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notifications about t
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the dr
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
Bugs, which is subscr
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
Bugs, whic
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
Bugs, which is su
** Changed in: oem-priority
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To mana
** Changed in: oem-priority/precise
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
T
** Changed in: lightdm (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has fini
+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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
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
Bugs, which is subs
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymout
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
Bugs, which is
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start b
@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
Bugs, which
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm drive
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X
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
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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/98288
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X t
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
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
1 - 100 of 171 matches
Mail list logo
