As of last December, with the version of ~/.config/monitors.xml attached
to comment #3 present, the problem occurred. With it absent, it did not.
Several updates to the kernel and other components have happened in the
intervening time. gnome-control-center is currently at version
1:2.28.1-0ubuntu1
There is one physical VGA connector on the card, and no other video
output such as a TV out connector, so I certainly didn't deliberately
configure more than one monitor. I am reasonably certain that this
specific CRT is also the only monitor that has been connected to this
box since Ubuntu was ins
I have found a workaround, and appear to have repaired my original user
account's settings. I found by comparing the various settings files and
folders that the bad user had a file named ~/.config/monitors.xml but
the newly created and usable user did not.
Renaming that file was sufficient to allo
Interesting. A brand new user account gets a working session.
I created a new user, and tried logging in to the default GNOME session.
This gave me the default desktop, panels and menus. At this point, I can
see that even a "successful" login produces a fair number of error
messages in the .xsessi
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/36672601/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/36672602/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36672603/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
I allowed the most recent high priority updates to install yesterday, on
an otherwise up to date installation of Ubuntu Karmic. I didn't take
careful notes on what packages were being updated, but I do recall
mention of both the kernel (to 2.6.31-16
