** Changed in: system-tools-backends (Ubuntu Jaunty)
Status: Triaged = Won't Fix
** Changed in: system-tools-backends (Ubuntu Hardy)
Status: Triaged = Won't Fix
** Changed in: system-tools-backends (Ubuntu Hardy)
Assignee: Chris Coulson (chrisccoulson) = (unassigned)
**
I am running lucid with system-tools-backends at 2.9.4 and am seeing errors
trying to run any of:
Time and Date
Users and Groups
example:
$ users-admin
(users-admin:12353): Liboobs-WARNING **: There was an unknown error
communicating with the backends: Failed to execute program
More info:
# cat /etc/issue
Ubuntu 10.04 LTS \n \l
# uname -m
x86_64
# apt-show-versions gnome-system-tools system-tools-backends
gnome-system-tools/lucid uptodate 2.30.0-0ubuntu2
system-tools-backends/lucid uptodate 2.9.4-0ubuntu1
--
users-admin (System-Administration-Users and Groups)
Again more info.
Don't know if any of this is related but here is messagebus group
related info from /etc/group and /etc/passwd:
# grep messagebus /etc/group
messagebus:x:108:
# grep 108 /etc/group
messagebus:x:108:
# grep 108 /etc/passwd
messagebus:x:102:108::/var/run/dbus:/bin/false
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
Ok, if you think this is not related I'll be glad to open a new bug. I
do think this is the same underlying problem though.
Also:
# apt-show-versions liboobs
liboobs not installed (even not available)
There is no such package.
--
users-admin (System-Administration-Users and Groups) overwrites
Lucid has s-t-b 2.9.4 now, closing lucid task.
** Changed in: system-tools-backends (Ubuntu)
Status: Fix Committed = Fix Released
--
users-admin (System-Administration-Users and Groups) overwrites group file
https://bugs.launchpad.net/bugs/160862
You received this bug notification
Chris, can you please upload the patch to hardy/jaunty/karmic and check
whether it is in lucid? Thanks!
** Changed in: system-tools-backends (Ubuntu)
Assignee: (unassigned) = Chris Coulson (chrisccoulson)
--
users-admin (System-Administration-Users and Groups) overwrites group file
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
John: That's why in Lucid the protocol has been completely redesigned to
accept changes to individual groups/users.
** This bug has been marked a duplicate of bug 522612
users-admin crashed with SIGSEGV in oobs_users_config_add_user()
** This bug is no longer a duplicate of bug 522612
Thanks for clarifying. That makes me sleep a little bit better at night
:)
--
users-admin (System-Administration-Users and Groups) overwrites group file
https://bugs.launchpad.net/bugs/160862
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
*cringe* ACK from ubuntu-sru for the 5bad3f... upstream git patch.
Personal commentary, though, is IMO there's something fundamentally
broken about zapping all the groups if the dbus backend dies. This seems
to be a defective/fragile design to me.
--
users-admin (System-Administration-Users and
This happened to me today, and although I was able to restore /etc/group
and /etc/gshadow, more things remain broken in my system, for example
pulseaudio, networkmanager, bluetooth, policykit, consolekit and (maybe
the root cause) dbus... My syslog is being spammed by pulseaudio failing
and many
** Attachment added: users admin destroying groups and users
http://launchpadlibrarian.net/39363327/users-admin-authlog
--
users-admin (System-Administration-Users and Groups) overwrites group file
https://bugs.launchpad.net/bugs/160862
You received this bug notification because you are a
** Also affects: gnome-system-tools (Ubuntu Hardy)
Importance: Undecided
Status: New
** Also affects: gnome-system-tools (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Also affects: gnome-system-tools (Ubuntu Karmic)
Importance: Undecided
Status: New
--
** Changed in: gnome-system-tools (Ubuntu Hardy)
Importance: Undecided = High
** Changed in: gnome-system-tools (Ubuntu Hardy)
Status: New = Triaged
** Changed in: gnome-system-tools (Ubuntu Jaunty)
Importance: Undecided = High
** Changed in: gnome-system-tools (Ubuntu Jaunty)
** Changed in: gnome-system-tools (Ubuntu Hardy)
Assignee: (unassigned) = Chris Coulson (chrisccoulson)
** Changed in: gnome-system-tools (Ubuntu Karmic)
Assignee: (unassigned) = Chris Coulson (chrisccoulson)
** Changed in: gnome-system-tools (Ubuntu Jaunty)
Assignee: (unassigned)
** Package changed: gnome-system-tools (Ubuntu) = system-tools-backends
(Ubuntu)
** Changed in: system-tools-backends (Ubuntu)
Status: Fix Released = Fix Committed
** Project changed: gst = system-tools-backends
--
users-admin (System-Administration-Users and Groups) overwrites group
Master5597: If you want to help, you can just confirm that the fix I
suggested actually fixes the bug in your box too, since I haven't
checked Jaunty. You can simply make the change by hand from the link I
posted above. Thanks!
--
users-admin (System-Administration-Users and Groups) overwrites
The fix (as linked aboved) is simply to ensure split() stops when it has
4 items. That way, we ensure we won't pass more arguments than the D-Bus
binding expects, which prevents the script from dying. So the garbage
gets packed in the last field, i.e. users that are members of the group.
This is
even though my perl is a little dusty (haven't used it since college) this is
my get in the GroupsConfig.pm.
sub get
{
my ($self) = @_;
my $groups, $logindefs;
$self-SUPER::reset_counter ();
$groups = Users::Groups::get ();
$logindefs = Users::Users::get_logindefs ();
return
Yes, I meant Users/Groups.pm. The syntax error is actually not a perl
message: it comes from the shell because of the parentheses in
ARRAY(). But that's not an issue since we only want to get the message
printed.
Everything seems to be fine - at least groups are found and filled
correctly. So I
update: it's fixed, read more to find out how.
ok i added those lines right before the return in get() in the
/usr/share/system-tools-backends-2.0/scripts/GroupsConfig.pm file.
although i had to change them to:
Utils::File::run (echo Min: . $$logindefs{gmin});
Utils::File::run (echo Max: .
You rock! Indeed, I had missed that tiny detail too... I must have been
introduced by some buggy script, but this must have been fixed a long
time ago without anybody noticing this had raised dramatic problems.
So the main culprit here is our very vulnerable code, which did not even
bother to
Rationale for SRU: discussed with Chris Coulson on IRC, since the patch
is only one line, it's worth backporting to Hardy, Jaunty and Karmic.
Intrepid is too close to end of life. This bug destroys the system from
the point of view of most users, since it completely prevents from
logging in. The
no Problem, glad i could help. i was also looking at the bug to see how
to fix it, but since you've got it, i won't worry about it.
btw, just for curiosity, what is the fix?
--
users-admin (System-Administration-Users and Groups) overwrites group file
https://bugs.launchpad.net/bugs/160862
You
Ok i tested this with my 64 bit vm, coped over all my files from
/etc/apt/sources.list.d/ then ran the script below. after all the
updates and installs the add user works as expected on that system. so
i really don't know what's messed up with my (and other few other random
people on the net's)
Thanks for that very valuable information. It may still worth give a
deeper look at this, since it seems to hurt people at random, and can
still raise issues in Lucid (even if that doesn't destroy your system as
now).
So what happens is that the backends have a problem creating group
structures
Actually it happens so far with any user name or password. it also
happens with a Desktop user and a different user and password. So far
it does it every time. So i don't think the 48 char password is the
case. I'm setting up a VM at the moment to test it on a clean system.
I'll report back when
** Attachment added: cleaned group file
http://launchpadlibrarian.net/38897666/group
--
users-admin (System-Administration-Users and Groups) overwrites group file
https://bugs.launchpad.net/bugs/160862
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Thanks for the files. They seem correct to me. I don't think there's any
special problem with your versions of gnome-system-tools and system-
tools-backends either.
An interesting hint is that you're using a 64 bits system. It may well
be that the GID we send to the backends triggers an int
ok I am still working on the vm, but the logs you had me run were interesting.
the users-admin.log just had 40 copies of the line below (each one followed by
a blank line):
(users-admin:14023): Liboobs-CRITICAL **: oobs_group_get_gid: assertion `group
!= NULL' failed
while the critical error
This bug was fixed in the package gnome-system-tools - 2.29.3-0ubuntu1
---
gnome-system-tools (2.29.3-0ubuntu1) lucid; urgency=low
* New upstream release (LP: #506365)
- Move to new System Tools Backends protocol (new liboobs API).
We now only commit changes to one user
Master5597: do you mean you're able to reproduce this bug consistently
when creating an user with a password longer than 48 chars? I've tried
to get the same result with a Live CD of 9.04, and I don't get any
problem. Could you attach your /etc/passwd and /etc/group files,
possibly replacing
** Changed in: gnome-system-tools (Ubuntu)
Status: Triaged = Fix Committed
--
users-admin (System-Administration-Users and Groups) overwrites group file
https://bugs.launchpad.net/bugs/160862
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Branch linked: lp:~ubuntu-desktop/gnome-system-tools/ubuntu
--
users-admin (System-Administration-Users and Groups) overwrites group file
https://bugs.launchpad.net/bugs/160862
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
so what are the plans to fix this error for the 9.04 LTS version? or is
it not reproducible for anyone else?
i also found out that my other odd errors are from my mangled
/etc/passwd file. what happened is that the System - Users and Groups
basically made my groups file the same as the one
i don't know if this will help but i just added a new user (already had
root and my current user) via users-admin and it basically wiped my
/etc/group file. it had 2 lines left in it. luckily i was able to boot
in recovery mode and copy the backup at /var/backup/group.bak so that i
could boot
Thanks for your proposal, but as I said I think the changes in Lucid
should have fixed that already, but they are too complex to be
backported. So I can't help except advising people to switch to Lucid
when it's released. If somebody ever reproduces the bug in Lucid I'll
have to consider it, but I
Telling us what version you're using would obviously have helped
debugging.
Anyway, this kind of behavior is not possible not in Lucid, the new
version only changes groups, and will never remove them when
creating/modifying an user. It would have been interesting to find out
what's going on, but
I can confirm this bug is happening. I just spent a couple of hours
diagnosing and helping a friend get this fixed. After it was all
resolved we were talking and he mentioned he had accessed user and
groups the night before. This resulted in his group file being reduced
to 3 entries and prevented
Well, just create a new user named 'admin'. That's how you reproduce the bug.
Be sure to have some sort of a rescue CD nerarby, though.
This should be it, am I missing something?
--
users-admin (System-Administration-Users and Groups) overwrites group file
https://bugs.launchpad.net/bugs/160862
Bubla: the procedure you describe does not completely destroy
/etc/group. It removes all users from the admin group, making it
impossible to fix the problem afterwards. But this bug has been fixed in
the development version, and users-admin will now refuse to overwrite
the existing group (just
Bubla (and others): the problem with this kind of serious bugs is that
we don't know how to reproduce them, and so cannot fix them. If you find
it so easy to reproduce it, please tell us how. Else we'll have to close
the report, knowing that the bug will bite somebody one day.
** Changed in:
44 matches
Mail list logo
