Bug 10105 – GUI installer does not list users for domain logons (due to adduser.conf)

Bug 10105 - GUI installer does not list users for domain logons (due to adduser.conf)


Summary:	GUI installer does not list users for domain logons (due to adduser.conf)

Status:	UNCONFIRMED

Product:	Development platform
Component:	installer
Version:	5.0-final
Platform:	All Linux

Importance:	Low normal (vote)
Target Milestone:	---
Assigned To:	J-P Jokela
QA Contact:	sdk-installer-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-05-05 12:18 UTC by Tatu Kilappa
Modified:	2010-05-10 09:11 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Changes SDK GUI installer to include logged-in users in addition to users with UIDs within the limits from adduser.conf. (1.06 KB, patch) 2010-05-05 12:26 UTC, Tatu Kilappa	Details
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description Tatu Kilappa (reporter) 2010-05-05 12:18:53 UTC

SOFTWARE VERSION:
maemo-sdk-install-wizard_5.0.py

EXACT STEPS LEADING TO PROBLEM: 
1. Start GUI installer (with sudo).
2. Move on to target user selection page.
3. Desired user not present in selection or selection is empty

EXPECTED OUTCOME:
Current user is selectable from list.

ACTUAL OUTCOME:
User is missing or the list is downright empty.

REPRODUCIBILITY:
Always, assuming desired target user using domain login.

OTHER COMMENTS:
The bug is related to get_all_usernames() -function in the SDK GUI installer.
The minimum and maximum UIDs are first specified to the integer limits, but
after reading adduser.conf, they will be overwritten with FIRST_UID and
LAST_UID extracted therefrom.

This behavior is sensible, but assuming the SDK should be installed for a user
that is logged via domain logon and has an UID outside the limits, that user is
not selectable from the list.

One possibility would be to at least check which users are currently logged in
the machine via a TTY or PTY and at least include them if no-one else. I will
attach a small patch that will do this.

Note: The installation will fail for users with domain logon anyway due to bug
9803, so I set the priority of this bug to low:
https://bugs.maemo.org/show_bug.cgi?id=9803

Comment 1 Tatu Kilappa (reporter) 2010-05-05 12:26:07 UTC

Created an attachment (id=2688) [details]
Changes SDK GUI installer to include logged-in users in addition to users with
UIDs within the limits from adduser.conf.

A better way would perhaps be to disable adduser.conf limits altogether if the
system has logged-in users outside the range defined by FIRST_UID and LAST_UID.

Comment 2 Ruslan Mstoi nokia

2010-05-07 16:59:51 UTC

Hi Tatu,

More info would be nice. Like what sort of domain login and what is your UID?

Can't the FIRST_UID-LAST_UID range in adduser.conf be adjusted to include UIDs
of domain logins?

I guess that would be better approach, because not only installer uses these
limits, but other programs too, e.g. kuser.

What could be done in the installer is a possibility (checkbox) to show all
users.

Thanks.

Comment 3 Tatu Kilappa (reporter) 2010-05-10 09:11:50 UTC

> More info would be nice. Like what sort of domain login and what is your UID?
> Can't the FIRST_UID-LAST_UID range in adduser.conf be adjusted to include UIDs
> of domain logins?

The system's using Active Directory domains with ids in the range of 300
million or so. adduser.conf is the normal one for Debian/Ubuntu etc. limiting
ids to between 1000 and 29999. It should not be modified, since this is
intentional to prevent adding local users with ids that would conflict with
those from AD.

> What could be done in the installer is a possibility (checkbox) to show all
> users.

This would probably be just fine. I tried disabling the adduser.conf limitation
from the script, and it worked too.

> I guess that would be better approach, because not only installer uses these
> limits, but other programs too, e.g. kuser.

Could this be related to bug 9803 mentioned earlier? I sidestepped the issue
for now by creating a local user I installed the SDK for.