Version: (using KDE 4.4.0) OS: Linux Installed from: Archlinux Packages If I lock the screen from my user session, or if I change the user starting a new kde session and then come back, the login box on black blackground in which it's supposed I enter my password is totally white No buttons, no field, but if I type my correct password and then press Enter, everything works as expected This strange behaviour works only with my current user. I can't replicate the problem using other users. What's wrong in my user session? I can't say if it's related: I just passed to kde 4.4 upgrading my intel graphic drivers (intel 4500hd) to the lastest 2.10
- is this behaviour related to active compositing (desktop effects)? - can you (in case) "fix" it by deactivating a specific plugin (try all first, if the problem is gone, one is likely the culprit) - using a custom UI style / windeco? - does switching the decoration (to a non tabbing, in doubt try kde2) help?
no way, I tried every hints but the login box keep showing totally white
so the box is "painted" entirely white despite compositing (Desktop FX) are not active (disabled or suspended)?
yes, but only locking my kde user session my brother has another account on the same computer, using the same desktop environment, composition active, but no problems
ok, this is hardly kwin related then. As you say it's also unrelated to the UI style and you're using the same HW and libs, and the problem is purely visual (the box still works) i'm tempted to blame the screenlocker, i.e. the screensaver could trigger vram polution by opengl calls (driver bug) - tried to change it?
I upgraded to kde 4.4.1 and the problem remains I'm using oxigen stardard style, and no screen savers graphic card Intel 4500HD with 2.10.0-1 drivers
(In reply to comment #5) > ok, this is hardly kwin related then. Yes, so I would like to reassign, but do not know to where. So please someone with the knowledge of all kde parts reassign to appropriate component.
Reassigning to krunner, since it manages the screensaver and locking.
I have found the problem! surfing the web I found that there's an issue in DRI2 architecture, so there might be conflicts with kde and running programs which use opengl In my case the guilty was cairo-dock started with opengl backend: if I don't start it or a I start it with no opengl backend I have no issues please patch this awful regression ;)
Is this still valid with KDE 4.9.0 or later?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!