arkose crashes when uid 1000 doesn't exist
Bug #1055677 reported by
Stéphane Graber
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| arkose (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Arkose seems to rely on UID being set in the environment or uid 1000 existing as a fallback.
Running on a system where uid 1000 doesn't exist causes a stacktrace at startup time.
The fix is to change arkose's cli tool to use the same uid logic as the python module, which is to first look at PKEXEC_UID, then SUDO_UID, then UID and finally try 1000.
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in arkose (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package arkose - 1.5.1-0ubuntu3
---------------
arkose (1.5.1-0ubuntu3) quantal; urgency=low
* When running under sudo, use SUDO_UID instead of falling back on the
potentially non-existing uid 1000. (LP: #1055677)
-- Stephane Graber <email address hidden> Mon, 24 Sep 2012 14:09:44 -0400