Month: August 2007

Windows Picasa in Linux

With the recent upgrade of my main computer from Slackware 11 to Slackware 12, I have also tried to update as much individual software as I can. I was pleased to see that Google had released a newer version of Google Earth in May of this year. But was equally disappointed to find out that the 2 year old version of Picasa I had been using was the same. I was really wanting to try out the new Picasa Web Albums.

Picasa up and runningWhile I enjoy using Picasa in Linux, it is not a native Linux application. It is kluged into Linux via Wine. This got me to thinking that I might be able to install Wine and get a recent Windows version of Picasa up and running. The only thing that concerned me was that I remember there was talk that the Wine install that Google built for its software was very modified and a standard install of Wine would probably not work.

I did some surfing around and found a nice tutorial on getting the current version of Picasa (2.7 build 28.3205,0) to play nicely with the current version of Wine (0.9.43).

This info is pulled off of a mailing list. The person who posted it said it was not original to him, but he did not know where he got it. If you know the original source of this, let me know. I will gladly give credit.

Let me step you through each part of the process. These steps were originally written for Ubuntu. I will leave them intact and comment under the steps if there are any changes.

The steps with commentary

1. I installed Picasa as usual (v2.2 for linux)

I installed the original version of Picasa for Linux. This is a truly enjoyable experience since it installs (somewhat) like a Windows program. While I am a dyed in the wool Linux user, there needs to be a standard way to install software. Google has done a good job with the installers for Google Earth and Picasa.

2. I started it up and scanned some folder containing photos

Just let it do it’s thing. For me this took no time at all since I had previously had Picasa running on my system, it found all the configurations and photos.

3. Shut down picasa AND the media detector

The media detector is the little Picasa logo that sits in the tray by the clock (on KDE). Right click it to choose the option of shutting it down.

4. Installed wine (apt-get install wine)

If you are using Slackware, then don’t use apt-get. It does not work here. I grabbed the latest version of Wine for Slackware 12 (even though the site is in Italian, the package was English). Install the package just like you normally would any other Slackware software package. If you don’t know how, there are tutorials for that too.

As a side note, and something that was confusing to me, there was no Wine configuration that I needed to do. Just keep plugging through the steps and you will get there.

