After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 683822 - 3.5.91: unlocking user panel doesn't allow changing user name or account type
3.5.91: unlocking user panel doesn't allow changing user name or account type
Status: RESOLVED DUPLICATE of bug 684207
Product: gnome-control-center
Classification: Core
Component: User Accounts
3.5.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-09-11 19:11 UTC by Olav Vitters
Modified: 2012-09-18 22:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Olav Vitters 2012-09-11 19:11:05 UTC 
To reproduce:
1. Goto System Settings
2. Click User Accounts
3. Click Unlock
4. Try to change account type or the username

Result:
- Cannot change account type or the username

Expected:
- Can change the account type or the username
Comment 1 Ondrej Holy 2012-09-13 13:04:58 UTC 
I'm not able to reproduce the bug. Unlocking and changing the user name and the account type works for me correctly in 3.5.91.
Comment 2 Matthias Clasen 2012-09-13 21:23:23 UTC 
Turns out I needed update my accountsservice to 0.6.24 - 0.6.22 doesn't have the is-local property, so the user panel was treating all accounts as remote
Comment 3 Olav Vitters 2012-09-13 21:29:17 UTC 
Ah, can we update the buildrequirement?
Comment 4 Matthias Clasen 2012-09-14 15:34:08 UTC 
We can, but it is really more of a runtime requirement.
Comment 5 Olav Vitters 2012-09-16 23:31:21 UTC 
I know, but this notifies the packager to upgrade another component.

Else just resolve this bug.
Comment 6 Bastien Nocera 2012-09-18 22:31:06 UTC 
The bug you've seen (all users being treated as remote for older versions of accountsservice) was worked-around in the fix for bug 684207, so I'll close this as a dupe.

*** This bug has been marked as a duplicate of bug 684207 ***