Last night, I updated to Firefox 6.0.2 and after it was finished installing, lo and behold the middle mouse button no longer opened links in new tabs. Using a middle click (Command+click on the Mac) on a link normally opens the destination in a background tab, but it just stopped working. However, I could still use the context menu (right-click on PC, Control+click on Mac) and select “Open Link in New Tab”.
Check your extensions. Are you using Greasemonkey 0.9.10? Are you also using Tab Mix Plus 0.3.8.6? As of this writing, they’re both the latest versions at the Firefox add-ons site. Nevertheless, there’s an incompatibility that causes the middle-click to fail.
To remedy the problem, download and install the latest version of Greasemonkey 0.9.11 directly at https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/versions/0.9.11 or if you’d rather wait for Mozilla to approve the version, it should eventually show up as an update in Firefox.
When using PuTTY to SSH to a Linux server and edit files, I’ve encountered on several occasions where navigating in vim using the cursor (arrow) keys on the keyboard while in insert mode results in control characters and/or new lines being inserted. Here are a couple of ways to rectify the situation.
- Check if the vim command is pointing to the full version of vim or vim tiny.
$ which vim
Some Linux distros link vim to vim tiny. If it’s pointing to the normal vim, skip to step 4, below.
- If you’re using vim tiny and want to continue to do so, then edit /etc/vim/vimrc.tiny and add the command set nocompatible to turn off compatibility mode.
- If you’d rather have the normal vim editor, then install it. After installation, confirm that the vim command points to the correct version and continue with step 4, below.
- Check that /etc/vim/vimrc (or ~/.vimrc) contains the command, set no compatible, to turn off compatibility mode.
That should do it. If you still have trouble, be sure that your terminal is set correctly in PuTTY and on the remote system.
Have another way to fix this issue? Post it in the comments.
For some reason, the Banshee media player on my Ubuntu installation stopped responding and, as a result, its database was damaged. The result? Whenever I tried to play a video podcast, Banshee would attempt to start playing and then crash.
Rebuilding Banshee’s database to fix the corruption is pretty easy.
- If you don’t already have sqlite3 installed, get it via the following command:
sudo apt-get install sqlite3
- Go to Bashee’s config directory:
- Dump out the database:
sqlite3 banshee.db ".dump" > dump
- Make a backup of the original database file, in case the repair doesn’t work properly:
mv banshee.db banshee.db.backup
- Reload the dumped data into a new database file:
cat dump | sqlite3 banshee.db
Worked great for me. Thanks to boombox1387 for posting the info. I ended up putting these commands into a shell script called BansheeFix.sh, so it’ll be even easier to take care of next time.
Is your Banshee crashing for a different reason? Got a fix for it? Post it in the comments.
Are you experiencing an intermittent popping sound from your speakers when nothing is playing? I encountered it after upgrading a PC with an HDA Intel audio controller to Xubuntu 9.10 Karmic Koala. It occurs 10 seconds after a sound stops playing because that’s when the audio chip is turned off to save power.
To prevent the popping noise, you just have to disable the power saving mode.
- With your favorite editor, open /etc/modprobe.d/alsa-base.conf as root (Important: Run the editor using sudo or gksudo to give it root permission. You can’t save the file otherwise.)
- Locate the line that reads, “# Power down HDA controllers after 10 idle seconds”
- Immediately following that comment is the offending option:
options snd-hda-intel power_save=10 power_save_controller=N
- Insert a hash # character at the very beginning of the option line to turn it into a comment. It should look like the following:
#options snd-hda-intel power_save=10 power_save_controller=N
- Save the file and restart Ubuntu
If you have a different sound controller and are experiencing this noise, look in the file for a similar-looking option (e.g., options snd-hda-something power_save…) and comment it out. Share your experience in the comments.
Today, my Pidgin IM client started giving the error, “Received unexpected response from http://api.oscar.aol.com/aim/startOSCARSession”, when connecting to the AOL Instant Messenger (AIM) server. Apparently, it can also happen when connecting to ICQ. Fortuantely, the fix/workaround on Windows and Linux is really easy.
- Go to Accounts
- Modify the AIM or ICQ account
- On the Advanced tab, clear the checkbox labeled Use clientLogin
Are you using Adium? It may also have this issue on the Mac. If you’ve solved it, post the steps in a reply.
Update: Alternatively, in step 3, you can clear the checkbox labeled Use SSL