Not working

[Manu311]

Hi,

this is not working on my pc. Neither in Firefox nor in Google Chrome, on not a single flash-video I found.
I've tested this before it was released on git (didn't worked back then neither) but now I can report it.
The script detects the correct display size and founds a lot of matches when I start it with the browsers - no errors found (in cerr or cout).
I'm using the following software:
System: Gentoo 64 bit
Chrome: 21.0.1161.0_alpha (didn't worked back then when I had stable and beta versions)
Firefox: 10.0.5

I'm using nvidia twinview, NO xinerama at all (since it's buggy, needs a lot of resources, etc).

Btw you should either remove the executable from git, or add the "make clean" command to the readme, since "make" will not recompile the executable if it's still there.

[ali1234]

Firstly, systems without Xinerama are not supported.

Secondly, there is no binary in the repo, and never has been.

[Manu311]

First: you should mention that somewhere
second: point taken, but a simple make without a make clean doesn't work at least on my pc - so something has to be there.
3rd: thanks for your reply.
4th: could you make it work without xinerama? Xinerama destroys my fps in every game, ruins a lot of programs if used with twinview and I simply don't want to use it. And I hate to downloda every videos via plugins in my browsers since there's not realy any other fix. (I'm thinking about running a windows version of some browser inside a wine desktop, since I think that will work, but seriously?)

[ali1234]

If you tell me how to set up a system which has twinview but not xinerama I will take a look at it. But I can't guarantee I will be able to fix it.

make works fine for me and I use it all the time when testing without doing make clean.

[ali1234]

Actually, your xorg.conf, Xorg.0.log and output from make test should be enough for me to figure out what is happening.

[Manu311]

I'm at work, while my pc is at home. So I'll give you those informations later.
I simply let nvidia-settings create my xorg.conf (thought I may change something, but it appears in every config I've tried).
Xinerama usually is for more then one xserver since twinview only uses one, it's not nessessary. I've installed the lib though (since you linked against libXinerama).
The output from make test was correct (I can't recitate it 100% accurate) it told me:
without hack: 2560x1024
with hack: 1280x1024
which is correct, but flash just did ignore and kept rendering at 2560 width.

[ali1234]

does the flash window cover more than one monitor?

also do you use 64 bit flash plugin? do you use ndiswrapper?

[Manu311]

no. I'm running chrome/firefox (same with both) maximized on one screen (1280x1024+0+0) click fullscreen on a flash movie and it renders on 2560x1024 but only the left half of it is visible. I've tried to use windowed mode in the browsers and resize them over both monitors - but the fullscreen of flash keeps maximizing on screen 1 the movie is only half visible.

I'm using the 64 bit plugins.

[ali1234]

ok. in that case, and given that the make test correctly identified your screen resolution, means you have a working xinerama setup.

nvidia twinview provides a xinerama-like api even if real Xorg xinerama is disabled. this is for compatability with window managers, so that a window can be maximized on a single display even there is really only one X11 display.

this means the problem is something to do with the way you are applying the library.

i have seen problems with chrome before, where chrome installs a shell-script in /usr/bin/chrome. the script messes with the environment. you need to check it.

for firefox, you need to make sure that you are not using nspluginwrapper. if you preload the 64 bit library with 64 bit firefox but are using ndiswrapper with either 64 bit or 32 bit flash then it will not work. in this case you have to add the preload to the nspluginwrapper environment, which is done in the nsplayer script. but you still have to compile it for the right architecture.

[Manu311]

I'm using gentoo, so if I tell my "package manager" to compile the 32 bit it adds the depency: "ndiswrapper" which is NOT installed on my system. So I'm definitly not using ndiswrapper (at least in firefox, as I said chrome is a binary which includes the flash player, it MAY use ndiswrapper internally).
I've tried different approaches to apply the hack, I've edited the chrome file. Recently I focused on firefox, since I thought that it may easier to apply it there (and I know there's no ndiswrapper) - when I preload your hack and start firefox it prints a lot lines where it has found and replaced the resolution, so I guess it applied correctly.

[ali1234]

sorry, ndiswrapper is the wrong thing. that's for windows network card drivers on linux. you actually need to check for nspluginwrapper. i always get them mixed up because they have similar names and similar purpose.

chrome never uses nspluginwrapper at all.

you will still see messages from the wrapper even if flash isn't using it - because firefox itself calls the same wrapped functions. you should see the library "loaded" message several times because each child process of firefox (of which plugins are one possible type) will inherit the environment variable and thus load the library again.

i'm assuming you changed Makefile to BITS=64?

[Manu311]

I did change the makefile.
I think I've searched for nspluginwrapper, but I may have mixed it up as well, I'll check this evening.
Anyways I've got options in flashplugign "32bit" and "64bit" and I know I've NOT set 32bit but I've set 64bit, so I should not use nspluginwrapper for this.
But if chrome doesn't use it anyways, why doesn't it work in chrome neither? I think it's something else.
What are the differences in our systems? Have you tried to compile a firefox by yourself? Under a 64bit system? Maybe we could reproduce this on your side. If it's of any help, I know how to program, including C++ (and a bit C), I've just not written any hacks (thought I've used a dynamic library as a plugin).

[ali1234]

I use Ubuntu 64 bit. I have not tried to compile firefox from source, but if I did I would use dpkg-buildpackage and get a result identical to the binary that I have installed anyway. I also use 64 bit flash now, but i developed the plugin when using 32 bit flash with nspluginwrapper, as there was no 64 bit flash back then. I also have reports of it working with chrome - at least on older versions.

You can check the architecture of the flashplugin.so (or any file) by "file flashplugin.so" - it will probably be in /usr/lib/firefox/plugins or /usr/lib/mozilla/plugins or some similar directory. perhaps you need to follow a chain of symlinks to find the real binary.

[Manu311]

I'll check that when I'm at home, I already found the correct file on my (single monitor 32bit gentoo) notebook: "/opt/Adobe/flash-player/flash-plugin/libflashplayer.so" I guess there should be "ELF 64-bit" on my desktop pc.
To give you the time when I'll be home: 6 pm GMT (more or less)

[Manu311]

/opt/Adobe/flash-player/flash-plugin/libflashplayer.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped
Xorg.0.log: http://pastebin.com/raw.php?i=RB8UVCSb
xorg.conf: http://pastebin.com/7KLxZsfj

I've just recognized, there's an error (without your hack as well) when pepper (chrome-flashplugin) is trying to fullscreen some video:
[25:25:3258100325:ERROR:render_widget_fullscreen_pepper.cc(187)] Not implemented reached in virtual void::PepperWidget::setFocus(bool)
It doesn't sound like it's in any relation but I wanted to mention that.

[ali1234]

I think that is the problem with Chrome. It uses a different plugin API and looks like different code to go fullscreen. Still not sure why Firefox doesn't work though.