336649 - v1.0.1 does not launch home page after first start

Status: VERIFIED WORKSFORME

(Camino Graveyard :: Preferences, defect)

Description

[dave oshel]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0

1.0.1 seems to ignore Home Page prefs, and relaunches the www.caminobrowser.org/start/ page.  This is supposed to be one time only, I thought.

Reproducible: Always

Comment 1

[froodian (Ian Leue)]

Can you try with a fresh profile?  Move ~/Library/Application Support/Camino/ and relaunch Camino.  Obviously, you'll have to relaunch twice to see if it's better or not... :p

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

If this is happening, it would not surprise me at all if this was something that the change in the build method (scripts to tinderboxen) caused, too.

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

This is WFM both on a profile created with 1.0 and then accessed with 1.0.1 and with a profile freshly-created with 1.0.1.

Dave, by any chance did you create a new profile at some point with a nightly build (which would have set the homepage pref to welcome.html aka cb.o/start)?

Comment 4

[froodian (Ian Leue)]

Dave, can you respond to comments 1 and 3 please? :)

Comment 5

[Jay Scott]

I have a similar problem with 1.0.2 (on 10.3.9 iBook G4). The symptom is that the /start/ page shows on the first launch every day; subsequent launches on the same day correctly bring up about:blank as configured. Seemingly small but I find it an extremely irritating bug. My profile was originally created under 1.0, upgraded successively to 1.0.1 (which was OK) and 1.0.2. I do not know whether a fresh profile shows the problem, because I have to wait until the next day to see if it shows up.

Comment 6

[Chris Lawson (gone)]

Thanks for commenting here, Jay. If the problem recurs for you (or for the original reporter), please re-open this bug and we'll try to investigate further.

Jay, is there any chance that something is deleting your prefs.js file every 24 hours? That would cause a similar symptom, as would an inability to write the prefs file.

cl

Comment 7

[Jay Scott]

The prefs.js file has create date = modify date = yesterday, which is the last time the bug occurred to me. It inexplicably did not happen today, to my surprise.

That suggests that something is deleting the prefs.js file. I have no idea what it might be, outside of Camino itself. Certainly nothing that I set up.