[SOLVED] can't add users after fresh install

[boulderite]

I just did a fresh install of PCLOS 2011.09 (KDE version).  During the install, I added one normal user with no problem.

But now, when I use the 'Configure Your Computer' menu (as root), if I go to System -> Manage users on system, I immediately get a pop-up window with the Warning message 'This program has exited abnormally' and I never get the user management window.  I've tried logging in initially both as myself and as root, but I get the same problem each time.  As far as I can tell, all of the other configuration options in the Control Center work fine.

I can probably figure out how to add users from the command line, but that would really be a pain.

Help please!

boulderite

[Old-Polack]

I just did a fresh install of PCLOS 2011.09 (KDE version).  During the install, I added one normal user with no problem.

But now, when I use the 'Configure Your Computer' menu (as root), if I go to System -> Manage users on system, I immediately get a pop-up window with the Warning message 'This program has exited abnormally' and I never get the user management window.  I've tried logging in initially both as myself and as root, but I get the same problem each time.  As far as I can tell, all of the other configuration options in the Control Center work fine.

I can probably figure out how to add users from the command line, but that would really be a pain.

Help please!

boulderite

Have you fully upgraded your installation?

[Texstar]

You should be able to add users through the PCLiunuxOS Control Center on a fresh installation. You may have a bad installation, bad burn or bad media. Also check to make sure you don't have any usb keydisks plugged in when booting to see if that helps. You can also try updating your system to get current to see if that will fix anything for you. This is not a normal occurrence.

[boulderite]

I updated all of the packages with Synaptic, rebooted, and I still have the same problem.

I checked the checksum value on the ISO I downloaded, no problem there.

Also, the install process was normal as far as I can tell, so I'm not sure what a 'bad install' looks like.

Any other suggestions?

This problem certainly isn't a deal-breaker for me, I like PCLOS very much!  Just a bit annoying.


boulderite

[Old-Polack]

I updated all of the packages with Synaptic, rebooted, and I still have the same problem.

I checked the checksum value on the ISO I downloaded, no problem there.

Also, the install process was normal as far as I can tell, so I'm not sure what a 'bad install' looks like.

Any other suggestions?

This problem certainly isn't a deal-breaker for me, I like PCLOS very much!  Just a bit annoying.


boulderite

At what speed did you burn the CD, and did you check the md5sum of the burned CD to see that it matches the .iso image?

Because of the high compression of the .iso image, one needs to burn the CD at the slowest possible speed, for the greatest accuracy.

[Texstar]

run userdrake in the konsole as su root user and see if it throws out a perl error.

[boulderite]

I used k3b to burn the installation cd, and did not change the default write speed.  I checked the checksum value of the iso I downloaded, but I did not look at the md5sum value of the burned cd.  Is there a way to do that 'after the fact' or only right after you burn the cd?  This is a new experience for me.  Any advice you have is greatly appreciated.

boulderite

[boulderite]

run userdrake in the konsole as su root user and see if it throws out a perl error.

Does this help at all?

[mnd@localhost ~]$ su
Password:
[root@localhost ~]# userdrake
Failed to load image '/usr/share/userdrake/pixmaps//userdrake.png': Fatal error in PNG image file: Not a PNG file at /usr/lib/libDrakX/mygtk2.pm line 316.
standalone::bug_handler() called from /usr/lib/libDrakX/mygtk2.pm:316
mygtk2::_gtk__Pixbuf() called from /usr/lib/libDrakX/mygtk2.pm:105
mygtk2::_gtk() called from /usr/lib/libDrakX/mygtk2.pm:41
mygtk2::gtknew() called from /usr/lib/libDrakX/mygtk2.pm:370
mygtk2::__ANON__() called from /usr/lib/libDrakX/mygtk2.pm:377
mygtk2::_gtk__Image() called from /usr/lib/libDrakX/mygtk2.pm:105
mygtk2::_gtk() called from /usr/lib/libDrakX/mygtk2.pm:41
mygtk2::gtknew() called from /usr/lib/libDrakX/ugtk2.pm:620
ugtk2::gtkcreate_img() called from /usr/sbin/userdrake:61
[root@localhost ~]#


boulderite

[Old-Polack]

I used k3b to burn the installation cd, and did not change the default write speed.  I checked the checksum value of the iso I downloaded, but I did not look at the md5sum value of the burned cd.  Is there a way to do that 'after the fact' or only right after you burn the cd?  This is a new experience for me.  Any advice you have is greatly appreciated.

boulderite

Place the CD in the tray and from a terminal;

[polack@fatman ~]$ md5sum /dev/cdrom        <Enter>

Wait for the results. Compare with the .iso image md5sum. They should be identical.

Example:

[polack@fatman ~]$ md5sum /dev/cdrom
59e1ba0b355b60c755f034433fc43f73  /dev/cdrom

This is with a burned CD from the pclinuxos-kde-2011.6.iso image and it checks out.

59e1ba0b355b60c755f034433fc43f73  pclinuxos-kde-2011.6.iso

[boulderite]

I used k3b to burn the installation cd, and did not change the default write speed.  I checked the checksum value of the iso I downloaded, but I did not look at the md5sum value of the burned cd.  Is there a way to do that 'after the fact' or only right after you burn the cd?  This is a new experience for me.  Any advice you have is greatly appreciated.

boulderite

Place the CD in the tray and from a terminal;

[polack@fatman ~]$ md5sum /dev/cdrom        <Enter>

Wait for the results. Compare with the .iso image md5sum. They should be identical.

Example:

[polack@fatman ~]$ md5sum /dev/cdrom
59e1ba0b355b60c755f034433fc43f73  /dev/cdrom

This is with a burned CD from the pclinuxos-kde-2011.6.iso image and it checks out.

59e1ba0b355b60c755f034433fc43f73  pclinuxos-kde-2011.6.iso

Ok, looks like you nailed it.  I ran md5sum twice, and both times it fails:

[root@localhost ~]# md5sum /dev/cdrom
md5sum: /dev/cdrom: Input/output error

I guess this means the CD is flaky.  I'll try reburning at the slowest speed and reinstalling tomorrow.

Thanks to you and TexStar.

boulderite

[boulderite]

Mark this issue SOLVED.

I reburned the CD at 4x write speed, with 'verify written data' turned on, and verified the burned cd with md5sum.

Then I reinstalled, and the problem disappeared.

Thanks for the help.

boulderite