19 November 2008

Ubuntu hardy: Fan got crazy because of a bug in NetworkManager

Found the soluton in the ubuntu forum:

Copy-paste from the forum:

Last update:
If you update hal to last version (0.5.11~rc2-1ubuntu2) you shouldn't have this issue anymore, and thus you could update network-manager again.

To check your installed version:

apt-cache madison hal

hal (0.5.11~rc2-1ubuntu2) hardy; urgency=low
* debian/rules: build using --with-deprecated-keys, since we don't want to
break packages that were assuming this worked right up through beta.
LP: #204768.

Old thread follows:

I've read some posts here regarding wireless issues since last update.

I had issues too, and noticed that NetworkManager was eating 100% CPU and avoiding wireless to work.

So this is what I did:
* Connect to the internet in other machine and download the previous version of network-manager:
or directly:http://launchpadlibrarian.net/124982...untu1_i386.deb

* Downgrade network-manager with:

sudo dpkg -i network-manager-gnome_0.6.6-0ubuntu1_i386.deb

It will automaticly stop and restart NetworkAdmin.
After that just configure again your connection.

EDIT:Bug reports follow (as some users reported):
#204931 - NetworkManager 100% cpu usage on WiFi

EDIT2: If you want to keep aptitude from installing the broken package:

sudo aptitude hold network-manager

When you want to release it again:

sudo aptitude unhold network-manager

To check its version after an update:

apt-cache madison network-manager

17 November 2008

Invalid Google Maps API key

Today, it took me 1 hour to find the reason why my google map was not showing in production env whereas everything was fine in development env. Needless to say I have a "view" spec + a selenium acceptance test which pass.

Google Maps API has only one error message for this kind of problem: "The Google Maps API key used on this web site was registered for a different web site. You can generate a new key for this web site at http://code.google.com/apis/maps/. "

Therefore, I started looking at the wrong place and changed the key set up for the "production" environment in the RAILS_ROOT + '/config/gmaps_api_key.yml many times without any success ...

Finally, I ended up looking at the source of the page and it appeared that the key parameter was empty!

  <script src="http://maps.google.com/maps?file=api&v=2.x&key=&hl=" type="text/javascript">
View Jean-Michel Garnier"s profile on LinkedIn
  • Services
  • Contact
  • Recommend Me

    Speaker at:
    Amsterdam 2008
    2007 & 2008