I checked that, I've gaim added, but nothing else. When I log into gnome (via gdm), it loads gaim, the rox windows I had open, the gconf editor and my /home folder in nautilus. Its annoyance, having to close them all everytime.

I recently had something like that...
Gnome saved a file from one of my users after close as .gconfd/saved_state not as empty file but a HUGE file, 1,5 G!!

Every time the user started a session (with the option of NOT to restoring sessions) Gnome tryied to load that THING, hanging and make my poor system terrible slow! I have 1Gb of RAM, less then the size of file.
And even when the user close her gnome session the thing continued aliving at background, eating memory and cpu. I just deleted... and next time user login things go normally again.

It seems that gnome forget to clean that and when in a restart, the fact that this file was not 0 size make gnome restoring the session (I don't know why it was so big)

I've seen the large ~/.gconfd/saved_state thing.. I'm hacking a bit on gconf, and I think I
introduced a bug into the program, which caused it to segfault. Since gnome-session
(I think) respawns gconfd-2 when it dies, it keeps respawning in an endless loop.
I think this is probably the reason that ~/.gconfd/saved_state gets extremely
large, although I'm unsure as to what the fix is... maybe putting a time limit on how fast
programs can respawn in gnome-session?

Well in my case saved_state usually goes to zero size when session closes... I suposse that din't happen for that time because something make it grow far behind the easily managed. I'm just a little woried that eventually that happen again. Hope not!
(btw, i deleted from a console not with the user login... just saying for the case it was not clear... in fact, i don't know if that matters)

@Fenster
You can always try to move your .gconf* and .gnome* files out of ~/ and then start the session. That should start a a fresh gnome configuration with the only down point that you'll lost your actual personalizations (if that fails you can move it back again).

@Fenster
You can always try to move your .gconf* and .gnome* files out of ~/ and then start the session. That should start a a fresh gnome configuration with the only down point that you'll lost your actual personalizations (if that fails you can move it back again).

Just did that, it still spawned its usual lot. Ah well, if nothing else, it probably narrowed down things some.

- Get your gnome session into the state you want it to be in when you log in (IE close down everything you don't want to load, also you can edit the session using the Session manager in Preferences)
- In the Session Options tab in the Session Manager tick "ask on logout"
- Now logout and tick "save current setup"

When you log back in the session you saved at logout should be restored.

- Get your gnome session into the state you want it to be in when you log in (IE close down everything you don't want to load, also you can edit the session using the Session manager in Preferences)
- In the Session Options tab in the Session Manager tick "ask on logout"
- Now logout and tick "save current setup"

When you log back in the session you saved at logout should be restored.

Cheers,
James

Cheers, that worked. However, I don't *want* to save a session, which is my problem with Gnome. If I want to load something when I log in, I will. If I save a blank session and then stop saving, it will load all that crap again. Ah well, I guess I'll stick with Flux, crappy fonts or not.

- Get your gnome session into the state you want it to be in when you log in (IE close down everything you don't want to load, also you can edit the session using the Session manager in Preferences)
- In the Session Options tab in the Session Manager tick "ask on logout"
- Now logout and tick "save current setup"

When you log back in the session you saved at logout should be restored.

Cheers,
James

Cheers, that worked. However, I don't *want* to save a session, which is my problem with Gnome. If I want to load something when I log in, I will. If I save a blank session and then stop saving, it will load all that crap again. Ah well, I guess I'll stick with Flux, crappy fonts or not.

If you dont tick save session on the logout dialog you'll load the session you saved last.

- Get your gnome session into the state you want it to be in when you log in (IE close down everything you don't want to load, also you can edit the session using the Session manager in Preferences)
- In the Session Options tab in the Session Manager tick "ask on logout"
- Now logout and tick "save current setup"

When you log back in the session you saved at logout should be restored.

Cheers,
James

Cheers, that worked. However, I don't *want* to save a session, which is my problem with Gnome. If I want to load something when I log in, I will. If I save a blank session and then stop saving, it will load all that crap again. Ah well, I guess I'll stick with Flux, crappy fonts or not.

If you dont tick save session on the logout dialog you'll load the session you saved last.

Mean while you can try another thing with gnome (a little extreme, but...). You can delete you from the list of users, move your ~/ to some temporary location and create your account again as a new user. That will start a fresh gnome configuration and if need you can get your personal files from your removed home.