Hi,
I'm running F13 KDE nightly build (20100328) in VirtualBox and experience high cpu usage. top shows that X is the 'culprit'. Jaroslav Franek opened a report [1] for this issue. The issue looks very the same as stated in report [2].
Does anyone else have seen X using lots of cpu sources in F13?
Thanks,
Martin Kho
[1] https://bugzilla.redhat.com/show_bug.cgi?id=577482 [2] https://bugzilla.redhat.com/show_bug.cgi?id=475890
Hi,
Does anyone else have seen X using lots of cpu sources in F13?
I see high CPU usage in kde i386 nightly-composes running in vmware.
If run 'telinit 3' and start KDE with startx then CPU usage normal.
Alexey Kurov nucleo@fedoraproject.org
2010/3/31 José Matos jamatos@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.
On 31/03/10 12:16, Andrew Mason wrote:
2010/3/31 José Matosjamatos@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.
Roderick
On 31/03/10 12:16, Andrew Mason wrote:
2010/3/31 José Matosjamatos@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.
Hi,
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' - fix? - the changes that were made in F11/F12 [1] have to be reversed:
In /etc/kde/kdm/kdmrc change:
* ServerVTs = -1 -> ServerVTs=1 and * ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6 -> ConsoleTTYs=tty2,tty3,tty4,tty5,tty6
Hope this helps.
Martin Kho
[1] https://bugzilla.redhat.com/show_bug.cgi?id=475890
Roderick _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Martin Kho wrote:
On 31/03/10 12:16, Andrew Mason wrote:
2010/3/31 José Matosjamatos@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.
Hi,
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' - fix?
- the changes that were made in F11/F12 [1] have to be reversed:
In /etc/kde/kdm/kdmrc change:
- ServerVTs = -1 -> ServerVTs=1 and
- ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6 ->
ConsoleTTYs=tty2,tty3,tty4,tty5,tty6
Not recommended. Forcing VT1 is what caused the "old issue of X and tty racing"
-- Rex
Martin Kho wrote:
On 31/03/10 12:16, Andrew Mason wrote:
2010/3/31 José Matosjamatos@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.
Hi,
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' - fix?
- the changes that were made in F11/F12 [1] have to be reversed:
In /etc/kde/kdm/kdmrc change:
- ServerVTs = -1 -> ServerVTs=1 and
- ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6 ->
ConsoleTTYs=tty2,tty3,tty4,tty5,tty6
Not recommended. Forcing VT1 is what caused the "old issue of X and tty racing"
Hi,
Okay, not recommended. Can you shed some light on the issue, so I can add that to the bug report.
Thanks,
Martin Kho
-- Rex
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
-
alekcejk＠googlemail.com -
Andrew Mason -
José Abílio Matos -
Kevin Kofler -
Martin Kho -
Rex Dieter -
Roderick Johnstone