Yes, I'll have to fix that string, but that will be for Lucid+1.
We can't really remove these checks because when changing password for a
user different than the current one, PAM doesn't check the password,
which is set using 'chpasswd'. The current situation is pretty lame, but
we'd have to
** Changed in: gst
Status: In Progress = Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Status: Triaged = Fix Released
--
binary users-admin hints using if not installed ecryptfs-utils
https://bugs.launchpad.net/bugs/544867
You received this bug notification because you
Works for us, please reopen if it still doesn't on your system.
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Fix Released
--
users-admin Help button doesn't do anything in Lucid
https://bugs.launchpad.net/bugs/529790
You received this bug notification because you are a
Fixed with 2.30.
** Changed in: ubuntu-translations
Status: Fix Committed = Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Status: Fix Committed = Fix Released
--
Information message from users-admin shows untranslated, albeit it's translated
Fixed with 2.30.
** Changed in: gst
Status: Fix Committed = Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Status: Triaged = Fix Released
--
Change... buttons on users-admin dialog untranslated and untranslatable
https://bugs.launchpad.net/bugs/543664
You received this
Closing, I think it's been fixed since then.
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Fix Released
--
time-admin crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/513233
You received this bug notification because you are a member of Ubuntu
Desktop
Fixed with 2.30.
** Changed in: gnome-system-tools (Ubuntu)
Status: Triaged = Fix Released
** Changed in: gst
Status: Fix Committed = Fix Released
--
users-admin and about-me hang when new password value only differs in case
https://bugs.launchpad.net/bugs/512315
You received
I've been able to reproduce the same crash after/while upgrading. So I
confirm my own bug (bad, bad!).
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Medium = High
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Triaged
--
gnome-settings-daemon crashed with
** Bug watch added: GNOME Bug Tracker #614800
https://bugzilla.gnome.org/show_bug.cgi?id=614800
** Also affects: gnome-settings-daemon via
https://bugzilla.gnome.org/show_bug.cgi?id=614800
Importance: Unknown
Status: Unknown
--
gnome-settings-daemon crashed with SIGSEGV
http://www.google.com/search?q=Matthias+Clasen%27s+accounts-dialog
--
[enhancement] Password strength meter in user creation
https://bugs.launchpad.net/bugs/155308
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in
Thanks for investigating the code, but I don't think the line you cite
is the source of the bug. This line is only run when changing your own
password, which is a completely different case. Furthermore, enabling an
account works for me following the same procedure as you.
So I rather suspect that
And in a more recent version like 9.10 or 10.04? Sorry, but many
warnings like that have been fixed since 9.04, and you really can't
expect a fix being backported there.
--
[network-admin] Gtk-WARNING **: Unknown property: GtkComboBox.items
https://bugs.launchpad.net/bugs/206291
You received
*Please* you two stop discussing your private issues here. This is a bug
report, if you want to talk about you like and existential questions,
use your mail or find a place to meet. You're really not furthering the
case of buttons on the right side with all this noise.
--
[Master] Window Control
Sure, if you want to implement it. But I'm not sure I'll work on that,
given Matthias Clasen's accounts-dialog already has this feature, we may
as well switch to it.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: gnome-system-tools (Ubuntu)
Yeah, you were also able to set the phone number, and tweak membership
to every kind of obscure privilege, plus changing home directory. But
how many people need that? If you really need a specific UID, just
create the user and change UID after, that doesn't hurt, and makes most
people not scared
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42967540/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42967541/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/42967542/Disassembly.txt
** Attachment
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42988297/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42988298/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/42988299/Disassembly.txt
** Attachment
Glad to know some people are actually using that feature! ;-)
I think that's fixed in the system-tools-backends 2.10.0, which I hope
will be uploaded soon to Lucid.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Triaged
** Changed in: gnome-system-tools (Ubuntu)
Importance:
*** This bug is a duplicate of bug 546874 ***
https://bugs.launchpad.net/bugs/546874
That's simply a bug that should be fixed before the release. See
informations on the other report.
** This bug has been marked a duplicate of bug 546874
passwd - can't login, change password (pam_winbind
OK, thanks for the reply. So you suffer from this bug because you were
an early tester. You can either continue using gnome-volume-control-
applet, or add the indicator applet to your panel.
** Changed in: gnome-media (Ubuntu)
Status: Incomplete = Invalid
--
volume icon is missing
*** This bug is a duplicate of bug 546874 ***
https://bugs.launchpad.net/bugs/546874
benohb: Are you joking? You already reported the same bug with the very
same description as #552026, and I said you that was a duplicate of bug
546874. You're generating extra work for triagers and developers
nhasian: you need to add the notification applet, which is different
from the notification area.
--
volume icon is missing
https://bugs.launchpad.net/bugs/552221
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-media in ubuntu.
--
Yeah, I noticed that yesterday too. Shouldn't be too hard to fix.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Triaged
** Summary changed:
- value of Configuration doesn't change on initial switch to Keep
synchronized with Internet servers
+ [time-admin] Value of
Thanks for the report. Have you checked that you're actually able to
change user passwords? Just create a test user, then run 'sudo passwd
$USER_LOGIN'. If you get a System Error message even when passwords
are long enough, then you're experiencing bug 546874 (which as a
workaround).
** Changed
Well, pasting a link, expecting triagers will go through the whole
thread to understand your problem is hardly a nice practice. I see there
that your problem is solved, and you don't provide any detail about the
problem. Did you upgrade from Karmic? Was the applet present in the
list, only
Actually, in Ubuntu, you need to add the notification applet to the
panel (not the notification area). It provides the messaging and the
volume icon, that's why gnome-volume-control-applet is disabled (not
sure how, though). The bug is in the fact that upgraders are not
suggested to add it, but
When exactly did you upgrade from Karmic? Normally, since beta1, the
indicator-applet is added to the panel automatically. If you upgraded
before that, then you may have missed that feature.
--
volume icon is missing
https://bugs.launchpad.net/bugs/552221
You received this bug notification
Looks like the icon name is not filled correctly:
theme_dir_get_icon_suffix (dir=value optimized out, icon_name=0x1 Address
0x1 out of bounds, has_icon_file=0x0)
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/551809
You received this bug notification because you
*** This bug is a duplicate of bug 513233 ***
https://bugs.launchpad.net/bugs/513233
** This bug has been marked a duplicate of bug 513233
time-admin crashed with SIGSEGV in strchr()
--
time-admin crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/515803
You received this
*** This bug is a duplicate of bug 513233 ***
https://bugs.launchpad.net/bugs/513233
** This bug has been marked a duplicate of bug 513233
time-admin crashed with SIGSEGV in strchr()
--
time-admin crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/514816
You received this
*** This bug is a duplicate of bug 513233 ***
https://bugs.launchpad.net/bugs/513233
** This bug has been marked a duplicate of bug 513233
time-admin crashed with SIGSEGV in strchr()
--
time-admin crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/516601
You received this
Thanks for your report and sorry for waiting so long before responding.
Could any of the reporters confirm the crash is still present in up-to-
date Lucid? I'm not able to reproduce it here. Thanks!
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Incomplete
--
time-admin crashed
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42508621/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42508622/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/42508623/Disassembly.txt
** Attachment
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42509350/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42509351/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/42509352/Disassembly.txt
** Attachment
That's fixed in Lucid. Since 2.29.92 we automatically add the user to
the group named after its login if it already exists. That's not really
optimal since it may not be what you want, though - that will be
improved in the next cycle.
** Changed in: gnome-system-tools (Ubuntu)
Status:
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed = Triaged
--
Alt+C access key does not work in time-admin
https://bugs.launchpad.net/bugs/287262
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in
Martin: I guess you can simply run 'sudo killall polkitd', and it will
forget your authentication.
One would have to check whether gvfs actually redirects
POLKIT_ERROR_CANCELLED to G_IO_ERROR_CANCELLED, and if so, then add it
to the ignore case in Nautilus. Or simply add that condition in
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/i686/cmov/libc.so.6
abort () from /lib/tls/i686/cmov/libc.so.6
?? () from /lib/tls/i686/cmov/libc.so.6
?? () from /lib/tls/i686/cmov/libc.so.6
--
system-tools-backends assert failure: *** glibc detected ***
** Attachment added: Stacktrace.txt
http://launchpadlibrarian.net/42383966/Stacktrace.txt
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
https://bugs.launchpad.net/bugs/550533
You received this
** Attachment added: ThreadStacktrace.txt
http://launchpadlibrarian.net/42383968/ThreadStacktrace.txt
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/42318890/CoreDump.gz
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided = Medium
--
** Attachment added: StacktraceSource.txt
http://launchpadlibrarian.net/42383967/StacktraceSource.txt
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
https://bugs.launchpad.net/bugs/550533
You
Woops! For some reason, apport-retrace removed the core dump even if it
failed to retrace...
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42384531/CoreDump.gz
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk():
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/i686/cmov/libc.so.6
abort () from /lib/tls/i686/cmov/libc.so.6
?? () from /lib/tls/i686/cmov/libc.so.6
?? () from /lib/tls/i686/cmov/libc.so.6
--
system-tools-backends assert failure: *** glibc detected ***
** Attachment added: Stacktrace.txt
http://launchpadlibrarian.net/42384662/Stacktrace.txt
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
https://bugs.launchpad.net/bugs/550533
You received this
** Attachment added: StacktraceSource.txt
http://launchpadlibrarian.net/42384665/StacktraceSource.txt
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
https://bugs.launchpad.net/bugs/550533
You
** Attachment added: ThreadStacktrace.txt
http://launchpadlibrarian.net/42384669/ThreadStacktrace.txt
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/42384531/CoreDump.gz
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends:
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42385283/CoreDump.gz
--
system-tools-backends assert failure: *** glibc detected ***
/usr/sbin/system-tools-backends: munmap_chunk(): invalid pointer: 0x0804bffd ***
https://bugs.launchpad.net/bugs/550533
You received this bug
*** This bug is a duplicate of bug 534154 ***
https://bugs.launchpad.net/bugs/534154
Ah, I've finally managed to retrace the core dump on my box - I wanted
to be sure I could check that crash before releasing 2.10.0 tonight.
Hopefully, it seems to be a duplicate of bug 534154, which has a fix
Are you in a hurry? I said in about 10 days, and I'm going to release
it tonight, so that will make 15 days, which is the same from the POV of
Lucid inclusion. The only requirement is to be here for GNOME 2.30,
which is released this week, and it's better to wait for testers to
report bugs instead
*** This bug is a duplicate of bug 475974 ***
https://bugs.launchpad.net/bugs/475974
Actually, I think that's a duplicate of bug 475974. What happens is that
the first time you open the group settings dialog, the GID is set to 0,
and group creation fails. Just close and launch the dialog
Thanks for you report. I think you should read more about how to write a
useful report before we go on trying to fix your problems. First, you
should never report several unrelated bugs at the same time. For each
bug, we need a precise procedure about how to reproduce it, and many
details, which
** Package changed: gnome-system-tools (Ubuntu) = gnome-panel (Ubuntu)
--
date and time applet mix up and turns unreadable
https://bugs.launchpad.net/bugs/544084
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in ubuntu.
--
*** This bug is a duplicate of bug 470743 ***
https://bugs.launchpad.net/bugs/470743
Thanks for your report. This bug has already been reported as bug #
470743. You may want to go and comment there to propose your solution.
Please continue testing Lucid and reporting bugs!
** This bug has
Moving to nautilus, as PolicyKit itself provides a way to know whether
authentication was canceled or whether it failed. See POLKIT_ERROR_CANCELLED,
which is the GError returned by polkit_authority_check_authorization_finish(),
at
Let's close the Intrepid task, nobody is going to backport the fix
there...
** Changed in: system-tools-backends (Ubuntu Intrepid)
Status: Triaged = Won't Fix
--
package system-tools-backends 2.6.0-1ubuntu1.1 failed to install/upgrade:
subprocess post-installation script returned error
Hmm. You reported the bug against the gnome-system-tools, so I thought
that was a bug in users-admin - actually, you first experienced it with
gnome-about-me, which is in gnome-control-center. But I can confirm it
happens with users-admin, which partly uses the same code.
OTOH you say you've been
I don't think we can close the bug because it was confirmed on the
upstream report to be still present in 2.28.0. No code changes have been
made since then, so the bug is still here. Sure, network-admin is no
longer shipped by default, so that's less of a problem, but from the POV
of this tool,
Ah, thanks for the clarification!
So:
- have you ever experienced this bug with users-admin?
- have you ever been able to change your password successfully using
gnome-about-me?
- have you installed special password or PAM packages such as pam-cracklib?
- is the fact that you change the password
What version are you using? Since 2.29, users-admin simply runs 'adduser
$LOGIN --disabled-password', so everything that happens after that is a
problem with adduser and adduser.conf. Profiles are a different matter,
and by default only add membership to special groups like video, admin,
etc.
**
*** This bug is a duplicate of bug 533870 ***
https://bugs.launchpad.net/bugs/533870
Thanks for your report. I strongly suspect your problem is the same as
bug 533870. Are you using a 64 bits version of Ubuntu? If so, then
please try the package from comment #30 on that report, and tell me
** Summary changed:
- Changing the long name in users-admin to the same name results in an error
+ Crash in SelfConfig on amd64
--
Crash in SelfConfig on amd64
https://bugs.launchpad.net/bugs/533870
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Sure, but you don't need feedback when the operation takes one second
instead of 20.
--
users-admin has significantly delayed response after clicking OK
https://bugs.launchpad.net/bugs/546873
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Confirmed. This doesn't occur everytime, but for some weird reason the dialog
hangs, and the password is set to something such as:
$6$X/OldoQr$HxKsor.mQesg6EXrtIZqEHK4wKm718YVDowpV97Gm60L8rwfz07moFvNneQzmFqDGB5kv9yR6cWlEbdAc619y.
which seems to be invalid because running 'passwd' doesn't ask for
Additional note: before debugging users-admin further, we should
determine whether we can reproduce the bug by running 'passwd' from
commandline. If the real bug is in 'passwd', that would explain why the
password got corrupt, which is hard to understand if only users-admin
hung.
** Summary
Yes, I see what you're talking about. And no, that's not a duplicate of
bug 542744 (there, committing leads to an error message).
What happens is that we don't check for actual changes when you click
OK, we always commit changes. Everytime groups are involved, we commit
changes to all groups,
Thierry: do you really believe this will happen for Lucid? We need
somebody to write the doc, then apply an Ubuntu-specific patch (upstream
is frozen), and get it translated...
Bryce: I know this is lousy, we also have problems with the Synchronize
Now button not always working. Feel free to
Fix pushed upstream, will be released with 2.30 next week.
** Changed in: gst
Assignee: Milan Bouchet-Valat (nalimilan) = (unassigned)
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Medium
--
binary users-admin hints using if not installed ecryptfs-utils
https
Fix pushed upstream, will be released with 2.30 next week.
** Changed in: gst
Status: In Progress = Fix Committed
** Changed in: gst
Assignee: Milan Bouchet-Valat (nalimilan) = (unassigned)
--
users-admin and about-me hang when new password value only differs in case
https
OK, that's the more likely scenario - sometimes knowing more leads to
more problems... ;-)
Could you open a new report about the main group problem? I'll see if I
can put together a not-so-ugly patch before 2.30 is released. But I
consider this bug as fixed for the first error.
** Changed in:
21h: I can't tell without more information (as always). If you're in
Karmic, then the only way to fix that is to upgrade to Lucid. ;-) If
you're on Lucid, then it's definitely not the same bug.
BTW I'm closing it due to lack of feedback, please reopen if it turns
out to be still present *in
= Invalid
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Triaged
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Assignee: (unassigned) = Milan Bouchet-Valat (nalimilan)
** Changed in: gst
Status: New = In Progress
--
binary
Ah, OK, now I see what you mean. But this is much more specific than
what you reported originally. I know how to fix this easily, but gnoem-
about-me also needs to be patched. Triggering this bug is relatively
hard, so that's not as major as not being able to change its password at
all.
**
** Also affects: gnome-control-center
Importance: Undecided
Status: New
** Changed in: gnome-control-center
Status: New = In Progress
** Changed in: gnome-control-center
Assignee: (unassigned) = Milan Bouchet-Valat (nalimilan)
--
users-admin and about-me hang when new
: None = GNOME Bug Tracker #613739
** Changed in: gnome-control-center
Assignee: Milan Bouchet-Valat (nalimilan) = (unassigned)
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New = In Progress
** Changed in: gst
Assignee: (unassigned
*** This bug is a duplicate of bug 432964 ***
https://bugs.launchpad.net/bugs/432964
Well, just have a look at bug 432964, but in short: remove the file
/etc/passwd.lock, /etc/shadow.lock or /etc/gshadow.lock.
** This bug has been marked a duplicate of bug 432964
System crash in guest
Cool. For the main group problem: the group is automatically created,
it's just that it's not shown right after adding it. Do you have a
precise reason to immediately go to the groups dialog and try to edit
this group? Fixing that bug currently requires a few hacks that I'm not
sure I can commit
network-admin won't be back in Lucid since it conflicts with
NetworkManager in most of its features BUT hostname setting. That's why
it's been removed for a few releases now.
It's really sad there's no GUI to change hostname, but adding a whole
tool to do that would be silly. If you really need a
No, it's just that I should have told you to patch the file
/etc/dbus-1/system.d/org.freedesktop.SystemToolsBackends.conf. :D
--
user group administration tool freezes temporary and reports failed
authentication even for successfull actions
https://bugs.launchpad.net/bugs/542744
You received
Thanks for the report. This bug is already fixed upstream, and will be
released with 2.30. Translations from GNOME will be provided with the
tarball.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = High
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Triaged
** Also affects: gst via
https://bugzilla.gnome.org/show_bug.cgi?id=613115
Importance: Unknown
Status: Unknown
--
Information message from users-admin shows untranslated, albeit it's translated
https://bugs.launchpad.net/bugs/543670
You received this bug notification because you are
Thanks for your report. I don't believe this is an actual bug: you can
still install network-admin with the package 'gnome-network-admin', as
it has been possible for several releases. There's still a problem with
NetworkManager not providing this option, but that should be requested
upstream.
**
Much thanks for the report. This was indeed a mistake : we were
identifying users using their UID instead of their login. When changing
their UID, we weren't able to find the user to apply the new settings
to. It's now fixed upstream and will be available in the system-tools-
backends 2.10.0, for
Thanks for the report. I think there are several different issues at
stake here.
First, when creating an user, its main group is creating under the hood
by adduser, and we don't show it until the tool is restarted. This is a
known problem, but it's not easy to fix properly, at least in a stable
Oh, I think I understand where the second issue comes from. Could you apply the
attached patch and retry? Save the file, and then run:
sudo patch
/usr/share/dbus-1/system-services/org.freedesktop.SystemToolsBackends.service
PATH_TO_SAVED_FILE
(You'll need to restart your computer after that
The problem is, most of the privileges shown in users-admin are old-
school Unix groups that aren't used at all by PolicyKit. So we'd have to
support a completely knew privileges tab, based on PolicyKit. Not sure
that will happen in users-admin.
Note that an easier solution would be to add an
policykit package is for PolicyKit 1, and is obsolete. policykit-1 is
used by most programs in Lucid.
** Changed in: policykit (Ubuntu)
Status: New = Invalid
--
policykit introduction broke unix user groups
https://bugs.launchpad.net/bugs/326135
You received this bug notification
Yes, Mark: flamewars aside, please ensure buttons on the left are not
turning into a nightmare when GNOME Shell is used. I can confirm that
reaching e.g. the icon button in the left corner of a maximized window
is very likely to lead you to hit the hot corner, especially on
touchpads - and even
*** This bug is a duplicate of bug 490093 ***
https://bugs.launchpad.net/bugs/490093
Thanks for the report. That's really a major problem, but it's already
known for some time.
** This bug has been marked a duplicate of bug 490093
[users-admin] Password is reset to old value when it's
*** This bug is a duplicate of bug 229169 ***
https://bugs.launchpad.net/bugs/229169
Thanks for the report, but that one is already known and fixed since
Karmic.
** This bug has been marked a duplicate of bug 229169
ntp support appears not to be installed after installing through Time
Thanks for the report. The warning you see on start is likely to come
from a bug on 64 bit machines, but it shouldn't be related with your
problem.
Are you able to change a user account type, or its name? Please check
this for a user different than the current one, as it won't work because
of the
If you can't authenticate from time-admin either, there must be a problem with
PolicyKit. Please run
pkcheck --allow-user-interaction --process PID --action-id
org.freedesktop.systemtoolsbackends.self.set
and
pkcheck --allow-user-interaction --process PID --action-id
OK, you have a PolicyKit problem: you just need to have an
authentication agent running. That's why it works in KDE and not in
GNOME. Start /usr/lib/policykit-gnome/polkit-gnome-manager in the
background, and everything will be fine.
Now we need to find out why this daemon is not running
The fix has been released with the system-tools-backends 2.9.3, which
are not in Lucid yet (but as I said, that bug isn't really harmful there
since we won't remove all groups if the configuration is empty).
--
users-admin (System-Administration-Users and Groups) overwrites group file
This must be a problem with the install tool not adding the original
user to these groups. But they are kind of obsolete for most of them,
anyway.
** Package changed: gnome-system-tools (Ubuntu) = user-setup (Ubuntu)
** Changed in: gst
Status: Confirmed = Invalid
** Summary changed:
-
We need to find out how D-Bus checks for authorization in order to
understand why reboot is needed for it to consider an user as member of
the admin group.
** Also affects: dbus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-system-tools (Ubuntu)
Status:
*** This bug is a duplicate of bug 490093 ***
https://bugs.launchpad.net/bugs/490093
Thanks for the report. This is a very unfortunate bug that's fixed in
Lucid, but not in Karmic.
** This bug has been marked a duplicate of bug 490093
[users-admin] Password is reset to old value when it's
No news on that bug?
--
Cant Change Password of existing user
https://bugs.launchpad.net/bugs/512315
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
I think this should be fixed in Lucid. Could you check that's the case
and report? Thanks!
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed = Incomplete
--
users-admin won't let you change anything
** Summary changed:
- [users-admin] Password is reset to old value when it's been changed using
about-me
+ [users-admin] Password is reset to old value when it's been changed by
running about-me
** Bug watch added: GNOME Bug Tracker #612812
https://bugzilla.gnome.org/show_bug.cgi?id=612812
The fix was really trivial: when writing the code, I forgot to make a
variable used to return an error message as NULL before passing it to
the authentication function. Since this is required for the function to
fill in the error message, we were getting an invalid pointer: in case
of error, we
501 - 600 of 1345 matches
Mail list logo
