maemo.org Bugzilla – Bug 4043
Application Manager should not depend on "user" account
Last modified: 2009-07-14 13:37:57 UTC
You need to
before you can comment on or make changes to this bug.
Hildon Application Manager depends on a "user" account in three places:
1) h-a-m.init starts the given process as `user'.
2) postinst migrates user settings for old versions of HAM from
3) sudoers is modified to allow `user' to call apt-worker and the various
This is a problem on non-Maemo systems (such as Mer) which do not mandate a
single user account called `user'.
The diff at the above URL solves all of these problems in a way compatible
with both Maemo *and* Mer, and so it would be good to have included upstream.
#1 h-a-m.init starts the process as `nobody' - an account which is
guaranteed to exist on both Maemo, Ubuntu, Debian and Mer.
#2 postinst migrates settings from /home/*, rather than just /home/user.
This isn't robust in all possible edge-cases, but handles the default
home directory locations on Debian. Ubuntu, Maemo & Mer. Also, if no
home directories exist, it is a no-op, rather than failing.
#3 Instead of granting the permissions in sudoers to `user', they are
granted to `%users' - i.e. all users in the "users" group. Since
on Maemo `user' belongs to that group, this change is safe both on
Maemo & Mer.
Any questions, please don't hesitate to ask: it is important for code which is
shipped on Maemo and Mer to be as close as possible (IMHO), and these small
changes do enable closer codebases between the two.
Created an attachment (id=1116) [details]
Patch equivalent of r7 in launchpad
Adding file encompassing the diff.
FIXED in Fremantle (but after SDK beta release).
Fix should be included in Fremantle SDK beta 2 hence updating Target Milestone.
If you are the reporter of this bug: Feel free to verify the fix if possible.