Here's an updated version of Jame's original patch, which used
g_find_program_in_path() to check that gnome-about-me is present. If
that's not the case, the normal password entries are shown, just like we
do for other users than the current one. The patch was written in such a
way that updating it
The fix only contains the minimal changes we need to avoid giving users
admin rights. We try not to introduce important changes in stable
releases, and absolutely never change the user interface. I'll fix that
for the next release, that's quite easy to do actually.
As for the label of the button,
*** This bug is a duplicate of bug 475974 ***
https://bugs.launchpad.net/bugs/475974
Good catch! That's a very bad side-effect of bug 475974, which already
has a fix committed upstream. Sadly we spotted it too late to include it
in 2.28.1... I'm not sure about the security vulnerability tag,
As reported in the duplicate bug 486130, this has more dramatic
consequences when creating a group: the GID is set to 0 by default,
which leads to adding users to the root group without notice. While
admins can be clever enough to change that, people may still miss this
detail, which could be
*** This bug is a duplicate of bug 463353 ***
https://bugs.launchpad.net/bugs/463353
** This bug has been marked a duplicate of bug 463353
[users-admin] Modifying user has no effect
--
users-admin lies about changing home directory
https://bugs.launchpad.net/bugs/484501
You received this
*** This bug is a duplicate of bug 386407 ***
https://bugs.launchpad.net/bugs/386407
This is not a problem in the gnome-system-tools actually. It was already
reported a while ago in network-manager-applet, where it should belong.
** Package changed: gnome-system-tools (Ubuntu) =
So I close the report. Feel free to reopen it if you or anybody else is
able to provide more information. Thanks for your help in improving
Ubuntu, anyway!
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Invalid
--
Users/Groups app doesn't allow changing of anything
*** This bug is a duplicate of bug 463353 ***
https://bugs.launchpad.net/bugs/463353
** This bug has been marked a duplicate of bug 463353
[users-admin] Modifying user has no effect
--
Changing Main group with users-admin GUI fails
https://bugs.launchpad.net/bugs/472525
You received this
I'm closing this report because we lack information to fix it. If you
can provide it to use at any time, please reopen it. Thanks!
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Invalid
--
Unexpected error when authenticating
https://bugs.launchpad.net/bugs/222571
You
Closing because we lack the information we need to fix the bug. Feel
free to reopen it if you can provide it to us. Thanks!
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Invalid
--
Having trouble adding user to multiple groups at once through gnome groups
applet
** Package changed: gnome-system-tools (Ubuntu) = gnome-control-center
(Ubuntu)
--
Network Proxy Preferences locations doubled
https://bugs.launchpad.net/bugs/337595
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
Proposal for SRU: either install gnome-about-me on Xubuntu, which will
require splitting it from the gnome-control-center package, or update
the Ubuntu patch to users-admin so that it checks that gnome-about-me is
present before hiding the original password fields. What way sounds the
best to you?
So that's a little more complex. Removable disks have the Eject and
Remove safely options, other drives don't. Asking upstream why it
words that way.
** Changed in: nautilus (Ubuntu)
Status: Fix Released = Confirmed
--
Unmount in volume right-click menu, is tech-speak and undiscoverable
Thanks for the reply. I'm not able to reproduce the problem on my
computer. Could you check that the command sudo usermod -d [PATH TO
HOMEDIR] [USER LOGIN] works? If it does please follow the instructions
for the too users-admin at
https://wiki.ubuntu.com/DebuggingGnomeSystemTools.
** This bug is
This is not trivial because nobody has found out where's the real
problem. A paper cut must have a clear and simple solution.
AFAIK, our /etc/pam.d/passwd file is right as it includes the line
passwordoptionalpam_gnome_keyring.so
So the problem is elsewhere. Please note that you
Err, correction: the command passwd will update your keyring. sudo
passwd can't do this because it does not ask for the old password.
That's a known issue, but this behavior is required for admins to change
user passwords by themselves.
--
Cannot access wireless networks keys when user change
If you can't change your password using gnome-about-me, then that's a
bug in that program. On my box, this is working fine. No need to comment
on other more or less related reports. Please report a new bug against
the package gnome-control-center for that.
The default keyring will never have it's
Agreed.
** Changed in: nautilus (Ubuntu)
Status: Triaged = Fix Released
** Changed in: hundredpapercuts
Status: Confirmed = Invalid
--
Unmount in volume right-click menu, is tech-speak and undiscoverable
https://bugs.launchpad.net/bugs/28835
You received this bug notification
Thanks for your report. We need more information to debug your problem. Could
you explain precisely what steps you followed to get to that point? What
settings have you entered? Did your modem give any signal of life? What's the
model/make of your modem? Have you tried other methods from
Ouch! Indeed, that was a side-effect of our recent patch that was not
expected. The rationale for running gnome-about-me was that its way of
changing your password allowed eCryptfs Private directory to be mounted
with the new password: see bug 307019. Maybe the best solution for now
would be to
Thanks for the report. Are you able to modify any settings at all? Is
your system up-to-date? I reckon this is a duplicate of bug 463353,
which has been fixed recently.
About reusing an already existing home directory: you know what you're
doing, but the program has to make sure 1) the directory
OK, thanks for your tolerance. ;-) Indeed, things must have changed so
much since Hoary that the debugging should be started from scratch, or
given up. Closing, anyway nobody will work on it as-is. But feel free to
open new reports about problems in the gnome-system-tools or network-
manager
Contemporaneo: This is not related at all wirh the present report. When
CSS support is installed, Totem works just fine with DVDs, and recent
versions have become quite good. Please report precise and documented
bugs, rather than random rants.
--
Totem should notify users about installing
Any idea about the status of this in shadow and pam? Is this fixed
because GDM is now considered as a secured tty, as it should?
--
users with no password can't log in with gdm
https://bugs.launchpad.net/bugs/104957
You received this bug notification because you are a member of Ubuntu
Desktop
Sorry, but I don't think the report was filed against the right package.
Sadly, you chose the gnome-system-tools, which were not maintained since
then. We should find the real culprit of the bug.
If I understand correctly the description, every reboot breaks
/etc/resolv.conf? So actually
*** This bug is a duplicate of bug 458883 ***
https://bugs.launchpad.net/bugs/458883
Thanks for your report. We believe this particular bug has already been
reported, and has a fix available that you can test by following the
instructions at bug 458883.
** This bug has been marked a
Thanks for your report. Could you explicit a bit more what's the problem
you're describing? Do you mean that your computer was shut down while
carrying out an upgrade because of an external cause (e.g. battery
shortage...)? Or do you think Ubuntu has a bug that made it shut down by
itself? And
That's nothing to do with the gnome-system-tools. umask is set by some
other part of the system, have a look at /etc/profile and
/etc/skel/.profile.
** Package changed: gnome-system-tools (Ubuntu) = base-files (Ubuntu)
** Summary changed:
- Add User GUI assigns 777 to ALL users, even when not
hamacker: See bug 458883, which is now fixed in Karmic. But please don't
comment on bugs that are not directly related to your problem, this
generates unnecessary noise. Better is to make a research, and then to
file a new bug.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided =
AFAICS the the synchronize button is here in Karmic. Is your LiveCD one
of the final release? Other than that, are there problems left?
--
time-admin does not update time
https://bugs.launchpad.net/bugs/400130
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Thanks for your report. I think you were right, this is a problem in ntp
and not in the gnome-system-tools. But luckily, I believe I've already
seen this problem, which has its root cause in yet another package (gdm-
guest-session).
The interesting part of the log is:
Setting up ntp
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Low
--
time-admin does not update time
https://bugs.launchpad.net/bugs/400130
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
It's a little button with a refresh icon, at the end of the line where
you can set hours/minutes/seconds. But I guess you're missing the fact
that it's only shown when in manual time setting mode (since it won't be
of any use if ntpd is already synchronizing time on the background).
--
Thanks Chris! When you say there are 2 issues documented in that bug
report, do you mean that the other issue that still needs to be fixed
is the update delay problem in bug 475754? If so, don't worry, because
1) that's not really blocker, and I believe that's actually not a
regression, and 2)
After asking on the D-Bus list, Thiago Macieira told me that it was safe
to send the plain text password over the bus, as long as we're on the
same host (which is always the case AFAIK), and that we're using the
system bus. So I think I'll make that change in the next cycle, so that
we use PAM or
No news on that one?
--
Unable to add or modify users
https://bugs.launchpad.net/bugs/312067
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to liboobs in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Much thanks for this list and the rationale behind it. It's now fixed
upstream, removing all the servers you told, including ntp.shim.org. It
will be available in the next release. See http://git.gnome.org/cgit
/gnome-system-tools/commit/?id=c1a76a43eb30a7e230d1eff5b9a240efd250e47e
Though I'm not
So you've found the info better than I did! I reckon you did not issue
this command through VNC? In that case, that would make things trickier.
As I suspected, there's something wrong with ConsoleKit, which should at
least have considered you as local for my tricks to work. You may get
more
Public bug reported:
Binary package hint: gnome-system-tools
When one wants to manually set the time via time-admin, the newly
entered values are overridden every second or so, which makes it very
hard to actually change the hour. This delay should be increased to a
few seconds, so that one can
I've opened bug 479617 for the delay issue, as the present report will
be kept for the Stable Release Update that is going on.
--
[time-admin] Time cannot be set manually because it is reset
https://bugs.launchpad.net/bugs/475754
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 459376 ***
https://bugs.launchpad.net/bugs/459376
The point doesn't get across, that's the whole thing. Good luck...
--
User can't authenticate via PolicyKit after using 'resume normal boot'
friendly-recovery mode option
OK, so it seems there's something strange with PolicyKit. What does 'ps ax |
grep polkit' reports? Please also run
pkcheck --action-id org.freedesktop.systemtoolsbackends.set --process `pidof
users-admin` -u
just after having started users-amin.
What does this command reports:
pkaction
Thanks! Seems that PolicyKit is running correctly. Does
sudo killall polkitd; sudo /usr/lib/policykit-1/polkitd
report any error?
It may be that you're not detected as an active user, which could come from a
ConsoleKit problem. Then, connecting via VNC would actually matter, if there's
a bug in
OK, this is clearer now. So bug 459376 explains that GDM is not started
as it should, which forces you to run startx manually. But what do you
mean with : gnome user admin not working? Are you saying that the
users-admin program from System-Administration-Users and Groups does
not work? Or is your
greehunter: Please have a look at bug 458883.
--
[users-admin] Modifying user has no effect
https://bugs.launchpad.net/bugs/463353
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to system-tools-backends in ubuntu.
--
desktop-bugs mailing
I'm not acting unprofessional; how do you want us to work
professionally if you don't start doing so yourself?! A bug title is not
here to completely explain a bug, but to make it easy to find. Detailed
explanation, in correct English (at least to the extent your mastering
of English allows you to
Note that the current implementation uses the EMap widget from Evolution
- you may want to have a look at this app too. ;-)
--
Make the generic timezone map look like the 9.04 installer timezone map
https://bugs.launchpad.net/bugs/398056
You received this bug notification because you are a
*** This bug is a duplicate of bug 459376 ***
https://bugs.launchpad.net/bugs/459376
Think what you want about my lectures, but don't tell me my debugging
instructions are useless. If you know better than I what's the problem,
please tell me, that will be quicker. Bug 459376 does not seem to
Thanks for this detailed report. To make it completely clear, you
experienced these problems after upgrade and before running users-admin,
so that it cannot be the culprit? I'm asking that because it may also
have led to that situation, it's a problem we've already seen.
About the admin rights
Thanks for your report. The error comes from PolicyKit, whose daemon
can't be started for some reason. You may work around this problem by
running 'sudo /usr/lib/policykit-1/polkitd' before starting users-admin.
Could you confirm that this works? That information will help us to
determine the
Martin: right, while the bugs are different, applying both patches at
the same time makes sense.
--
[users-admin] Modifying user has no effect
https://bugs.launchpad.net/bugs/463353
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
So here we are. I've found the problem, which is a wrong command passed
to set the time. The delay before time is reset to its previous value is
quite short, and should be raised I guess. But at least with the patch
at [1], if you're relatively quick, the changes will be applied.
You can apply it
Chris: Please also include a third patch that you will find at [1]. It
will fix time/date setting, which was broken due to the same kind of
mistake (which is why I should never ever have done that kind of change
so late in the cycle!), a problem that was report as part of bug 475754.
With those,
The situation is actually more complex than that. If you're still using
Jaunty, this can be checked easily. But in Karmic, you should have
noticed, services-admin is not present. Further, cron is now handled via
an upstart job, which are not supported ATM by services-admin upstream.
So we can't
Good for a start. Could you manually set the time to something obviously
wrong, and then enable automatic NTP synchronization, so that you can
check if it works or not. If that's fixed too, we can close this report
and open another one about the synchronize button.
--
time-admin does not update
** Bug watch added: GNOME Bug Tracker #600602
https://bugzilla.gnome.org/show_bug.cgi?id=600602
** Changed in: system-tools-backends
Importance: Undecided = Unknown
** Changed in: system-tools-backends
Status: Fix Committed = Unknown
** Changed in: system-tools-backends
Remote
*** This bug is a duplicate of bug 458883 ***
https://bugs.launchpad.net/bugs/458883
Thanks for your report. This bug is already known as bug 458883. You can
read instructions there about working around this bug, and I may need
more informations from you at some point.
** This bug has been
Thanks for the feedback!
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Fix Released
--
gnome-network-admin crashes in Jaunty
https://bugs.launchpad.net/bugs/366897
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Yeah, very detailed, now I'm sure the path is '/' and not something
strange. dbus-monitor seems to indicate that this wrong message is
actually D-Bus introspection asking for an answer, so nothing very
problematic. I don't know why I don't see it here, maybe I've not
updated my system enough.
There's no regression potential here. This bug was about Ubuntu 7.10,
things can only improve in that regard. If you're thinking of the
Upstart support problem, the bugs are #433701 and #435935, but that's
another problem.
BTW, no need to report that upstream. I am actually most of the
developers
Jaya: Please check that you have the system-tools-backends 2.8.2
installed. You can use 'apt-cache policy system-tools-backends' to check
that. If that's the case, please open a new bug, since you may be
experiencing another problem. Thanks!
--
[time-admin] Time admin seems not to remember
I already had a quick look: WORKSFORME. It may well be solved for a
long time, I just hope the reporter is still using Jaunty - else we'll
have to wait for big changes to happen.
--
Cannot disable cron from the Services preference pane
https://bugs.launchpad.net/bugs/172841
You received this bug
Thanks for your report. Could you check that users-admin also fails to
change ANY user settings at all, and not only main group? If so, this
problem is known and hopefully has a fix available - see bug 468922.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Incomplete
--
Gosh, one mistake brings another... Here is the patch for the present
bug.
** Attachment added: 0001-Fix-user-password-modification.patch
http://launchpadlibrarian.net/35022067/0001-Fix-user-password-modification.patch
** Attachment removed: fix-modifying-users.patch
Rationale for SRU:
- changing settings of an existing user always fails, so this leaves Karmic
without GUI to do that
- this fix merely fixes a typo where a non-existent variable was used
- already applied upstream in the same form, should be available in 2.8.3
--
[users-admin] Modifying user
Rationale for SRU:
- changing a user password fails with any user other than self, so this leaves
Karmic without GUI to do that
- this fix merely brings back a line that should never have been removed since
Jaunty, so there's basically no risk
- already applied upstream in the same form, should
Wow, not very verbose, but at least now we know that there was not
error, and that message destination was set (because it took you 7
'next' to get out of the function). So it seems that the problem is only
that the destination was different from
org/freedesktop/SystemToolsBackends/*.
Could you
*** This bug is a duplicate of bug 463353 ***
https://bugs.launchpad.net/bugs/463353
Thanks for the report. This particular bug is already known, and
hopefully has a fix that could be uploaded soon. See duplicate bug
463353 for more informations.
** This bug has been marked a duplicate of
Philippe: could you open a new report and copy/paste your description
above into it? This bug is already complex to handle because of the many
problems it raises, and your problem deserves a special treatment ASAP.
About the original report, I should add:
- does not update time, even if Keep
Thanks for the feedback. So if that doesn't work, could you follow the
procedure I described in my first comment?
** Summary changed:
- [users-admin] Modifying settings of an existing user has no effect
+ [users-admin] Modifying user password has no effect
** Changed in: system-tools-backends
It seems that bug 463353 is more complex than that, so I'm going to make
it separate.
Please apply the attached patch using
sudo patch /usr/share/system-tools-backends-2.0/scripts/Users/Users.pm [PATH
TO FILE]
and report if that fixes the issue for you. Thanks!
** This bug is no longer a
Sebastien: any link to the duplicate? We can't close a bug that way...
--
Show users with UID 1000 according to /etc/login.defs definition of minimum
UID
https://bugs.launchpad.net/bugs/247910
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
OK, this sound more logical.
Any chance you could run the system-tools-backends in gdb to identify the
precise source of the error? You should install the debug packages for your
version (2.8.2-1) and architecture from
http://ddebs.ubuntu.com/pool/main/s/system-tools-backends/
Then you should
Good. Yet another step and we should know where the problem really comes
from - it seems to be a D-Bus problem.
Could you try 'sudo G_DEBUG=fatal_criticals gdb system-tools-backends' again,
but then do:
break get_destination
run
and when the breakpoint is reached
print dbus_message_get_path
OK, renaming the bug then. Could you open a new report about the shells
list problem? I'd like to track it separately before I forget about it.
** Summary changed:
- users-admin does not change shell
+ [users-admin] Modifying user has no effect
** Package changed: gnome-system-tools (Ubuntu) =
Yeah, you're right, that's what I eventually found out too. I've removed
that line when fixing something else in the latest release. I know it
was risky to commit such changes in a stable release, but I'd have
thought we'd have discovered it before. Next cycle we'll make
development releases to
So we should put the icon and text together in a button, and let GTK+
choose to display the icon or not, just like it's done since Karmic for
all (standard) buttons. This is much like the old Unlock button, after
all.
We'd need a comment from an usability engineer here, because it's not
really
Yeah, I was aware the patch was not about the very same problem, but I
preferred testing that one too, since the problem here is very strange -
some cleaning is always helpful.
So you say using userdel solves the issue. Are you completely sure of
that? I.e., does that work even when rebooting
So does that fix your problem?
To packagers: I think this applies for a quick SRU - except if we wait for
other fixes to publish at the same time, which can happen.
Ugly is mostly a matter of taste... ;-) perl in itself is not the
cause of this bug. I think I'll make it more strict about
*** This bug is a duplicate of bug 279308 ***
https://bugs.launchpad.net/bugs/279308
Oh, sorry, I've just found out that this bug is already fixed in Karmic.
I should have made the link without asking you for a trace, even if
that's always hard to do with relatively old fixes. I don't really
*** This bug is a duplicate of bug 279308 ***
https://bugs.launchpad.net/bugs/279308
Very same crash as bug 279308, even if it does not happen in the same
function (g_utf8_validate instead of strstr) - seems to be kind of
random.
--
network-admin crashed with SIGSEGV in strstr() when
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Incomplete
--
gnome-network-admin crashes in Jaunty
https://bugs.launchpad.net/bugs/366897
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
Actually I have committed a fix in August that allows you to choose a UID/GID
up to MAX_UINT32, because we use this type in the D-BUS spec of the backends.
So that should be good for what you asked. See
Note that the problem you describe is more a GDM bug. The gnome-system-
tools don't handle the Login Screen at all. You should report a new bug
about that.
Other than that, see bug 247910 about showing users with UIDs 1000 in
users-admin.
--
[users-admin] show all users checkbox is gone and
I've investigated a little more how we are getting the minimum UID for
normal users, and it seems that /etc/login.defs settings are used if
present, rather than those from /etc/adduser.conf. Could you try editing
that file too? Though, I don't know why those two files are present,
since some of
*** This bug is a duplicate of bug 463353 ***
https://bugs.launchpad.net/bugs/463353
Thanks for your report. I think your problem is the same as bug 463353,
but applied to another operation. You can try the patch there to fix it.
** This bug has been marked a duplicate of bug 463353
** Summary changed:
- change of password with users-admin has no effect
+ [users-admin] Modifying settings of an existing user has no effect
--
[users-admin] Modifying settings of an existing user has no effect
https://bugs.launchpad.net/bugs/463353
You received this bug notification because
Thanks Jaime! I've been a little stupid asking for 'ps ax | grep .p'
because it prints much noise too, but the information is interesting. If
others want to try, you can concentrate on the simple step 'sudo system-
tools-backends -v', since everything else seems to be fine.
The message
CRITICAL
OK, so moving the task to GDM, where the only problem left is. Updating
description accordingly.
** Package changed: gnome-system-tools (Ubuntu) = gdm (Ubuntu)
** Summary changed:
- [users-admin] show UID below 1000
+ Show users with UID 1000 according to /etc/login.defs definition of minimum
Thanks for the report. I guess the password is actually not changed at
all when using users-admin. Are you able to change your username or any
other setting? To create/delete users? If yes, please read the
instructions at https://wiki.ubuntu.com/DebuggingGnomeSystemTools, and
follow the procedure
Darren: Then please report this separately, that's likely to be another
problem.
--
[users-admin] deleting a user doesn't work
https://bugs.launchpad.net/bugs/458883
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in
*** This bug is a duplicate of bug 463353 ***
https://bugs.launchpad.net/bugs/463353
Could you follow the instructions at
https://bugs.launchpad.net/ubuntu/+source/gnome-system-
tools/+bug/458883/comments/24 and confirm that it fixes your problem?
I'm almost sure it does.
--
Can't enable
OK I guess I've found the culprit, which is a stupid-but-major typo. Please
apply the attached patch using
sudo patch /usr/share/system-tools-backends-2.0/scripts/Users/Users.pm [PATH
TO FILE]
and report if that fixes the issue for you. Thanks!
Darren: This dialog is itself a major difference
*** This bug is a duplicate of bug 463353 ***
https://bugs.launchpad.net/bugs/463353
Oh, and BTW this is a duplicate of bug 463353. You can change your own
password without trouble because it does not use the same system to do
it.
** This bug has been marked a duplicate of bug 463353
Well, forget about my previous comment. Instructions and patch at
https://bugs.launchpad.net/ubuntu/+source/gnome-system-
tools/+bug/458883/comments/24 should fix the problem.
--
change of password with users-admin has no effect
https://bugs.launchpad.net/bugs/463353
You received this bug
** Also affects: gst via
https://bugzilla.gnome.org/show_bug.cgi?id=600056
Importance: Unknown
Status: Unknown
--
[users-admin] deleting a user doesn't work
https://bugs.launchpad.net/bugs/458883
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Thanks for the details. Does that happen even if you create the user,
restart the computer, and then try to delete it? The only bug I can
think of is that we would not be removing users that were just created
during the current session.
--
[users-admin] deleting a user doesn't work
Thanks for the report and the upstreaming. Could you see if your problem
is identical to that reported as bug 103960? Especially, see the
workaround given in one the the latest comments.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Incomplete
--
User not removed from
Sorry, please have a look at bug 458883, not the number I gave in the
previous comment...
--
User not removed from users-admin interface
https://bugs.launchpad.net/bugs/463582
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thanks for your report. Do you get the same problem if you run
sudo killall /usr/bin/perl; sudo
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m
UsersConfig
from console, and reproduce the procedure in users-admin without stopping the
above command? Do you get the same
901 - 1000 of 1345 matches
Mail list logo
