User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217 I have Windows and Linux running on the same machine. When I configure the default search engine of my Mozilla Browser in Windows, it's going lost in the identical profile under Linux or revert: configured under Linux throws the search engine configuration from Windows away)! Anything else works fine! Sharing bookmarks, histroy, emails.... I use the physical identical hdd-space (its a FAT32 partition where both OS have read/write access) and the same version number in both OS. Reproducible: Always Steps to Reproduce: 1. create 2 OS systems (Windows and Linux) on sepparate partitions (I have NTFS, and Reiser) 2. create a FAT32 partition and store the Mozilla profile on this sepparate patition 3. set the Mozilla's profile for both instances on this FAT32 partition location 4. setup mozilla and choose a default search engine, I use "google" 5. type in a search term/key words in histroy bar and click the down-key to send this term to the specified search engine (google). 6. shut down your computer and restart it in the other OS 7. check if your bookmarks are the same and the history bar is identical to the instance of the other OS (that should be working). 7. try to search in the same way on this mozilla version now 8. Now, Mozilla cannot detect the selected default search engine. Actual Results: I cannot send the search term/key words in the other Mozilla version to the selected search engine (e.g.). Expected Results: I want to select a default search engine that is active for any mozilla instance which uses the shared profile. I need this, because I want my mails and bookmarks to be identical in Linux and Windows. Its not neccessairy to synchronize in an complicate way.. :)
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.