Description of problem: If KDE screen lock is activated then ksmserver keeps spawning the screen lock process continuously in an infinite loop. As a result, it becomes impossible to unlock the screen (it does not even show a password prompt). The only way out is to kill the X-server or kill the parent ksmserver process (which also kills the X-server). My system is at run-level 3 (which means it does not have kdm running). It is also a fresh install of Mageia 4. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce 1. Activate screen lock (directly or indirect by putting the laptop to sleep) 2. Try to unlock (no password prompt is shown anyways) 3. Switch VT and login. Run ps command to check that the PID of the screen lock process is constantly changing. Reproducible: Steps to Reproduce:
Additional info: 1) Desktop effects are not enabled since required X extensions (XComposite and XDamage) are not enabled. 2) Widget style is Oxygen or Plastic (problem is seen in either case).
How exactly do you start KDE? It doesn't happen to me but I do use kdm.
CC: (none) => lmenutAssignee: bugsquad => mageia
In my previous comment I mentioned that run-level is 3 which implies that display manager is not running after boot. I launch X/KDE manually using 'startx' command.
(In reply to bolak T from comment #3) > In my previous comment I mentioned that run-level is 3 which implies that > display manager is not running after boot. I had read and understood that :) > I launch X/KDE manually using 'startx' command. Thanks
Summary: KDE screen lock goes into infinite loop (no way to unlock) => KDE screen lock goes into infinite loop (no way to unlock) - KDE started with startx
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD