Ubuntu
flashplugin-nonfree package

  1. Bug #326609
  2. Comment #22

Comment 22 for bug 326609

Revision history for this message
Jamie Lokier (jamie-shareable) wrote :

I just did an upgrade from Intrepid to Jaunty and have the same problem.

I spotted this in the output from update-manager:

Setting up flashplugin-installer (10.0.22.87ubuntu2) ...
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Downloading...
--2009-04-18 21:05:57-- http://archive.canonical.com/pool/partner/a/adobe-flash
plugin/adobe-flashplugin_10.0.22.87.orig.tar.gz
Resolving archive.canonical.com... failed: Name or service not known.
wget: unable to resolve host address `archive.canonical.com'
download failed
The Flash plugin is NOT installed.

As others have reported, NetworkManager stopped working for a large part of the install and dropped my _wired_ ethernet connection. NM started working again towards the end, after "Setting up flashplugin-installer".

The NetworkManager problem isn't a flashplugin bug.

But flashplugin not being able to fix itself when the network comes back would be best fixed in flashplugin. After all, there might be other reasons why the network is down at that exact moment.

Some ideas:

   - Can it tell dpkg that setup failed and needs to be run again after everything else?

   - Can it use a trigger on the upgrade of NM, or a generic trigger on network change?

   - If fetching fails during upgrade, can it attempt to fetch the file the next time Firefox is started? This would be quite robust.

Also, earlier comments say that uninstalling without --purge then reinstallng does not fix it. --purge shouldn't be necessary, just to trigger fetching the file it needs which it hasn't installed yet.