** Description changed:
On startup I need to move my mouse or press a key to get the display to
come back. It is like it goes into power-saving mode seconds after
- initializing the X display, as I get the beige background and a status
- window just before when I would expect the desktop to appear, and then
- the monitor stops getting video signal.
+ initializing the X display, as I get X for the mouse int he center of
+ the display just before when I would expect the beige background to
+ appear, and then the monitor stops receiving a video signal.
Steps to reproduce:
- Power up and boot Feisty-Herd3 LiveCD.
+ 1.) Power up and boot Feisty-Herd3 LiveCD.
Wait several minutes to finish boot, giving at least 30 seconds after there
is no more drive activitity.
- [Display will be blank. On my CRT the power light turns amber indicating
there is no video signal.]
- Move mouse or press any key
+ [Display will be blank. On my CRT the power light turns amber
+ indicating there is no video signal.]
+
+ 3.) Move mouse or press any key
Gnome Desktop appears.
The only things that might offer a clue:
If I Alt-F1 I see
agpgart: Aperture conflicts with PCI mapping
bog1_init failed: setting screen sze: Cannot allocate memory
screen init failed
Then, at bottom of screen:
kernel alive
kernel direct mapping tables up to 100000000 @ 8000 - d000
However I've discovered on subsequent boots that those appear well before X
is started.
I doubt this is related but the only other anomoly is that there is a "Crash
report detected" notifier on the system tray, which then says "Add/Remove
failed", and I can then submit a crash report on gnome-app-install.
** Tags added: boot display energy-saver energy-saving feisty herd
herd-3 herd3 livecd power power-saver power-saving saver saving startup
x
--
[feisty-herd3] X Display in Power-Saving mode on Startup, LiveCD even
https://launchpad.net/bugs/83726
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
