J.C. Roberts wrote:
On Sun, 28 Feb 2010 12:12:36 -0600 Chris Bennett
<[email protected]> wrote:
latest current and packages as of yesterday
thanks. you're more up to date than I am. ;)
mplayer-20090708p4
mplayerplug-in-3.55p2
gnash-0.8.3p3
gecko-mediaplayer-0.9.8
Hmmm... why both plugins?
Can you see both plugins from within firefox?
Tools->AddOns->Plugins
or
Edit->Preferences->Main->Manage Addons->Plugins
Possibly the two plugins are conflicting?
OK now maybe there is something useful, whether for this or not.
When you say two plugins, do you mean gnash and mplayerplug-in?
Yes The output from about:plugins seems odd to me, but not from just
checking, but from previous looks
Also using Youtube without Flash Auto which works through
Greasemonkey.
Have you tried disabling greasemonkey?
Yes, didn't help
I am getting this error also through sites not using Flash.
Do you have other "addons" or "userscripts" installed to handle video
sites such as "DownloadHelper" or similar?
I have a simple youtube download as MP4 plugin. Its pretty simpleminded
so I doubt its the problem.
Only error message in browser is (no video)
I am getting those error messages by hitting Ctrl-Alt-F1 and watching
that stream of errors
I do not know how to capture that stream
You're obviously doing the pointy/clicky/icony/menuy thingy in a
big (bloated) "desktop" like kde or gnome. You should upgrade to cwm (in
xbase) or scrotwm. ;)
I have been using scrotwm exclusively since it came out. Heck, I can't
even figure out how to get my dual head to work properly in KDE.
I do use kate and kolourpaint, but nothing else. kolourpaint is great
for really simple tasks since it loads quick. GIMP is preferred for any
real work
There are tons of ways to get the output. On a typical terminal, you
have three streams, and each is assigned to a file descriptor.
Standard Input (STDIN) 0
Standard Output (STDOUT) 1
Standard Error (STDERR) 2
What you're seeing on the first virtual terminal (CTRL-ALT-F1) is the
output written to the "Standard Error" file descriptor.
The most simple way to see the output of STDERR is to start an xterm,
and then start firefox from it.
$ firefox35 -ProfileManager
$ firefox35 -P <profile name>
The above will give you the stderr messages for just firefox because
normally STDERR is redirected to STDOUT in an xterm.
A more complex and complete way (assuming you're not using xdm), is to
edit your /etc/syslog.conf and uncomment the entry for /dev/console
Then manually start X with redirection:
$ startx > /dev/console 2>&1
In the above, you're redirecting the output of startx to /dev/console
but you're also redirecting STDERR (2) to STDOUT (1) so it all gets to
the /dev/console device.
You could also alias 'startx' to the above in your ~/.kshrc
Then once you're in X,
$ xconsole -daemon
Or better, put the above in your ~/.xinitrc so you always have it.
An alternative to using xconsole(1) is using `xterm -C` for basically
the same thing.
This will give you all the error messages from all the applications you
start in X through the pointy/clicky/icony/menuy thingy that you call a
desktop.
If you do this, then you will not believe the number of error messages
that you've been missing from all your applications.
Off the top of my head, I can't remember if the default /etc/fbtab
takes care of the changing the ownership of /dev/console device at
login, but I think it does. Either way, it's worth checking.
OK, I will study all these methods carefully.
I have started stuff in xterm many times but never did that for error
capturing.
--
A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects.
-- Robert Heinlein
