Seems to be fixed after applying todays Updatemanager patches. Tested
with bot cold boot and reboot.
Thanks for the quick fix!
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You received this bug notification because you are
An update from 2 weeks ago fixed this for me, but today I had another
interesting variation: after checking the disk during boot, it reverted
back to tty1.
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You received this bug
On Wed, 2010-03-17 at 03:19 +, teh603 wrote:
> Massive improvement over before, but its still a little rough. The
> bootsplash still doesn't show as often as its supposed to for some
> reason.
>
We have a switch to smooth off the messages appearing over top; will be
doing that for Beta 2.
Sc
I finally got the PPA in and it now works without going to textual VT
login.
I also got a ubuntu logo on first couple of boots and then nothing on
the next 10. I always get a ubuntu logo on reboot and shutdown though,
if any of that matters.
--
Booting with graphical renderer leaves the system a
Ok, got it and installed.
On initial shutdown, I saw a "broken pipe" for a few moments.
On restart, it flickered thru several text screens and showed an fcsk
check (sp?) before finally dumping me into the bootsplash. Boot went
normally from there.
Next shutdown showed some text before the closin
Doesn't seem to be in the suppository, or at least not as of now. Should
I give it a few minutes more and try later?
Also: Did this make it in time for the Beta 1 freeze?
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You re
Thanks, I got it keyed this way:
For future reference...
I added your ppa this way:
$ sudo add-apt-repository ppa:scott/ppa
and sources.list, added:
deb http://ppa.launchpad.net/scott/ppa/ubuntu lucid main
deb-src http://ppa.launchpad.net/scott/ppa/ubuntu lucid main
but still get 404 on that p
On Wed, 2010-03-17 at 01:48 +, vmc wrote:
> Strange, but I keep getting 404:
> $ sudo add-apt-repository ppa:1024R/4929B943
> Error reading https://launchpad.net/api/beta/~1024R/+archive/4929B943: HTTP
> Error 404: Not Found
>
Err, that's a GPG key, not a PPA :)
YM add-apt-repository ppa:
Strange, but I keep getting 404:
$ sudo add-apt-repository ppa:1024R/4929B943
Error reading https://launchpad.net/api/beta/~1024R/+archive/4929B943: HTTP
Error 404: Not Found
W: GPG error: http://ppa.launchpad.net lucid Release: The following signatures
couldn't be verified because the public k
This bug was fixed in the package plymouth - 0.8.0~-15
---
plymouth (0.8.0~-15) lucid; urgency=low
* debian/plymouth.upstart, debian/plymouth.plymouth-stop.upstart:
- Replace the "stop on" clause in plymouth's own job with a job that
handles stopping plymouth for the norma
fixed for me too
checked on 3 cold boots and 3 reboots with no problem at all
great work!
hope it goes in beta 1
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You received this bug notification because you are a member of U
Same here. Thanks.
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
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.ubun
The new package fixed the bug for me.
Thanks!
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
There's a new plymouth package in my PPA -
https://launchpad.net/~scott/+archive/ppa
Please try it and see whether it fixes this bug for you
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You received this bug notification b
** Changed in: plymouth (Ubuntu Lucid)
Status: Incomplete => Fix Committed
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Got this bug today after applying recent Updates. Lucid ALpha 3. P5QPL-
AM motherboard, Intel chipset.
Tends to NOT happen when cold booting, but consistently happens on
reboots. Alt+F7 consistently a useful workaround. (Thanks!)
--
Booting with graphical renderer leaves the system at textual "l
** Tags added: iso-testing
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Based on discussion on IRC today, I understand it's possible to get us
booting to the DM consistently, possibly at the expense of also leaving
server installs at the splash screen instead of the login prompt. I
think this is the right tradeoff for us to make for beta1 (reopening bug
#506297), so r
Seeing the same thing. One thing I've noticed is that if I Ctrl-Alt-
SysReq-B from the console (I know, bad form) the system pretty
consistently comes up correctly the next time.
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/53821
On Mon, 2010-03-15 at 18:00 +, Wolfgang Kufner wrote:
> >You see the "login:" issue on this too?
> All my comments so far about these plymouth bugs are based exclusively
> on testing with this acer extensa 5630Z notebook (intel core2duo
> generation with intel graphics) without an external mon
Just downloaded source, compiled with error on "test" hook, installed
and... nothing changed.
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Before and after "--verbose" option:
kr...@krypt-laptop:~$ cat /proc/fb
0 radeondrmfb
1 VGA16 VGA
** Attachment added: "syslog after tty1 bootup"
http://launchpadlibrarian.net/40966744/syslog
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpa
>You see the "login:" issue on this too?
All my comments so far about these plymouth bugs are based exclusively on
testing with this acer extensa 5630Z notebook (intel core2duo generation with
intel graphics) without an external monitor.
Just booted again into the installed system with "quiet sp
FWIW, booting with '--verbose' leaves me with:
[18:59] ~ $ cat /proc/fb
0 VGA16 VGA
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
On Mon, 2010-03-15 at 17:09 +, Lion1969 wrote:
> and here is my syslog with system booting to vt1 after plymouth appears
> for no more than a couple seconds
>
>
> ** Attachment added: "syslog"
>http://launchpadlibrarian.net/40962034/syslog
>
Same as vmc.
Scott
--
Scott James Remnant
s
On Mon, 2010-03-15 at 16:48 +, vmc wrote:
> Finally, after 8 restarts and one cold boot, I get to text screen VT1
> Here's the attached syslog
>
>
> ** Attachment added: "/var/log/syslog"
>http://launchpadlibrarian.net/40961349/syslog
>
This logs confirms my suspicions.
Scott
--
Scott
and here is my syslog with system booting to vt1 after plymouth appears
for no more than a couple seconds
** Attachment added: "syslog"
http://launchpadlibrarian.net/40962034/syslog
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bug
@#7: For the record, blacklisting 'vga16fb' didn't fix anything - I was
just "lucky" to get ten consecutive boots straight to desktop...
Adding '--verbose' results in a black screen (LCD backlight turned off,
no blind/remote login possible) - at least the last 20 boots (some
restarts, some cold bo
Finally, after 8 restarts and one cold boot, I get to text screen VT1
Here's the attached syslog
** Attachment added: "/var/log/syslog"
http://launchpadlibrarian.net/40961349/syslog
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bug
LOL, so adding "--verbose", is the fix :)
I did that and thought to myself, watch it NOT fail.
Sure enough adding "--verbose", and rebooting 6 times and I cannot get
to just VT1 text screen.
Will keep at it until it fails or I do...
--
Booting with graphical renderer leaves the system at tex
(obviously of a boot where you end up at the VT rather than in X)
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Actually, there is something you can all do to help!
If you could boot with "--verbose" on the kernel command-line and attach
your /var/log/syslog files - that would be very useful!
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Incomplete
--
Booting with graphical renderer leaves
On Mon, 2010-03-15 at 14:55 +, IKT wrote:
> Anything useful we can do?
>
Not unless you can step through the plymouth code line-by-line while the
X server starts to see why it's invoking a VT switch back to the
original VT when it shouldn't
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Anything useful we can do?
--
Booting with graphical renderer leaves the system at textual "login:" screen
https://bugs.launchpad.net/bugs/538214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
** Summary changed:
- Booting with the framebuffer renderer leaves the system at textual "login:"
screen
+ Booting with graphical renderer leaves the system at textual "login:" screen
** Description changed:
Binary package hint: plymouth
- This bug occurs with the Framebuffer renderer back
35 matches
Mail list logo
