** 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 Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs
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
Desktop Bugs, whi
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
Desktop Bugs,
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plym
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notifications
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm drive
** Branch linked: lp:ubuntu/precise-updates/lightdm
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To ma
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm 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 thi
** Branch linked: lp:ubuntu/precise-proposed/lightdm
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
T
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To man
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 Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpa
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X tryin
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To mana
** Changed in: gdm (Ubuntu Saucy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using
** Branch linked: lp:ubuntu/gdm
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notification
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
** Changed in: gdm (Ubuntu Saucy)
Assignee: (unassigned) => Tim (darkxst)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finish
** Tags removed: verification-failed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished usin
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage noti
** 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 Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notificat
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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To
** Branch linked: lp:~tjaalton/lightdm/lp982889
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To man
** 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
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.
61 matches
Mail list logo
