Flash player initially works then disappears after a while

Bug #295926 reported by Chris Latham
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: seamonkey

Upgrading from Hardy 8.04 to Intrepid 8.10 (x86-64) has fixed the problem with npviewer causing Seamonkey to hang (it would eventually recover if left for a few minutes). However, now the flash player initially works for a while, then disappears so that the page element containing a flash entity is a blank space. Restarting Seamonkey restores flash until it fails again after a while. This bug is very irritating. Seamonkey version details follow.

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.8.1.17) Gecko/20080829 SeaMonkey/1.1.12 (Ubuntu-1.1.12+nobinonly-0ubuntu1)

When run from a terminal window, many errors are generated, relating to npviewer.

% seamonkey
 *** NSPlugin Viewer *** WARNING: unhandled variable 17 in NPN_GetValue()

(npviewer.bin:1742): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed
*** NSPlugin Viewer *** WARNING: unhandled variable 17 in NPN_GetValue()

(npviewer.bin:1762): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed
*** NSPlugin Viewer *** WARNING: unhandled variable 17 in NPN_GetValue()
*** NSPlugin Viewer *** WARNING: unhandled variable 17 in NPN_GetValue()

(npviewer.bin:2078): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed
[....]

These errors repeat many times.

Reinstalling seamonkey and nspluginwrapper does not fix the problem.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: ath_hal fglrx
Package: seamonkey 1.1.12+nobinonly-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/tcsh
SourcePackage: seamonkey
Uname: Linux 2.6.27-7-generic x86_64

Tags: apport-bug
Revision history for this message
Chris Latham (latham) wrote :
Revision history for this message
markor (markoresko) wrote :

I use Seamonkey 1.1.12 on Xubuntu 8.04.1 64-bit and Flash windows
are continuing to play even when I close its`t tabs.
I installed Flash from http://ubuntuforums.org/showthread.php?t=772490,
using `Hardy Heron`instructions.
Should I stick to Flash available in Ubuntu repositories?

Revision history for this message
Chris Latham (latham) wrote :

Sorry for the delay responding: I have been away on business. The answer to your (makor's) question "Should I stick to Flash available in Ubuntu repositories?" is, I don't know.

The bug is still present as of 2.11.2008, so none of the updates since my first posting have fixed it yet.

Revision history for this message
Laurent Dinclaux (dreadlox) wrote :

I have that bug _every day_ on Firefox3 using Intrepid 64 Desktop updated.

Changed in firefox-3.0:
status: New → Confirmed
Revision history for this message
markor (markoresko) wrote :

Curiously, I have just small with Firefox3 and flash installed from alternate source on Hardy/8.04.1 64-bit.
Sometimes Flash on new tab won`t start until I close tab in FF3 paste link to new opened tab and load it.
Laurent Dinclaux: Try to apply Flash for FF3 from link I posted.

But I think this bug is about Seamonkey browser/suite with flash.

Revision history for this message
Chris Latham (latham) wrote :

I have now observed that this bug occurs on a freshly installed Intrepid 8.10 32-bit system (plus necessary stuff to play flash) using the Firefox browser. However, it occurs much less often than on the 64-bit system. So, perhaps the bug is in the flash plugin rather than the browser.

Revision history for this message
patman0623 (patman0623) wrote :

New to bug reporting... please be patient here.

I noticed the same error on my machine:
Ubuntu 8.04 Hardy Heron
x86_64
Firefox 3.0.5
nspluginwrapper with 32bit Flashplayer (the native 64 bit version from Adobe was just awful)

It rarely seems to manifest, but it can be duplicated by going to http://blogtv.com and observing any stream (normally on the front page). I surmise is the fault of nspluginwrapper.

*** NSPlugin Viewer *** WARNING: unhandled variable 17 in NPN_GetValue() (error desplayed twice)

Then, upon navigating away from the page:
(npviewer.bin:2390): Gtk-CRITICAL **: gtk_style_detach: assertion
`style->attach_count > 0' failed (error displayed 6 times)
(npviewer.bin:2390): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed

Not surprisingly, the browser crashes when navigating away (detach, destroy fails).

I personally consider this to be a rather important issue, as it affects live streams, and I am unable to browse the site, a favorite of mine, at all.

The error does not duplicate with anything at http://stickam.com

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report didn't yield the required information. Could you please add more information for it by following the instructions at https://wiki.ubuntu.com/MozillaTeam/Bugs . Thanks in advance.

Changed in firefox-3.0:
status: Confirmed → Incomplete
Revision history for this message
patman0623 (patman0623) wrote :

Unfortunately, in the meantime, I have uninstalled and reinstalled Ubuntu.

The two major differences are:
1) I am not running on wubi (which I don't suspect is the issue)
2) I am no longer running nspluginwrapper; I am directly running 64-bit Flash. I am 99% sure that is the difference. I believe the bug was in nspluginwrapper.

Revision history for this message
rcarrozza42 (rcarrozza42) wrote :

You can use the Seamonkey browser and flash keeps working.

I can temporarily fix the problem in Firefox this way.

In Firefox go to

edit/preferences/ shockwaveflash/ press down arrow and select / use other

then select /usr/lib/flashplugin-installer/libflashplayer.so

close

then restart firefox

May the Flash will keep working this day until a permanent fix is created.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in firefox-3.0 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.