Bug 906561

Created attachment 614542 [details]
Installed Firefox Versions

Installed Firefox Versions

Created attachment 614543 [details]
Terminal output of gdb session

Output of gdb session in the start-terminal window

Interesting.
Why would Firefox/Seamonkey load a library from /usr/lib64/chromium/PepperFlash/?

Both are not supposed to use that but apparently it's loaded somehow
Program received signal SIGILL, Illegal instruction.
0x9fff6eb3 in ?? () from /usr/lib/chromium/PepperFlash/libpepflashplayer.so

This needs some investigation.

Did chromium-pepper-flash come from packman?

(In reply to Wolfgang Rosenauer from comment #3)
> Interesting.
> Why would Firefox/Seamonkey load a library from
> /usr/lib64/chromium/PepperFlash/?

The package "freshplayerplugin" (which the reporter apparently had installed) is a "wrapper" to allow Firefox to use the pepper-flash plugin:
http://software.opensuse.org/package/freshplayerplugin

Regarding the crash: Adobe's Flash-Player requires SSE2 support even on 32bit since version 11. I suppose the newer pepper-flash plugin requires the same, which leads to this crash.

That would make sense since SIGILL sounds pretty much like such a reason.
But then how to solve that. In that case it cannot be fixed at all but the packman packages should not be provided in the fist place for x86-32, right?

(In reply to Wolfgang Rosenauer from comment #5)
> But then how to solve that. In that case it cannot be fixed at all but the
> packman packages should not be provided in the fist place for x86-32, right?
Then flash-player should not be provided for 32bit in the standard non-oss repo either...

No, the problem is not a general one. Most 32bit CPUs do support SSE2, just some old ones don't (e.g. AMD's K7 generation which includes Athlon and Athlon XP).

Ok, still not solvable within Firefox.
Might be runtime detectable in freshplayerplugin if at all.

Please report there.

The first of the PC's with firefox and semaonkey problems
has an AMD Duron(tm) 800MHz cpu,
the second PC has a AMD Athlon XP 3000+ (axda3000kv4e) CPU.

Both systems run the browser without any problems with opensuse 13.1.
The crashes begun with opensuse 13.2.

Regards 
Egon

(In reply to Wolfgang Rosenauer from comment #7)
> Ok, still not solvable within Firefox.
> Might be runtime detectable in freshplayerplugin if at all.

At least freshplayerplugin should not crash the whole browser.
IIANM, in the case of the standard flash-player, only the plugin-container crashes, i.e. the flash content is not shown.

Still, I agree that this is not a Firefox bug, rather a bug/flaw in freshplayerplugin, which is not even included in the distribution.

Created attachment 614564 [details]
lspci output on of the 800 MHz PC

Output of the lspci -v 
command on the 800 MHz AMD Duron(tm) PC

(In reply to Egon Niessner from comment #8)
> The first of the PC's with firefox and semaonkey problems
> has an AMD Duron(tm) 800MHz cpu,
> the second PC has a AMD Athlon XP 3000+ (axda3000kv4e) CPU.

Right, those CPUs do not support SSE2.

> Both systems run the browser without any problems with opensuse 13.1.
> The crashes begun with opensuse 13.2.

But did you have freshplayerplugin and chromium-pepper-flash installed in 13.1?
It's definitely pepper-flash causing the crash.
As this is proprietary closed-source software, this cannot be fixed by openSUSE (nor Packman).
But I doubt that you had flash working on 13.1 at all (unless you manually installed the old Flashplayer 10).

And the browser runs fine when you uninstall both as you stated yourself.

As I said, freshplayerplugin shouldn't crash the whole browser, but again, you should report this to the developers of freshplayerplugin. (AFAIK this is still in an experimental stage though)

Hello,
in my old working 13.1 machines, 
freshplayerplugin and chromium-pepper-flash are not installed.

But it seems, that this packages are installed by an update
from 13.1 to 13.2 or a fresh install of 13.2 by default.

There should be a hint in the release notes, that this packages
should be removed on old 32 bit machines, if browser problems appears.

(In reply to Egon Niessner from comment #12)
> But it seems, that this packages are installed by an update
> from 13.1 to 13.2 or a fresh install of 13.2 by default.

Again, freshplayerplugin and chromium-pepper-flash are not even included in the distribution, as I wrote already.

They might have been installed as recommended packages though.
I noticed now that Packman does include freshplayerplugin since recently, which provides "flash-player" and might therefore be installed automatically by the default patterns instead of flash-player if you have the Packman repo on your system.
I'd suggest you report the problem to them then:
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

> There should be a hint in the release notes, that this packages
> should be removed on old 32 bit machines, if browser problems appears.

See above. freshplayerplugin is not part of the distribution. Neither the standard flash-player nor chromium-pepper-flash should cause a crash of the browser AFAIK, even on systems without SSE2 support (Flash will not work though, but that's the case since at least openSUSE 12.1 already, which was the first release containing flash-player 11).

Please check your browser settings - having out-of-process plugins is a good idea in any case. This may still be disabled - check dom.ipc.plugins.enabled (in about:config). Setting it to true spawns the plugins in a separate processes (plugin-container). Optionally you may fin-grain it a bit more with dom.ipc.plugins.enabled.<plugin_so_name> prefs (e.g. dom.ipc.plugins.enabled.libpepflashplayer.so should govern your plugin).

PS: I want to add, that I did not get freshplayer-plugin installed on neither of my 2 systems that I upgraded to 13.2 via "zypper dup", nor automatically via the standard update applet or "zypper up".

And even if I run "zypper dup" now with Packman active, it does not want to install freshplayerplugin.

So I don't really see a possible problem here.
Although, as mentioned, you might get freshplayerplugin installed instead if flash-player (recommended by the patterns), if the latter is not installed already, although this shouldn't happen either I think as it has a lower version (0.2.1 vs. 11.2.202.418).

Hello,
for your information...

When I installed opensuse13.2 (KDE)
I modified with yast the repository settings.

I added the community repositories,
set the priority of packman and libdvdcss to 75
(that it becomes higher than the other directories with priority 99 to get
better multimedia support)
and made an update.

After that, I installed the other wished software by selecting the
according patterns.

I think, in this way, chromium cames into my system.