Bug 35390 - Account type changes
Summary: Account type changes
Alias: None
Product: accountsservice
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Matthias Clasen
QA Contact:
Depends on:
Reported: 2011-03-17 07:37 UTC by David Zeuthen (not reading bugmail)
Modified: 2011-03-17 13:02 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Proposed patch (7.04 KB, application/octet-stream)
2011-03-17 07:37 UTC, David Zeuthen (not reading bugmail)

Description David Zeuthen (not reading bugmail) 2011-03-17 07:37:19 UTC
Created attachment 44549 [details]
Proposed patch

From: David Zeuthen <davidz@redhat.com>
Date: Thu, 17 Mar 2011 10:30:07 -0400
Subject: [PATCH] Use wheel group instead of desktop_admin_r and nuke supervised accounts

See https://bugzilla.redhat.com/show_bug.cgi?id=688363 for details.

This change makes accountsservice stop depending on Fedora-specific
groups desktop_admin_r and desktop_user_r. Instead, being an
administrator is now equivalent to membership in the wheel
group. Which is what most Unix-grey-beards would expect.

Signed-off-by: David Zeuthen <davidz@redhat.com>
 data/org.freedesktop.Accounts.User.xml |    8 -----
 data/org.freedesktop.Accounts.xml      |    4 ---
 src/daemon.c                           |    8 ++---
 src/user.c                             |   45 ++++++++-----------------------
 4 files changed, 15 insertions(+), 50 deletions(-)
Comment 1 Ray Strode [halfline] 2011-03-17 10:47:58 UTC
*** Bug 35368 has been marked as a duplicate of this bug. ***
Comment 2 Bill Nottingham 2011-03-17 11:11:52 UTC
Bug 35368 isn't a dup of this... this bug just changes what's hardcoded.
Comment 3 Ray Strode [halfline] 2011-03-17 11:33:15 UTC
The bugs are closely enough related that I think we should deal with them at the same time.  I merged it this direction instead of the other way since this bug has a patch.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.