On 9 May 2012 16:28, Matthew Sturdy <matt.stu...@gmail.com> wrote:
>
>> You could also look into /var/log/Xorg.0.log and see what X is doing on
>> startup.
>
> Nothing obvious in there.. but I will check next time immediately after
> boot.
>
Nope - there's nothing interesting in there... and it even seems to be
finding the proper drivers:
[ 180.874] (II) intel: Driver for Intel Integrated Graphics Chipsets:
i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server
>
> One thing I like to try is to stop gdm/lightdm whatever, and then run
>> startx. If it fails it often gives a helpful message.
>
> Good suggestion! thanks... Will try it next boot.
>
This time when I dropped down to the console I killed the initx process
that was running, and then ran startx. It started without errors.
It took me straight to my desktop, bypassing the usual login screens...
where it prompted me to unlock the login keychain with my password.
however, the desktop didn't seem to load properly, and after accepting my
password, it stopped responding to the keyboard.
I return to tty3 and killed the process (CTRL+C). then I started gdm and
all was ok again.
It seems to be a bug in gdm or unity at this stage.. .but I can't really
raise it without knowing which!
Any other suggestions?
Matt
--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/
