Description of problem: After starting rpmdrake text can be entered in the search field but after changing either the view packages option or the filter option, text can no longer be entered in the search field. If I start rpmdrake in a konsole window I see these warnings: Fontconfig warning: "/etc/fonts/conf.d/25-mdv-CJK-disable-hinting.conf", line 15: Having multiple values in test> isn't supported and may not works as expected Fontconfig warning: "/etc/fonts/conf.d/25-mdv-CJK-disable-hinting.conf", line 15: Having multiple values in test> isn't supported and may not works as expected The first warning appears when the "Enter root password" window opens. The second warning appears when the rpmdrake window opens, after entering the root password. (The same error appears if I start, for example, drakconf or mcc from a konsole window.) I'm running a fully updated Cauldron desktop installation with KDE. How reproducible: Every time. Steps to Reproduce:As described above.
Depends on: (none) => 6806
for the warning see the depends bug, for the first part I don't know, Thierry ?
Assignee: bugsquad => thierry.vignaudTarget Milestone: --- => Mageia 3
I had an issue with that textbox awhile back. Can't recreate it now though. I think it may have had something to do with the KDE Widget style/setting used. Could you tell me which Widget style you are using and have you had any other KDE application textbox issues?
CC: (none) => digigold808
I'm using the Oxygen widget style and I've not noticed a problem with any other KDE application. I've discovered today that when I am unable to enter text, if I "right" click in the search field first and then, without selecting anything from the context menu, I "left" click in the search field, I am now able to enter text normally. This procedure is totally repeatable. Probably doesn't help find a solution to the problem but it's a bit more information ! I'm going to update my packages now to see if the problem is still occurring.
I updated 280 packages but the problem still exists, however I no longer have the Fontconfig warnings, so I guess they were not connected with the problem. I first noticed this problem after completing the UsrMove procedure, but the procedure also involved many package updates as well.
After updating 894 packages today the problem has gone away. I will change this bug report to RESOLVED and FIXED.
Status: NEW => RESOLVEDResolution: (none) => FIXED