23409 - Profile manager freezes up on startup

Status: VERIFIED INVALID

(Core Graveyard :: Profile: BackEnd, defect, P3)

Description

[benjamin-bugzilla]

Overview:

When launching ./mozilla, the profile manager windows comes up, is (I assume)
correctly displayed and then  it freezes, i.e. no input is accepted at all.

Btw, I looked at the other bugs and there are some around which look similar,
but all of them had significant differences to what happens to me, so I
considered that a new bug would fit better.

Steps to Reproduce:

Install tarball, cd into the package directory and type ./mozilla. Deleting
~/.mozilla before doing so did not change this behaviour. Copying ~/.mozilla
from a working machine did also not change the result! (It should not start the
profile manager, but it does)

Acutal Results:

The profile manager windows pops up and seems to be displayed correctly. Then
nothing happens anymore. Not only the buttons don't work (there seems to get no
event through), but also the window will not refresh (areas which got
overpainted stay gray) and the windows manager "close" button shows no result.

In the shell, I get:

MOZILLA_FIVE_HOME=/tmp/phi/mozilla/package
  LD_LIBRARY_PATH=/tmp/phi/mozilla/package
       SHLIB_PATH=/tmp/phi/mozilla/package
          LIBPATH=/tmp/phi/mozilla/package
      MOZ_PROGRAM=./mozilla-bin
      MOZ_TOOLKIT=
        moz_debug=0
     moz_debugger=
nNCL: registering deferred (0)
WEBSHELL+ = 1
WEBSHELL+ = 2
calling loadpage...
startPage:: newProfile1_1
got a request

If I kill the window (from window manager), still no change (the application
does not quit). But I can stop it with CRTL-C.

Expected Results:

Well, of course, the window should not freeze, but accept the button events and
let me create a profile.

Build Date:

I tried both, M12 and 2000-01-05-16.

Platform:

Redhat based Halloween 6.1 distribution, Linux kernel 2.2.13-12, GNOME,
Elightment, libc 2.1.2, gtk+-1.2.6-5, gtk+-devel-1.2.6-5, gtk+10-1.0.6-6,
gtk---1.0.3-1, gtk---devel-1.0.3-1, gtk-engines-0.8-1,

IT WORKS with another computer, which has RedHat 5.2 installed (no GNOME, but
fvm)...

If I copy the ~/.mozilla directory created by the second system to the first and
try again, I still get the absolut identical behaviour.

Well, if you need further information, just ask.

Comment 1

[selmer (gone)]

Ben, do you know of any FE bugs that would cause this behavior in the profile
manager interface.  I doubt this is the profile manager per-se, but rather
something in the event handling code.

Comment 2

[benjamin-bugzilla]

No, I don't have any insight to the reasons of this bug. Your guess with the
event handling code sounds reasonable for me.

Hm. Just... it does not explain the issue why the ~/.mozilla is ignored and the
profile manager starts up nonetheless.

Comment 3

[Ben Goodger (use ben at mozilla dot org for email)]

No idea why this is happening. I dont see it with either PM or CPWiz on windows.
This doesn't sound like its me because it doesnt seem to be a JS or XUL issue.

Can we get someone else to take a look at it?

Comment 4

[selmer (gone)]

We need to reproduce this locally.

Comment 5

[Grace Bush]

I cannot reproduce this 'freeze' in profile manager- with this build or todays
build.  What I do see on this build:
after removing ./mozilla:
1. running ./mozilla    Create Profile Wizard comes up, and new profile is
created.
2. running ./mozilla -installer Profile Manager comes up and I am able to
migrate a profile
(see bug 22916 for other problems) but not freezing and am able to launch

Comment 6

[racham]

Unbale to reproduce.
Could probably a user machine-specific or a due to hidden bug of some other
component that got fixed with the later builds.

Marking invalid.

Comment 7

[selmer (gone)]

Uh, that should have been "WORKSFORME"...

Comment 8

[Grace Bush]

verified

Comment 9

[leger]

Moving all Profile Manager bugs to new Profile Manager Backend component.
Profile Manager component to be deleted.

Comment 10

[Pulsebot]

Pushed by ffxbld-merge:
https://hg.mozilla.org/releases/mozilla-beta/rev/2637d9204de0
[fenix] For https://github.com/mozilla-mobile/fenix/issues/23409 - Specify fetchProvidedTopSites parameter for TopSitesConfig