Version: 2.1 (using KDE 3.5.6, Kubuntu (edgy) 4:3.5.6-0ubuntu1~edgy1) Compiler: Target: x86_64-linux-gnu OS: Linux (x86_64) release 2.6.17-11-generic I am using KUser 2.1 on Ubuntu and for unknown reasons I cannot enter any users or groups into ldap data base as I used todo with previous versions of KUser. When adding a "ldapest" user and group with LdapBrowser (Java app) this "ldaptest" user is available : - by logging from a console, - for connection with kdm. So maybe something is wrong in my Kuser settings but I do not think so !
And how did you set up KUser? Any error messages when trying to add an user/group?
Sorry I did not enter the full username "cn=admin,ou=ressources,dc=azun,dc=bearn,dc=net" along with the password in the logging window but only "cn=admin,ou=ressources" when I reported unapropriately my bug. The problem I have though is that I have to log all the time in the logging window for both users and groups and I do no see which option I have to set to avoid this all the time over and over. Before I think all this could be memorized for direct access to Kuser Ldap data ! Is this a bug or can this be fixed. Thanks.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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 mark the bug 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!
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!