firefox[2,3] will not start after recent ports upgrade

Daniel Roethlisberger daniel at
Mon Feb 2 08:38:11 PST 2009

Alexander Konovalenko <kono at> 2009-02-01:
> > From: Daniel Roethlisberger <daniel at>
> >...
> > Could it be the case that firefox-bin hangs in umtxn state?
> you're right!
> > (Check using ps -laux instead of -aux)
> > >
> > >
> > >
> >
> > These trace the wrong process: the wrapper shell script (sh).
> > The actual hanging process would be firefox-bin, not sh.  Try
> > ktracing with child processes (-i).
> "ktrace -i" showed last line:
>   firefox-bin CALL  _umtx_op(0x65f8e0,0x8,0x1,0x65f8c0,0)
> Do you know which port/lib causing this hang on _umtx_op?

Unfortunately, no.  I have a box with ports tree from around
mid-January on which I was unable to fix this problem.  Native
firefox 2 and 3 hung in umtxn state.  So I did pkg_delete -a, rm
-rf /usr/local, rebuilt and installed all ports: now the firefox3
build hangs in umtxn state while running a tool called shlibsign.
No idea how to fix this.  I don't want to update the ports tree
to after the unpretty xorg-7.4 changes just yet.

I suspect the problem may be related to upgrading using
freebsd-update from 7.0 to 7.1, but that's just a wild guess
based on the problem appearing after the upgrade; I did make sure
no old leftover libraries or binaries were still lying around.

Daniel Roethlisberger

More information about the freebsd-ports mailing list