System doesn't start X on first boot

2012-01-05 Thread George
When I boot my computer, most of the time I get a command line without X starting. I have to "sudo reboot", wait for the system to reboot and then I get the correct X environment (I'm using awesome window manager but I also have kde installed). Any suggestions to troubleshoot this? -- To UNSUBS

Re: System doesn't start X on first boot

2012-01-05 Thread Alberto Luaces
George writes: > When I boot my computer, most of the time I get a command line without > X starting. I have to "sudo reboot", wait for the system to reboot and > then I get the correct X environment (I'm using awesome window manager > but I also have kde installed). > > Any suggestions to trouble

Re: System doesn't start X on first boot

2012-01-05 Thread George
On 1/5/12, Alberto Luaces wrote: > George writes: > >> When I boot my computer, most of the time I get a command line without >> X starting. I have to "sudo reboot", wait for the system to reboot and >> then I get the correct X environment (I'm using awesome window manager >> but I also have kde i

Re: System doesn't start X on first boot

2012-01-05 Thread Alberto Luaces
George writes: > On 1/5/12, Alberto Luaces wrote: >> George writes: >> >>> When I boot my computer, most of the time I get a command line without >>> X starting. I have to "sudo reboot", wait for the system to reboot and >>> then I get the correct X environment (I'm using awesome window manager >

Re: System doesn't start X on first boot

2012-01-05 Thread Christofer C. Bell
On Thu, Jan 5, 2012 at 10:24 AM, Alberto Luaces wrote: > George writes: > >> On 1/5/12, Alberto Luaces wrote: >>> George writes: >>> When I boot my computer, most of the time I get a command line without X starting. I have to "sudo reboot", wait for the system to reboot and then I

Re: System doesn't start X on first boot

2012-01-05 Thread Scott Ferguson
On 06/01/12 03:10, George wrote: > On 1/5/12, Alberto Luaces wrote: >> George writes: >> >>> When I boot my computer, most of the time I get a command line without >>> X starting. I have to "sudo reboot", wait for the system to reboot and >>> then I get the correct X environment (I'm using awesome