Kommentare zu: http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/ /usr/home/miwi Wed, 08 Feb 2012 10:26:15 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Von: theman http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/comment-page-1/#comment-792 theman Wed, 16 Sep 2009 20:48:48 +0000 http://bsdcrew.de/blog/?p=456#comment-792 How i fixed the firefox 3.5 crash problem: The error I was getting that killed firefox was: Assertion 'pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE) == 0' failed at pulsecore/mutex-posix.c:52, function pa_mutex_new(). Aborting. Abort trap (core dumped) How I fixed it: "Try rebuilding libcanberra and firefox35 WITHOUT pulseaudio support." from http://www.mavetju.org/mail/view_message.php?list=freebsd-gecko&id=2996595 # cd /usr/ports/audio/libcanberra/ # make deinstall clean # make config DISABLE -> Enable Pulse Audio support # make install clean I did not have to reinstall firefox 3.5 but you may have to. Now firefox 3.5 does not crash [: How i fixed the firefox 3.5 crash problem:

The error I was getting that killed firefox was:

Assertion ‘pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE) == 0′ failed at pulsecore/mutex-posix.c:52, function pa_mutex_new(). Aborting. Abort trap (core dumped)

How I fixed it:
“Try rebuilding libcanberra and firefox35 WITHOUT pulseaudio support.” from http://www.mavetju.org/mail/view_message.php?list=freebsd-gecko&id=2996595

# cd /usr/ports/audio/libcanberra/
# make deinstall clean
# make config
DISABLE -> Enable Pulse Audio support
# make install clean

I did not have to reinstall firefox 3.5 but you may have to.

Now firefox 3.5 does not crash [:

]]> Von: NEWBIE http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/comment-page-1/#comment-791 NEWBIE Wed, 15 Jul 2009 17:02:48 +0000 http://bsdcrew.de/blog/?p=456#comment-791 cannot find firefox35 in /usr/ports/www/firefox35? how do i put it there? cannot find firefox35 in /usr/ports/www/firefox35? how do i put it there?

]]> Von: Martin http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/comment-page-1/#comment-790 Martin Mon, 06 Jul 2009 10:46:27 +0000 http://bsdcrew.de/blog/?p=456#comment-790 If you like to help please read the following discussion http://lists.freebsd.org/pipermail/freebsd-gnome/2009-July/022732.html If you like to help please read the following discussion

http://lists.freebsd.org/pipermail/freebsd-gnome/2009-July/022732.html

]]> Von: Lucius Windschuh http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/comment-page-1/#comment-789 Lucius Windschuh Mon, 06 Jul 2009 10:35:36 +0000 http://bsdcrew.de/blog/?p=456#comment-789 Hi. I'm also getting the same assertion failure as Andrew: Assertion 'pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE) == 0' failed at pulsecore/mutex-posix.c:52, function pa_mutex_new(). Aborting. It comes sometimes randomly (?), but every time I start Firebug with the Google Pagespeed extension. :-( Hi.
I’m also getting the same assertion failure as Andrew:
Assertion ‘pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE) == 0′ failed at pulsecore/mutex-posix.c:52, function pa_mutex_new(). Aborting.

It comes sometimes randomly (?), but every time I start Firebug with the Google Pagespeed extension. :-(

]]> Von: Ken Stein http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/comment-page-1/#comment-788 Ken Stein Sun, 05 Jul 2009 13:31:23 +0000 http://bsdcrew.de/blog/?p=456#comment-788 Hi, great that it's in ports - but for some reason on 7.0-RELEASE the tarball is corrupt or missing on *every* mirror my portinstall knows of. When I tried forcing it anyways using -m NO_CHECKSUM=yes, tar complained of the corrupt file (I figured someone just forgot to update the sha/asc file) Hope this can be corrected soon! My firefox2 build currently crashes every few hours whether I am actually browsing the web or not and I am looking forward to the new release. Hi,
great that it’s in ports – but for some reason on 7.0-RELEASE the tarball is corrupt or missing on *every* mirror my portinstall knows of. When I tried forcing it anyways using -m NO_CHECKSUM=yes, tar complained of the corrupt file (I figured someone just forgot to update the sha/asc file)

Hope this can be corrected soon! My firefox2 build currently crashes every few hours whether I am actually browsing the web or not and I am looking forward to the new release.

]]> Von: Stephen http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/comment-page-1/#comment-787 Stephen Fri, 03 Jul 2009 04:27:57 +0000 http://bsdcrew.de/blog/?p=456#comment-787 Waiting for port mail/thunderbird3 Waiting for port mail/thunderbird3

]]> Von: Chris (seraphyn) 's status on Thursday, 02-Jul-09 16:49:20 UTC - Identi.ca http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/comment-page-1/#comment-786 Chris (seraphyn) 's status on Thursday, 02-Jul-09 16:49:20 UTC - Identi.ca Thu, 02 Jul 2009 16:49:25 +0000 http://bsdcrew.de/blog/?p=456#comment-786 [...] @olhe http://bsdcrew.de/blog/2009/07/firefox-35-in-ports/ firefox 3.5 is in !freebsd ports [...] [...] @olhe http://bsdcrew.de/blog/2009/07/firefox-35-in-ports/ firefox 3.5 is in !freebsd ports [...]

]]> Von: Oliver Herold (olhe) 's status on Thursday, 02-Jul-09 16:20:33 UTC - Identi.ca http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/comment-page-1/#comment-785 Oliver Herold (olhe) 's status on Thursday, 02-Jul-09 16:20:33 UTC - Identi.ca Thu, 02 Jul 2009 16:20:45 +0000 http://bsdcrew.de/blog/?p=456#comment-785 [...] http://bsdcrew.de/blog/2009/07/firefox-35-in-ports/ firefox 3.5 is in !freebsd ports !bsd [...] [...] http://bsdcrew.de/blog/2009/07/firefox-35-in-ports/ firefox 3.5 is in !freebsd ports !bsd [...]

]]> Von: Andrew Lankford http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/comment-page-1/#comment-784 Andrew Lankford Thu, 02 Jul 2009 15:46:00 +0000 http://bsdcrew.de/blog/?p=456#comment-784 Okidoke. Okidoke.

]]> Von: Martin http://miwi.bsdcrew.de/2009/07/firefox-35-in-ports/comment-page-1/#comment-783 Martin Thu, 02 Jul 2009 07:31:02 +0000 http://bsdcrew.de/blog/?p=456#comment-783 Andrew, could you please send a mail to gecko@ with a full descripton of your problemes, I think here the wrong place for the discussion. Andrew, could you please send a mail to gecko@ with a full descripton of your problemes, I think here the wrong place for the discussion.

]]>