Strange Happenings In Firefox

I use Firefox. I also use the password manager along with the password exporter plugin.
But the other night I was in a panic. I recently signed up at a few new sites and didn't export my newest password list.
And when I went to a site that I've been a member of for a long while my user name and password didn't appear!

And when I went to view my password list inside Firefox, it was empty!
Uh Oh! Now what?

So I take a look around Google and see there was a bug due to a problem with a Linux file. But that bug was a bit old and all was supposedly fixed.
I also came across some articles that mentioned what files stored the user names and passwords. The data would be encrypted but I figured that I could try a few things with them.

First, I could check the file sizes and verify if indeed they held my data or where actual zero byte toast.
Secondly, I figured I could save a copy elsewhere, reinstall Firefox then put these files back in place. This solution didn't thrill me because I felt that the encryption was based on an algorithm generated when Firefox was installed.
But I was willing to give it a try since I did have the key file.

So I copied the files to a new location, saved off my bookmarks and was ready to uninstall Firefox. But something told me to try a reboot first.
So I rebooted the computer and sure enough, my user names and passwords returned. I immediately exported the list just in case it happened again.

And it did! The following evening I had it happen again. Funny thing about all this. Both times it happened was at the same forum. Both times I went to log in at the same forum and both times I temporarily lost my user name and password list. Hasn't happened since but I now make sure to export my password list every time I sign up at a new site.

And if you are wondering about the reputation of the forum and possible games by the owner. Uh-Uh! Not there. It is one of the strictest forums I have ever been a member of.
Don't even think of asking how to recover your lost Windows password or anything else like that. Not allowed.

And in case you were wondering about those 2 files?
Open you home folder and view hidden files.
Now look for the .mozilla/firefox folder.
Open the abcxyz.default folder were abcxyz will be some mix of letters and numbers created when you installed Firefox.

Now look for the key3.db file. This is the encryption file.
Now grab the signons3.txt file. This contains your user names and passwords.

Enjoy!

TaZMAn

Lock The Software or Kernel Versions

There are times you want to lock in your software or kernel version so that it won't upgrade to the next available version.
This article will show you how to do it and provide examples why you might want to do this.

You just got your Ubuntu system all tweaked out and running sweet. The Nvidia driver problems are all fixed and you are happy. BLINK! The updater has informed you about new updates.
So you click on the updater and start the download and install process. One of the updates is a new kernel. Cool! Might have some new features in it.
You finish the updates and restart your computer to enable the new kernel.

Disaster!!
The video is screwed again. The new kernel hosed your old settings. After a few minutes of making changes you toss up your hands and scream at the top of your lungs.
Lucky for you, you can reboot and select the old kernel for your boot up.
Then you can use one of the tips from my previous blog entry to remove that new kernel.
However, every time you start your computer, the updater informs you that you have a new update. That update is the kernel you just got rid of. How can we tell the updater to ignore it?
Here's how;

Open up the Synaptic Package Manager and do a search for linux-headers.
Find the version you are now using and highlight it.
Now go to the Package button and click on the Lock Version button.
Go back to the search field and do a search for linux-image.
Find the version you are now using and lock that version also.

Now the update manager won't bug you about an update for the new kernel.
You can also use this for software you have installed.
Use this technique to prevent update problems when your system takes a dive with a new kernel or software version.

Enjoy!

TaZMAn

Hardy Heron Problems

I was hyped up! Ready to make the leap.
And I was going to do it without taking any chances.
I wanted Hardy and I upgraded.
But not in the usual upgrade style. Oh no. That can cause problems.
Nope! I saved off all my email and bookmarks along with my other files.
Then I formatted the hard drive saying goodbye to Gutsy and loaded Hardy.

And Hardy lasted only a few weeks. I'm back to Gutsy.
I couldn't take all the broken software, coasters burned with K3b, lock ups, high cpu usage and web sites that looked terrible in Firefox 3.

The list of problems was long. And the fixes were sporadic, uncertain or very labor intensive.
Wine didn't work along with several other software packages.
Playing videos or doing certain other chores on my system caused the cpu to load up to 100% and at times caused the system to lock up completely.

Watching videos in Firefox like at Youtube would cause Firefox to close unexpectedly.
I have always used K3b for all my burning needs. But it was impossible to use K3b because all it did was burn coasters. The cause of the coaster production line was due to a file K3b needed for speed sensing. The log files showed that K3b didn't have permission to access that file.
What??!!!!

