Although you can’t easily edit or modify the characters that are stored, you can remove individual items in the form history with just a few keystrokes.

1. Go to the form that has the field with the auto-complete history entry that you want to delete
2. Type the first few characters of the value you want to remove. You’ll see the value appear in the drop down list below the form field as usual. In this example, I want to remove the misspelled entry, “knwoledge”.
   
3. Use the down-arrow key to highlight the history item to be deleted. Don’t click it with the mouse.
   
4. Press the Delete (Del) key, instead of Enter, and the item will be gone
   

Yea! No more garbage in your form auto-complete history.

This method is also useful for security and privacy purposes to selectively remove data, such as credit card, Social Security, bank account and other identification numbers, that you don’t want lying around in Firefox’s form history.

The next time you see a PDF form that shows a message such as,

“You cannot save data typed into this form. Please print your completed form if you would like a copy for your records.”

do the following:

1. Install a PDF printing tool such as the one included with the full Adobe Acrobat package or a free one such as PDFCreator.
2. Fill in the PDF form as you normally would
3. When you’re done with the form, print it
4. Rather than using your default printer, select the one from the PDF tool you installed in step #1

Voila! Now you’ll have a PDF of the filled-in form to save for your records.

1. Open a terminal window
2. Go to the X11 directory (cd /etc/X11)
3. Make a backup of the current xorg.conf file (e.g., sudo cp xorg.conf xorg.conf.backup)
4. Use your favorite editor to open xorg.conf (e.g., sudo vim xorg.conf)
5. In the section “Device”, add the following line:
       Option “UseEdid” “False”
6. The “Device” section should now look like the following:
       Section “Device”
           Identifier “Default Device”
           Driver “nvidia”
           Option “UseEdid” “False”
       EndSection
7. Save the xorg.conf file
8. Log off and restart the X server (from the login screen, click on Menu and select Restart X server)

That’s it. Now, when I log in, I’m able to see the screen and select a resolution using the nVidia X Server Settings tool.

Note: In the nVidia X Server Settings tool, if when you click the Save to X Configuration File button, you get an error message that it can’t save, run nvidia-settings from a terminal window using gksudo (for Gnome, e.g., gksudo nvidia-settings) or kdesudo (for KDE, e.g., kdesudo nvidia-settings). If, instead, you get a “can’t parse xorg.conf”, just rename /etc/X11/xorg.conf to something else so nvidia-settings can create a new file.

Can’t set your screen to the native resolution of your monitor? See the companion post, Ubuntu 9.04 nVidia Driver Screen Resolution Problem.

I was able to get all the resolutions, including 1920×1200, for my monitor as well as have the nVidia driver recognize the monitor as a 2407WFPHC, by doing the following:

(If you can’t see your screen at all after enabling the nVidia driver, first read the companion post, Ubuntu 9.04 Screen Resolution/Monitor Out of Range (nVidia Driver 180).)

1. Open a terminal window
2. Go to the X11 directory (cd /etc/X11)
3. Make a backup of the current xorg.conf (e.g., sudo cp xorg.conf xorg.conf.backup)
4. Run nvidia-xconfig with root permission (sudo nvidia-xconfig). If you get a parsing error, delete xorg.conf so nvidia-xconfig can create a fresh one.
5. Open xorg.conf with your favorite editor (e.g. sudo vim xorg.conf)
6. You’ll see a lot of extra settings now
7. Look for Section “Monitor”. Mine defaulted to the following settings:
       Identifier “Monitor0″
       VendorName “Unknown”
       ModelName “Unknown”
       HorizSync 28.0  – 33.0
       VertRefresh 43.0 – 72.0
       Option “DPMS”
8. Change the HorizSync and VertRefresh values to the correct ones for your particular monitor. For my 2407WFPHC, I put the following:
       HorizSync 30.0 – 83.0
       VertRefresh 56.0 – 76.0
9. Save the xorg.conf file
10. Log out and restart the X server (at the login screen, select Menu, then Restart X server)
11. Log in and run the NVIDIA X Server Settings tool. You should now have a whole bunch of resolutions from which to choose. I selected 1920×1200.

The reason that this works is that the nVidia driver needs to know the frequency ranges for your monitor in order to know what resolutions are safe to use. Setting the HorizSync and VertRefresh in xorg.conf provides this necessary information.

Taking the rechargeable battery out also results in the flashing red LED. So, the battery is clearly not being recharged. This is further corroborated by the short battery life.

Microsoft LaserMouse 7000 upside-down with open battery compartment

I saw online that some people have found some sort of button underneath the battery and that it’s not being depressed. However, the mouse I was having problems with did not have such a button. There is a small hole under the battery, but no switch or button in the hole.

Upon further investigation, I noticed that the positive metal plate in the battery compartment of the mouse has two plastic rails holding it in place.

Battery removed showing the plastic rails at the positive conductor

When putting the battery inside, the rails tend to press back against the top of the battery such that the battery’s tip doesn’t make good contact with the metal. Since the metal plate is tapered inward, it only makes reliable contact with the battery when the battery is pushed all the way down into the compartment.

Notice the short tip on the rechargeable battery and the rails pressing back against it

