Please don't bother installing Jaunty - if that's failing in Karmic,
that's enough for me. So to sum up, it seems that both PolicyKit and
gksu authentications fail. Does a simple "sudo echo test" works? I guess
not, but I'd like to be sure. A log that you could also post here is
/var/log/auth.log (
Hmm... Charlie, I did not notice your step:
3. enter "sudo passwd expiry USER1"
Is there a specific reason why you didn't use the standard 'passwd' command?
Could you post the log when using it? Don't even use 'sudo passwd', as it
doesn't work the same way. Does it work then?
Anyway, the gnome-s
That doesn't work because you're passing the '-e' option, which means:
mark the password for expiration to force the user changing it on next
login. That operation requires admin rights. BUT please simply use
'passwd', without anything else.
(This is the best way of changing passwords in the gener
That's not a workaround, that's the normal procedure. Why would you use
'passwd -e' in the first place, if you want ot change your own password?
The only bug I can see here is that PolicyKit should allow users to
authenticate even if their password is marked for expiration until they
log change it
** Bug watch added: freedesktop.org Bugzilla #25461
https://bugs.freedesktop.org/show_bug.cgi?id=25461
** Also affects: policykit via
https://bugs.freedesktop.org/show_bug.cgi?id=25461
Importance: Unknown
Status: Unknown
--
Changing your password does not allow admin authenticati
OK, I've just committed a fix that allows IDs to be handled correctly as
long as they don't go beyond G_MAXINT32 when the system supports it,
which means on Ubuntu you can go up to 2,147,483,647. I guess that's
enough for most people, but I'll see if we can guarantee we support the
full range for 3
** Changed in: system-tools-backends (Ubuntu)
Status: Confirmed => Triaged
--
ecryptfs Private directory not mounted after changing password in users-admin
https://bugs.launchpad.net/bugs/307019
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is su
*** This bug is a duplicate of bug 490093 ***
https://bugs.launchpad.net/bugs/490093
Yeah, that was a little hard to find, but that's actually bug 490093,
which was spotted recently. The problem is that we're starting another
tool (about-me) to change the password, and that when you have chang
Are people actually watching liboobs development?! ;-)
I've tried using << before, but I was getting strange results because when
converting the constant value to signed int, something was going wrong and I
was getting -GMAX_INT32. I've tried again with your solution, and that does not
work eit
That won't happen, as explained by Chris in the previous comment. It's
far too late now, that will be for Lucid.
--
System > Administration >Services (services-admin) missing (Karmic)
https://bugs.launchpad.net/bugs/437905
You received this bug notification because you are a member of Ubuntu
Desk
Development version 2.29.1 contains the fix for the "GID is 0 on start"
problem, and also prevents you from choosing already used GIDs when
creating/editing groups.
** Changed in: gst
Status: Fix Committed => Fix Released
--
[users-admin] Group Properties dialog sets GID to 0 on first lau
Hm, silly: the latter is actually not in 2.29.1, but will be in the next
release. Anyway, that's for Lucid.
--
[users-admin] Group Properties dialog sets GID to 0 on first launch
https://bugs.launchpad.net/bugs/475974
You received this bug notification because you are a member of Ubuntu
Desktop B
This is now fixed upstream. Since deluser does not remove active users,
we simply refuse to delete them, showing a dialog: "John Doe is
currently using this computer. Please ensure the user has logged out
before deleting this account."
Feel free to suggest a better formulation if you find one... ;
This is now fixed upstream, will be included in 2.29.2.
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New => Fix Committed
--
users-admin fakes adding groups with existing gid
https://bugs.launchpad.net/bugs/491434
You received this bug notif
Thanks for your report. I don't think the problem you describe is a bug,
rather an intended feature. There's no Cancel button: you can't close it
without applying the changes you've performed, because they are applied
on the go. I don't see how this behavior could hurt anybody: you can
always rever
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
David: what's your problem exactly? You can set up a password for root
in Karmic too, it's just that PolicyKit won't allow you to enter the
root password to authenticate. I fail to see how upgrading from Intre
Oh, sorry, your problem wasn't clear to me. I'm not very familiar with
gnome-network-properties, since it's not actually part of the gnome-
system-tools, as you originally reported it (I know, it's confusing...).
So the issue is that you are using different proxies for various
protocols, the conne
I'd avise you to report that upstream before you start working on it.
It's possible that the problem is known, maybe even already fixed.
Unfortunately, bugzilla.gnome.org is down for the week-end... Maybe it
would be worth waiting monday - that's up to you. Else, sure, you can
attach the patch here
I think we could add this option to the new Advanced Settings dialog,
but we won't move home dir and other things: just rename the user in
/etc/passwd. Not sure our architecture allows for this easily.
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed => Triaged
--
Can not chan
Any trace of this bug in Karmic (or at least Jaunty)? I really can't
afford going through our code in Hardy to check where this was coming
from, we have already enough bugs to tackle in recent versions. The
trace upstream is too old, I'll have to close the report there without
more information.
--
Sorry, it's been a long time since you reported this bug. Sadly, we need
more information to work on it. The chances are low we can actually do
anything about it, since it's kind of late to get the details... :-(
First, did it happen after you had changed user settings via
System->Administration->
Development version upstream has a GConf option to show root, which
means its hidden by default.
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New => Fix Committed
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed => Triaged
Thanks for your report. Could you report each problem separately?
There's absolutely no chance that a developer will try to fix all those
bugs at once, you're discouraging people from reading your report. And
feature requests such as "please write a GUI for XXX" are completely
useless: we know this
Thanks for your report. I'm not able to reproduce your problem. Can you
confirm it still exists in Karmic? Thanks!
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-system-tools (Ubuntu)
Status: New => Incomplete
--
[users-admin] adding ne
That's a problem with the installer that does not add the user to all
the privilege groups used in Ubuntu. Have a look at /etc/gnome-system-
tools/profiles for a list of them.
** Package changed: gnome-system-tools (Ubuntu) => user-setup (Ubuntu)
** Changed in: user-setup (Ubuntu)
Importance:
** Package changed: gnome-system-tools (Ubuntu) => network-manager
(Ubuntu)
--
Network manager deletes eth1 default gw when eth0 has Static IP
https://bugs.launchpad.net/bugs/223575
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-s
Fixed in Karmic AFAICS.
** Package changed: gnome-system-tools (Ubuntu) => language-selector
(Ubuntu)
** Changed in: language-selector (Ubuntu)
Importance: Undecided => Low
** Changed in: language-selector (Ubuntu)
Status: New => Fix Released
--
[intrepid][gnome-language-support] pro
Thanks for your report. I think the problem you describe is an intended
feature: developers upstream have considered this option was not useful
for enough users, and it makes our control center more complex for
everyone.
Though, you can start 'gconf-editor' and tune the key
/apps/nautilus/preferen
** Package changed: gnome-system-tools (Ubuntu) => human-theme (Ubuntu)
--
Bug in human-theme_0.18_all.deb prevents upgrade
https://bugs.launchpad.net/bugs/222330
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubunt
This is not committed in Ubuntu. It's committed upstream, waiting for a
release upstream (2.29.2) to be committed on Ubuntu's Baazar repository,
and then released in Lucid. See https://wiki.ubuntu.com/Bugs/Status.
Thanks for helping, though! ;-)
** Changed in: gnome-system-tools (Ubuntu)
S
jxparo: are you sure you are in Manual mode? I've reinstalled the gnome-
system-tools and I can still see this button in this mode. And I don't
see the patch that used to hide it in Ubuntu.
--
time-admin does not update time
https://bugs.launchpad.net/bugs/400130
You received this bug notificatio
I've no personal problem with that, but if we don't respect what we
write on the Wiki, we may as well change it instead of using
inconsistent statuses. Don't worry about the wrong upstream status for
that, I always go over all bugs registered in the GNOME System Tools
Launchpad project (i.e. for up
That's tightly related to bug 484559. If you don't mind losing the
improvement brought by fixing bug 307019, I think you can commit the
debdiff that is available on the former. Anyway the goal is to get rid
of this hack and do all the work right by ourselves, i.e. without
dependencies.
--
gnome-s
If it's just for reviewing purposes, the only changes I added are in:
> about_me_path = g_find_program_in_path ("gnome-about-me");
> show_passwd = (user != oobs_self_config_get_user
> (OOBS_SELF_CONFIG
> (GST_USERS_TOOL (tool)->se
The rationale behind this feature vs. the standard nullok_secure way is
that *you actually have a password*. This means users can be admins,
type their password to use sudo, PolicyKit or lock their screen, but
they are not asked to type it on login. They can additionally connect
over local SSH for
Could you follow the procedure at
https://wiki.ubuntu.com/DebuggingGnomeSystemTools#For%20Users%20[users-
admin] to provide more information? This way we would be able to find
out what's going on. Thanks!
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete => Confirmed
** Changed
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete => Fix Released
--
[hardy] Unlock button not in dialog
https://bugs.launchpad.net/bugs/245809
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
Thanks for your report. This was indeed a silly detail that I've just
fixed. It will be available in the next minor release.
Please continue to report bugs about the gnome-system-tools, especially
the next version that should land in Lucid in a month or so. Not many
people do this, which makes you
*** This bug is a duplicate of bug 210710 ***
https://bugs.launchpad.net/bugs/210710
Hmm, seems a duplicate of bug 210710. Please follow the instructions I
gave in my latest comment there, and I'll have a look. So far, your
/etc/passwd file looks right to me. And AFAICT the root account is
alw
You could just try changing in /etc/login.defs
UID_MAX 6
I think that should do the trick. Then it would mean the bug is in the
program that set this value...
--
System > Admin > Users and Groups: only root available
https://bugs.launchpad.net/bugs/210710
You received this bug notification b
It's not unlikely that users-admin itself has introduced those broken
settings, but we can't really be sure. I'd need a list of all programs
that may change this file (maybe there aren't at all). But that doesn't
mean there isn't something broken here. I've checked our code, and
everything seems fi
In Karmic, I can confirm that the -m Platform script does not die after
3 minutes, consuming 10MB until reboot. I'll give a look at this
problem.
Though, you mention in the description that there's a 90MB usage on
first launch. I guess this comes from the package installation, isn't
it? If that us
Pjotr12345: please report your problem separately against the package
'passwd', this has nothing to do with the present bug. BTW, when
changing your own password, you should use 'passwd' instead of 'sudo
passwd'. The latter won't update your eCryptfs Private dir and your main
keyring password. Plea
So by "first time" you mean first time from fresh boot; there's no
package installation involved then. I think you're slightly wrong about
memory usage, because the fact that every SystemToolsBackends perl
process uses 10MB doesn't mean you can sum up those values to get the
total: there's shared m
ceciliavergara: Please don't open new tasks against upstream projects
without any explanation. Why do you think this bug is still valid? I've
just tried to reproduce it, and it seems be fixed.
** Changed in: gst
Status: New => Invalid
--
[network-admin] Gtk-WARNING **: Unknown property: G
Good news, I've just finished a future patch that allows us to stop
creating the main group ourselves. When creating an user, the backends
can now omit the --gid option, and we let adduser (and equivalents) do
the work. This is simpler for everyone. Should be in the next release.
Now I need to get
** Changed in: gst
Status: Fix Committed => Fix Released
--
[network-admin] Modem connection types not listed
https://bugs.launchpad.net/bugs/485641
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
If you are willing to help debugging this, then please run 'sudo ntpd
-q' and report its output, and whether that fixes the problem. Is your
clock highly different from the real hour, i.e. by hours as the title of
the bug says?
--
[jaunty] Synchronizing with a time server does not work when time
Thanks for your report. Actually, you're not using network-admin from
the gnome-network-admin package, but network-manager. Reassigning.
I think you should tell us what kind of encryption is using your
network: WEP or WPA? And what type of password authentication too.
** Package changed: gnome-sy
OK, sorry for the delay Roger. So if I understand correctly, the only
way to reproduce this problem is to create a new user when the users
list appears empty? That would be logical, since we commit the data we
have, which would be empty if it could not be loaded.
But do you mean that the second ti
This Debian bug is not related at all.
** Changed in: debian
Importance: Unknown => Undecided
** Changed in: debian
Status: Fix Released => New
** Changed in: debian
Remote watch: Debian Bug tracker #470123 => None
** Changed in: debian
Status: New => Invalid
** Also affects:
What I asked Xande to test should be interesting for you too:
One interesting test (for both of you) would be to start the scripts before
starting users-admin, and to compare the startup times: start users-admin once,
run it again and see the time it needs, then wait for 5 minutes so that the
sc
Chris, you said you were able to reproduce the problem too? So that
wouldn't be specific to the reporter's configuration... I'm absolutely
not able to see this, maybe I'll have to get the package form Lucid.
--
Users-admin password->password confirm requires 2 Tab keys
https://bugs.launchpad.net/
Confirmed for the power menu part. But you can choose language (Alt+L)
and log in right after, just type the password and hit Return.
** Summary changed:
- karmic gnome login requires mouse
+ Can't access GDM's power menu with keyboard
** Package changed: gnome-system-tools (Ubuntu) => gdm (Ubun
Good catch indeed! That's the button used to change password when the
selected user is the current one. Does the bug appear only with that
user? In other cases, it should be hidden.
Anyway, this hack should go away in the next release, with a more
generic dialog from upstream.
--
Users-admin pas
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m U$
This is a bad copy/paste: U$ can't work, obviously, that should be UsersConfig.
/usr/sbin/system-tools-backends
Should be /usr/bin/system-tools-backends in 8.04.
Anyway, you don't need to run those to perform the test I sug
Thanks for your report. We need more information to debug it. Could you follow
the instructions at
https://wiki.ubuntu.com/Apport#How%20to%20enable%20apport
to get a stacktrace? Thanks!
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-system-tool
*** This bug is a duplicate of bug 490093 ***
https://bugs.launchpad.net/bugs/490093
Thanks for your report. This bug is actually a variant of bug 490093.
The whole problem is that we start gnome-about-me to change the
password, so it doesn't integrate well with users-admin. In Lucid I hope
to
Hey, I didn't see that was you! Are you sure you followed the right
instructions? There are Apport informations here, but no stacktrace.
--
users-admin don't start - segmentation fault
https://bugs.launchpad.net/bugs/505902
You received this bug notification because you are a member of Ubuntu
Des
The best would be that you double click on that .crash file, and follow
the instructions to open a new bug. This way apport will be able to find
the symbols that are missing in the above trace. As it is now, it's very
hard to find the problem. Thanks again!
--
users-admin don't start - segmentati
Fixed in 2.29.2.
** Changed in: gst
Status: Fix Committed => Fix Released
--
users-admin: shortname field does not update when name field is cleared.
https://bugs.launchpad.net/bugs/498970
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
Fixed in 2.29.2.
** Changed in: gst
Status: Fix Committed => Fix Released
--
shows root user in users-admin
https://bugs.launchpad.net/bugs/188757
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
Thanks for your report. Does that happen when changing your own
password, or when changing password for other users? Two different
programs are used for these operations.
** Changed in: gnome-system-tools (Ubuntu)
Status: New => Incomplete
** Changed in: gnome-system-tools (Ubuntu)
Impo
In 2.29.2 we let adduser choose the main group, so that must be fixed.
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New => Fix Released
--
[users-admin] adding new user sets groups to nogroup
https://bugs.launchpad.net/bugs/313990
You receiv
This is fixed in 2.29.2, even if Launchpad doesn't show it.
--
[users-admin] should warn the user of what he's doing when unselecting the
administration group
https://bugs.launchpad.net/bugs/25947
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Fixed in 2.29.2.
** Changed in: gst
Status: Fix Committed => Fix Released
--
users-admin fakes adding groups with existing gid
https://bugs.launchpad.net/bugs/491434
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-too
Fixed in 2.29.2.
** Changed in: gst
Status: Fix Committed => Fix Released
--
users-admin pretends logged in users can be removed, while they aren't
https://bugs.launchpad.net/bugs/349453
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribe
Hmm, I've checked how this could be implemented, and I'm sorry to say
you that would be very hard. Currently, we are identifying users with
their login, which means anything can change but that setting. Else we
wouldn't be able to find what user it corresponds to.
I'm not sure there are very commo
No news on that bug?
--
users-admin lies about changing home directory
https://bugs.launchpad.net/bugs/484501
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.
This has been fixed in 2.29.1, already in Lucid for some time.
** Changed in: gst
Status: Fix Committed => Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Low
--
Pleas
This is fixed in Lucid with 2.29.1 for some time.
** Changed in: gst
Status: Fix Committed => Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Low
--
[users-admin] Shel
In 2.29.2 we let adduser create the home directory from the login name.
Home dir can only be changed for existing users, this is a design
decision. So this bug can't happen now, since it would mean that a user
with the same login already exists, which we don't allow.
I've just tested it with addus
Fixed in Karmic with 2.28.1.
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Low
--
System groups are hidden
https://bugs.launchpad.net/bugs/442806
You received this bug notification becau
Fixed in 2.29.2 upstream.
--
Users Administration Tool should enable to delete home directory
https://bugs.launchpad.net/bugs/123490
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubunt
I consider this fixed in Lucid with the new design. We don't really
follow your ideas, but we now show user profiles instead of detailed
privileges, which is explained in one word on the main window.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: gn
onfirmed => Triaged
** Changed in: gnome-system-tools (Ubuntu)
Assignee: Milan Bouchet-Valat (nalimilan) => (unassigned)
--
creating new user account silently fails when UID is already used
https://bugs.launchpad.net/bugs/372695
You received this bug notification because you are a me
As I said, that's not primarily a users-admin problem for me. Anyway, in
Lucid we now hide the detailed privileges in an Advanced dialog.
** Package changed: gnome-system-tools (Ubuntu) => ubuntu-meta (Ubuntu)
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided => Low
--
Remove obsolet
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed => Triaged
--
[users-admin] users & groups: should have some mention than a session restart
is required to apply a group change
https://bugs.launchpad.net/bugs/48262
You received this bug notification because you are a member of
OK, this is now in 2.29.2, should be in Lucid soon.
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New => Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed => Triaged
** Changed in: gnome-system-tools (Ubuntu)
Sorry if I change my mind, but I don't see how this could happen. We
need a list of groups desktop users and administrators should be in, and
it would be very complex to make that list dynamic. OTOH, it would be
really easy to put in that list groups that *may* be used even if they
don't exist, sin
** Changed in: gnome-system-tools (Ubuntu)
Status: New => Triaged
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Low
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New => Confirmed
--
[users-admin] default first
Sorry then, I'm closing this report because we won't be able to get
enough information. But I have other reports with similar problems that
reporters are able to reproduce, we may eventually fix it. Anyway in
Lucid we are much more careful when committing changes, that should
partly fix it.
** Cha
users-admin 2.29.1 (in Lucid) accepts underscores even for new users.
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed => Fix Released
--
[users-admin] Don't accept underscore "_" in usernames
https://bugs.launchpad.net/bugs/49296
You received this bug notification because you
If these groups are really obsolete, we should not create them at all,
they would disappear from users-admin.
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided => Low
--
User Privileges ignored
https:/
Thanks for your report. Are you still able to reproduce it? I'd like to
see if we can fix it.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-system-tools (Ubuntu)
Status: New => Incomplete
--
newly created user account freezes the syste
This is fixed in 2.29.2 which should be in Lucid soon.
--
Removing a user does not remove its main group
https://bugs.launchpad.net/bugs/192443
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@
Thanks for your report. Are you able to reproduce this problem? I'd
really like to fix that if we can get enough information.
At least I'm sure that in Lucid users won't be affected, and groups
won't be removed. Only group membership will be affected, which is still
a problem though.
** Changed i
This is fixed upstream with 2.29.2. Should be in Lucid soon.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: gnome-system-tools (Ubuntu)
Status: New => Triaged
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: g
Hey, thanks for the patch, but we needed a little more than that to make
the file translated: Makefile.am had to be changed too, that was a
little tricky. See http://git.gnome.org/browse/gnome-system-
tools/commit/?id=4b3806048a0e0913b78615c85db6c43853151d1f.
Feel free to suggest other patches in
Thanks for the report, but in 2.29.2 (in Lucid) we don't allow selecting
any other setting than Real name and login when creating and user. You
can only change the main group after that. So that bug is obsolete.
** Changed in: gnome-system-tools (Ubuntu)
Status: New => Invalid
--
[users-a
This is fixed with 2.29.2.
--
[users-admin]cannot create user when the /home directory already exist
https://bugs.launchpad.net/bugs/190815
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
desktop-bugs ma
Since 2.29.1 in Lucid we no longer use the unlock button, so that's
obsolete.
** Changed in: gnome-system-tools (Ubuntu)
Status: New => Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Low
--
users-admin doesn't fully update UI after unlock
https://bugs
No news on that bug?
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-system-tools (Ubuntu)
Status: New => Incomplete
--
Cannot unlock user priveledges.
https://bugs.launchpad.net/bugs/282065
You received this bug notification because you
Since Karmic we show all system groups by default, regardless of system
users being hidden.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: gnome-system-tools (Ubuntu)
Status: New => Fix Released
--
users-admin should have a 'show all groups
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed => Triaged
--
in users-admin the name 'root' is checked instead of uid 0
https://bugs.launchpad.net/bugs/255980
You received this bug notification b
In 2.29.2 we hide root, and don't allow the last admin to be removed. If
user is about to lose its own admin rights, we warn him. For home
directory, there will be more improvements to come, like making user the
owner of the dir.
** Also affects: gst
Importance: Undecided
Status: New
**
** Summary changed:
- Unexpected display of /etc/group nfs entry in the user setting interface.
+ [users-admin] Unexpected display of /etc/group NIS entry
--
[users-admin] Unexpected display of /etc/group NIS entry
https://bugs.launchpad.net/bugs/107422
You received this bug notification because
Too bad, that's generally the problem with such major bugs - they happen
only once, else we would have fixed that for a long time. As I said, I
can't happen anymore in Lucid, at least not with such harsh
consequences. For the rest (group memberships), I let you follow
progress on bug 240437 if you
Yeah, that's it. Sorry for the short comment, that was mainly a
technical note for reference when we will be able to close it after the
upload.
But don't hope for a SRU, that fix relies on a whole series of
architectural changes that are being introduced in Lucid.
--
[users-admin]cannot create u
Well, we respect the settings from /etc/adduser.conf and
/etc/login.defs/. Just change the min value to 500, and you're good. We
can't guess that number for you.
--
Creating users with UID under 1000 creates account but it is hidden in GUI
https://bugs.launchpad.net/bugs/99265
You received this b
201 - 300 of 1160 matches
Mail list logo
