So I was doing some fiddling around, installing some stuff into my Slack64 that I hadn't yet installed, and doing some general cleaning & organizing, etc..

And, I decided to change my user/login name from 'sasha64' to 'sasha'. I had been using the 'sasha64' name in case I ever needed/wanted to use my previous /home partition with my new Slackware, which I am not going to do now. The old /home which is for my Slack-11 installation, and I didn't want to mix together configurations between the two systems.

Anyhow, not necessarily in the following order, here's what I did:

0-- Start: I'm logged in as sasha64
1-- used Kuser to delete the unused 'sasha' user
2-- Kuser again to delete the 'sasha64' user, but left the /home/sasha64 folder
3-- rename /home/sasha64 --> /home/sasha
4-- Kuser to make a new sasha user, with the new /home/sasha home folder. Added the requisite groups, and finished.

And that's about it. Everything seems fine, other than Firefox, which starts up with what appears to be a basic, default configuration.

I've logged out, rebooted, logged in again, and everything else I try seems to be OK, except Firefox. I tried re-installing Firefox, but still the same.

NOW: If I create a symlink from /home/sasha to /home/sasha64 then Firefox works with my profile and theme and everything like it should. But obviously I don't want this.

Anyone know what I'm missing?

EDIT - I just discovered that `su` isn't working either. When I try to use it, it just says "Sorry." and returns the bash prompt :|

Thanks,
Sasha

You renamed /home/sasha64 to /home/sasha. So /home/sasha is now the home directory for user sasha (who does not exist yet). Then you create user sasha. I believe this has overwritten directory /home/sasha (or just the config files)and created the default directory of a new user.

To clarify (sorry for the omission) -- when I created the new user 'sasha' I did NOT create a new /home folder; so it would use the one already there.

UPDATE: I have (after a lot of screwing around) managed to re-create the original sasha64 user and for the most part, things appear normal.

Firefox finds the correct profile now, and otherwise my settings seem to be OK.

One thing's a little weird, but I'm sure I just need to configure something: When I login, I get the XFCE settings manager and profile configurator on the screen, and can't seem to make them not appear when I log in. It's minor, and I'll probably get that figured out soon..

OK, all seems well -- except that I've gone back to using the 'sasha64' user name.

The only thing I can't figure out is why, every time I log in, the stupid XFCE settings manager and XFCE session configurator always pop open, despite my repeatedly disabling them.

I've tried setting the session manager to both of "Start Empty Session" and "Restore Previous Session" but it ignores both configurations. I've even deleted the startup items from the XFCE session application startup thing, yet they STILL start

But, I'm happy that everything else works as it should. Even `kdesu` works probably because earlier I reinstalled most of the KDE pieces.

So,besides these silly XFCE things starting when I tell them not to, the only issue remaining is: How can I (the correct way?) rename myself to 'sasha'?

Sasha

Firefox uses hard coded path names in its config files. If the profile was created under sasha64, then all of its configurations will have something like this -
You can try to export the sasha64 profile, then import it while logged in with the sasha user. Launch the firefox profile manager by completely closing firefox, then from a terminal, type firefox -profilemanager

Xfce does the same. Look in $HOME/.config/xfce4/xfconf/xfce-perchannel-xml for some of the files.

You may want to look at man usermod

Whew.. what an ordeal :|

@ disturbed1 -- thanks for the mention of the XFCE config files; that got me started. I had discovered the usermod command meanwhile, and executed that, and it basically produced almost the same effect as when I manually did the change the first time using Kuser, although a little more cleanly I think..

So, basically what I've done to this point:

1-- used FEBE to backup my whole Firefox configuration.
2-- changed to init1 ; userdel sasha ; usermod sasha64 to sasha
3-- went to init4 and logged in as sasha
4-- deleted all firefox profiles, created a new sasha profile.
5-- using FEBE, I restored all the firefox configuration stuff (I missed one or two things during the backup, so I had to do a tiny bit of re-configging once the profile was restored)
6-- did a recursive `find` for all files in my home/sasha/ folder and executed a `sed s/sasha64/sasha/g` on them all. For the record, there was only a single file in the xfce/.config folder that contained a path at all, so I changed that one by hand.
6b** I have yet to do the same recursion to check for any files elsewhere on the system either owned/grouped as sasha64, or containing "sasha64"
7-- went to init1 and cleaned out /tmp and rebooted
8-- logged in as sasha.

Now all is well as can be, except I STILL get those Xfce session-manager and session autostart applications started up when I log in. I'll update when I get those to stop and let y'all know how I did it.

Thanks again, disturbed1

Sasha

Well, I'm a Fluxbox user and know almost nothing about xfce but I would either look into ~/.config/xfce4 directory to see what I could change or simply (re)move it and relaunch xfce and see what happens.

Edit. I have also a file ~/.config/autostart/xfce4-settings-helper-autostart.desktop but do not know what is its purpose.

$HOME/.config/xfce4/xfconf/xfce-perchannel-xml

I went into the above directory and moved everything from there, into the trash.

Logged out & logged back in, and startup was back to the default, as though I had configured nothing at all. So, from there, one file at a time, I replaced the ones that affected my preferences, wallpapers, mouse, keyboard, and that sort of thing, and now it all works great!
I did NOT replace any of the several files with names including "*session*" which I think were what was making the session & settings tools pop open.
PLUS -- an added bonus: something that never seemed to work before, was the session management; like, if I log out while some applications are running, and/or windows open, they were never there when I logged in next time. But now they are

So, I can't put what I've learned into a single rule, as to what to do when your XFCE borks up, but that folder, initially pointed out by disturbed1, is the place to look.

Hey
Have you checked that /home/sasha and all the files in it are owned by sasha, not sasha64?
You can just do a:
chown -R sasha:users /home/sasha

Yes, I did do that thanks for asking though. I *think* that usermod may have done (some of) that, not sure, but I did do it manually too.

Things are pretty good now -- better than they were by default originally, before the name change, but also *different* in some ways, which I am still adjusting to; funny how when stuff works *exactly* as it should, it takes adjusting to :/

Sasha