Ubuntu PulseAudio Problems
PulseAudio depends on ALSA
Well, after months of successful Hardy, my audio just died! Silence!
Panic stricken, I booted into XP and sighed in relief as the all-too-familiar-and-hated windows sound came from my 2 year old Dell 6400 laptop.
Ok, so confirmed it was not hardware related, I booted back to Ubuntu 8.04 and the silence. Time to Google!!
I found various interesting things including the paprefs and pavucontrol packages for configuring and diagnosing specific problems, but the final solution came from PulseAudio themselves: Check the alsamixer levels! Ok!
So I found the PCM levels in the ALSAMixer at 0, raised them and we're done!
References:
Panic stricken, I booted into XP and sighed in relief as the all-too-familiar-and-hated windows sound came from my 2 year old Dell 6400 laptop.
Ok, so confirmed it was not hardware related, I booted back to Ubuntu 8.04 and the silence. Time to Google!!
I found various interesting things including the paprefs and pavucontrol packages for configuring and diagnosing specific problems, but the final solution came from PulseAudio themselves: Check the alsamixer levels! Ok!
So I found the PCM levels in the ALSAMixer at 0, raised them and we're done!
References:
- Magarto Blog: http://magarto.com/blog/archivo/2008/05/18/howto-manejar-el-sonido-con-pulseaudio/
- PulseAudio Ticket: http://www.pulseaudio.org/ticket/379
GWT in Eclipse
Cypal Studio Tips & Tricks
While using Cypal Studio for GWT programming is very intuitive, I have come across various bits and pieces that have taken me a while to sort out, specially with older versions, and that I'll list here for convenience, along with a brief description.
References:
Module Configuration
The module configuration is via a xml and eclipse likes to have the corresponding DTD, so here is the 1.5 version (just cut'n'paste):<!DOCTYPE document SYSTEM "http://google-web-toolkit.googlecode.com/svn/releases/1.5/distro-source/core/src/gwt-module.dtd">
Running in Hosted -NoServer mode
To setup a hosted tested environment that uses your favourite tomcat server you must complete the following steps:- Setup a hosted run configuration but deactivate the Use Embedded Tomcat Server and the Use default URL for module while setting this last to
http://localhost:8080/MyModuleName
according to wherever your server is configured & the module you are trying to run. - Modify your project so that it can find the module's web page by adding a
<welcome_file>MyModuleName.html</welcome-file>
to your web.xml in the WEB-INF folder.
References: