Description of problem: When I enter my name in the KDE systemsettings -> Account details -> Password & User Account -> User information, then click "apply", it will pump out a window to ask my password to save information. After entering the password, the systemsettings hangs there. It happened everytime. Version-Release number of selected component (if applicable): 4.6.3 How reproducible: As described in the description Steps to Reproduce: 1. 2. 3.
What are you trying to do ? Update any else than your password ? With my own user i don't have any popup asking for a password . With the xguest user i've got a popup asking for a password (blank in the case of xguest user) but i don't have any hangs :/ Changing the password popup the window under my user but systemsettings does not hang either.
Keywords: (none) => NEEDINFOCC: (none) => balcaen.john
1. Install a fresh Mageia 1 RC1. 2. Create a new user account without .kde4 folder. 3. Launch systemsettings and Enter my name in the Account details -> Password & User Account -> User information, then click apply It jumped out a dialog and asked me password so that it could save my information. After inputting my password it hung there. I think the problem might be that, when I click Apply and input my password, it would launch chfn, which would ask my password if I call it in the shell. However, using kubuntu 11.04 would not have the same problem. It would even not ask my password. It just applied my changes.
Hum ok. Could you report it upstream with the full procedure to reproduce it & past the url here after ? aka like you said 1) create an user using adduser, create a password with passwd user 2) log to this user using su - user 3) launch systemsettings & have change the account detail.
I guess that if you're logging directly in this user you don't have this problem ?
(In reply to comment #3) > Hum ok. > Could you report it upstream with the full procedure to reproduce it & past the > url here after ? > aka like you said > 1) create an user using adduser, create a password with passwd user > 2) log to this user using su - user > 3) launch systemsettings & have change the account detail. Do you mean to report to KDE? But I wonder if it is a KDE problem or not, since I don't have the same problem using KDE 4.6.2 in Kubuntu 11.04. (In reply to comment #4) > I guess that if you're logging directly in this user you don't have this > problem ? I don't understand what you meant by 'logging directly in this user'. I thought I did log in my account directly (via kdm). What else could it be?
(In reply to comment #5) [..] > Do you mean to report to KDE? Yes. > But I wonder if it is a KDE problem or not, > since I don't have the same problem using KDE 4.6.2 in Kubuntu 11.04. > Well we're not using the same version of KDE here :/ > (In reply to comment #4) > > I guess that if you're logging directly in this user you don't have this > > problem ? > > I don't understand what you meant by 'logging directly in this user'. I > thought I did log in my account directly (via kdm). What else could it be? You did log via kdm ? When logging via kdm i'm not able to reproduce your problem :/ I'm only able to reproduce it if i create a new account & log in using the konsole (via su - $newuser) to start systemsettings.
ok seems like i'm able to reproduce in fact. i'll check a kubuntu because if i'm not wrong they are not using kcm_useraccount utility at all.
Hardware: i586 => All
Created attachment 422 [details] Screenshot of kcm_useraccount under ubuntu Ok i was wrong, they still using kcm_useraccount but they did disable the functionnality to change name.
Status: NEW => ASSIGNEDAssignee: bugsquad => balcaen.john
Ok i'm going to disable full name edition since we can use userdrake for this purpose.
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=156396
ok with the new kdebase4-4.6.3-2.mga1 you won't be able to edit the fullname anymore (yes it's just a workaround about the bug). You can still use userdrake for that purpose and we'll wait for upstream to fix it. I decreased priority & severity since we're waiting for upstream for that bug & we've got a workaround for the moment.
Keywords: NEEDINFO => UPSTREAMPriority: Normal => LowSeverity: major => normal
The upsteam bug report is still "new" and has gotten 40 votes so far.
CC: (none) => marja11
Keywords: (none) => NO_PATCH
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
I'm closing it as "works for me " since we're not able anymore to edit this section (even if the bug is still open upstream). For the record the bug affects mga1,mga2 & probably mga3 if it's not fixed for kde 4.9+
Status: ASSIGNED => RESOLVEDResolution: (none) => WORKSFORME