On Mon, May 03, 2010 at 02:58:15AM -, Ernesto Manriquez wrote:
> I still have this around, with Lucid release.
That's not possible. This bug is specific to the interaction between
nouveau DRM and plymouth, and in the final Lucid release, plymouth does not
use the DRM backend on nouveau. You
I still have this around, with Lucid release. This bitter bug has also
bitten me with Fedora 12 and Fedora 13 Alpha, under AMD64. With Lucid,
I'm using the official CDs.
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You rec
I confirm the issue is fixed after an upgrade!
Many thanks guys!
Keep up the good work :)
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is
live CD 16-Apr-2010 I check. With my hardware (LCD (DVI) 'n' TV (DVI-
VGA) have booting good.
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which
plymouth 0.8.2-1 is included on the daily CDs for April 16. If you are
still having problems, it's not the same bug as this one.
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you
** Attachment added: "Console error message, maybe not related to this bug"
http://launchpadlibrarian.net/44496480/Screenshot-Supermicro.png
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notificati
I'm still noticing this issue with current-build live CD / Install
Ubuntu option from grub menu - http://cdimage.ubuntu.com/daily-
live/current/ 16-Apr-2010 08:30 695M Desktop CD for PC (Intel x86)
computers (standard download)
Will it take time to reach the current-build ?
Thanks
--
System f
This bug was fixed in the package plymouth - 0.8.2-1
---
plymouth (0.8.2-1) lucid; urgency=low
[ Steve Langasek ]
* New upstream release.
* debian/plymouth.plymouth-stop.upstart: trust the new kdm to stop plymouth
for us, too. LP: #540177.
* plymouth needs to depend on in
** Branch linked: lp:ubuntu/plymouth
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Beta2 LiveCD (and fresh install)
I also get this ; the system becomes unresponsive at "4 red dots".
Booting to a recovery console and replacing nouveau with nvidia-current
fixed the problem for me.
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.lau
This may be a kernel bug; tracked in bug #539655.
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Also affects: plymouth (Ubuntu Lucid)
Importance: Medium
Status: Triaged
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/43865938/lspci.txt
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Alt+SysReq+K is a workaround though.
** Attachment added: "dmidecode.txt"
http://launchpadlibrarian.net/43865894/dmidecode.txt
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because yo
I just nominated this for Lucid because it prevents the beta 1 or beta2
install disks from proceeding beyond the initial screen with the dots.
Kind of ironic, since the purpose of plymouth was to provide a smooth
boot experience.
Anyway, if this is not fixed for the release, Ubuntu is going to hav
With dual VGA card I'm able to successfully install Ubuntu 10.04 beta2
with the following procedure:
* Install Ubuntu 9.10 32/64-bit
* Update /etc/apt/source.list, Find Karmic, Replace with Lucid
* sudo apt-get update
* sudo apt-get install
Other changes I did:
* In Ubuntu 9.10 have installed Gru
Possible upstream bug:
https://bugs.freedesktop.org/show_bug.cgi?id=23813
** Bug watch added: freedesktop.org Bugzilla #23813
http://bugs.freedesktop.org/show_bug.cgi?id=23813
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/5331
I can confirm this bug too when trying to boot Lucid beta 2 from the
Live CD. Having two monitors connected to a Nvidia card hangs the boot
process exactly as described. There is no hang when only one monitor is
plugged in.
--
System fails to boot with plymouth installed (nouveau driver with >1
I believe I may also be experiencing this bug, with a brand-new install
of Lucid beta-2. The title certainly matches my problem.
lspci shows:
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200]
(rev a1)
...this card has one DVI and one VGA output. When both outputs are
c
I am also facing this issue. Thinkpad W700 with NVidia FX3700M. The boot on the
laptop with LVDS LCD screen is fine. Boot with laptop attached to a dock with 2
monitors (VGA and DVI-D) hangs with no key presses acknowledged.
I can work around the issue by booting in recovery mode or without "spla
I am also facing this issue. Thinkpad W700 with NVidia FX3700M. The boot
on the laptop with LVDS LCD screen is fine. Boot with laptop attached to
a dock with 2 monitors (VGA and DVI-D) hangs with plymouth running. I
can work around the issue by booting in recovery mode or without
"splash" parameter
fd 11 is /dev/dri/card0.
So, plymouth sends some ioctl to the gfx card and then decides to hang
completely.
Alt+SysRq+K on the plymouth terminal kills plymouthd and it allows gdm startup.
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net
After digging further I see that sometimes plymouthd does not receive
quit command, but when it does, it hangs with the following:
(me sends quit command):
read(6, "Q\2", 2) = 2
read(6, "\1", 1)= 1
read(6, "\0", 1)= 1
getsockop
I am experiencing this issue and I found plymouthd process running when it
should not be (at least it shuts down on my Aspire One netbook when GDM starts
up).
The plymouthd process is so stuck that it is not possible for gdb to attach to
it. It is not possible to kill plymouthd process with KILL
** Changed in: plymouth (Ubuntu)
Status: Incomplete => Triaged
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The theme plymouth-theme-spinfinity also breaks booting.
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
The ubuntu-logo and ubuntu-text themes are very different; if ubuntu-
text works, and ubuntu-logo does not, that implies a fault with the
renderer.
Could you try one of the other graphical themes (e.g. plymouth-theme-
spinfinity) and see whether it works or fails with that
** Changed in: plymouth
Same as Ruben, only the logo theme hangs the system.
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
For me it works with the Ubuntu text theme, but the system hangs with
the Ubuntu logo theme...
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which
Still broken for me.
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Just wanted to say: This bug is fixed for me now (not sure why).
Although the resolution of Plymouth changes while booting and it doesn't
quite look right I get successfully to the login.
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net/b
Experiencing this bug with a Sony Vaio VGN-FE41Z which has an LVDS
internal monitor and an external DVI-D connected via the docking
station. During start-up output is mirrored to the external monitor.
The display 'stops' with the plymouth splash screen and the message
"Press C to cancel checking d
I have the same problem. Can t booting live cd Ubuntu 10.04 beta1 when >1
display. But problem was began earlier( alpha3 10.04), when i update kernel
from 2.6.32-15 to 2.6.32-16, after reboot i had picture 1024 768 in the left
high corner my display(22 inch 1680 1050) (i had nvidia driver at t
I've been able to reproduce this here on a test machine.
** Changed in: plymouth (Ubuntu)
Importance: Undecided => Medium
** Changed in: plymouth (Ubuntu)
Status: New => Triaged
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://bugs.launchpad.net
psierra, please file a separate bug report for your issue.
** Summary changed:
- System fails to boot with plymouth installed
+ System fails to boot with plymouth installed (nouveau driver with >1 display)
--
System fails to boot with plymouth installed (nouveau driver with >1 display)
https://
Hi, I've the same issue with plymouth, my system doesn't at all. Tried to use
'S' 'I' 'F' or 'M' which appears on the screen nothing special besides a
message saying 'init: plymouth main process (341) killed by SEGV signal'
I'm using a presario CQ61, intel, no additional monitor
--
System fails
** Attachment added: "Xorg.0.log-single-output-plymout.txt"
http://launchpadlibrarian.net/4877/Xorg.0.log-single-output-plymout.txt
--
System fails to boot with plymouth installed
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
** Attachment added: "Xorg.0.log-double-output-plymout.txt"
http://launchpadlibrarian.net/4859/Xorg.0.log-double-output-plymout.txt
--
System fails to boot with plymouth installed
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
** Attachment added: "Xorg.0.log-double-output-noplymouth.txt"
http://launchpadlibrarian.net/4851/Xorg.0.log-double-output-noplymouth.txt
--
System fails to boot with plymouth installed
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of
I am confirming that booting with DVI-D cable attached fails as well with
nouveau.
Plymouth splash stays on the screen and X does not seem to be able to take over
the screens.
02:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8400M
G] (rev a1)
If splash is removed from commandl
I am afraid I am going to have to reopen this bug. Plymouth is still
hanging when i have two displays attached, i just got lucky after the
first reboot after the update to ~14.
Are there any log files I could provide that might be helpful? Now that
I know the alt+sysreq+k workaround I can provide
** Changed in: plymouth (Ubuntu)
Status: Fix Released => New
--
System fails to boot with plymouth installed
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
will confirm that the new version of plymouth fixed the problem.
--
System fails to boot with plymouth installed
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
This bug was fixed in the package plymouth - 0.8.0~-13
---
plymouth (0.8.0~-13) lucid; urgency=low
[ Steve Langasek ]
* Don't attach /proc/cmdline to apport reports, this is already in the
standard info that gets collected...
[ Alberto Milone ]
* ubuntu_logo theme:
-
haha okay i figured something was up since it did not do anything when
it was working, so i went and found an old standard keyboard and it
worked. I experimented with my main wireless keyboard and it turns out
the F lock was on causing my SysRq not to send a signal.
So yes, Alt+SysRq+K does reset
okay after testing that i unplugged the tv again and as usual with one
display hooked up it booted beautifully, but just to make sure i pressed
Alt+SysRq+K after it was completely booted and it did nothing, is this
normal or should it kill X or something similar?
--
System fails to boot with plym
Alt+SysRq+k did not do anything for me.
--
System fails to boot with plymouth installed
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
When the system is in this broken state after boot, please see whether
Alt+SysRq+K succeeds in resetting it.
** Changed in: plymouth (Ubuntu)
Status: New => Incomplete
--
System fails to boot with plymouth installed
https://bugs.launchpad.net/bugs/533135
You received this bug notification
plymouth 0.8.0~-12
The boot problems with ureadahead/plymouth have been documented, but with
today's updates 3-10-10 my system became unbootable. The system boots to an
empty Desktop on which two blinking cursors intermittently jump as if
proceeding along a text line, leaving a thin, garbled
yep after a fresh install i can confirm that plmouth only hangs with two
displays plugged in.
I have this bug pinned down as specifically as i can so this should be
the end of my comments :), if you need anymore info just ask i check my
email frequently and i am running lucid for the sole purpose
sorry I don't see a way to edit my comments. the bug referenced in post
7 should be bug 516412.
--
System fails to boot with plymouth installed
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
I did a little more work to try and isolate this bug, i removed the
nvidia proprietary driver and then unplugged the hdmi cable going to my
tv. I then restarted twice and both went amazingly, the plymouth splash
screen stayed up until my background image came up, first time i have
seen the boot wor
okay installed the nvidia proprietary drivers and did two soft restarts,
both worked great, then did a complete shutdown and power on and it also
worked great.
nouveau plus an nv50 card has got to be a pretty common setup for lucid
testers is no one else getting this bug?
--
System fails to boot
haha sorry for all the comments but I am trying to get as much info
about this bug as i can. I installed a few packages and ran sensors-
detect. I then shut it down, waited ten seconds and then powered it back
up. It failed to boot due to Plymouth hanging again, so i did a hard
shut down and tried
I tried another fresh install. The only significant change i made from
the default install was to install the updates. Where it stands right
now is that pressing restart causes the system to fail to boot, but if i
do a full shut down and then press the power button to start it up again
it boots.
-
Okay fresh install the problem came back after a few restarts,
unfortunately I am unsure what caused the problem to reappear. Once
again removing plymouth let the system boot normally.
** Changed in: plymouth (Ubuntu)
Status: Invalid => New
--
System fails to boot with plymouth installed
marking as invalid because a fresh install seems to have fixed the
problem. Hopefully it was just a strange quirk with my setup.
--
System fails to boot with plymouth installed
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: plymouth (Ubuntu)
Status: New => Invalid
--
System fails to boot with plymouth installed
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/40315022/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/40315023/CurrentDmesg.txt
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/40315024/Lspci.txt
** Attachment adde
59 matches
Mail list logo
