This was bothering me enough on the drive home that I contemplated dropping down to Fedora 9 for now. Luckily I ran across Fedora’s Common F10 bugs and added nomodeset to my kernel parameters in /etc/grub.conf. I did not have high hopes for that to work, but it does….and then some. The boot process is not as pretty but I’m suspending and resuming, I could not care less about what the boot process looks like. So now I successfully suspend, but the fun comes with the resume. When I open the laptop the system just about resumes, then suddenly suspends again. This would continue the sad panda moment, but resuming again works. So I just have to resume twice, I can live with that.

*sad panda face*

I have no name!@urbs-19979

Now that’s weird, but I ignored it since the machine was working and I was in a series of meetings. However, when I started trying to ssh into other systems I was getting told

You don’t exist, go away!

At this point I verbally told my laptop “You don’t tell me no” which caused some weird looks but people moved on just fine. Since the problem was now getting in my way I had to look into it. After a while I had realized that by adding a username to my ssh commands (through -l user or user@host) I could use ssh again. This caused me to think something was wrong with /etc/passwd, and I was right. My user couldn’t read /etc/passwd, fixed the permissions and all was well. I forget what I did to muck up /etc/passwd, but I’m sure if I had been using vipw like you’re supposed to I wouldn’t have had this problem…..but then again I would have missed out on the great gems that programmers leave in their programs.