[gentoo-amd64] Re: firefox-bin crashing a few times every day

[Duncan <1i5t5.duncan@cox.net>]

"Mark Knecht" <markknecht@gmail.com> posted
5bdc1c8b0711121635t5a1e02abx807e5be4bab7c45e@mail.gmail.com, excerpted
below, on  Mon, 12 Nov 2007 16:35:31 -0800:

> OK, it seems that sometimes FLash is working on my system. It never
> works on Yahoo but sometimes works on YouTube. I think it may fail on
> YouTube after going to Yahoo, but not sure yet.

Interesting.  I'm running swfdec (freedomware flash, was in the Sunrise 
overlay, don't know if it still is or if it moved into the main tree by 
now) on 64-bit firefox here.  Of course, it's not a full latest version 
implementation yet, but it does work on YouTube, which uses an older 
flash version, and I've been enjoying catching up on what everyone else 
has been raving about for awhile.

The thing is, apparently there's some sort of timing issue with the way 
the youtube pages load, as sometimes they detect swfdec as flash, 
sometimes they don't, but when they don't, I can reload the page and they 
usually do.  If not, I reload again...

So it's interesting that someone running real flash seems to be 
experiencing somewhat similar issues.  If it's the same thing, then it's 
not particularly that it doesn't work after Yahoo, but that sometimes the 
pages detect it and sometimes they don't.  Why, I haven't delved into, 
but that seems to be the case.  Try refreshing the page a few times, and 
if it's the same problem I've had on youtube with swfdec, it'll detect 
the flash somewhat over 50% of the time, probably ~60-75% of the time, or 
at least that's been my experience here.

> I'm thinking that for win32codecs the quicktime use flag isn't supported
> in the version from portage, but I'm not sure what the (-quicktime%)
> indication really means. Does that mean the quicktime falg has been
> 'recently removed' from win32codecs?

I see it's actually (-quicktime%*).  The negative parenthesis/percent can 
indicate a masked flag as well, but the asterisk indicates a recent 
change.  Thus, it's indicating either that it was recently masked 
(unlikely) or that your current version has the flag, but the new version 
you'd be merging no longer has the quicktime flag.  If it's something you 
care about, that's when you do an emerge --pretend --changelog 
win32codecs and see if the flag change is mentioned in the changelog.  
Often, it will be.  (Occasionally portage's --changelog functionality 
won't work, and you'll have to manually view the changelog at, for this 
package, $PORTDIR/media-libs/win32codecs/Changelog, opening it in an 
editor or catting it to the screen or whatever.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list