Closed Bug 133309 Opened 23 years ago Closed 22 years ago

Profile Picker busted, can't enter product

Categories

(SeaMonkey :: Startup & Profiles, defect)

x86
Windows 98
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: selmer, Assigned: neil)

Details

(Whiteboard: [adt3])

3/22 and 3/25 trunk builds On my win98 machine, I downloaded the N6SetupB.exe for each of these builds and installed them. When the profile picker comes up, I get a short, wide dialog with a white background and some text explaining what profiles are. There are no buttons. The only available choice is to use the [X] to close it but then I can't get into the browser with these builds.
Setting severity to critical. No regular users would be able to get past this.
Severity: normal → critical
Bhuvan came to help me - thanks Bhuvan! The problem is that I am the only person in the world testing *not* installing the classic skin. There is a bug that is forcing the profile manager to use the classic skin even though I am (and have always) used only the modern skin. When the classic skin is not installed, the product is completely unusable. If I then install the classic skin, the profile picker comes up with the classic skin and is usable. (Unfortunately, it also changed my skin to classic somehow, I had to manually change it back to Modern and restart.) This sucks! Nominating nsbeta1. Adding to the CC.
Keywords: nsbeta1
approving nomination and assigning impact to adt2 due to severity. Not clear to me how many people use the profile picker. Any data on that? shuehan-can you take a look at this bug?
Keywords: nsbeta1nsbeta1+
Whiteboard: [adt2]
I'm changing this to adt3. To get into this state you must choose the custom install and then also choose not to take the classic skin (which is chosen by default.) Then, you need to have multiple profiles. So, even though the problem itself is very severe I think we're down in the 1% range of affected users.
Whiteboard: [adt2] → [adt3]
Is this related to http://bugscape/show_bug.cgi?id=12686 - where commercial builds are showing classic skin instead of modern?
Sounds like a Netscape only problem, probably dependent on the bug andrew mentions
Ben, if a Mozilla user didn't install Classic then they'd probably hit this too. (Once I chose to install classic my problem went away.)
Mass moving nsbeta1+/adt3 bugs assigned to Navigator team engineers out to target milestone 1.0.1. Please confine your attentions to driving down our list of TM 1.0 bugs for beta. Better to help, debug, or test one of them than fix one of these.
Target Milestone: --- → mozilla1.0.1
Steve, You cannot install Mozilla without classic, as it is the default.
Ah, right. Maybe this should migrate to bugscape or be duped against the bug Andrew noted.
Changing nsbeta1+ [adt3] bugs to nsbeta1- on behalf of the adt. If you have any questions about this, please email adt@netscape.com. You can search for "changing adt3 bugs" to quickly find and delete these bug mails.
Keywords: nsbeta1-
Changing nsbeta1+ [adt3] bugs to nsbeta1- on behalf of the adt. If you have any questions about this, please email adt@netscape.com. You can search for "changing adt3 bugs" to quickly find and delete these bug mails.
Keywords: nsbeta1+
This is on the windows (win2k) 8/28 build also. I had to revert! I was using the Classic skin. I did a complete install and used all the other defaults. How do I get past this?????? When I tried it on a different machine, I got a missing dll message and it also crashed.
Also, if you have more than one profile, the profile picker always comes up as the first thing, and you are dead in the water!
What is happening on this? Its impossible to use Mozilla if you have more than one profile. It should be a blocker.
James Rome, sounds like bug 162593 not this one.
No, I get exactly the dialog described in the first report here. Since there are no buttons to press, and hitting return does nothing, Mozilla does not launch because you cannot choose the dialog!
I've just started seeing this with CVS builds (WinXP). What fixed it in my case was to delete the \Program Files\mozilla.org directory that is left behind after uninstalling the previous version using Control Panel->Add/Remove Programs. Given that this bug is 6 months old I tried to figure out why I've only just started seeing it (I normally leave the mozilla.org directory in place). The one thing I'd done before I started seeing this was to install the latest Skypilot theme which now installs in the system Chrome directory rather than the users. Since skins have been mentioned in previous comments I figure it is related.
retargeting
Target Milestone: mozilla1.0.1 → Future
.
Assignee: bugs → neil.parkwaycc.co.uk
Target Milestone: Future → ---
As follows from comment #9, this bug is INVALID for mozilla (we always install classic), and netscape is dead anyway.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.