Martin Kho wrote:
>> On 31/03/10 12:16, Andrew Mason wrote:
>> > 2010/3/31 José Matos<jamatos(a)fc.up.pt>:
>> >> On Tuesday 30 March 2010 23:16:46 Martin Kho wrote:
>> >>> Does anyone else have seen X using lots of cpu sources in F13?
>> >> No problem here, with a real install (not a virtual machine :-) ).
>> > Hi,
>> > I got this on my thinkpad X200. Was unusable. Just figured it wasn't
>> > quite baked yet.
>> Is this the old issue of X and tty racing to start on tty1? I'm sure
>> there is a redhat bz entry about this. Dont have time to search now but
>> will later if noone else finds it.
> It looks like :-). Upstart is in F13 updated from 0.3.x to 0.6.x. The way
> tty's are handled has changed in this version. It seems that X is fixed -
> again - to vt1. If I'm wrong please let me hear. As a 'workaround' -
> - the changes that were made in F11/F12  have to be reversed:
> In /etc/kde/kdm/kdmrc change:
> * ServerVTs = -1 -> ServerVTs=1 and
> * ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6 ->
Not recommended. Forcing VT1 is what caused the "old issue of X and tty
Okay, not recommended. Can you shed some light on the issue, so I can add that
to the bug report.
kde mailing list
New to KDE4? - get help from http://userbase.kde.org