I can confirm this problem. After some time, there are just white boyes instead
of the flash video objects. The time it occurs seems not reproducable to me.
Neither it seems to be a certain time, nor a certain number of played flash
videos nor a certain website/video.
Restarting firefox helps.
I am getting the occasional empty white box as well. Usually restarting
firefox fixes it temporarily. But as Iyeru mentioned, there has to be an
easier way. Hopefully this will get patched soon if we can narrow down
the problem (firefox, pulse, gstreamer, flash-nonfree, 64-bit emulation,
etc.).
Ki
the white flash object issue is NOT a pulseaudio issue, it happens with
esound as well. I'm currently running Jaunty 9.04
it happens on homestarrunner.com too. There are no reproduction steps,
you just have to wait for it to become white.
Closing Firefox then re-opening firefox fixes the white bo
This doesn't work for me anymore, but I use PulseAudio from PPA, do I
think the bug is different. I switch to flash 64bits from adobe labs
witch works better than the 32bits release for me.
--
[jaunty/amd64] flash plugin no longer has any sound
https://bugs.launchpad.net/bugs/314739
You received
This bug was fixed in the package ia32-libs - 2.7ubuntu3
---
ia32-libs (2.7ubuntu3) jaunty; urgency=low
* fetch-and-build:
- add libgdbm3, needed as a dependency of libpulse. LP: #314739.
- drop libxcb-xlib0, which is now obsolete.
- replace libpulsecore8 with libpulsec
Steve, yes, you're right of course. Thanks for following up!
--
[jaunty/amd64] flash plugin no longer has any sound
https://bugs.launchpad.net/bugs/314739
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Changed in: ia32-libs (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
Status: Triaged => In Progress
Target: None => jaunty-alpha-4
--
[jaunty/amd64] flash plugin no longer has any sound
https://bugs.launchpad.net/bugs/314739
You received this bug notification bec
$ ldd -d -r /usr/lib32/libpulse.so.0
linux-gate.so.1 => (0xf7fab000)
libSM.so.6 => /usr/lib32/libSM.so.6 (0xf7f2b000)
libICE.so.6 => /usr/lib32/libICE.so.6 (0xf7f13000)
libX11.so.6 => /usr/lib32/libX11.so.6 (0xf7e23000)
libcap.so.1 => /lib32/libcap.so.1 (0xf
** Changed in: pulseaudio (Ubuntu)
Target: jaunty-alpha-4 => None
--
[jaunty/amd64] flash plugin no longer has any sound
https://bugs.launchpad.net/bugs/314739
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
At this point, getting bi-arch pulseaudio libraries is going to be a lot
of work. In order to prevent pulseaudio libraries being linked against
libraries that aren't needed, a substantial rewrite of autoconf/automake
and possibly m4 code would be needed for the pulseaudio package. Even
then, the pu
flashplugin-nonfree downloads only the 32-bit from archive.canonical.com
in the partner repository. The 64-bit is alpha (thus non-final).
Bogdan Butnaru wrote:
>I'm not sure I understand what you mean by distributing non-final
>versions via partner; isn't the Flash plugin downloaded from Adobe a
I'm not sure I understand what you mean by distributing non-final
versions via partner; isn't the Flash plugin downloaded from Adobe at
install time? And anyway, is only the 64-bit version in beta?
--
[jaunty/amd64] flash plugin no longer has any sound
https://bugs.launchpad.net/bugs/314739
You r
Bogdan, nspluginwrapper is used to isolate the (historically crash-
happy) Flash instances. We are not permitted to distribute non-final
versions of the plugin via the partner repository, which is the current
download source regardless of arch.
I agree that having native versions provides a better
Steve, you're missing the fact that the upload of Flash 10 to jaunty
(10.0.15.3ubuntu1) using native 64-bit did not, in fact, depend on
nspluginwrapper for amd64. Native 64-bit plugin bypasses ia32-libs and
avoids the symptom.
Currently, installing flashplugin-nonfree on amd64 installs the wrong
v
I have another question: why exactly is flashplugin-nonfree using
ndiswrapper on 64bit? I use the 64-bit release of Flash directly from
Adobe, installed manually, and it work perfectly with Pulseaudio without
ndiswrapper.
I have had zero crashes or sound problems with it ever since I removed
the c
This analysis makes no sense; flashplugin-nonfree on amd64 has *always*
used ia32-libs, and it's orthogonal whether it uses it on i386 given
that this bug report is against amd64. Furthermore, the ia32-libs
package in both intrepid and jaunty include all of the pulseaudio libs
and plugins. So wha
** Changed in: alsa-plugins (Ubuntu)
Importance: Undecided => High
** Changed in: ia32-libs (Ubuntu)
Importance: Undecided => High
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => High
** Changed in: pulseaudio (Ubuntu)
Importance: High => Undecided
Status: Confirme
Very quickly, I'll summarise what I told Alexander and Luke some time
ago:
The most recent upload to jaunty of flashplugin-nonfree (to use
nspluginwrapper for both i386 and amd64) has one important regression-
related ramification for amd64: nspluginwrapper depends on ia32-libs,
which currently co
** Changed in: flashplugin-nonfree (Ubuntu)
Importance: Undecided => High
Status: New => Confirmed
** Also affects: alsa-plugins (Ubuntu)
Importance: Undecided
Status: New
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: flashplu
By the way, I've just installed
http://download.macromedia.com/pub/labs/flashplayer10/libflashplayer-10.0.d21.1.linux-x86_64.so.tar.gz
manually and it works perfectly. It appears as "ALSA plug-in [firefox]"
in pavucontrol.
--
[jaunty/amd64] flash plugin no longer has any sound
https://bugs.launch
20 matches
Mail list logo