5. Downloaded picasa 2.5 for windows (wget http://dl.google.com/picasa/picasaweb-current-setup.exe)

Again, this is a step in Ubuntu (and other Debian based systems). Just go download the Windows .exe file from Picasa.

6. Installed it using wine (wine picasaweb-current-setup.exe)

This is done from the command line. cd to the directory where you downloaded the picasaweb-current-setup.exe file and issue this command: wine picasaweb-current-setup.exe

7. When asked if I want to run Picasa, I did so, then I shut down picasa AND the media detector (if running)

This will happen after Wine gets through with the install. The media detector ran for just a second and found only a few pictures. I became concerned at this point thinking that I was going to have to start all over getting the new Picasa set up with my pictures. But that problem is taken care of in the following steps.

7. Moved the old picasa installation (as root):
cd /opt/picasa/wine/drive_c/Program Files
mv Picasa2 Picasa22

Why this is also step 7, I don’t know. You enter the lines under step 7 into your console as root. Each line is done separately. The first line gets you into the directory where Picasa is stored and the second line moves the whole install into a different directory (so you don’t lose it). I believe this is the original Picasa install, not the one you just installed.

8. While in the same dir i copied the new installed Picasa 2.5:
cp -R home/USERNAME/.wine/drive_c/Program Files/Picasa2/ .

Just run the line of code at your command prompt. You will need to substitute your username where it says USERNAME. That period on the end is important. Don’t leave that off or it won’t work.

8. Then it just worked… Good luck!
I had big troubles getting the start up logo disappearing, this is why some steps are kind of awkward.

That was exactly my experience. It worked! Except…Picasa showing a closeup

The fallout (however minor)

I was not able to start it from the newly created desktop shortcut. When I did that, it was like I was starting the new version, but with no photos (like after the first step 7 above). But going to the command line (or ALT+F2) and typing in “picasa” (without quotes) started the program just fine.

My only issue now is with getting connected to the Web Albums (the reason I wanted to upgrade to begin with). I am getting the “Failed to connect to server. Please try again later.” error. This can be caused by a few of different issues. I think mine is tied to the fact that I am outside the US and their only Web Albums server is a US one.

Let me write that up as a separate issue in a later post.

The ongoing headphone debate

Today I read an article written by Dave McGillivray, the race director for the Boston Marathon. He was talking about the use of iPods specifically, but what he meant was MP3 players in general. However, he does point out that the iPod was the biggest brand he consistently saw.

The rub is whether headphones are good and healthy for runners. As a race director of a USATF sanctioned event, he has to lay down the law and say that no headphones are allowed. This is for insurance purposes, but also has social reasons. He does a good job of pointing out the reasons why one should not wear headphones while running. I agree with many of his reasons.

However, I run almost all of my training runs with headphones. If I am fortunate enough to get someone to run with me, then I will not take my player with me at all. Or, sometimes during speed workouts I will ditch the player. Those are times that I am focusing on the event and not the podcasts. But at all other times I wear my headphones during training.

I used to wear them during races too. After my 3rd race or so, I gave up on them. I wanted to experience the atmosphere as a whole and do my best while running. I really enjoy chatting with other runners. While I am not a competitive runner, I do try to push myself at races.

There has been quite a bit of discussion about this topic at another site that I visit regularly.

MightySearch

After I did all the work to customize a search results theme page, I found a link at the original site telling of an easier way to do the same thing.

Get the mightysearch plugin and follow a couple of tutorials for getting it up and running. You can see what this plugin does for your site by doing a search in the sidebar to the left. It allows you to do Google searches but display results with your own website’s theme.

Ironically, the page that got me started on all of this does not use either method to display his search results as of this writing.

New search tool and theme update

I just spent some time getting a new search box running on the site here. Now I am using Google to handle the searches. With this you are also able to search the web, not just my site. I don’t have it working completely the way I want, but I am getting closer.

As a result of this, I have had a wonderful side benefit. The theme that I have used and modified for the site was a nice theme, but poorly coded. What made it poorly coded was that the whole theme was in 1 (one) file! If you know anything about theming or style sheets, you know that is a horrible mess to manage. I did not notice that until I had been using the theme for a while. Then I did not want to change.

As I have been thinking about updating the theme in the future, I really needed to break this theme down into several documents and make it a proper theme. That has been done. Hopefully there is nothing that you will be able to notice in this change (yet). Everything should look and act exactly the same with the exception of the search box now serving results from Google.

I got my information about creating a custom search results page from another blogger who has a tutorial on generating a custom Google AdSense search page.

Speed day

Today was a “speed work” day in my training. I had planned to trot down to the track that is about 3/4 mile from my house and then run 2 X 800 meter repeats. I needed to run a mile for my speed session. Last week I did 4 X 400 meters. My training plan does not specify how I need to do the speed work, it just specifies the distance.

I got to the track to find the gate was locked. That is the first time that has ever happened. I am not sure why it was closed unless it will be closed for the 2 week summer vacation that the university has. I hope not.

As a result I did a bit longer of a loop and made it back home for my warm up run. I then stretched for a bit and got ready to just run around my house for 1 mile. No, not in my house, but in the streets around the house. I have a 1 mile course laid out for such occasions.

I did not give myself much of a break before I started off on my speed run. I was supposed to cover the mile between 8:36 and 8:55. I ended up with an 8:57 mile. So I was on the slow side, but not horrible. However, I was quite wiped out after the run and just did a 10 minute cool down walk instead of a cool down run.

Tomorrow is a rest day from running. I will put the dumbbells to work. I will get both my sisters to clean the house and wash the car.