Chauncellor: at least, if you were able to play with permissions, you
should be able to find this bug report. With the new users-admin, it's
harder to tweak fine-grained permissions, so hopefully nobody will do
this anymore.
--
[Karmic][Lucid] Only one user has sound; no hw shows in Sound
no!chance: See bug 160862 rather. This is a know problem that is fixed
in Lucid and should be fixed at some point in Hardy too. Though the
original issue is that you had weird characters in your /etc/group file,
nowadays users-admin shouldn't get crazy when it encounters this kind of
thing.
I'm
*** This bug is a duplicate of bug 433654 ***
https://bugs.launchpad.net/bugs/433654
** This bug has been marked a duplicate of bug 433654
[Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences
--
[Users and Groups] Advanced Settings: User Privileges on using
No, that's really the same bug. users-admin shouldn't show that group at
all since it's plainly broken. This behavior doesn't make sense. That's
why I said we should remove the audio group, which would fix the bug for
all people that were added to it without noticing.
If that doesn't seem right,
'sudo update-rc.d cups defaults'
And for the tool, a new one is being developed ATM. See
http://jacob.peddicord.net/blog.html
--
System Administration Services (services-admin) missing
https://bugs.launchpad.net/bugs/437905
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 570828 ***
https://bugs.launchpad.net/bugs/570828
If you're not using Ubuntu Studio, you have NetworkManager, else you can
install it, or wait for the tab to come back (hopefully). The decision
was made by developers that didn't know Studio wasn't installing
Thanks for your report. Could you run the command:
'sudo apt-get install --reinstall gnome-system-tools'
and see if that fixes your problem?
The file triggerring the error is a file present in 2.28 but not in
2.30. But I don't know why it makes the upgrade fail. Nobody has
reported this problem
** Bug watch added: GNOME Bug Tracker #619588
https://bugzilla.gnome.org/show_bug.cgi?id=619588
** Also affects: gdm via
https://bugzilla.gnome.org/show_bug.cgi?id=619588
Importance: Unknown
Status: Unknown
--
ampersand in user real name freezes login screen
What problem still exists? ;-) There were three of them, and I got no
answer to confirm. So I'm closing it, please open a new report with
detailed explanations.
David: feel free to reopen when you can answer my question.
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete =
Please don't reopen a fixed bug at random. Why on earth do you believe
this is the same problem?! None of the symtoms you describe is similar.
It's not because it has high priority that people will fix your bug more
quickly. As you said yourself, I checked and /etc/groups did not appear
to be
As I suggested on the other report (bug 295405), could you try setting
UID for user messagebus to 102 (if that's not used by another one)? More
generally, please follow the procedures I described there to check that
it's not the same problem (very likely).
(BTW, when I said liboobs, I thought
True, but you have to find a better place for it! ;-) The only other
area I could think of was behind the users list, but that wasn't really
nice either.
Anyway, users-admin is going to be replaced by accounts-dialog, so this
will probably never be fixed. Thanks for reporting, though.
** Changed
I meant 108 of course.
When I referred to the other report, I thought about things like:
ls -l /lib/dbus-1.0/dbus-daemon-launch-helper
Or the one explained at:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/295405/comments/10
The idea is that I'm going to have to reproduce the same steps
*** This bug is a duplicate of bug 599050 ***
https://bugs.launchpad.net/bugs/599050
** This bug has been marked a duplicate of bug 599050
Cant change username
--
Cant make auto login to Lubuntu
https://bugs.launchpad.net/bugs/599044
You received this bug notification because you are a
*** This bug is a duplicate of bug 599050 ***
https://bugs.launchpad.net/bugs/599050
** This bug has been marked a duplicate of bug 599050
Polkit authentication fails in Lubuntu
--
Cant open advanced settings
https://bugs.launchpad.net/bugs/599052
You received this bug notification
*** This bug is a duplicate of bug 599050 ***
https://bugs.launchpad.net/bugs/599050
** This bug has been marked a duplicate of bug 599050
Polkit authentication fails in Lubuntu
--
Cant change account type
https://bugs.launchpad.net/bugs/599051
You received this bug notification because
Thanks for your report. Usually, reporting two very close issues is not
a good idea because they are likely to be related. In your case,
authentication failure is probably the cause of both.
Please run 'users-admin' from a console and post the output here.
Also, please run
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
OK, the problem is obvious and exactly the same as for the other report.
/lib/dbus-1.0/dbus-daemon-launch-helper shouldn't be owned by the
'avahi' group, but by 'messagebus'.
See my comment at
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
Ah, I hadn't noticed this comment before posting on the other bug, where
you didn't mention the fix didn't work.
Could you try the solution described at:
Could you run
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
and retry?
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided = Medium
** Changed in: system-tools-backends (Ubuntu)
Status: New = Incomplete
--
users-admin Click to make changes button
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
If the solutions of the duplicate didn't work, it may be something
different in the end. Have you tried the suggestion above too?
Do you get the same problem when try to run other programs, e.g. jockey-
gtk
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
OK, so that's not a bug specific to users-admin. Didn't reinstalling the
package solve the problem?
As I said above, /even if it's not the same issue/, please follow the
instructions given by Martin Pitt
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
Ah, sorry for missing the strace! I've looked at it, and comparing with other
bug, the same permission issues appear. So, please continue the steps described
by Martin from comment #12, and go on while
Looks like a gnome-panel bug, since it's the program using CPU. But if
you're not able to reproduce it, we cannot do anything but close the
bug! What happens if you retry the same operation, e.g. from a separate
user accout?
For the record, when trying to debug, you should move configuration
So could you post the output of 'ps x | grep polkit' here? Also, please
run 'users-admin' from a terminal, and paste the messages here too.
--
users-admin Click to make changes button does nothing
https://bugs.launchpad.net/bugs/599441
You received this bug notification because you are a member
Weird. polkit-gnome-authentication-agent-1 should definitely be running,
and though starting it doesn't solve your problem.
What does users-admin and /usr/lib/policykit-1-gnome/polkit-gnome-
authentication-agent-1 output if you start them in a terminal (the
second first), and reproduce the bug?
** Changed in: gnome-panel (Ubuntu)
Importance: Undecided = High
** Changed in: gnome-panel (Ubuntu)
Status: New = Incomplete
--
gnome-panel did not start properly after I moved it
https://bugs.launchpad.net/bugs/599462
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
So we're on a completely different bug now. The dbus issue was likely
related to permissions on a file included in the package. It would be
interesting to reproduce in a virtual machine a fresh install of
Could be interesting then! ;-)
The problem is, you're using GNOME 2.28 and it's not impossible that the
bug is already fixed in 2.30. So debugging could be a waste of time.
Since Lucid is a LTS release, do you plan to upgrade to it at some
point? It would be much better to check that 2.30 has the
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
And what about the other questions? The error message you see can be
related to several know bugs and may not be related. The output of
polkitd might be much more interesting.
--
Failed to execute program
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
users-admin worked but it didn't provide interesting information. The
polkitd output would still be required to understand why PolicyKit
thinks you cannot authenticate. See the end of my comment #17, after
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
** (process:32132): DEBUG: not authorized
So that's polkitd that thinks you don't have the required privileges.
Does that user have a password? I not, please try with a user with a
password.
What does
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
Maybe PolicyKit is unable to authenticate a user with its key. Could you
try with a test account that has a password?
ConsoleKit seems to work fine, so it's very likely that password is the
problem.
--
Thanks for the infos. So that's really a problem with PolicyKit or it's
configuration files. Pretty hard to guess where the problem may come
from.
Please check that your /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
file contains,
[Configuration]
AdminIdentities=unix-group:admin
and
What does these commands say?
pkcheck --action-id org.freedesktop.systemtoolsbackends.set --process $PID -u
pkcheck --action-id org.freedesktop.systemtoolsbackends.self.set --process $PID
-u
(replacing $PID with the output of the command 'pidof gnome-settings-daemon'
for example).
--
Polkit
Hm, that didn't work , probably because you didn't provide a PID. I was
silly, since you're on Lubuntu, gnome-settings-daemon isn't running. So
start users-admin, get its PID using 'pidof users-admin', and replce
$PID with this value in the command.
BTW, you can paste command outputs directly
Is the user member of the 'admin' group? Are you logged in remotely
(VNC...)? What's the output of 'ck-list-sessions'?
--
Polkit authentication fails in Lubuntu
https://bugs.launchpad.net/bugs/599050
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
OK, I see the problem. Actually, it's completely the contrary of what
you said. ;-)
The button doesn't seem to check for PolicyKit authorizations when
activated by keyboard, while it does when clicked using the mouse. So in
your case this *appears* to work when you press Space, but it actually
You can check easily what groups you are in by running the 'groups'
command.
Could you run the two pkcheck commands again, but after having run
sudo killall polkitd
sudo /usr/lib/policykit-1/polkitd
and post the three outputs here? (Don't stop the last command while
running the two pkcheck
Please don't mix bugs. You refused to mark this one as a duplicate, and
know you act as if it was!
So in the other report, we should find what's the exact lxde package
that should disable gdm when installed, or at least find a solution. I
don't know lxde at all, so you'll need to find it yourself
Thanks for the debugging and for the patch, but I don't think it fixes
the root cause. tzmap-point_hover should already contain the point that
was retrieved using e_map_get_closest_point() when the pointer moved. So
if tzmap-point_hover isn't valid, we have to find out why. The
questions I asked
The problem isn't that I fear people won't do the work, as I know
packaging will happen anyway. It's just that the way Ubuntu devs
consider patching is plain wrong: there's generally no hurry pushing a
fix to the development release, so downstream patching only generates
useless work. I wish
Thanks! The interesting part is:
file_run_full_failed::Command [/usr/sbin/adduser --gecos --disabled-password
bugta] failed.
Since the user wasn't created, everything else fails.
What do you get when you run:
sudo /usr/sbin/adduser --gecos --disabled-password bugta
in a terminal? You'll get
So your system isn't broken, it's just that adduser doesn't interact
well with automount. I'm not sure why this doesn't work (i.e. why /home
isn't mounted when adduser tries to access it), nor if it should work.
But that's not a bug in users-admin. You could report a bug against
adduser in Debian
OK, thanks! Could you get more debugging information by following instructions
for users-admin at:
https://wiki.ubuntu.com/DebuggingGnomeSystemTools
No issue with the delays, I'm not in a hurry... ;-)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
That's not a regression. In the worst case, nothing changes. But I
suspect for some reason Charlie isn't using the version with the fix,
since he also said bug 533870 wasn't fixed. What's your version number
of system-tools-backends?
--
You received this bug notification because you are a member
** Package changed: gnome-panel (Ubuntu) = gnome-settings-daemon
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
https://bugs.launchpad.net/bugs/708143
Title:
wnck-applet shows rotated
According to people having the same bug in Gentoo, running
sudo chmod o+x /usr/libexec/dbus-daemon-launch-helper
solves this bug. Could you report if it's also a solution for you? Thanks!
** Changed in: system-tools-backends (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug
OK, I'm closing because there's not much we can do without somebody
experiencing the bug. The Gentoo fix doesn't sound very logical to me,
but...
** Changed in: system-tools-backends (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of
Thanks for your report. Could you post the errors you get when logging
in?
Please also follow instructions from
https://wiki.ubuntu.com/DebuggingGnomeSystemTools
and attach information here.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Incomplete
--
You received this bug
Let's deal with the gnome-screensaver task on the other bug, then, and
close this one.
The gdm/gnome-system-tools part is fixed with the g-s-t 2.32 in
Maverick.
** Changed in: gnome-screensaver (Ubuntu)
Status: Triaged = Invalid
** Changed in: gnome-system-tools (Ubuntu)
Status:
Confirming the suggested solution. As I said on bug 630430, this will simply
require adding a:
auth sufficient pam_succeed_if.so user ingroup nopasswdlogin
line in /etc/pam.d/gnome-screensaver, right before:
@include common-auth
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided
To be fair, only one address is outdated. The project homepage, mailing
list, FTP server, GNOME module name and IRC channel are all valid. And
it's not like GNOME is a completely unknown project! I'll remove the
whitepaper address, and maybe I'll fix the website to stop telling about
CVS/SVN since
You shouldn't be running shares-admin as root, this creates many issues.
Just run 'shares-admin', and authenticate via PolicyKit. (And anyway
your version is really too old, sorry.)
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Won't Fix
--
You received this bug
Upstream said it is the intended behavior: users for which password has
expired shouldn't be allowed to authenticate until they have logged out
and in back, so that they change their password.
** Changed in: policykit (Ubuntu)
Status: Triaged = Invalid
--
You received this bug
Fixed upstream with 2.91.90.
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
Upstream pushed a fix in 2.91.4.
** Bug watch added: GNOME Bug Tracker #573125
https://bugzilla.gnome.org/show_bug.cgi?id=573125
** Changed in: evolution
Importance: Critical = Unknown
** Changed in: evolution
Status: Invalid = Unknown
** Changed in: evolution
Remote watch: GNOME
Please open a new report, as this bug is fixed. And please attach the output of
rgrep default-applications /usr/share/glib-2.0/schemas/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in ubuntu.
Yeah, the latter result is more what I expected. There's a bug and a fix
for that, but nobody committed it for such a long time... Basically, you
can't use shares-admin since 10.04...
Be sure to remove /etc/init/nfs*, /etc/init.d/nfs*, /etc/init/samba and
/etc/init.d/samba if these files exist.
I can hardly imagine how the fact that you're running in VMWare should
change anything WRT authentication. More likely a config file was
edited... Or you weren't asked for authentication because you had just
provided your password for the same action a few seconds before.
Anyway, let's close this
Thanks for the report. This is indeed a synchronisation issue between
users-admin and adduser, the tool which is responsible for actually
creating users. I've filed a bug in Debian so they make adduser allow
dots in usernames.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided =
I've committed both changes (stratum 1 and unreachable servers)
upstream. Thanks for the help! Of course, the proper fix would be
creating a pool, but better fix this in the short term.
Commits are 0fef206 and 8e01e05.
** Also affects: gst
Importance: Undecided
Status: New
** Changed
What's the exact behavior of the installer? It doesn't use the same code
at all, so that's purely a coincidence it it suffers from the same
problem.
Don't worry about the importance, though: I'm currently discussing with
an adduser developer, and the fact that I set it to Low doesn't mean it
*** This bug is a duplicate of bug 677929 ***
https://bugs.launchpad.net/bugs/677929
** This bug has been marked a duplicate of bug 677929
users-admin: create new user with dot/period fails
* You can subscribe to bug 677929 by following this link:
Of course, we can pass --force-badname, but if we consider dots as
acceptable, adduser should accept them by default.
About chown, there's absolutely no need to change the tool, as long as
people that add dots to their usernames and use chown from the
commandline know what they are doing. Anyway,
*** This bug is a duplicate of bug 533870 ***
https://bugs.launchpad.net/bugs/533870
Yeah, that's known but we need to backport fixes to Lucid.
** This bug has been marked a duplicate of bug 533870
Crash in SelfConfig on amd64
* You can subscribe to bug 533870 by following this link:
Richard: It's fixed in Maverick, but still present in Lucid. See
https://wiki.ubuntu.com/Bugs, and especially
https://wiki.ubuntu.com/Bugs/Status.
--
[users-admin] Changing UID doesn't work
https://bugs.launchpad.net/bugs/542183
You received this bug notification because you are a member of
Seriously, I've moved on to other things since Lucid has been released -
glad to know SRUs are considered even when they are that old, though!
;-)
The only translation change between Lucid and Maverick package is in one
file and for two strings, so definitely not something to care about. If
Thanks Chris! But we really don't need to backport 2.10.1, 2.10.0 will
be enough. 2.10.1 only brings in a few improvements that are used by the
gnome-system-tools 2.32, which are not in Lucid. This removes most of
the changes (in terms of lines of code), which makes the SRU even safer.
--
OK, let's say bug 683972 is the place where we track the crash that
still occurs with nautilus 1:2.32.0-0ubuntu1.1. What feels weird is that
the trace is very very similar, but let's see...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
What you should have said in the description is that this crash is very
close to bug 630884, which is reported to be fixed with nautilus
1:2.32.0-0ubuntu1.1.
** This bug has been marked a duplicate of bug 630884
nautilus crashed with SIGSEGV in g_closure_invoke()
* You can subscribe to bug
Thanks for the report. Could you follow the procedure For users [users-
admin] at https://wiki.ubuntu.com/DebuggingGnomeSystemTools and attach
the resulting files here? Also, I'd need you to run 'sudo killall
polkitd; sudo /usr/lib/policykit-1/polkitd' before you carry out the
other actions, and
There's an error in the log file you provided, though. Could you check
when it exactly happens (e.g. when pressing OK for the password
dialog...)?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
But this is not a bug. You shouldn't run users-admin as root, as you
don't need to, and it potentially creates security issues.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
You could, but I can sear you nobody will ever work on this because 1)
nobody usually works on users-admin except myself, and 2) users-admin is
going to be replaced, so we're not really fixing this kind of detail.
Feel free to provide a patch though, but filing a bug would really waste
your
You can just open the file after each time you validate a dialog by
clicking a button, and for example note somewhere what line was the last
at that point, and then mark this in the file by introducing comments.
You may also run the commands in a terminal without the stb-
users.log part, so that
The gksu issue is not related at all, since users-admin doesn't use it
(else, that would mean it's running as root).
I suspect no user is shown in the list, or the current user isn't. Is it
the case? Can you test that by creating a test user using 'adduser' in a
console and check if it's enough?
Of course, it would be slightly better to fix users-admin not working as
root, rather than showing an error message, just in case some very
special distributions or users need this. But I'd accept a patch showing
a dialog too if it's well written... I don't think translators will mind
- if you
So it sounds like a PolicyKit issue. Please run
sudo killall polkitd; sudo /usr/lib/policykit-1/polkitd
start users-admin, and click on a button that doesn't work. Then please attach
the output here.
What happens if you run
export PID=`pidof gnome-settings-daemon`
pkcheck --action-id
Ah, sorry, I didn't know you weren't using GNOME. The gnome-settings-
daemon part is not essential at all: the idea was only to use the PID of
a process that is known to be running - you can use any program name
here.
The polkitd log contains the explanation to your problem:
** (polkitd:1592):
Thanks for the diff!
Looks good to me, except that the change log line:
- Identify users and groups by login instead of UID (LP: #533870, LP: #542183)
is wrong: Bug 533870 is a crash on amd64 too, not a login vs. UID issue.
--
You received this bug notification because you are a member of
No, I don't think it is. ;-) As long as the right number is listed...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to system-tools-backends in ubuntu.
https://bugs.launchpad.net/bugs/616682
Title:
Backport system-tools-backends
Thanks for the report. Please run
sudo killall polkitd; sudo /usr/lib/policykit-1/polkitd
And reproduce the problem. Then, copy/paste the output of the above command
here.
Also, what's the output of
apt-cache policy libpolkit-gobject-1-0 libpolkit-gtk-1-0
** Changed in: gnome-system-tools
Oh, and are you able for example to install software upgrades using
updates-manager? Are you able to authenticate from from
System-Administration-Network connections?
** Summary changed:
- Polickit authentication error: Only trusted callers (e.g. uid 0) can use
CheckAuthorization() and pass
You mean there's nothing else printed than:
** (polkitd:1752): DEBUG: system-bus-name::1.56 is inquiring whether
unix-process:2283:1752924 is authorized for
org.freedesktop.systemtoolsbackends.set
** (polkitd:1752): DEBUG: user of caller is unix-user:connor
** (polkitd:1752): DEBUG: user of
Thanks. So everything works but the lock buttton, which means it's a bug
in polkit-gnome. The good news is, I'm going to stop using it in the
gnome-system-tools before the next release since it's not compatible
with GTK+ 3. We still need to find out what's going wrong, though - I'll
try to get
The button was moved in 2.32, which is present in Maverick.
** Changed in: gnome-system-tools (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
This is a mix of bug 685596, which is that users-admin doesn't report
authentication errors, and bug 187585, which is about
PolicyKit/ConsoleKit not detecting that remove sessions are active
users.
To
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
Ah, and what I said is actually exactly bug 221363, which I'm going to
fix now, so marking as duplicate.
** This bug has been marked a duplicate of bug 221363
Policy Kit Unlock Buttons Greyed Out when
** Also affects: system-tools-backends
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to system-tools-backends in ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy Kit Unlock
I've eventually pushed the allow_any fix to the system-tools-backends
upstream, it should be available in 2.10.2 for Natty.
Somebody should really go over all actions from
/usr/share/polkit-1/actions/ and file a new bug task for all actions
that don't consider allow_any as a valid case without a
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
If the patch doesn't apply, that just means it's not meant for Maverick, it
can't be linked with the kind of bug you have. Trust me, it's the right fix. If
you want to try it by yourself, you can edit
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
Hm, I hadn't read your two latter replies... Yes, the real question (see
duplicate report) is why remote sessions are considered as inactive. I
don't really understand whether they should be reported as
Don't worry for the delays... some bugs are opened for years, often with
a higher priority! As regards the active/inactive issue, that would
likely be a bug in ConsoleKit.
users-admin is not going away today nor in the next year, else I
wouldn't even reply to bug reports. It's just that I don't
*** This bug is a duplicate of bug 542183 ***
https://bugs.launchpad.net/bugs/542183
Yeah, that's a known bug that's going to be fixed soon in Lucid.
** This bug has been marked a duplicate of bug 542183
[users-admin] Changing UID doesn't work
* You can subscribe to bug 542183 by
xlash911: are you seeing the same messages as the ones from the
description of this bug in /var/log/auth.log?
Andreas: does your problem still happen in 10.10?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
*** This bug is a duplicate of bug 685655 ***
https://bugs.launchpad.net/bugs/685655
Thanks for the report. Why do you see in the title it occurs in Natty if
distro information says you're using Maverick (10.10)? This is important
to debug the problem.
Anyway, that's a duplicate of bug
usermod always fails when trying to change the home for an active user.
This is very reasonable since many files are likely to be open, so
moving/removing them will fail.
I've changed users-admin upstream to disable the home dir field and show
and explanation notice in that case. This will be
KeithG: What version exactly? Both are 2.32.0, what we need is the
-ubuntu part. It works here on Maverick. (Note you need to click the
unlock button after installing packages, which can be confusing - even
for me...)
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 685655 ***
https://bugs.launchpad.net/bugs/685655
** This bug has been marked a duplicate of bug 685655
PolicyKit authentication error: Only trusted callers (e.g. uid 0) can use
CheckAuthorization() and pass details
* You can subscribe to bug 685655 by
401 - 500 of 1655 matches
Mail list logo
