Public bug reported:
Binary package hint: gnome-power-manager
Dell Latitude D630
Package details:
gnome-power-manager:
Installed: 2.29.91-0ubuntu9
Candidate: 2.29.91-0ubuntu9
Version table:
*** 2.29.91-0ubuntu9 0
500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
100
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/42240889/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/42240890/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42240891/Dependencies.txt
** A
Some further testing shows that every alternate wake from suspend to RAM while
running off the amd64 live image results in a blank screen at wake. Switching
to the first or second virtual console works, and then going to virtual console
7 (in which the x session is running) brings back the displ
Public bug reported:
Binary package hint: gnome-system-tools
The "Time and Date Settings" panel has text on the bottom that says "Click to
make changes". The time to click is not highlighted or differentiated in any
way. Clicking on the text does nothing and the click target padlock icon is so
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42310036/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/42310037/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/42310038/ProcStatus.txt
** Attachm
Public bug reported:
Binary package hint: gnome-system-tools
When initially changing the value of the "Configuration" dropdown in the
Time and Date Settings window to "Keep synchronized with Internet
servers" on a newly set up machine, a dialog pops up informing the user
that NTP is required but
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42524897/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/42524898/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/42524899/ProcStatus.txt
--
value
I've updated to Natty on the one laptop to which I currently have
access and haven't seen this issue. I have also installed as a VM in
Virtualbox and have not seen the problem again.
--
Ali
On Wed, Jun 22, 2011 at 20:20, Pedro Villavicencio wrote:
> Thanks for the report, it has been some time wi