Numerous times my computer would stop responding.
Finally I had enough and last week I reinstalled Gutsy.
Was tempted to go with Etch but decided I had enough 'fun' in the last 3 weeks.
I needed something familiar and stable.

Ubuntu really pissed me off and dropped the ball big time with this release.
Had this been a new user looking to get rid of the MicroShaft shackles they would
have screamed all the way back to Bi$$y Boy thinking he really was the god of programmers.

Canonical needs to rethink their release schedule. Oh it sounds good, a new release every 6 months, but it is too aggressive.
Heck! I don't think many would have minded if this version was a few weeks late as long as it was less buggier. I can hear the board room banter the week before the release date.
"We have to ship on time otherwise we will look like we aren't for real."

Well shipping out an OS that acts like a beta version not only puts a blemish on your corporate image, it puts you on the same level as Microshaft and the crap they call an operating system.

Hardy is a Long Term Support (LTS) version.
To me that means it should be very stable at release time. It shouldn't be a Long Term Fix It As We Go (LTFIAWG) version.
And if this is what you expect to use to lure new users from Windowz, you blew it!

I'll sit back awhile and see what happens in the next few months.
But if it looks like problems still exist because everyone is gearing up for the next big 6 month release I will be looking for another flavor like Etch or other Debian derivative.

I still like Ubuntu and will continue promoting it albeit Gutsy and not Hardy.
Remember that people are looking towards Linux because of the crap being fed to them by MicroShaft.

TaZMAn

Hardy Heron Nvidia Driver Problem and Fix

Seems there are some problems with Ubuntu Hardy Heron and certain Nvidia video cards.
Especially the AGP 8X interface cards.

3 Ubuntu users I know have installed Hardy on their systems.
All of them have the GeForce 5200 FX video cards.
2 were unsuccessful with the install of the Nvidia driver and were stuck with 2 resolution options.
They were 800 x 600 and 640 x 480.

The final user installed the Nvidia driver and had full screen resolution and full access to Compiz.

So what were the differences that caused 2 failures and 1 success?
It was the way they installed the driver. The first 2 users installed the Nvidia driver like any user would. They downloaded it and installed it using the restricted driver manager.

The third user installed the driver using a program called Envy.

So why did the Nvidia driver fail to detect the proper resolution for the 5200 when installed via the restricted driver manager?

It's kind of hard to pinpoint but I have some thoughts after doing lot's of research.

The only real difference between all 3 systems is the monitor. I believe that if the monitor is of an older variety it doesn't have the ability to report back it's frequency or resolution settings to the x server and this causes the x server to default to the basic low resolution settings.

But why did Envy work?
Envy is a script written to download the driver (Either ATI or Nvidia) configure the driver based on a standard set of resolution settings then tells x server to use these resolution settings once the driver is installed.

So should you use Envy?
The jury's out on this one. I've read plenty of pro's and con's on using it.
I do know that if you do use Envy you will have to remove the driver you installed with Envy before upgrading Debian or Ubuntu to a newer release.

This however is not required anymore if you use the EnvyNG available for Hardy.

You will have to keep Envy installed if you want upgraded drivers. And even using Envy is not a 100% sure thing.

You can grab Envy through the repositories if you have Universe and Multiverse reositories enabled.
Or go here to their web site;

Envy

So are there any other options?
Yep!

Another way to install the Nvidia driver which seems to work most of the time is to go to Nvidia's web page, download the driver and install it yourself.
Installing the driver requires that you kill the x window (Your Desktop), navigate to the driver through a command line style of interface, run the Nvidia installer then restart the x window.

If you want the gory details on how to install the driver yourself you can get the directions from this Ubuntu forum post;

Install Nvidia Driver

You can try either method. I would suggest taking the long road and install it on you own but that is my choice. If Envy works for you then Great!
But if it doesn't, follow the directions on how to remove the installed drivers then reinstall them on your own.

What really bothers me about this whole driver fiasco is that Hardy is a LTS release.
It's supposed to make things easier for the novice and lure potential users away from Windowz and to the wonderful world of Linux.
But they dropped the ball big time. If anything, this problem will frustrate new users and drive them away.
Hardy should never have been released with this problem present. Damn the release schedule.
Make a solid release with no bugs or very few minor bugs and people won't care if it's a few weeks late.
These 6 month release schedules are a great marketing tool but in reality it's allowing more bugs to be running rampant and causing users many hours, days or weeks of grief!

I hope this post will help Hardy users with Nvidia driver issues get them fixed.

TaZMAn