Picasa's bugs cause my images to be deleted.

I use Picasa client and Picasa Web Album for a time and it works enough for me. In addition to managing my photos in Picasa client, I also use Picasa Web Album as images hosting for my thai blog. It's really easy and safe in an album.

Yesterday, an unlucky day, I wanted to sync the blog album to my Picasa client and tried setting them to keep syncing in the future therefore I can upload an image via either the client or the web album. It would be great, isn't it?
I clicked the "download album to picasa" button in the web client. The album was downloaded to the client beautifully and it was shown as a downloaded web album. Then I clicked the "sync to web" button in the client. It asked something and uploaded all images in the album. Why did they need to be uploaded again?
The problem is here. In the web client, there were 2 album now in the same name, the original and the recently uploaded. At first I thought it was not a bug, you might need to have a fresh uploaded album at the first time to keep syncing in the future and these twin albums was different album and unique.
and this idea leads to the mistaken operation.
I right-clicked at the downloaded web album in the client and chose to delete the album with "delete the online copies" checked. Then both original and recently uploaded album were gradually deleted! and they were deleted successfully.
So I don't have any copies of this album left. It's a bug of Picasa and I reported to its forum yesterday.
but good luck of me that the album has only 25 images and google still cache some of them. :P

Emesene crashes during logging in

I use emesene 1.0 on Debian. It usually works great and I prefer it to pidgin.

But there are a few bugs. Emesene crashed during logging in. It'll crash everytime after it occurs the first time. I don't know why. It hardly occurs and it crashed unexpectedly. I used to see this bug a few times in the past. My friend found it too and has already found the solution. Deleting all the files in ~/.config/emesene1.0/[your_account] is the solution but you have to sacrifice your config files and preferences.

I got it crashed again. But this time I found the better solution. I digged in the file and found that deleting the PersonalMessage.conf in ~/.config/emesene1.0/[your_account] is enough.

The file contains you personal message. After I deleted it, emesene can logging in and online again. The preferences still be but only personal message not.

I took experiment something. I set presonal message to the previous personal message that's in the PersonalMessage.conf before It's deleted. It contains Thai and English word in mix. It crashed immediatly. I run it and set it again. It crashed. This time I set the personal message to only English message like "test". It didn't crash. Now I can set the previous message and crashing haven't occured anymore.

Maybe this is the clue of this bug. I'll report it to the bug tracker later.

Firefox 3 beta 5 lags on ubuntu 8.04

I upgraded from Gutsy to Hardy last week. It comes with the new Firefox 3 beta 5. After I had used for a few days, I found that firefox lags very much. When I switch the tab or scroll the page or just leave it , it start to lag the system and then system sometime freeze after that. In the system monitor, firefox process was interruptible. I noticed the harddisk light always show or blink fast but I'm not sure it's the same case.

At first I though that it resulted from upgrade process that it's not a fresh install. Maybe some configs file are not upgraded correctly. After few days passed, I felt very annoy. I started to find out what it is.

I found this bug. It's the same. In the bug page they give a method to solve this bug temporarily
There is an easy workaround.

This workaround is successful:
1. Open Firefox 3
2. Disable phishing/attack detection in the security section of the Preferences
3. Close Firefox
4. Make hidden files visible (Locations - Personal folder - View - show hidden files)
5. Delete /home/user/.mozilla/firefox/blahblahblah.default/urlclassifier*.sqlite
6. Open Firefox.
7. There is no next step. You're done. :-)

Greetz, Pjotr.

I follow this instruction. It works!!

I like the bug report system too much. haha

I hope that the patch will be published very soon. I wait for it.