Closed Bug 1076892 Opened 10 years ago Closed 10 years ago

No executable for Firefox Linux builds

Categories

(Toolkit Graveyard :: Build Config, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(firefox35 verified)

VERIFIED FIXED
mozilla35
Tracking Status
firefox35 --- verified

People

(Reporter: pauly, Assigned: glandium)

References

Details

(Keywords: regression)

Attachments

(2 files)

STR:
1. Download latest nightly linux build
2. Unzip
3. Enter on FF executable --> Error: Could not open
4. Right click/Properties on the file

AR: Type: shared library (application/x-sharedlib)
ER: Type: executable (application/x-executable)
Last good revision: 9e3d649b80a2 (2014-09-26)
First bad revision: 818f353b7aa6 (2014-09-27)
Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=9e3d649b80a2&tochange=818f353b7aa6
Flags: needinfo?(robert.strong.bugs)
Paul, is there something I checked in that you think caused this? The only checkin I see from me in the range you posted is bug 1070428 which just changes a message from configure.
Flags: needinfo?(robert.strong.bugs) → needinfo?(paul.silaghi)
OS: Windows 7 → Linux
Last nightly works fine for me. Would you happen to be trying to run the i686 build on a x86-64 system that doesn't support i686 executables (or vice-versa)? What does running it from the command line say? What does "file firefox" say? What does "uname -a" say?
Status: NEW → UNCONFIRMED
Ever confirmed: false
(In reply to Robert Strong [:rstrong] (use needinfo to contact me) from comment #2)
> Paul, is there something I checked in that you think caused this?
Sorry, forgot to mention. Just as a build config/app startup expert.

(In reply to Mike Hommey [:glandium] from comment #3)
> Last nightly works fine for me.
For me, it doesn't - 35.0a1 (2014-10-02)
> Would you happen to be trying to run the
> i686 build on a x86-64 system that doesn't support i686 executables (or
> vice-versa)? 
No. I reproduced this on 3 different machines, Ubuntu 13.04 x64, Ubuntu 14.04 x86, Ubuntu 14.04 x64 using the specific 32/64 build for each one.

> What does running it from the command line say? What does "file
> firefox" say? What does "uname -a" say?
For 35.0a1 (2014-10-02) Ubuntu 13.04 x64:

svuser@P4904:~/Desktop/Latest Nightly$ ./firefox
(process:6031): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
(process:6031): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed

svuser@P4904:~/Desktop/Latest Nightly$ file firefox
firefox: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, BuildID[sha1]=0x69e87aecd0169dd6dced75bb1062f0611316c4c5, not stripped

svuser@P4904:~/Desktop/Latest Nightly$ uname -a
Linux P4904 3.8.0-29-generic #42-Ubuntu SMP Tue Aug 13 19:40:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(paul.silaghi)
(In reply to Paul Silaghi, QA [:pauly] from comment #4)
> (In reply to Robert Strong [:rstrong] (use needinfo to contact me) from
> comment #2)
> > Paul, is there something I checked in that you think caused this?
> Sorry, forgot to mention. Just as a build config/app startup expert.
> 
> (In reply to Mike Hommey [:glandium] from comment #3)
> > Last nightly works fine for me.
> For me, it doesn't - 35.0a1 (2014-10-02)
> > Would you happen to be trying to run the
> > i686 build on a x86-64 system that doesn't support i686 executables (or
> > vice-versa)? 
> No. I reproduced this on 3 different machines, Ubuntu 13.04 x64, Ubuntu
> 14.04 x86, Ubuntu 14.04 x64 using the specific 32/64 build for each one.
> 
> > What does running it from the command line say? What does "file
> > firefox" say? What does "uname -a" say?
> For 35.0a1 (2014-10-02) Ubuntu 13.04 x64:
> 
> svuser@P4904:~/Desktop/Latest Nightly$ ./firefox
> (process:6031): GLib-CRITICAL **: g_slice_set_config: assertion
> `sys_page_size == 0' failed
> (process:6031): GLib-CRITICAL **: g_slice_set_config: assertion
> `sys_page_size == 0' failed

And that's all? What does "echo $?" say after that? Could you paste the output for "strace ./firefox" ?
Attached file output.zip
That's all.
'echo $?' returns '0'.
Does "firefox -safe-mode" start?
Yes, and the same 2 lines show up in the console.
Note that the normal firefox also works fine from the console.
(In reply to Paul Silaghi, QA [:pauly] from comment #8)
> Yes, and the same 2 lines show up in the console.
> Note that the normal firefox also works fine from the console.

What is the "normal firefox" ?
non safe mode (as in comment 0)
(In reply to Paul Silaghi, QA [:pauly] from comment #10)
> non safe mode (as in comment 0)

I'm not following. Are you saying that running firefox from the command line works but not when launching it from nautilus or whatever file manager you're using?
Exactly
(In reply to Paul Silaghi, QA [:pauly] from comment #0)
> AR: Type: shared library (application/x-sharedlib)
> ER: Type: executable (application/x-executable)

What do AR and ER mean?
Actual results / Expected results.
Note this is a regression (comment 1).
Ah, now it all makes sense, although I don't know exactly why, but it's a regression from bug 857628
Blocks: 857628
Attached image FF no executable.png
Bug 857628 has been backed out.
Merge of backout:
https://hg.mozilla.org/mozilla-central/rev/e36bdb0150b9
Assignee: nobody → mh+mozilla
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
Verified fixed FF 35.0a1 (2014-10-05) Ubuntu 13.04 x64
Status: RESOLVED → VERIFIED
I just reported this to the nautilus bugtracker: 

https://bugzilla.gnome.org/show_bug.cgi?id=741183
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.