On Sunday 20 November 2011 20:16:46 Sven Burmeister wrote:

Am Sonntag, 20. November 2011, 09:05:45 schrieb Jon Nelson:

...

The first issue is that the fonts don't seem to render with the correct height -- frequently the lower part of the 'q', 'g', etc... are missing and lines with underscores don't show them at all. This only happens on the line that is taking input and no other.

You could run fetchmesttfonts again in case those got lost.

...

The second issue is that I've noticed, quite frequently actually, that some part of KDE goes unresponsive. khotkeys and plasma stop accepting input, but 'alt-f2' brings up krunner right away. The clock in the taskbar stops updating during these 'pauses'. I checked .xsession-errors and /var/log/messages and there wasn't anything that stuck out. It's becoming quite annoying.

Me too. Yet I have not been able to trace down the cause. I thought it had something to do with the launchers or nepomuk enabled. Also it happens often when closing applications. It happens every time I log into KDE, i.e. you can reproduce it by logging-in and immediately clicking on the networkmanagement plasmoid and hovering the connections. The bar that indicates which one is below the cursor stops moving for quite some time at some point.

I notice this on startup. Plasma appears, then refuses all input and does not update for a few seconds. My hunch is that it is trying to query Nepomuk in a blocking way, in order to set up its Activities UI, while Nepomuk is still starting up and doesn't answer promptly. I haven't investigated further. Will -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

* Sven Burmeister [11-23-11 06:02]:

I found that if I remove all activities but one the lags (on start-up) are gone.

I only have one activity on my test_121 laptop but see the delay if I immediately try to type the password after reaching runlevel 5. If I delay, frequently I am accessing remotely (ssh), for a while the password is accepted as expected. I have not experimented to determine the delay required, but this fact indicates something has not completed reaching full runlevel 5, doesn't it. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Am Mittwoch, 23. November 2011, 09:40:11 schrieb Patrick Shanahan:

* Sven Burmeister [11-23-11 06:02]:

...

I found that if I remove all activities but one the lags (on start-up) are gone.

I only have one activity on my test_121 laptop but see the delay if I immediately try to type the password after reaching runlevel 5. If I delay, frequently I am accessing remotely (ssh), for a while the password is accepted as expected. I have not experimented to determine the delay required, but this fact indicates something has not completed reaching full runlevel 5, doesn't it.

I am talking about plasma being unresponsive after the KDE login. Are you talking about kdm and its password? Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Wed, Nov 23, 2011 at 3:23 PM, Patrick Shanahan wrote:

* Sven Burmeister [11-23-11 16:14]:

...

Am Mittwoch, 23. November 2011, 09:40:11 schrieb Patrick Shanahan:

...

* Sven Burmeister [11-23-11 06:02]:

...

I found that if I remove all activities but one the lags (on start-up) are gone.

I only have one activity on my test_121 laptop but see the delay if I immediately try to type the password after reaching runlevel 5.  If I delay, frequently I am accessing remotely (ssh), for a while the password is accepted as expected.  I have not experimented to determine the delay required, but this fact indicates something has not completed reaching full runlevel 5, doesn't it.

I am talking about plasma being unresponsive after the KDE login. Are you talking about kdm and its password?

yes, sorry.  I should have been more descriptive and maybe the OP is referring to plasma and *not* the log-in screen not accepting the second password character.

I am referring to plasma (or dbus or kded). I just filed a bug, 735150. I'm guessing, but it looks dbus<->kded related. -- Jon -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org