39743 - Composer will not start/launch on linux (may 18)

Status: VERIFIED WORKSFORME

(Core :: DOM: Editor, defect, P3)

Description

[John Morrison]

For the smoketest this morning, I cannot get the composer to start:
1) from the icon in the taskbar
2) from the tasks menu
3) from ./netscape -edit on the command line (or -editor or -composer if those 
   are the right switches)

There is simply no activity; no console messages; no crash; but no composer

Comment 1

[John Morrison]

Adding smoketest keyword, but it's up to editor team to decide if this should 
hold the tree (i.e., this may be a packaging issue, or my local config).

Comment 2

[John Morrison]

composer *can* be launched on *win32* build for today

Comment 3

[Akkana Peck]

It starts for me, using -edit or the taskbar, using my debug linux build from
this morning or the 2000051805 mozilla release build, with my existing profile
or after moving ~/.mozilla aside.

Is this with a commercial or mozilla build?  Installer or tar?  Perhaps there's
an installer problem?

Comment 4

[John Morrison]

This is with the commercial build, using the tar.gz file (not the installer)

I tried with an existing profile dir, and with /bin/rm -rf ~/.mozilla

Comment 5

[rubydoo123]

assigning this one to akk

Comment 6

[John Morrison]

so akkana can start composer using the same steps that fail me (untar, clean 
profile, ./netscape -edit). 

Comment 7

[sujay]

worksforme using today's build. tever also said it worksfor him...

Comment 8

[John Morrison]

Dropping blocker as it seems to work for most others. Any ideas on why 
this is broken for my vanilla redhat 6.1 installation.

Comment 9

[Jon Granrose]

this one works on my RH 6.1 system as well untarring the netscape tarball.

the only thing I can think of is maybe your system is finding another version of
netscape in your path.

Comment 10

[John Morrison]

Nope. I say './netscape -edit' so there is no search (and I can't launch from 
the browser task menu /taskbar either). Oh well ... won't be writing any great
works of HTML on linux today.

Comment 11

[sujay]

so should we mark this WORKSFORME or leave it open?

Comment 12

[John Morrison]

marking WORKSFORME. I downloaded the tar.gz again, and untar'd it, switched
to the package directory, './netscape -edit' and composer came up.

The weird thing is that when I compared the ./package/... directory that did
not work, with the one that did, I found that 89 files in core/editor/content
were missing. I still had the log of the initial untar, and it claims that
these were untar'd at that time. How they got deleted (or never untar'd), and 
why only this one directory got hit, is a mystery to me. The only thing I can 
think of is that I untar'd to an NFS directory (my home jrgm directory) and 
something silently failed at that time. 

Sorry for the inconvenience (and anyone is welcome to review my logs, if they're 
feeling particularly masochistic).

Comment 13

[sujay]

verified in 5/18 build.