https://bugzilla.novell.com/show_bug.cgi?id=490733 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- QAContact|sndirsch@novell.com |qa@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=490733 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=490733#c1 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |robin.listas@telefonica.net --- Comment #1 from Stanislav Brabec 2009-03-31 11:12:19 MDT --- I see similar crashes, too. All of them I was able to debug were not crashes of npviewer, but a crash of Adobe Flash plugin running inside npviewer or firefox itself. Are you able to get a backtrace of crashed application? Example: ps ax | grep npviewer Then pick the process uid, run gdb, "attach {the process uid}", "continue", wait for crash, bt. You can also try a different flash version. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=490733 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=490733#c3 --- Comment #3 from Stanislav Brabec 2009-04-01 05:09:17 MDT --- As browser is a 64-bit application and Flash 32-bit plugin, things work in this way: - There is a 64-bit browser plugin npwrapper.libflashplayer.so. - There is an invisible 32-bit browser npviewer.bin running 32-bit Flash plugin. - npwrapper.libflashplayer.so itself just sends all actions to npviewer.bin, and it calls the the action in the plugin and any replies are translated in the same way back to the browser. Flash itself crashes pretty often. With a native Firefox browser, it crashes the browser. With the nspluginwrapper, it crashes just the npviewer.bin and Firefox survives (without Flash). Starting with openSUSE 11.1, nspluginwrapper detects viewer crashes and is capable to restart it. To identify, whether the crash is caused by nsplugiwrapper or the plugin, you need a backtrace. If it is a crash in the proprietary plugins, I cannot help. If it is a crash of nspluginwrapper itself, it can be debugged and fixed. I don't know, how it Flashblock works and whether it can be the cause of the crash. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=490733 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=490733#c5 --- Comment #5 from Carlos Robinson 2009-04-01 05:51:29 MDT --- (In reply to comment #4)

I might disable the plugin for a while and see what happens - as it needs a firefox restart I'll have to close this comment first.

Well, with the blocker disabled I don't see segfaults and no crashes, and there is an "npviewer" process running. I think we have to assume it is some effect of the flashblocker. No problem, then :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=490733 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=490733#c7 Carlos Robinson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|robin.listas@telefonica.net | --- Comment #7 from Carlos Robinson 2009-04-01 06:45:52 MDT --- (In reply to comment #6)

On 32-bit system, you should not have nspluginwrapper installed. At least not on openSUSE 11.0. Wrapping native plugins is not supported there. Did you install nspluginwrapper manually?

Nop, all automatic - at least as far as I remember. I wouldn't know how to install it myself, unless YaST does it. This system has been upgraded all the way from SuSE 7.3 or 8.1 and up, since Dec 2001. Perhaps it is a glitch of that, I have no idea. Interesting!

On openSUSE 11.1 it should work, but it was never tested.

Wrapping native plugins as a crash protection may be available in openSUSE 11.2.

Well, you see it works on 11.0 - don't ask me how or why, I have no idea. O:-) cer@nimrodel:~> which nspluginwrapper /usr/bin/nspluginwrapper cer@nimrodel:~> rpm -q -f /usr/bin/nspluginwrapper nspluginwrapper-0.9.91.5.99.20071225-22.2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=490733 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=490733#c9 --- Comment #9 from Carlos Robinson 2009-04-01 09:13:56 MDT --- (In reply to comment #8)

...

Nop, all automatic - at least as far as I remember. I wouldn't know how to install it myself, unless YaST does it.

Could you provide relevant y2logs (i. e. these that contain string nspluginwrapper) to find, why nspluginwrapper was installed.

I'll investigate a bit, I'm curious. I'll have to dig out some backups. I'll come back later.

...

This system has been upgraded all the way from SuSE 7.3 or 8.1 and up, since Dec 2001. Perhaps it is a glitch of that, I have no idea.

That's an interesting system. It would be nice useful to find orphan files and directories (relicts of ancient system) there.

Sure! Sometimes I have some "fun" having to clear some configs or empty dirs. It even happens that a directory is not empty, there is a config there, but obsolete and not used... and me wondering why the changes did not take (hybernation method, for instance). But I also used to have, on another partition, a clean install of the current distro, or nowdays, factory, which I use to compare with the main one to find out those things. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.