Unknown user and sound issues

SaintsOfTheDiamond · 01-31-2006, 10:30 PM

After I used swaret to update my computer and deleted all the .new files created I can't log into my user account anymore. When I try to change the password with passwd it says there is an error because that user doesn't exist.

Code:

passwd: Unknown user nate

Also, when I try to start KDE I get this error message:

Code:

Sound server informational message:

Error while initializing the sound driver device /dev/dsp can't be opened (No such device)

The sound server will continue, using the null output device

And when I try to run alsamixer I get this error:

Code:

alsamixer: function snd_ctl_open failed for default: No such device

I should probably just have a running thread dedicated to my

issues.

dive · 01-31-2006, 11:35 PM

For the alsa problem, have you installed or compiled a new kernel? Your may need to reinstall asla if so, and of course you will probably need to reboot.

As for the missing user, I can't think why upgrading anything should affect that. You could try backing up your home dir, adding a new user and copying all your settings over from the backup maybe.

SaintsOfTheDiamond · 02-01-2006, 06:52 AM

Quote:

Originally Posted by dive

For the alsa problem, have you installed or compiled a new kernel? Your may need to reinstall asla if so, and of course you will probably need to reboot.

I guess you've never seen my other posts.

I haven't done anything (knowingly anyway) to the kernel .. it quit working after I updated with swaret about a week ago. I tried to download and reinstall alsa but I get an error message on install as well.

Quote:

Originally Posted by dive

As for the missing user, I can't think why upgrading anything should affect that. You could try backing up your home dir, adding a new user and copying all your settings over from the backup maybe.

That's what I've done as a *hopefully* temporary measure.

dive · 02-01-2006, 07:10 AM

I know most of these auto update progs have a blacklist and its usual to put the kernel + headers in there to avoid problems

That would be a place to look. If you have accidently install new kernel and headers it may be fixable by reinstalling the originals off the slack cd