Building a nightly resulted in a build with window which is not responding to clicks or search commands on the home page. No elements below the main search bar were responsive.

UNCONFIRMED
Unassigned

Status

()

Firefox
Build Config
UNCONFIRMED
4 years ago
a year ago

People

(Reporter: durgaprsd04, Unassigned, NeedInfo)

Tracking

({64bit})

33 Branch
x86_64
Linux
64bit
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 (Beta/Release)
Build ID: 20140627194317

Steps to reproduce:

install firefox using the instructions given here using ssh from another pc. 
https://developer.mozilla.org/en-US/docs/Build_and_Install



Actual results:

I got a firefox executable in /src/obj/dist/bin, . I started it with ./firefox under the directory and then a nightly build window pops up . This window is unresponsive to any search requests or any clicks(on preferences addons and so on) .The only responsive thing is the search bar and other elements at the top. I haven't installed firfox in my pc. 
I just build it and executed it. My pc is a dell with 4Gigs of RAM 500GB hard disk and I am using ubuntu  14.04 fresh install. 


Expected results:

All the clicks and search requests must have been responsive
(Reporter)

Updated

4 years ago
Summary: On building I got a nightly window which is not responding to clicks or search commands on the front page. I cannot use any elements below the search bar. → On building a nightly window was got which is not responding to clicks or search commands on the front page. No elements below the main search bar could be used.
(Reporter)

Updated

4 years ago
Summary: On building a nightly window was got which is not responding to clicks or search commands on the front page. No elements below the main search bar could be used. → On building a nightly window was got which is not responding to clicks or search commands on the front page. No elements below the main search bar was responsive
(Reporter)

Updated

4 years ago
Summary: On building a nightly window was got which is not responding to clicks or search commands on the front page. No elements below the main search bar was responsive → On building a nightly window was got which is not responding to clicks or search commands on the front page. No elements below the main search bar were responsive
(Reporter)

Updated

4 years ago
Summary: On building a nightly window was got which is not responding to clicks or search commands on the front page. No elements below the main search bar were responsive → On building a nightly window was got which is not responding to clicks or search commands on the home page. No elements below the main search bar were responsive.
(Reporter)

Updated

4 years ago
Keywords: 64bit

Comment 1

4 years ago
That page has terrible instructions. I've asked the MDN folks to redirect it to the actual docs. Use:

https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions

instead.

More generally, can you attach your mozconfig file, if you used one, and detail if, when you download a regular build downloaded from www.mozilla.org, that build does work?
Flags: needinfo?(durgaprsd04)
(Reporter)

Comment 2

4 years ago
I didn't use any .mozconfig file. When I did the same in another pc without ssh it kinda worked.So it may
be a trouble with ubuntu 14.04.
Flags: needinfo?(durgaprsd04)

Updated

4 years ago
Summary: On building a nightly window was got which is not responding to clicks or search commands on the home page. No elements below the main search bar were responsive. → Building a nightly resulted in a build with window which is not responding to clicks or search commands on the home page. No elements below the main search bar were responsive.

Comment 3

4 years ago
(In reply to durgaprsd04 from comment #2)
> I didn't use any .mozconfig file. When I did the same in another pc without
> ssh it kinda worked.So it may
> be a trouble with ubuntu 14.04.

Can you provide information on what was different about the system where it didn't work? Without more information we don't really have a good way to figure out what the issue is and/or how to fix it, and we should mark the issue incomplete.
Flags: needinfo?(durgaprsd04)
(Reporter)

Comment 4

4 years ago
I have built firefox atleast 3 times hoping this would happen. Fortunately it ain't. For ease of reproducing the bug I will brief what I did.
1. Downloaded firefox at 19/06 about noon from mozilla central. 
2. Extracted it to a folder under ~/Public
3. I left the system and 'ssh'ed  into it from another system with same config same os and all. 
4. Started building firefox as told earlier( using make -f client.mk)
5. And I started firefox in the other system(in dist****/bin/firefox) 
6. None of the buttons or fields were responsive expect for the search and menu bars at the top.

As I mentioned earlier building using the same nightly build in a different machine with same specs and that too through ssh I didn't end up with such a firefox . So I would assume it had something to do with machine used earlier. I have the same nightly with me. I will try it once again and if no trouble I will put it up here. I assume it is OK.
Flags: needinfo?(durgaprsd04)

Comment 5

4 years ago
(In reply to durgaprsd04 from comment #4)
> I have built firefox atleast 3 times hoping this would happen. Fortunately
> it ain't. For ease of reproducing the bug I will brief what I did.
> 1. Downloaded firefox at 19/06 about noon from mozilla central. 
> 2. Extracted it to a folder under ~/Public
> 3. I left the system and 'ssh'ed  into it from another system with same
> config same os and all. 
> 4. Started building firefox as told earlier( using make -f client.mk)
> 5. And I started firefox in the other system(in dist****/bin/firefox) 
> 6. None of the buttons or fields were responsive expect for the search and
> menu bars at the top.
> 
> As I mentioned earlier building using the same nightly build in a different
> machine with same specs and that too through ssh I didn't end up with such a
> firefox . So I would assume it had something to do with machine used
> earlier. I have the same nightly with me. I will try it once again and if no
> trouble I will put it up here. I assume it is OK.

Do you know if the build used GTK 3  rather than GTK 2, perhaps?
Flags: needinfo?(durgaprsd04)
(Reporter)

Comment 6

4 years ago
Dunno!. How could I know this?
Flags: needinfo?(durgaprsd04)

Updated

4 years ago
Flags: needinfo?(durgaprsd04)
Component: Untriaged → Build Config
durgaprsd04 can you still reproduce this?
You need to log in before you can comment on or make changes to this bug.