Hi @all,
I had the same problem today on Hardy with the latest updates. I did
boot with a live CD and restored my password, shadow and group file from
by backup. I found out, that there have been 5 lines of characters with
hex sequence 0a 41 in the group file. The line before this sequence is
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
Run script in terminal 1:
sudo killall perl /usr/bin/perl; sudo
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m
UsersConfig --platform ubuntu-8.04
Run script in terminal 2:
sudo killall system-tools-backends; sudo /usr/bin/system-tools-backends -nd
Run users-admin in
OK, so it seems there's a problem when the scripts are not running
(first and third times). Error messages from D-Bus are really not
expected, that would explain the bug.
Xande, could you reproduce that test too? I'd like to see what this
looks like in Karmic, I'm really more familiar with that
Milan - I have tried to run the two scripts as requested but there
appear to be problems already...
Terminal 1:
ubu...@ubuntu:~$ sudo killall perl /usr/bin/perl; sudo
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m U$
perl: no process killed
/usr/bin/perl: no process
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m U$
This is a bad copy/paste: U$ can't work, obviously, that should be UsersConfig.
/usr/sbin/system-tools-backends
Should be /usr/bin/system-tools-backends in 8.04.
Anyway, you don't need to run those to perform the test I
OK, sorry for the delay Roger. So if I understand correctly, the only
way to reproduce this problem is to create a new user when the users
list appears empty? That would be logical, since we commit the data we
have, which would be empty if it could not be loaded.
But do you mean that the second
This Debian bug is not related at all.
** Changed in: debian
Importance: Unknown = Undecided
** Changed in: debian
Status: Fix Released = New
** Changed in: debian
Remote watch: Debian Bug tracker #470123 = None
** Changed in: debian
Status: New = Invalid
** Also affects:
Thanks for the reply Milan. As I am getting a bit confused as to where
to go from here would you please advise exactly what tests I should now
run with the Xubuntu Live CD, specifying if I should first set a user
password for ubuntu.
--
Creating an user destroys most of users and groups
What I asked Xande to test should be interesting for you too:
One interesting test (for both of you) would be to start the scripts before
starting users-admin, and to compare the startup times: start users-admin once,
run it again and see the time it needs, then wait for 5 minutes so that the
I can confirm that this is still an issue in freshly (from scratch) installed
Karmic (9.10), updated to current as of 7 Jan 2010. This is on a fit-PC 1.0,
so the statement above in the thread about it being a slow PC applies. Since
the technical info has been handled above, I'll add some
Fresh boot from Live CD. Copy /var/log/auth.log to attached file
auth_no_passwd.
Use passwd command to change default ubuntu password from (null) to
123456789. Copy /var/log/auth.log to attached file auth_new_passwd.
Note the Error attempting to open/unwrap messages at the end!
Run the two
Just to clear up any confusion I will reiterate the comments in my
original post. I am using an old, slow, AMD-K6 PC. The problem I
raised is only apparent with this PC, although it works fine with other
applications (albeit s l o w l y ! ). When I have tried the same Live
CDs in more powerful
Thank you for the info Milan. Yes, I did click Ctrl+C before creating
the user as the output had apparently stopped. I have now re-run the
test with the following results:
After opening users-admin, the GLib-GIO-WARNING (x3) appears, together with a
GUI error
box The configuration could not
The logs show that all groups are removed when trying to create the
user, thus the subsequent failure since 'ubuntu' is not in the 'admin'
group. So the problem is, why no users/groups are detected on start. Do
the D-Bus errors in auth.log appear before or after you try to create
the user? This is
Background: I originally experienced this problem with an installed
version of Xubuntu Hardy (8.04). I established that the Live CD had the
same bug. As I do not wish to change my LTS installation at present, I
have since tried Live CDs for Jaunty (9.04) and Karmic (9.10) with
similar results.
Thanks for these new tests! Something seems weird to me: the commands I
asked you to run did not print the messages they should when creating an
user. Did you Ctrl+C before creating the user? Maybe I was not clear
enough: you should run these commands, and reproduce the procedure
without stopping
17 matches
Mail list logo
