After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 395056 - Changing UID needs notice to reboot
Changing UID needs notice to reboot
Product: gnome-system-tools
Classification: Deprecated
Component: users-admin
Other Linux
: Normal normal
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
Depends on:
Reported: 2007-01-10 16:32 UTC by Sebastien Bacher
Modified: 2009-08-20 16:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18

Patch to address problem (1.24 KB, patch)
2007-01-13 01:14 UTC, Bryce Harrington
needs-work Details | Review

Description Sebastien Bacher 2007-01-10 16:32:49 UTC
That bug has been opened on

"Binary package hint: gnome-system-tools

This is tested against Feisty.

From User settings, go to Properties for the currently logged in user, select the Advanced Tab, and change the User ID to a different number, and click Okay.

It becomes impossible to launch other applications (for example, restarting the User settings dialog). Logging out results in a number of error messages from Gconf and other gnome system tools.

Perhaps the safest behavior would be to prohibit changing the UID of the currently logged in user. The ideal solution would be to delay the change until the next login, but I don't know if gnome-system-tools is set up to do that."
Comment 1 Bryce Harrington 2007-01-13 01:14:13 UTC
Created attachment 80161 [details] [review]
Patch to address problem

Here's a proposed patch to fix the problem.  I'm a bit iffy on relying on the USERNAME environment variable, but it seems to work ok on my Ubuntu Feisty system.
Comment 2 Carlos Garnacho 2007-02-11 17:33:31 UTC
Thanks a lot for working on this issue, however, it should also apply to *any* logged in user, not just the one who's running the tools, and should guard against deleting the user, not just modifying it.

IMHO a proper fix would be getting UTMP info (kind of like what /usr/bin/who does) to know which users are logged in.
Comment 3 Milan Bouchet-Valat 2009-08-20 16:08:25 UTC
Fixed in 47f51819808cdada015c480f81bc5664a9cae4e5. We now disable the entry when user is logged in, and show a notice.

Bryce: using oobs_user_get_active (user) you could get what Carlos wanted - but this function is not listed in the docs for some reason. ;-)