There is an issue with Steam for Linux that seem to be persistent on machines with HDMI enabled displays or similar unused HD audio inputs.
Steam for Linux seems to use these controllers despite them being ignored by the system, which results in weirdly muted games while YouTube as well as any sound tests are loud and clear.
To fix this issue open sound settings and select analog controller or (for pulseaudio sound server) install pulseaudio volume control
sudo apt-get install pavucontrol
under “Output Devices” check if it tries to use the HD audio controller to output sound, go to “Configuration” and disable the HD audio controller profile so that analog audio will always be used.
Here we went through the Ubuntu 13.10 process, Ubuntu 14.04, though using the same Apache 2.4, again has a small thing that have to be done differently:
Config files in sites-available have a .conf (and not .config) extension
gksudo gedit /etc/apache2/sites-available/project.conf
As for the rest, previous Ubuntu 13.10 Tutorial can be used for newer Ubuntu as well.
Another cutting age (at least in terms of privacy) app lets users share files directly and anonymously via Tor network.
Further infos on wired.
Here is a new hacker made peace of software that would make Bitcoin transactions far less traceable (or more untraceable).
The whole process was described in this article, but there are few quirks to fix in newer Ubuntu (namely 13.10 / Apache 2.4).
- Every config file in sites-available has to have a .config extension now, so instead of
gksudo gedit /etc/apache2/sites-available/project
gksudo gedit /etc/apache2/sites-available/project.config
if upgrading fist add the extension to the /etc/apache2/sites-available/project config file, then delete /etc/apache2/sites-enabled/project and re-run “sudo a2ensite project” / restart apache.
- If your project root is located in your home directory you might get a persistent 403 / Forbidden error, that (weird as it is) has nothing to do with Linux permissions. To fix it add “Require all granted” directory directive. Here is how the new config file might look:
Allow from all
Require all granted
So here are updated instructions for Ubuntu 13.10+ (and maybe some older versions). Continue reading
A Media Development Investment Fund (MDIF) project, Outernet will use a network of small satellites to transmit selected Internet data to any Wi-Fi-enabled device anywhere in the world at no cost.
By leveraging datacasting technology over a low-cost satellite constellation, Outernet is able to bypass censorship, ensure privacy, and offer a universally-accessible information service at no cost to global citizens. It’s the modern version of shortwave radio, or BitTorrent from space.
Sounds like fun, let’s hope it works out.
Recently I’ve upgraded a Laravel 4 application from version 4.0.10 to 4.1.18. Despite Laravel’s website having a nice upgrade guide I did encounter few quirks that needed a little attention and some extra work.
So the very first thing to do, would be to follow the mentioned guide, hopefully you’ll end up with working new version of your application and wouldn’t need anything else (use “php artisan” command in your application folder to check out the current Laravel version).
Though I ended up with the following error each time I tried to run an artisan command (including simple “php artisan”):
PHP Fatal error: Class 'Illuminate\Foundation\Providers\ConsoleSupportServiceProvider' not found ...
And there were indeed no ConsoleSupportServiceProvider in my installation. Surely “composer.phar update” did not work as well as it tries to execute “php artisan …” commands and suggested “composer.phar update –no-scripts” worked, but didn’t fix anything.
After a bit of research I ended up with a kind of “clean install” solution, so if you have the same or similar issue you may try following: Continue reading