Comment 54 for bug 84591

Persistent mode actually does work for me in Tribe 5. There are two issues that I experience, though: gnome-network manager does not seem to maintain the WPA password that I enter for my access point; and I get a "umount" failure on shutdown. But, booting in persistent mode saves my installed programs; it saves my changes in firefox; and it saves my configurations in nautilus. So, it seems possible that persistence is actually fixed and there are some different issues causing these other problems. Don't know.

Looks like someone is working on the umount failure - looks like they confirmed there is an issue (see bug report 125702).

As far as the gnome-network manager not maintaining the password, I wonder if that is a persistence issue or a different issue given that other persistence functionality works (at least it did for me the most recent few times I tried it). While I don't understand all the details of the functionality of persistence, it seems it would be odd for persistence to work partially (e.g. maintain installed programs, but not network manager settings). As far as the gnome-network manager issue I experience, see bugs 131233 and 132473, for example. Bug 131233 sounds a lot like what I experience when using gutsy persistence. I also think some people reported this same network manager issue in the "patched" feisty iso that was prepared where persistence otherwise worked.

Jerry, did you try installing a program to see if it is still installed upon reboot? Or configuring firefox or nautilus? Just curious if persistence might be working for some people and not others. I have actually been wondering if this bug has actually been fixed, but if you are still having issues . . . . Anyone else tried it?