As a result of this plastic getting in the way and preventing the battery from making contact with the positive conducting plate, of course it can’t recharge. It also explains why it only charges for a few seconds–just until the battery slips out of position and loses contact. However, the fix for this recharging problem is rather simple.

Fold the paper (left); place on top of battery (center); insert into mouse (right)

1. Cut a small piece of paper a little shorter than the length of the battery and about twice as wide
2. Fold the paper in half to achieve a thickness of two sheets of paper
3. Place the battery into the battery compartment
4. Put the paper on top of the battery
5. Close the battery cover

The cover should go on snugly so that it firmly presses the battery into the compartment. That will enable the positive tip of the Laser Mouse’s battery to stay in contact with the positive conductor plate. If it doesn’t press firmly enough, add one more sheet that’s half the width of the first one (for a thickness of three sheets).

After applying this little fix, the problem mouse’s LED properly throbs green and charges up completely.

(Update: Added photos)

real 0m0.005s
user 0m0.004s
sys 0m0.000s


However, by default, the time command outputs this information to the standard error device and, as a result, it’s not always obvious how to get this information into a file.

If you’re using the GNU time command, it’s pretty easy with the -o or --output option. For example, the following command writes the time information from executing ls into the file time.log:

time -o time.log ls

On some systems, such as a Linux server I was using recently, the only available time command may be the one built into the shell. This time command does not have an output option. As a result, if you want to redirect the output of both the time command and the program it’s executing, you might think you want to do the following:

time ls > output.log 2>&1

Then, you discover that it doesn’t work as expected. All you get in the log file is the output of the ls command while the time command still prints to the console, even though you redirected standard error to standard out.

Why does this happen? It’s because those redirects apply only to the ls command, not to the time command. Fortunately, there’s an easy solution. Group the time command and the program you want it to time using parentheses. Try changing the previous command to the following:

( time ls ) > output.log 2>&1

When you view the output.log file now, you’ll find that the output of both the ls and time commands went into the log file, as desired.

Enjoy!

Of course, more fixes to interesting tech problems (including a long-standing Microsoft Word data corruption bug that I think I’ve finally worked around). Also, a new theme for this blog is certainly in order. I believe I’ve finally found one that I like that also fits the blog’s name. So, I’ll be busy with that for a little bit to get things dialed in and working just right.

Meanwhile, feel free to leave comments, questions and suggestions. Here’s hoping that your digital life in 2009 is prosperous and trouble-free.

My laptop has an Intel 945GM but this problem seems to affect other cards such as the GMA915 and some ATI as well. It has also manifested itself as flicker, rather than the periodic blanking that I’m experiencing.

According to bug 278471, this problem is associated with the monitor detection function in KDE4. So, to stop the flickering, flashing and blanking, simply turn off the detection service as follows.

1. Click on the K menu
2. Go to the Applications tab
3. Click on the System menu followed by System Settings
4. In the System Settings window, click on the Advanced tab
5. Click on the Service Manager
6. In the Startup Services list, select the service named, “Detecting RANDR (monitor) changes” so that it’s highlighted
7. Click the Stop button to stop the service, then click the checkbox to clear it (so it doesn’t start up anymore)
8. Click the Apply button

Voila! No more flashing. What a relief. After this bug is fixed, you can turn the service back on so that Kubuntu can detect monitors again.

Since then, that article became and has remained the most frequently read post on my blog. What amazes me is how so many people are trying to transfer their Palm smartphone contact info to or from a Blackberry and unable to get help from the manufacturers and wireless carriers after hours on the phone. The worst “solution” I’ve heard was from an anonymous commenter who said, “[I] just spent 2 hrs with T-mobile/BBerry support. They gave up and told me to transfer contact[s] manually.” Ouch!

Have a look through the original comments about syncing these smartphones. Some are quite entertaining.

The comments have also surfaced other related problems that needed solving. I’ll reprint some of them here since the comment history is getting rather long. But feel free to check out the original list for other goodies.

Transferring data from Blackberry to Palm
Some visitors wanted to actually go the other way, converting their Blackberry info to a new Palm Treo (or perhaps a Palm Centro). That’s pretty easy to do as well:

1. Sync your Blackberry with Outlook.
2. Export the data to a CSV file (e.g. Contacts.csv).
3. Using the Palm Desktop software, import the CSV file from step #2 into the Palm Contacts database.
4. If all the contacts look good after step #3 (make any correction in Palm Desktop), then HotSync the Treo.

Transferring data from Blackberry to Palm without Outlook

1. Sync the Blackberry.
2. Open the Blackberry Desktop Manager.
3. Go to Intellisync.
4. Click on Configure PIM.
5. Select the Address book item.
6. Click on Choose and select ASCII Import/Export as the type of address book.
7. Select Export under Operation.
8. In the file name field, enter Contacts.csv
9. Click the OK button, then click on Synchronize Now.
10. When the sync is complete, import the file into Contacts in Palm Desktop
11. Sync the Palm Treo/Centro, etc.

Syncing from Palm to Blackberry without Outlook

The least expensive shareware/commercial tool to convert from Palm DBA format to CSV is datebookCSV. I haven’t tried it but it looks like it’ll do the job. If you use this tool, post a comment with your experience.

Well, that’s it for now. If you have more tips for Palm or Blackberry users, be sure to post it here.