http://qa.mandrakesoft.com/show_bug.cgi?id=3076
------- Additional Comments From [EMAIL PROTECTED] 2003-03-10 02:22 ------- After a complete reformat and install, I see exactly the same behaviour. As a sanity check, I checked and made sure that I am not using any form of a proxy at this time, as well as confirming that the configuration is to accept all cookies and not to discard them at the end of a session. It is not related to previously existing accounts or folders, as this situation does not have any pre-existing accounts, or user folders at all. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: When using Galeon to log into sites such as my.yahoo.com, slashdot.org, ClubMandrake, etc, my expectation is that cookies specific to thes sites should be used to retain login ingormation so that returning to these sites after closing Galeon should not require logging in again unless the cookie has expired due to old age, (generally not on the same day as the previous login.) I am not having that experience. in an attempt to get Galeon to behave as expected, I have deleted the following folders with no apparent effect. ~/.galeon ~/.gconf/apps/galeon ~/.gconf/apps/gnome-config/galeon After deleting the ~/.mozila directory, all history items were also lost, however Galeon is still either not saving cookies with the appropriat einformation, or is not able to retreive that information at a later time. searches for cookies from the ~/ directory by root do not show any files with a partial name of cookie, nor any file with the name of the domain that the cookie belongs to. This may be reated to the method of install I made for Beta3, RC1 and RC2. I had made an earlier install of Knoppix (debian based distribution) with the /home folder being it's own partition, and everything else in the / folder (partition) Instalation of Beta3 was done by formatting the / partition, and leaving the /home partition as /home. As this system has no mission critical data on it I will attempt another install by deleting content from all partitions (clean install) and will provide an update that way as well. I suspect this problem will be most obvious to people who upgrade from other operating systems.
