Bug 437317 - user added via firstboot should then be visible in gdm
Summary: user added via firstboot should then be visible in gdm
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F9Blocker
TreeView+ depends on / blocked
 
Reported: 2008-03-13 15:13 UTC by Jeremy Katz
Modified: 2008-03-19 18:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-19 18:27:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jeremy Katz 2008-03-13 15:13:29 UTC
When installing, one of the steps is adding a user in firstboot.  Not having
this user show up in the list of the greeter seems suboptimal

Comment 1 Ray Strode [halfline] 2008-03-13 16:18:57 UTC
Totally agree.

GDM gets the list of users from ConsoleKit.  See ck-history --frequent.

I guess firstboot should tell ConsoleKit about the new user.

Jon, what's the best way to do that?


Comment 2 Jeremy Katz 2008-03-13 18:34:26 UTC
It's more than just firstboot, though.  It's just as true if I add a user via
system-config-users.  Or useradd in the livecd initscript.

While ck-history --frequent could be nice for the case where I have centralized
account management and not wanting to deal with lag to get account lists via nis
or AD, in many deployments (especially with Fedora) that's just not the case. 
Instead it's a small number of local accounts.  So I really think this is better
fixed in gdm than having to spread changes all over the world.

Comment 3 Ray Strode [halfline] 2008-03-19 18:27:46 UTC
Jon made GDM include local users now.


Note You need to log in before you can comment on or make changes to this bug.