https://bugzilla.novell.com/show_bug.cgi?id=728554 https://bugzilla.novell.com/show_bug.cgi?id=728554#c54 Roland Hughes <roland@logikalsolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|rens.groenewegen@xs4all.nl | --- Comment #54 from Roland Hughes <roland@logikalsolutions.com> 2012-01-23 20:55:55 UTC --- (In reply to comment #53)
Another test: I activated in /usr/share/kde4/config/kdm/kdmrc in section "[General]" the setting "AutoRescan=false". Since then the problem is gone. Can anyone confirm this?
disclaimer: I do NOT recommend to use this setting except for testing until someone with more inside knowledge than me, tells us if it is safe. Otherwise it might be necessary to reboot the machine to get changed settings to work...
Thanks for definitively proving this problem is directly related to the current slow-hanging-disk-io problem KDE and Linux in general has been experiencing since EXT4 started making its appearance. According to the doc. http://docs.kde.org/stable/en/kdebase-workspace/kdm/kdm-files.html ======== AutoRescan This boolean controls whether kdm automatically re-reads its configuration files if it finds them to have changed. The default is “true”. ========= This explains the sheer randomness of the issue since it depends both upon the amount of disk IO currently going on AND if the network has a blocking interrupt causing disk IO to wait. I propose we push this bug to the people working on the slow-hanging-disk-io issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.