Bug 245989

If the freezes are appearing both with KWin as well as Compiz, why do you believe it is a KDE bug?

I dont have problerm with compiz or kwin. The system freezes with both
disable and all efects Disable and whem xorg goes to 100% and I don't kown
why.
So to use kde we need xorg, right? I And I saw in google many post in
ubuntu, kubuntu, and others dist the same problem and no solution, but
change to older dist...
think that is a duty of kde or gnome  check
if xorg integration is good enough to be used, if you want that we use, because
you seem to have caught the errors in the windows ... to launch new versions
without fixing the bugs and still compete internally between gnome and kde
and leave the user without the proper attention. So yes, kde has an
obligation to also check the bugs kde depends on third parties to be used
for these third-party programs such as xorg and the video drives.


2010/7/28 Christoph Feck <christoph@maxiom.de>

> https://bugs.kde.org/show_bug.cgi?id=245989
>
>
> Christoph Feck <christoph@maxiom.de> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                 CC|                            |christoph@maxiom.de
>
>
>
>
> --- Comment #1 from Christoph Feck <christoph maxiom de>  2010-07-28
> 14:49:27 ---
> If the freezes are appearing both with KWin as well as Compiz, why do you
> believe it is a KDE bug?
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

It is not the responsibility of the KDE team to handle bugs in xorg or other upstream components. The provider or your distribution selects the versions of the packages to ensure they work together.

If you think you are using unstable versions of the components, please file the bug to your distributions' bugtracker https://bugs.launchpad.net/ubuntu/

If you think it is an xorg bug, file a bug for product "xorg" at https://bugs.freedesktop.org/

If you found the issue to be caused by KDE, please provide more information (e.g. which KDE applications that run in the background consume CPU resources). You can use Ctrl+Esc to start the System Activity monitor.

You could also ask in a forum how to gather additional information when xorg consumes 100% CPU resources.

after 24 hours of use the computer is super slow to be restarted.
Was using the hardy version since its release and all worked ok and 27 
days without rebooting.
Thanks


On 07/28/2010 09:49 AM, Christoph Feck wrote:
> https://bugs.kde.org/show_bug.cgi?id=245989
>
>
> Christoph Feck<christoph@maxiom.de>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |christoph@maxiom.de
>
>
>
>
> --- Comment #1 from Christoph Feck<christoph maxiom de>   2010-07-28 14:49:27 ---
> If the freezes are appearing both with KWin as well as Compiz, why do you
> believe it is a KDE bug?
>
>

It is probably an NVIDIA driver issue, but KWin developers know best. Reassigning.

By *kindly* skipping the nonsense talk in the second hal of comment #2:

you're using the legacy nVidia CSS driver (while it's no clear whether you actually successfully use the 173.xxx series or just mentioend that even that fails: this particular GPU is quite old and probably only supported by the 71.xx or 96.xx series) alongside an XOrg patched by your distro.

If by any chance they backported stuff from the 1.8 server branch there's a great chance of an incompatibility.
nVidia has so far not released a compatibility update for xserver 1.8 and the 173.xxx series and it's quite unlikely they ever will for the other two series.

Conclusion:
Either you 
- by new HW
- downgrade your xorg-server package or
- you should install and use the nouveau driver. (recommanded to avoid further trouble)
It will atm not provide OpenGL (thus no compiz either, but the XRender backend of kwin works ... "in a way") but you'll hopefully bypass the X11 deadlocks and get back a usable system.

Still not sure what I'll do but the explanation you gave me was very good and only found here. Thank you very much.