Plugins on Ubuntu 7

3 views
Skip to first unread message

psaf...@googlemail.com

unread,
Aug 21, 2007, 5:26:32 AM8/21/07
to
I'm trying to install video plugins (Quicktime, wmv etc) on Opera for
Ubuntu. The opera plugins page seems to see a variety of plugins for
these media types, but all I get are the grey boxes. Videos work fine
on Firefox. I guess I need to enable it in some way. Any ideas?

Thanks,

Peter

Eirik Byrkjeflot Anonsen

unread,
Aug 21, 2007, 5:39:40 AM8/21/07
to
"psaf...@googlemail.com" <psaf...@googlemail.com> writes:

Gray boxes usually means the plug-in dies for some reason. You may
want to try running opera from a terminal and see if you get any error
messages.

eirik

psaf...@googlemail.com

unread,
Aug 21, 2007, 6:47:56 AM8/21/07
to
>
> Gray boxes usually means the plug-in dies for some reason. You may
> want to try running opera from a terminal and see if you get any error
> messages.
>
> eirik

Thanks for your response. I get several messages like this:

opera: Plug-in 14235 is not responding. It will be closed.
opera: Define environment variable OPERA_KEEP_BLOCKED_PLUGIN to keep
blocked plug-ins.

if I do "export OPERA_KEEP_BLOCKED_PLUGIN=1", the error messages stop,
but I still only have grey boxes. I also get this:

** Message: NP_Initialize
** Message: GetValue variable 2 (2)
** Message: GetValue variable 2 (2)

but that looks like debugging output. The only other thing that might
be incriminating is when Opera starts up, I get this:

ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be preloaded:
ignored.
ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded:
ignored.
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device


Any ideas?

Peter

Eirik Byrkjeflot Anonsen

unread,
Aug 21, 2007, 7:11:26 AM8/21/07
to
"psaf...@googlemail.com" <psaf...@googlemail.com> writes:

>>
>> Gray boxes usually means the plug-in dies for some reason. You may
>> want to try running opera from a terminal and see if you get any error
>> messages.
>>
>> eirik
>
> Thanks for your response. I get several messages like this:
>
> opera: Plug-in 14235 is not responding. It will be closed.
> opera: Define environment variable OPERA_KEEP_BLOCKED_PLUGIN to keep
> blocked plug-ins.

Bad sign. The plug-in is probably hanging (or dead).

>
> if I do "export OPERA_KEEP_BLOCKED_PLUGIN=1", the error messages stop,
> but I still only have grey boxes. I also get this:

Yes, that hardly ever helps. It just keeps opera from killing the
plug-in when we believe it is stuck.

>
> ** Message: NP_Initialize
> ** Message: GetValue variable 2 (2)
> ** Message: GetValue variable 2 (2)
>
> but that looks like debugging output. The only other thing that might
> be incriminating is when Opera starts up, I get this:

Yes, I'd say it's debugging output from the plug-in itself.

>
> ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be preloaded:
> ignored.
> ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded:
> ignored.

Old workaround for java crashes which doesn't work quite as it should
anymore. I'm pretty sure they're not related to this problem, though.

> X Error: BadDevice, invalid or uninitialized input device 169
> Major opcode: 145
> Minor opcode: 3
> Resource id: 0x0
> Failed to open device
> X Error: BadDevice, invalid or uninitialized input device 169
> Major opcode: 145
> Minor opcode: 3
> Resource id: 0x0
> Failed to open device
>

A bit strange. But if these errors show up before you go to a page
that tries to load the plug-in, it's probably not related.

It's possible to turn on a whole lot of debug output from opera's
plug-in handling by setting an environment variable before starting
opera, but I'm not really involved in that code any more. But you
can try:

export OPERA_PLUGINWRAPPER_DEBUG=12

or any other number. If I remember correctly, 4 will give all error
messages, 10 will trace through most of the calls, and 20 is about the
most you can get (And will print out every byte in the communication
between opera and the pluginwrapper).

eirik

psaf...@googlemail.com

unread,
Aug 21, 2007, 7:17:57 AM8/21/07
to
> It's possible to turn on a whole lot of debug output from opera's
> plug-in handling by setting an environment variable before starting
> opera, but I'm not really involved in that code any more. But you
> can try:
>
> export OPERA_PLUGINWRAPPER_DEBUG=12
>

