From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] firefox-bin crashing a few times every day
Date: Mon, 12 Nov 2007 14:50:26 -0800 [thread overview]
Message-ID: <5bdc1c8b0711121450j20760ecfjc2ef040b29b5cb2d@mail.gmail.com> (raw)
In-Reply-To: <d257c3560711121323k37b5918h8e8c372b6fa2db9c@mail.gmail.com>
On Nov 12, 2007 1:23 PM, Beso <givemesugarr@gmail.com> wrote:
> this one breaks your firefox!!!!
>
> Helix DNA Plugin: RealPlayer G2 Plug-In Compatible
> npwrapper.nphelix.so
> remove helix and use xine in its place for the apps that are using it. also
> remove all real player apps, and build win32codecs with real flag, and then
> install the mplayerplug-in. you cannot use helix-real with firefox-64> 1.5
> versions for what i know.
This may be something stranded but even the data in about:plugins is
somewhat suspect.
File name: npwrapper.nphelix.so
Helix DNA Plugin: RealPlayer G2 Plug-In Compatible version
0.4.0.626 built with gcc 3.2.0 on Jul 26 2007
>From emerge.log, nothing was built on July 26, 2007:
1185207076: Started emerge on: Jul 23, 2007 09:11:16
1185207076: *** emerge sync
1185207076: === sync
1185207076: >>> Starting rsync with rsync://134.68.220.97/gentoo-portage
1185207227: === Sync completed with rsync://134.68.220.97/gentoo-portage
1185207315: *** terminating.
1185729994: Started emerge on: Jul 29, 2007 10:26:34
1185729994: *** emerge sync
1185729994: === sync
1185729994: >>> Starting rsync with rsync://140.211.166.165/gentoo-portage
1185730131: === Sync completed with rsync://140.211.166.165/gentoo-portage
1185730227: *** terminating.
Maybe that July 26th date was from when something was built off of
this machine. I'm not sure.
I've removed realplayer. I need to search out exactly what you meant
by using xine inside my browser. I don't see an nsplugin for xine.
I'm a little worried that my machine here might need some looking
after in terms of getting up to date. I'm going to give the current
use flags a once over and then do an emerge -DuN world to make sure
everything is more or less consistent with what the Gentoo devs would
expect. I'll look at the wiki's and see if I can find a good AMD64
wiki that addresses all this stuff in parallel. If you get a chance to
clarify any of this then thanks in advance!
Back later, and thanks!
- Mark
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-11-12 22:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 17:34 [gentoo-amd64] firefox-bin crashing a few times every day Mark Knecht
2007-10-29 17:41 ` Javi Moreno
2007-10-29 17:48 ` Mark Knecht
2007-10-29 18:45 ` Beso
2007-10-29 23:45 ` [gentoo-amd64] " Duncan
2007-10-30 0:02 ` [gentoo-amd64] " Mark Knecht
2007-11-11 21:49 ` Mark Knecht
2007-11-11 22:52 ` Beso
2007-11-11 23:05 ` Mark Knecht
2007-11-12 8:36 ` Beso
2007-11-12 17:14 ` Jeffrey Gardner
2007-11-12 18:35 ` Mark Knecht
2007-11-12 18:56 ` Beso
2007-11-12 19:25 ` Mark Knecht
2007-11-12 21:02 ` Beso
2007-11-12 19:32 ` Drake Donahue
2007-11-12 21:03 ` Mark Knecht
2007-11-12 21:23 ` Beso
2007-11-12 22:50 ` Mark Knecht [this message]
2007-11-12 22:46 ` Drake Donahue
2007-11-13 1:31 ` nuitari
2007-11-12 21:09 ` Beso
2007-11-12 19:39 ` Sergio Polini
2007-11-12 21:06 ` Beso
2007-11-13 0:35 ` Mark Knecht
2007-11-13 3:03 ` Drake Donahue
2007-11-13 17:30 ` [gentoo-amd64] " Duncan
2007-11-13 17:55 ` Mark Knecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bdc1c8b0711121450j20760ecfjc2ef040b29b5cb2d@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox