This bug seems to be dependant on the user to have a encrypted home
folder or not. If not encrypted installing themes works, if encrypted
only shutdown works. So it seems to me like ecryptfs is somehow blocking
initramfs when reading the theme.
--
You received this bug notification because you ar
Just to say that the bug is still present in 12.10 Quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850895
Title:
[nouveaufb] Plymouth refuses to show on boot, only at shutdown
(mountall erro
I'm affected too. Fortunalely in opensuse 12.2 I don't have this
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850895
Title:
[nouveaufb] Plymouth refuses to show on boot, only at shutdown
FWIW, based on the above comments and my experience I'd lay at least
some of the blame on this on nouveau: I have two setups affected by the
Plymouth no-show, both with Nvidia graphics:
01:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7300 GT]
(rev a2) (prog-if 00 [VGA controlle
I think i have something like this bug on my system. When i was running
the Nouveau driver (now i have the Nvidia prorietary driver installed)
the system was booting correct but i don't saw the plymouth splash
screen. It was showing a short time (as a purple background, no ubuntu
text) popping at t
I have this bug at boot, mangled screen with partial purple colouring,
message 'Input not Supported' from the monitor bouncing around the
screen. When boot finishes, all is well. I think it's okay on shutdown,
I only shutdown occassionally and don't hang around to watch. Ubuntu
12.04 (fresh install
Just confirming that this bug is still present in Precise; I have
overwritten my 11.04 partition and installed 12.04 over that, along with
its own GRUB. The above workarounds still work, as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The hwinfo output also shows that the native panel resolution is not
known to the BIOS.
To the best of my knowledge there have been no relevant changes to grub
in precise; I don't expect the behavior to change whether or not you
overwrite the bootloader.
--
You received this bug notification bec
I have just followed a suggestion here on my question about saving the
output of vbeinfo by trying hwinfo: http://askubuntu.com/q/83085/18612
I'm not sure if the output gives any additional information that could
be useful; it looks similar to but is not the same as what vbeinfo
returns.
On an unr
ok, interesting. I don't know why this check is failing for you at
boot, then. Will have to dig further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850895
Title:
[nouveaufb] Plymouth refuses to
I ran both commands and pasted the terminal output into this attachment.
** Attachment added: "readlink and ls output.txt"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/850895/+attachment/2551146/+files/readlink%20and%20ls%20output.txt
--
You received this bug notification because
Right, the lack of centering is not unsurprising. That may be something
you can adjust in your monitor's settings, fwiw.
When you have a chance, please show the output of this command:
readlink -f /sys/dev/char/$((0x$(stat -c %t
/dev/dri/card0))):$((0x$(stat -c %T /dev/dri/card0)))/device/driver
I just tried the 1280x1024 resolution. It looks better resolution-wise,
but it's no longer centered onscreen, and instead is slightly off to the
left, leaving a black bar at the right edge.
Running vbeinfo in that resolution left no artifacts, but was still off-
center. It did produce the full out
On Sun, Oct 16, 2011 at 06:46:22AM -, WarriorIng64 wrote:
> I was able to get this picture of vbeinfo on my desktop using Cheese,
> after resetting grub to use GRUB_GFXMODE=640x480 again. I think some of
> the output at the top is cut off, and you can see black artifacts along
> the edges of th
On Sun, Oct 16, 2011 at 06:26:22AM -, WarriorIng64 wrote:
> Okay, using plymouth:force-drm without setting GRUB_GFXMODE returns to
> the original problem, with neither grub nor Plymouth showing. Attached
> is the output from that.
> ** Attachment added: "plymouth-debug.log"
>
> https://bug
Okay, never mind on the camera bit. I just realized that I do have a
camera: my laptop webcam.
I was able to get this picture of vbeinfo on my desktop using Cheese,
after resetting grub to use GRUB_GFXMODE=640x480 again. I think some of
the output at the top is cut off, and you can see black artif
Okay, using plymouth:force-drm without setting GRUB_GFXMODE returns to
the original problem, with neither grub nor Plymouth showing. Attached
is the output from that.
** Attachment added: "plymouth-debug.log"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/850895/+attachment/2549562/+f
I was about to say that using
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash plymouth:debug=file:/var/log
/plymouth-debug.log "
GRUB_GFXMODE=640x480
works too, without the plymouth:force-drm bit on the end.
I just saw your last comment and I will be trying that out next.
Unfortunately, I no longer ha
On Sun, Oct 16, 2011 at 05:37:29AM -, WarriorIng64 wrote:
> Okay, I've altered the following lines in my /etc/default/grub:
> GRUB_CMDLINE_LINUX_DEFAULT="quiet splash plymouth:debug=file:/var/log
> /plymouth-debug.log plymouth:force-drm"
> GRUB_GFXMODE=640x480
> (I only use one monitor in my
Okay, I've altered the following lines in my /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash plymouth:debug=file:/var/log
/plymouth-debug.log plymouth:force-drm"
GRUB_GFXMODE=640x480
(I only use one monitor in my setup, btw, so I figured that option would
be safe to add.)
And lo and
>From the plymouth debug log:
[./plugin.c] initialize_head:initializing
2048x1536 head
Those sure don't look like the dimensions we want. So this may be a bug
with the resolution being handed off from grub, or it may be a bug in
the nouveau framebuffer driver itself
Just tried the third and last suggestion. Still nothing.
Looking back at what was posted on my AskUbuntu question, I'm going to
try setting GRUB_GFXMODE=640x480 and see if I can at least get grub to
display. If that works, then from there I'll take a look at vbeinfo.
--
You received this bug not
On Sat, Oct 15, 2011 at 11:50:54PM -, WarriorIng64 wrote:
> Steve, attached is my output from running xrandr. I'm not entirely sure
> what you mean by "[configuring] grub to use the same mode"; could you
> tell me from this output exactly what I should set GRUB_GFXMODE to
> (i.e., which numbers
Steve, attached is my output from running xrandr. I'm not entirely sure
what you mean by "[configuring] grub to use the same mode"; could you
tell me from this output exactly what I should set GRUB_GFXMODE to
(i.e., which numbers to use)? Thanks.
** Attachment added: "xrandr output.txt"
https:
Ok. That's the expected output from running the command, fwiw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850895
Title:
[nouveaufb] Plymouth refuses to show on boot, only at shutdown
(mountall
Here's my output from the second suggestion.
** Attachment added: "plymouth-debug.log"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/850895/+attachment/2548957/+files/plymouth-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Steve, I've just tried the first option to no effect. Attached is a copy
of my terminal output from running that command. I'll get to trying the
other two shortly.
** Attachment added: "First suggestion output.txt"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/850895/+attachment/2548
WarriorIng64,
>From the context of your AskUbuntu thread, I understand that the root
issue here is a mismatch between your video card's preferred VBE mode
(as returned by the 'vbeinfo' command in grub2) and the modes supported
by your external monitor. If you are seeing the splash at shutdown but
I'm still getting this problem on my desktop in Oneiric final. I have
just upgraded my Toshiba Satellite laptop yesterday to Oneiric and it
still doesn't have this problem, just my desktop does.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plymouth (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/850895
Title:
[n
No, it's not because I have the same problem despite I use burg as boot manager
(which works well).
Even with a working Grub 2 before it didn't show up.
Confirmed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
The bug that I said I would file separately for my grub not displaying
is bug #850908, in case it's relevant in any way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850895
Title:
[nouveaufb] Plymo
** Summary changed:
- Plymouth refuses to show on boot, only at shutdown
+ [nouveaufb] Plymouth refuses to show on boot, only at shutdown
** Summary changed:
- [nouveaufb] Plymouth refuses to show on boot, only at shutdown
+ [nouveaufb] Plymouth refuses to show on boot, only at shutdown (mountal
33 matches
Mail list logo