libnpp: NPP_GetMIMEDescription (npp)
libnpp: NPP_GetValue: instance=(nil), var=1, val=0xbf813648
libnpp: NPP_GetValue: instance=(nil), var=2, val=0xbf813648
operapluginwrapper: Destructing pluginController
operapluginwrapper: Destructing pluginController
** Message: GetValue variable 1 (1)


** Message: GetValue variable 2 (2)

operapluginwrapper: Destructing pluginController
** Message: GetValue variable 1 (1)


** Message: GetValue variable 2 (2)

operapluginwrapper: Destructing pluginController
operapluginwrapper: Destructing pluginController
** Message: GetValue variable 1 (1)


** Message: GetValue variable 2 (2)

operapluginwrapper: Destructing pluginController
** Message: GetValue variable 1 (1)


** Message: GetValue variable 2 (2)

operapluginwrapper: Destructing pluginController
libnpp: Setting startup timeout=45
libnpp: Setting response timeout=20
libnpp: Setting search path=/usr/lib/opera/plugins:/usr/lib/mozilla/
plugins
libnpp: Setting motifwrapper path=/usr/lib/opera/plugins/
operapluginwrapper
libnpp: Setting socket watcher=0x882f060/0x882ee40
libnpp: Setting timer func=0x882cd30
libnpp: Setting BroadcastWindowAdded func=0x826cb10
libnpp: Setting BroadcastWindowRemoved func=0x826cb00
libnpp: NP_Initialize
libnpp: NPP_New (npp, instance=0x91c0c0c, pluginType=video/quicktime:/
usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so)
libnpp: Setting env var before exec: 'LD_PRELOAD='
libnpp: execing operapluginwrapper (/usr/lib/opera/plugins/
operapluginwrapper)
operapluginwrapper: motif init
operapluginwrapper: sW: 0x8062448, w(sW): 4200001
operapluginwrapper: trying to open /usr/lib/mozilla/plugins/libtotem-
narrowspace-plugin.so


** Message: GetValue variable 2 (2)
** Message: GetValue variable 2 (2)

** Message: NP_Initialize
operapluginwrapper: NPN_GetValue (14)
operapluginwrapper: NPN_GetValue with unknown variable: 14
NP_Init failed (8)
operapluginwrapper: Segmentation fault!!!


Peter

Eirik Byrkjeflot Anonsen

unread,
Aug 21, 2007, 7:54:40 AM8/21/07
to
"psaf...@googlemail.com" <psaf...@googlemail.com> writes:

It asks for NPNVSupportsXEmbedBool, which we probably don't support in
this version (I believe we have added some support for it since then,
although it is likely that the plug-in is using it wrong...)

I'm pretty sure the current unix-plug-in-master has done some
experiments around similar problems. We have some ideas how to solve
this, but I don't know how far the implementation has come.

> NP_Init failed (8)

Well, at least the plug-in has the good sense to give up in this case.

> operapluginwrapper: Segmentation fault!!!

Although crashing is distinctly unsociable of it.

I would guess that the plug-in is specifically written to work with
firefox, and makes unreasonable assumptions about the browser it is
running in.

eirik

psaf...@googlemail.com

unread,
Aug 21, 2007, 8:09:26 AM8/21/07
to
Well, I guess I'm stuck with Firefox for now. Thanks for your help
anyway.

Should I register this problem with the Opera developers in some way?

Peter

Eirik Byrkjeflot Anonsen

unread,
Aug 21, 2007, 9:11:04 AM8/21/07
to
"psaf...@googlemail.com" <psaf...@googlemail.com> writes:


I guess it doesn't hurt to file a bug report (https://bugs.opera.com/wizard/).

eirik

Alan Hoyle

unread,
Aug 23, 2007, 2:08:00 PM8/23/07
to

I get some similar "grey boxes" appearing from my plugins on Ubuntu 7.04.

Often with the Flash plugin: it'll run for a while, but then I'll come
back and find the grey box.

I haven't bothered debugging anything yet though.

-alan


--
Alan Hoyle - al...@unc.edu - http://www.alanhoyle.com/
"I don't want the world, I just want your half." -TMBG
Get Horizontal, Play Ultimate.

