![]() Registered Member ![]()
|
I had originally posted this at the Gentoo forums, but since no one there has had any advice for me, I am reposting this here:
This happened again to me today without using fast user switching. It seems to be semi-random and I have not been able to isolate a cause from X server logs or .xsession-errors. Does anyone have any suggestions on what I can do to try to fix this? |
![]() Manager ![]()
|
Is Strigi running when this happens? If so, go to System Settings > Advanced tab > Desktop Search and switch it off. Leave Nepomuk enabled. It may just be that Strigi is taking too many of your resources.
annew, proud to be a member of KDE forums since 2008-Oct and a KDE user since 2002.
Join us on http://userbase.kde.org |
![]() Registered Member ![]()
|
Desktop Search is not present in System Settings' Advanced Tab. I compiled KDE without semantic-desktop support, so Nepomuk and Akonadi-Server are not installed. Strigi is installed because the rest of KDE requires it for linking purposes. |
![]() Administrator ![]()
|
Please check the configuration of your graphics drivers. Also, did the removals include /var/tmp/kdecache-$USER/?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
In particular, what should I check? Nvidia's drivers give no complaints in the X server logs. And yes, the removals included those directories. Edit: It just happened again. Here is a copy of my .xsession-errors file: http://paste.pocoo.org/show/216592/ Running "grep error" produces the single line "XRANDR error base: 177". I also went into my desktop effects settings, unchecked "Enable Desktop Effects", clicked apply and then checked "Enable Desktop Effects" and clicked apply. The result was:
Here is my xorg.conf file: http://paste.pocoo.org/show/216594/ Edit: Upon closer inspection of ~/.xsession-errors, I found the following:
This is an issue where ConsoleKit is using names that KDE's developers intrepreted as being illegal under the D-Bus specification. From what I have read, the D-Bus specification is unclear as to what constitutes valid property names, but the easiest fix seems to be to have ConsoleKit use FirstLetterCaps-style property names, which is what Debian is doing. I have filed a bug report with Gentoo's bug tracker: http://bugs.gentoo.org/show_bug.cgi?id=320875 It might be a good idea if I filed one in KDE's bug tracker as well, although I am not sure if it is something that KDE's developers should fix. In addition to the above issue, I also found the following issues in ~/.xsession-errors:
I have filed a bug report with Gentoo's bug tracker: http://bugs.gentoo.org/show_bug.cgi?id=320877 Does anyone know whether or not any of the above issues I identified could be related to my issues with Compositing? Also, does anyone have any idea what ""XRANDR error base: 177" means? |
![]() Administrator ![]()
|
Unfortunately I don't know why this could be occurring, however watching system load on a remote system while logging in may reveal the cause.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
Thankyou for trying. You were right about the configuration of my graphics drivers. I did a google search for "195.36.24 kde compositing" and found the following: http://bbs.archlinux.org/viewtopic.php?pid=756736 I appended the following options to my xorg.conf file and that seems to have fixed things:
|
![]() Registered Member ![]()
|
I just ran into this issue again. I assume that I failed to resolve it.I just tried commenting out unnecessary stuff from xorg.conf and now it seems to be gone again. I am not sure if it is gone for good or just for now. :/
|
![]() Registered Member ![]()
|
It just happened again. ~/.xsesson-errors contains the following:
Edit: I just downgraded to x11-base/xorg-server-1.7.7. So far, everything appears to work. I do not recall this issue occurring before the x11-base/xorg-server-1.8.0 upgrade, so hopefully this will resolve my issues. Unfortunately, because this issue occurs randomly, I have no way of verifying that it is gone. ![]() |
![]() Registered Member ![]()
|
I had this issue again earlier today. I have downgraded the nvidia drivers to x11-base/nvidia-drivers-190.53-r1. If this fixes it, I am going to conclude that the issue is with the drivers. If not, the next logical places to look will be either KDE or the kernel. I hope that this will fix things. If this does not fix things, then it would seem that I have an extremely rare issue that is only affecting me as I cannot find any reports online of other people suffering from anything like it. :/
Edit: It seems that I was wrong. Other people seem to be having similar problems, except it is with even older versions of the nvidia drivers and xorg server: http://forums.gentoo.org/viewtopic-t-79 ... art-0.html Many of them are reporting that the latest available drivers fixed their issues. Unfortunately, assuming this is the same kind of problem, the latest drivers seem to be introducing issues for me. ![]() |
![]() Registered Member ![]()
|
I just had this issue again. At this point, I feel like I am playing whack a mole. Anyway, I just reverted my xorg-server and nvidia drivers back to the latest versions. I also downgraded my kernel from 2.6.34 to 2.6.33.5. I am not sure if this issue started before or after the 2.6.34 upgrade, but I do not need any of the stuff that the 2.6.34 kernel brought (I only wanted to try out compcache), so hopefully this will finally fix things.
|
![]() Registered Member ![]()
|
I seem to have become overly zealous, because I had a brief lag with the older xorg-server and nvidia-drivers and mistook that for the issue I am having. Since going back to the older kernel, I have encountered this issue again several times, and it is much more severe than the brief lag I encountered with the old nvidia drivers, so I am going back to those. I think this "fixes" the issue. |
![]() Registered Member ![]()
|
First, would a moderator please split Aardwolf's discussion into its own independent thread? Allowing his discussion to hijack one that documents a significant issue is probably not a good idea.
Secondly, I believe that the cause of this issue has been identified: http://www.nvnews.net/vbulletin/showthread.php?t=152065 The revelation that later versions of drivers from Nvidia were improperly patched is consistent with my observation that this never occurs in properly patched 190.53 drivers and since this issue had to do with ACPI, it should manifest itself randomly, which is also consistent with my observations. Those two things together suggest that the issue I encountered was in fact the application of a bad patch by Nvidia's developers. The fact that almost no one else encountered this is likely because very few distributions are using kernel 2.6.33+ to be affected by this issue at this time, as the issue only exists because 2.6.33 broke compatibility and a patch to restore compatibility was improperly written. I could validate my theory by using unpatched 190.53 drivers, but after having been through hell since the xorg-server 1.8.0 upgrade forced me to upgrade from the properly patched 190.53 nvidia drivers, I would rather not test a theory that I am 99% certain is correct. |
![]() Administrator ![]()
|
Topic split as requested. Good to know that the cause of this has likely been identified as well.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
After reading this thread I successfully solved slow compositing problem in my side.
|
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]