Robt. W. Fletcher Jr

unread,
Aug 23, 2007, 5:04:00 PM8/23/07
to
"psaf...@googlemail.com" <psaf...@googlemail.com> writes:

You'll probably have better success with

http://dekorte.homeip.net/download/gecko-mediaplayer/

and

http://dekorte.homeip.net/download/gnome-mplayer/


These packages play .qt videos (but HD videos) at
www.apple.com/trailers. Specifically this link
http://www.apple.com/trailers/wb/michaelclayton/trailer1/ plays on my
system.

--
-rwf

Balaam's Miracle

unread,
Aug 25, 2007, 9:15:25 AM8/25/07
to
On Tue, 21 Aug 2007 12:47:56 +0200, psaf...@googlemail.com
<psaf...@googlemail.com> wrote:

> X Error: BadDevice, invalid or uninitialized input device 169
> Major opcode: 145
> Minor opcode: 3
> Resource id: 0x0
> Failed to open device
> X Error: BadDevice, invalid or uninitialized input device 169
> Major opcode: 145
> Minor opcode: 3
> Resource id: 0x0
> Failed to open device

If i'm not mistaking, this is a "problem" with xorg.conf. By default, a
bunch of wacom-related stuff is added. As long as you don't have any wacom
hardware, you can safely delete the wacom-related entries from your
xorg.conf.
The parts that i'm talking about are the following:

Section "InputDevice"
Identifier "stylus"
Driver "wacom"
Option "Device" "/dev/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4"
EndSection

Section "InputDevice"
Identifier "eraser"
Driver "wacom"
Option "Device" "/dev/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4"
EndSection

Section "InputDevice"
Identifier "cursor"
Driver "wacom"
Option "Device" "/dev/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4"
EndSection

Do not forget to remove the entries for "stylus", "cursor" and "eraser"
from the "ServerLayout" section.

If you do not feel comfortable removing it from you xorg.conf, then you
can simply comment them out by adding a hash (#) at the beginning of those
lines.

I hope this helps, or at least a little.
One thing though. If you ever upgrade your X.org, the wacom entries will
be put back...
--
Balaam's Miracle

Alan Hoyle

unread,
Sep 6, 2007, 1:59:55 PM9/6/07
to
On Thu, 23 Aug 2007 14:08:00, Alan Hoyle wrote:
> On Tue, 21 Aug 2007 05:26:32, psaf...@googlemail.com wrote:
>> I'm trying to install video plugins (Quicktime, wmv etc) on Opera for
>> Ubuntu. The opera plugins page seems to see a variety of plugins for
>> these media types, but all I get are the grey boxes. Videos work fine
>> on Firefox. I guess I need to enable it in some way. Any ideas?

> I get some similar "grey boxes" appearing from my plugins on Ubuntu 7.04.

> Often with the Flash plugin: it'll run for a while, but then I'll come
> back and find the grey box.

> I haven't bothered debugging anything yet though.

Here's the debugging output from visiting

http://finance.google.com/finance?client=ob&q=AAPL

(process:22096): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function

(process:22096): Gtk-CRITICAL **: gtk_clipboard_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Adobe FlashPlayer: gtk_clipboard_get(GDK_SELECTION_PRIMARY); failed. Trying to call gtk_init(0,0);
opera: Plug-in 22096 is not responding. It will be closed.


opera: Define environment variable OPERA_KEEP_BLOCKED_PLUGIN to keep blocked plug-ins.

(process:22118): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function

(process:22118): Gtk-CRITICAL **: gtk_clipboard_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Adobe FlashPlayer: gtk_clipboard_get(GDK_SELECTION_PRIMARY); failed. Trying to call gtk_init(0,0);

Eirik Byrkjeflot Anonsen

unread,
Sep 7, 2007, 3:15:12 AM9/7/07
to
Alan Hoyle <al...@unc.edu> writes:


We've been working quite a bit with trying to get flash to work again,
now that adobe have decided there are only two browsers in the world.
On the good side, we're hoping that this will make several other
"mozilla-only" plug-ins (e.g. mplayer) work as well. I don't know how
much of this is completed in the current 9.50 alpha, though.

eirik

Reply all
Reply to author
Forward
0 new messages